What I'm doing is that I look up the ManagedConnectionFactory once, and then use it from different threads to obtain a connection. What then happens is that different threads receive handles to the same ManagedConnection object. As I don't know much of the JCA spec, I can't tell whether that is legal or not, and where the source of this behaviour might even be. However, concerning this, I've been told the following by the guys who maintain the JCA adapter I'm using (which was originally written by David Jencks): anonymous wrote : You may ask JBOSS why the ManagedConnect(thread 1) was given to MCF.matchManagedConnection in thread 2 while the user requested a new ManagedConnection (getConnection()) | | You have | | Thread 1 | MCF (1) | MC (2) | | Thread 2 | MCF (1) | MC (2) <-- why?Sounds like this could be related to the warning, what do you think?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3917332#3917332 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3917332 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
