[
https://issues.apache.org/jira/browse/OPENEJB-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevan Miller closed OPENEJB-1239.
---------------------------------
> Bad client connection is never getting discarded from pool
> ----------------------------------------------------------
>
> Key: OPENEJB-1239
> URL: https://issues.apache.org/jira/browse/OPENEJB-1239
> Project: OpenEJB
> Issue Type: Bug
> Affects Versions: 3.1.x
> Reporter: Kevan Miller
> Assignee: Kevan Miller
> Fix For: 3.1.3
>
>
> If I lookup a Stateless Session bean and invoke a method from a long running
> client then kill the server, a subsequent invocation by the client fails
> (Client.java gets an error flushing the OutputStream. However, if I then
> restart the server, the client keeps grabbing the stale connection (which is
> not removed from the pool). The connection remains in the pool for some
> amount of time. But does eventually get cleaned up (after a socket timout
> period, I suppose).
> When the server is down, the Client receives an IOException for the flush at
> line 162. We handle the error, but as long as retry is false, the connection
> will not be removed from the pool. write() operations on the OutputStream are
> not failing. Good chance that this behavior is environmental. So, on
> different OS's (this test is on Windows), we may see a different error that
> is cleaning up the connection.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
