You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org> on 2009/02/02 16:23:59 UTC
[jira] Created: (UIMA-1286) UIMA AS Service Doesnt Start a Timer On
Connection To a Temp Reply Queue
UIMA AS Service Doesnt Start a Timer On Connection To a Temp Reply Queue
------------------------------------------------------------------------
Key: UIMA-1286
URL: https://issues.apache.org/jira/browse/UIMA-1286
Project: UIMA
Issue Type: Bug
Components: Async Scaleout
Reporter: Jerry Cwiklik
The Uima AS service doesnt time out idle connections to a broker. This may lead to an exception:
ERROR TransportConnector - Could not accept connection : java.net.SocketException: Too many open files
java.net.SocketException: Too many open files
This problem may occur when a client application repeatedly restarts Uima Client API many times. After each restart the client sends a CAS and receives a response, then it is stopped. The service accumulates connections to the client's temp reply queue. When the client terminates the broker kills the temp queue but the service still keeps the connection open causing a leak.
Start a timer after each reply.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1286) UIMA AS Service Doesnt Start a Timer On
Connection To a Temp Reply Queue
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik closed UIMA-1286.
-------------------------------
Resolution: Fixed
> UIMA AS Service Doesnt Start a Timer On Connection To a Temp Reply Queue
> ------------------------------------------------------------------------
>
> Key: UIMA-1286
> URL: https://issues.apache.org/jira/browse/UIMA-1286
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Attachments: uimaj-as-activemq-UIMA-1286-patch.txt
>
>
> The Uima AS service doesnt time out idle connections to a broker. This may lead to an exception:
> ERROR TransportConnector - Could not accept connection : java.net.SocketException: Too many open files
> java.net.SocketException: Too many open files
> This problem may occur when a client application repeatedly restarts Uima Client API many times. After each restart the client sends a CAS and receives a response, then it is stopped. The service accumulates connections to the client's temp reply queue. When the client terminates the broker kills the temp queue but the service still keeps the connection open causing a leak.
> Start a timer after each reply.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1286) UIMA AS Service Doesnt Start a Timer On
Connection To a Temp Reply Queue
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-1286:
--------------------------------
Fix Version/s: 2.3AS
> UIMA AS Service Doesnt Start a Timer On Connection To a Temp Reply Queue
> ------------------------------------------------------------------------
>
> Key: UIMA-1286
> URL: https://issues.apache.org/jira/browse/UIMA-1286
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Fix For: 2.3AS
>
> Attachments: uimaj-as-activemq-UIMA-1286-patch.txt
>
>
> The Uima AS service doesnt time out idle connections to a broker. This may lead to an exception:
> ERROR TransportConnector - Could not accept connection : java.net.SocketException: Too many open files
> java.net.SocketException: Too many open files
> This problem may occur when a client application repeatedly restarts Uima Client API many times. After each restart the client sends a CAS and receives a response, then it is stopped. The service accumulates connections to the client's temp reply queue. When the client terminates the broker kills the temp queue but the service still keeps the connection open causing a leak.
> Start a timer after each reply.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1286) UIMA AS Service Doesnt Start a Timer On
Connection To a Temp Reply Queue
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-1286:
--------------------------------
Attachment: uimaj-as-activemq-UIMA-1286-patch.txt
Starts a timer after each reply to enable idle connection cleanup. A default connection timeout is 30 minutes. To override this add -DSessionTimeoutOverride=XXX, where XXX is time out value in millis
Re-factored sendCasToRemoteEndpoint() methods to remove duplicate code.
> UIMA AS Service Doesnt Start a Timer On Connection To a Temp Reply Queue
> ------------------------------------------------------------------------
>
> Key: UIMA-1286
> URL: https://issues.apache.org/jira/browse/UIMA-1286
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Attachments: uimaj-as-activemq-UIMA-1286-patch.txt
>
>
> The Uima AS service doesnt time out idle connections to a broker. This may lead to an exception:
> ERROR TransportConnector - Could not accept connection : java.net.SocketException: Too many open files
> java.net.SocketException: Too many open files
> This problem may occur when a client application repeatedly restarts Uima Client API many times. After each restart the client sends a CAS and receives a response, then it is stopped. The service accumulates connections to the client's temp reply queue. When the client terminates the broker kills the temp queue but the service still keeps the connection open causing a leak.
> Start a timer after each reply.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.