Nested EJB calls and the infamous ClosingConnection error: I

[squeak]

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/ReadMsg?listName=[e-mail]&msgNo=13591

Can someone tell me if this to be expected?

BTW, I am using 3.2.5 and seeing the issue.

[adrian.brock]

I've added this to the FAQ for all those people who don't realise that questions may have
been answered many times before in this forum.

See the section: "Thread Local Patterns"

http://www.jboss.org/wiki/Wiki.jsp?page=WhatDoesTheMessageDoYourOwnHousekeepingMean

[squeak]

I apologize for missing that. I had searched to no avail.

Thanks for adding that to the FAQ