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)" <de...@uima.apache.org> on 2012/05/20 19:17:40 UTC
[jira] [Created] (UIMA-2404) UIMA-AS session inactivity timer
thread doesnt cleanup jms correctly
Jerry Cwiklik created UIMA-2404:
-----------------------------------
Summary: UIMA-AS session inactivity timer thread doesnt cleanup jms correctly
Key: UIMA-2404
URL: https://issues.apache.org/jira/browse/UIMA-2404
Project: UIMA
Issue Type: Bug
Components: Async Scaleout
Reporter: Jerry Cwiklik
Priority: Minor
Fix For: 2.4.0AS
Session inactivity timer pops by default after 30 minutes of inactivity and it closes JMS connection to a broker. Current code first closes the connection and subsequently tries to close all JMS Sessions associated with the connection. It should be other way around, first close Sessions and than the Connection.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (UIMA-2404) UIMA-AS session inactivity timer thread
doesnt cleanup jms correctly
Posted by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik closed UIMA-2404.
-------------------------------
Resolution: Fixed
Reverse the order of JMS cleanup when the inactivity timer pops. Closes sessions and subsequently a connection to a broker.
> UIMA-AS session inactivity timer thread doesnt cleanup jms correctly
> ---------------------------------------------------------------------
>
> Key: UIMA-2404
> URL: https://issues.apache.org/jira/browse/UIMA-2404
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Priority: Minor
> Fix For: 2.4.0AS
>
>
> Session inactivity timer pops by default after 30 minutes of inactivity and it closes JMS connection to a broker. Current code first closes the connection and subsequently tries to close all JMS Sessions associated with the connection. It should be other way around, first close Sessions and than the Connection.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira