Hi Lukas, I wouldn't use the JDO part of OJB - as far as I recall it isn't really intended for "serious" use right now.
As for pooling connections in general, many JDBC drivers (JDBC 2+) now have connection pooling built in - this is certainly true of oracle and postgres (I use these now). To use these you simply need to specify the appropriate JDBC driver class in repository.xml (eg OracleConnectionCacheImpl) and then forget about pooling. This has the added advantage that the driver connection pools clean up their connection states properly ready for the next user, they may also have eg statement caching built in and in general should be optimised for connections to your particular DB. Don't forget to turn off the OJB connection pooling if you take this route though otherwise you end up with a pool of pooled connections...... If the pooling screws up you can then always blame oracle or whoever wrote the driver :-) Cheers, Chris Lukas Severin wrote: > Thanks. Would it make a difference in setup of the pooling in the JDO case > compared to the PBAPI ? Is it not strange to have the pooling in OJB, when > this should be the task of the container (at least in the j2ee world) ? Does > it matter which connection manager to choose ? I feel inclined to choose the > DBCP based, but what do I know ;-) > > Burt, you are using the PBAPI, and I have decided to go for the java > standard JDO. What difference regarding pooling and synchronization can I > expect ? > > Anyone else care to share their opinions on this ? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
