I diagnosed the problem using the following steps:
1. I successively commented out ejb calls from the client to determine the
misbehaving ejb.
2. Once I knew which ejb was misbehaving, I did a search for "Connection"
in my ejb code and any helper classes that the ejb was using.
This way I found the orphan connection.
3. I corrected the code and tested again: the problem had disappeared.
To avoid this problem:
When coding, keep track of your connections and make sure any connections
are being closed when they are no longer needed.
My orphan connection was left over from legacy code. Initially, each method
that needed a connection was retrieving and returning back to the pool
their own connection. Later, I changed this to use an instance variable for
the connection. This connection was closed right before the class went out
of scope.
Consequently, I removed all code that created and remove connections
locally to methods. As it turned out, I removed all code that removed local
connections, but I forgot one statement that created a connection.
Thomas Kirsch
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
