CachedConnectionManager does not retain EJB context during transaction
synchronizations
---------------------------------------------------------------------------------------
Key: JBJCA-12
URL: http://jira.jboss.com/jira/browse/JBJCA-12
Project: JBoss JCA
Type: Bug
Versions: JBossAS-4.0.1, JBossAS-3.2.6
Reporter: Adrian Brock
Assigned to: Adrian Brock
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 the ejb context during the transaction
interceptor
since this is outside the lock interceptor for entity beans meaning it won't be
thread safe.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
