[
https://issues.apache.org/jira/browse/UIMA-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eddie Epstein resolved UIMA-950.
--------------------------------
Resolution: Fixed
Well, the problem went away after discovering a dependent jar
file,common-collections, was not in the distribution. I had updated pom.xml but
missed bin.xml :(
The ClassNotFoundException only showed up when deploying the service by itself;
nothing when the service was deployed by the client API.
Burn, please close the issue after confirming the fix, or let us know otherwise.
Thanks,
Eddie
> Connection times out waiting for long running remote service and temp reply
> queues are lost ... cannot recover
> --------------------------------------------------------------------------------------------------------------
>
> Key: UIMA-950
> URL: https://issues.apache.org/jira/browse/UIMA-950
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.2.2S
> Reporter: Burn Lewis
> Fix For: 2.2.2S
>
>
> Using an aggregate client with a remote tcp service with remote temp reply
> queue. After 45 secs (in one case) get:
> 3/28/08 2:34:15 PM - 30:
> org.apache.activemq.ActiveMQConnection.onAsyncException: WARNING: Async
> exception with no exception listener: java.io.EOFException
> java.io.EOFException
> at java.io.DataInputStream.readFully(DataInputStream.java:204)
> at java.io.DataInputStream.readInt(DataInputStream.java:380)
> at
> org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268)
> at
> org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:192)
> at
> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:184)
> at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:172)
> at java.lang.Thread.run(Thread.java:803)
> The connection is refreshed, but the temp queue is not recreated
> 3/28/08 2:35:36 PM - 34:
> org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.handleListenerSetupFailure:
> WARNING: Jms Listener Failed. Endpoint: ID:telly-1196-1206729192229-2:5:1
> Managed By: tcp://ikmc09b02.watson.ibm.com:61616 Reason:
> javax.jms.InvalidDestinationException: Cannot use a Temporary destination
> from another Connection
> Addiing "?wireFormat.maxInactivityDuration=0" to the broker URL when starting
> it avoids the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
