[
https://issues.apache.org/jira/browse/UIMA-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583191#action_12583191
]
Eddie Epstein commented on UIMA-950:
------------------------------------
The API client does not have this problem, and does not show any inactivity
messages in the log while waiting patiently :)
Adding ?wireFormat.maxInactivityDuration=0 to the transport connector
definition in the broker did fix the problem for aggregate clients; after a 9
minute wait the missing service was started and all ran ok. However, an ugly
exception was logged in the aggregate client's logfile:
3/28/08 4:15:55 PM - 10:
org.apache.uima.adapter.jms.activemq.SpringContainerDeployer.waitForServiceNotification:
INFO: Uima EE Client Blocking - Awaiting Top Level Controller Initialization
Notification
3/28/08 4:19:54 PM - 15:
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
org.apache.activemq.transport.InactivityIOException: Channel was inactive for
too long: localhost/127.0.0.1:61616
at
org.apache.activemq.transport.InactivityMonitor$4.run(InactivityMonitor.java:108)
3/28/08 4:19:54 PM - 16:
org.apache.activemq.ActiveMQConnection.onAsyncException: WARNING: Async
exception with no exception listener: java.net.SocketException: socket closed
java.net.SocketException: socket closed
at java.net.SocketInputStream.read(SocketInputStream.java:155)
at
org.apache.activemq.transport.tcp.TcpBufferedInputStream.fill(TcpBufferedInputStream.java:50)
at
org.apache.activemq.transport.tcp.TcpBufferedInputStream.readStream(TcpBufferedInputStream.java:72)
at
org.apache.activemq.transport.tcp.TcpBufferedInputStream.read(TcpBufferedInputStream.java:92)
at java.io.DataInputStream.readFully(DataInputStream.java:202)
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)
3/28/08 4:19:54 PM - 17:
org.springframework.jms.listener.DefaultMessageListenerContainer.refreshConnectionUntilSuccessful:
INFO: Successfully refreshed JMS Connection
3/28/08 4:24:09 PM - 18:
org.apache.uima.adapter.jms.activemq.JmsInputChannel.onMessage: FINE: Service:
Received New Message
Hopefully there is some way to tell the spring listener not to do this.
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.
