It looks to me like you can't use Oracle's statement caching and Minerva
pools together without modifying JBoss and/or Minerva code. Minerva
does statement caching itself, but there is no way to control it
centrally, either from jboss.jcml or from a hand-written service MBean.
The statement cache size seems hard-coded to 10 for startup and can
only be changed on a connection-by-connection basis.
When I set up my jboss.jcml OracleDB for transactions and use minerva's
XADataSourceImpl, minerva creates plain OracleConnection objects and
does all of the XA magic itself. When I set up my OracleDB to use
Oracle's OracleXADataSource, minerva creates OracleConnection objects
factoried from an OracleXAConnection. In both cases, minerva statement
caching interferes with Oracle statement caching.
My perfect world would be to use the OracleXADataSource, Oracle's
statement caching, and minerva's pooling. This just sounds a lot more
reliable WRT 2PC and database resource management (e.g., cursors), to
name a couple of reasons. However, it looks like code has to be written
to get that done. Does anyone have any other experience trying to do this?
Thanks,
Tim
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
