-
Feature Request
-
Resolution: Obsolete
-
Major
-
JBossAS-4.0.1 Final
-
None
The CachedConnectionManager does not maintain the ejb context correctly
for transaction synchronizations.
If a connection is closed during afterCompletion(), it will use the caller's context
to remove the connection from the list of unclosed connections.
In fact, it is unsafe to be dealing with the ejb context during the transaction interceptor
since this is outside the lock interceptor for entity beans meaning it won't be
thread safe.
- relates to
-
JBAS-1662 Memory leak with SpecCompliant=true in transaction-service.xml
-
- Closed
-