You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Eddie Epstein (JIRA)" <ui...@incubator.apache.org> on 2009/06/15 23:10:07 UTC
[jira] Created: (UIMA-1382) Change log level for JMS timeout
between services and their reply queues
Change log level for JMS timeout between services and their reply queues
------------------------------------------------------------------------
Key: UIMA-1382
URL: https://issues.apache.org/jira/browse/UIMA-1382
Project: UIMA
Issue Type: Improvement
Components: Async Scaleout
Reporter: Eddie Epstein
Assignee: Eddie Epstein
UIMA AS Services respond to the temp reply queues specified in the requests. The service maintains the JMS connection with the reply queue to minimize overhead on subsequent replies. However, in order to avoid holding on to too many resources, these connections are dropped after a specified period (default = 30 min).
These connection drops are currently logged at INFO level, which can be a problem for a highly scaled system. Moving them to CONFIG.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1382) Change log level for JMS timeout
between services and their reply queues
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-1382:
--------------------------------
Fix Version/s: 2.3AS
> Change log level for JMS timeout between services and their reply queues
> ------------------------------------------------------------------------
>
> Key: UIMA-1382
> URL: https://issues.apache.org/jira/browse/UIMA-1382
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Eddie Epstein
> Assignee: Eddie Epstein
> Fix For: 2.3AS
>
>
> UIMA AS Services respond to the temp reply queues specified in the requests. The service maintains the JMS connection with the reply queue to minimize overhead on subsequent replies. However, in order to avoid holding on to too many resources, these connections are dropped after a specified period (default = 30 min).
> These connection drops are currently logged at INFO level, which can be a problem for a highly scaled system. Moving them to CONFIG.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1382) Change log level for JMS timeout between
services and their reply queues
Posted by "Eddie Epstein (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eddie Epstein closed UIMA-1382.
-------------------------------
Resolution: Fixed
> Change log level for JMS timeout between services and their reply queues
> ------------------------------------------------------------------------
>
> Key: UIMA-1382
> URL: https://issues.apache.org/jira/browse/UIMA-1382
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Eddie Epstein
> Assignee: Eddie Epstein
>
> UIMA AS Services respond to the temp reply queues specified in the requests. The service maintains the JMS connection with the reply queue to minimize overhead on subsequent replies. However, in order to avoid holding on to too many resources, these connections are dropped after a specified period (default = 30 min).
> These connection drops are currently logged at INFO level, which can be a problem for a highly scaled system. Moving them to CONFIG.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.