[jira] Commented: (UIMA-787) Migrate code to the latest version of ActiveMQ (5.0.0)

["Burn Lewis (JIRA)" <ui...@incubator.apache.org>]

    [ https://issues.apache.org/jira/browse/UIMA-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582695#action_12582695 ] 

Burn Lewis commented on UIMA-787:
---------------------------------

If a getMeta timeout is large, say 60 secs, we get a broker inactivity exception ... seems to recover but generates a lot of errors, e.g.

3/26/08 6:29:24 PM - 20: org.apache.activemq.ActiveMQConnection.onAsyncException: WARNING: Async exception with no exception listener: org.apache.activemq.transport.InactivityIOException: Channel was inactive for too long: localhost/127.0.0.1:61616

I cannot reproduce as a JUnit test but the fix is to disable this check in the broker URL in activemq-nojournal.xml:

       <transportConnector name="default" uri="tcp://localhost:61616?wireFormat.maxInactivityDuration=0"/>


> Migrate code to the latest version of ActiveMQ (5.0.0)
> ------------------------------------------------------
>
>                 Key: UIMA-787
>                 URL: https://issues.apache.org/jira/browse/UIMA-787
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Async Scaleout
>    Affects Versions: 2.2.1
>            Reporter: Jerry Cwiklik
>            Assignee: Marshall Schor
>             Fix For: 2.2.2S
>
>         Attachments: uimaj-as-activemq-UIMA-787-patch.txt, uimaj-as-jms-UIMA-787-patch.txt
>
>
> Update build dependencies to use the latest version of ActiveMQ. Update UIMA-AS install scripts to download the latest ActiveMQ distribution.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.