JDBC

There is a setDataSource method on the JdbcLogFactory and JdbcMessageStoreFactory. If the data source is set explicitly (e.g. to the Oracle data source) then Proxool is not used. This was added because of the problems between Proxool and Oracle. Does that satisfy your needs?

Basically, yes. But I also prefer to have an configurable option to do so.

Would that be very difficult?

I see a several issues with the configurable option. One is that the data sources often need special vendor-specific configurations. For example, the Oracle data source supports configurable prepared statement caching. This would be messy to support with the QF session settings file format. Another issue is that the factories are already created programatically so it seems natural to set the data source at that time. The last issue is that the data source might be created directly or it might be loaded from JNDI (in an application server context) or using some other technique (e.g., Spring injection). Again, the current settings file is not well suited for supporting these options.

We could add an option just to disable Proxool independent of whether a data source has been specified. However, I don't think this is the behavior most people will want since performance will suffer greatly without the connection pooling capabilities provided by most JDBC data sources.

OK, Steve. We finally found the issue: If you use CHAR with Oracle, you should always fill up with spaces
up to the full length.

Other way round: If you define all character columns in the tables (specifically beginstring) as VARCHAR2, then it works fine.
(If you avoid to have empty session qualifiers.)

So I will close this issues.