I am currently using OJB as our persistence mechanism. I have configured OJB successfully to take part inside of the JTA-TX that are dicated by my TX affinity declarations for my EJB methods. Everything works the way it is suppose to, except we get the "Closing a connection for you" warning given a certain scenario.
The idea is that due to the way that OJB handles it's Broker and Connection pooling, a connection that is created in a top-level EJB call can be closed in a call from a secondary, nested EJB call. There is confusion as whether the way OJB is handeling it is accurate, or if it is an issue with JBoss. Here is a link to a more detail-description of the issue given by one of the developers of OJB. http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=13591 Can someone tell me if this to be expected? BTW, I am using 3.2.5 and seeing the issue. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3847664#3847664 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3847664 ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
