Furthermore, I have noticed that my GlassFish monitoring setup reports to
me that the current number of used JDBC connections is negative. Potential
connection leaks are reported which I cannot confirm after code inspection
(some of the reports shows leaks in the EJB container). If my data source
is not specified as XA these leaks are not reported.
Maybe this is the problem. GlassFish thinks that is should reclaim a
connection which is actually not a leak and now in use by another
transaction?
--
[Message sent by forum member 'mphaua']
View Post: http://forums.java.net/node/791265