Do you use the same connection pool? also it is possible that the pool did not return the same connection for different request in the same transaction.
It looks like a configuration issue, but you might share a bit more information if you need more help.
Thanks Wolf-Dieter Fink for response.
You might be correct I do think that it is getting new connection when querying within transaction.
My jboscmp-jdbc.xml has following
My Oracle-ds.xml file has following
And the dao references OracleDS using JNDI. We are using jboss 4.2.2.
Is there any test which I can do to find out if the connection object returned is different than what is used by session bean?
Not sure whether this was possible in AS4.2.
Maybe you do a short test and set the root-logger to TRACE and see if you have details from the connection-pool
I modified jbossjta-properties.xml and jboss-log4j configuration to enable jta logging and it dump too much logs. Application is taking long time to deploy and access is very slow. I review the logs to see if I can understand anything...is there any way we can check only see transaction related or connection pool related logs?