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/07/24 16:35:34 UTC
[jira] [Closed] (UIMA-2437) UIMA AS not checking state of a
Connection when stopping resulting in ConnectionClosedException
[ https://issues.apache.org/jira/browse/UIMA-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik closed UIMA-2437.
-------------------------------
Resolution: Fixed
Added code to check if broker connection is valid before doing jms cleanup
> UIMA AS not checking state of a Connection when stopping resulting in ConnectionClosedException
> ---------------------------------------------------------------------------------------------------
>
> Key: UIMA-2437
> URL: https://issues.apache.org/jira/browse/UIMA-2437
> Project: UIMA
> Issue Type: Task
> Components: Async Scaleout
> Affects Versions: 2.3.1AS
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.4.0AS
>
>
> Jenkins reports an exception when running a new testcase testGenerateAndDeployPrimitiveDD():
> org.apache.activemq.ConnectionClosedException: The connection is already closed
> at org.apache.activemq.ActiveMQConnection.checkClosed(ActiveMQConnection.java:1363)
> at org.apache.activemq.ActiveMQConnection.checkClosedOrFailed(ActiveMQConnection.java:1350)
> at org.apache.activemq.ActiveMQConnection.deleteTempDestination(ActiveMQConnection.java:1933)
> at org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl.stopConnection(BaseUIMAAsynchronousEngine_impl.java:236)
> at org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl.stop(BaseUIMAAsynchronousEngine_impl.java:281)
> at org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl$UimaASShutdownHook.run(BaseUIMAAsynchronousEngineCommon_impl.java:3040)
> at java.lang.Thread.run(Thread.java:595)
> Check the state of a connection while doing cleanup.
--
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