Thanks, yes I figured it out in the end, and actually I've removed transactions altogether
for the beans involved because everything is read-only and there's no worries about
inconsistent state.
I think there's probably a bug in the Connection Manager, so that when
There's an SQLException thrown when calling getConnection() on the Datasource retrieved
from JNDI. This gets wrapped in an application exception (ISISConnectionException) with
the message ISISDatabaseConnection: Unable to create connection to ISIS Database, but
the nested SQLException is being
OK here's the SQLException when trying to get a connection from the datasource after a
NoSuchObjectException has been caught:
org.jboss.util.NestedSQLException: Could not enlist in transaction on entering meta-aware
object!javax.transaction.SystemException: Could not enlist XAResource!
Alright, so the issue is that a stateful session is being accessed after it has
been thrown out due to its inactivity exceeding its max age value. Either you
need to increase the period over which passivated sessions are kept or isolate
the access of the stateful session from the encompassing
Our production application has on several times run out of connections from a pool and
we've had to restart the server to reset the pool.
We have a pool of 100 Oracle connections used for BMP entity beans and calls to the
database from Session beans via Data Access Objects:
What is the real problem occuring here at BrowseUtilities.java:214, an
SQLException or what?
Caused by: javax.ejb.EJBException: null; CausedByException is:
ISISDatabaseConnection: Unable to create connection to ISIS Database.
at
