Uploaded image for project: 'OpenEJB'
  1. OpenEJB
  2. OPENEJB-1239

Bad client connection is never getting discarded from pool

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.1.x
    • Fix Version/s: 3.1.3
    • Component/s: None
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              kevan Kevan Lee Miller
              Reporter:
              kevan Kevan Lee Miller
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: