I think the parameter prepared-statement-cache-size is per transaction. But I'm not sure.
what do you meen hen you say " per transaction".
I use an JDBC DataSource. Transaktions are Handled by DB2 Database.
I do not use CMP or User Transacton in JBoss.
So my Conncetion Pool just Pools Connections for my Application.
Each Connection is used only by my custom Classes (called from SLSB).
I'm using direkt JDBC API calls. As far as I understood, there are no transaktion performed in JBoss.
So am I wrong ?
thanks for help (also some further help :-) )
We are seeing the same behaviour, setting the prepared-statement-cache-size doesn't seem to have any effect. Is there another setting that needs to be set apart from just the datasource descriptor?
Hi Dear JBoss Cracks !
Would be nice to get an answer to my question (thanks "pants" and Rafal).
Isn't there any JBoss Develeper who can answer this little question?
Why can't I see any Difference when declaring a PreparedStatement Cache in the DataSource config ?
well thanks a lot .. I will wait some more months :-)
Found answer, if you call prepareStatement with any arguments other than just the sql then caching doesn't work.
What is not yet clear for me is why in the JMX-Console the "JBoss LocalTransaction JDBC Wrapper"the attribute "PreparedStatementCacheSize"has the value null.
Is it a JBoss bug? I'am working with JBoss 3.2.5
Any help will be really apreciated,