activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <gary.tu...@gmail.com>
Subject Re: Channel was inactive for too long
Date Fri, 17 Jul 2009 14:22:13 GMT
I don't think the inactivity timeouts are negotiated, they need to be
configured on both ends.
Enabling full logging for org.apache.activemq.transport on both
brokers will allow you to see the wireFormat parameter negotiations to
verify what parameters are being offered and accepted.
I think you may find a need to configure an inactivityDuration on the
brokers bind/listen uri as well as on the networkconnector uri.

2009/7/17 RossStanton <ross_stanton@hotmail.com>:
>
> Hi
>
> We're in the process of implementing two AMQ brokers (v5.2.0) - one in Lille
> and the other in Hong Kong - in order to exchange data between a set of
> applications but are hitting a problem. All too frequently the connection is
> dropped - messages build up as pending on the broker producing them as the
> broker reports zero consumers.
>
> Lille is linked to HK via a NetworkConnector configured as follows:
> <networkConnector name="HK"
> uri="static://(tcp://10.247.88.57:61416?wireFormat.maxInactivityDuration=0&keepAlive=true&trace=true)"
> duplex="true"/>
>
> The following messages are logged repeatedly in HK but i don't think they
> are actually causing a problem.
>
> 2009-07-17 14:27:38,185 [247.32.82:51855] INFO  TransportConnection
> - Created Duplex Bridge back to LilleDevelopment
> 2009-07-17 14:27:38,200 [//localhost#224] INFO  DemandForwardingBridge
> - Network connection between vm://localhost#224 and
> tcp:///10.247.32.82:51855(LilleDevelopment) has been established.
> 2009-07-17 15:58:20,497 [247.32.82:58504] WARN  DemandForwardingBridge
> - Network connection between vm://localhost#212 and
> tcp:///10.247.32.82:58504 shutdown due to a remote error:
> java.net.SocketException: Connection reset
>
> HK also logs the following message occasionally and it's this that i believe
> is breaking the connection:
>
> 2009-07-17 15:59:24,169 [//localhost#222] WARN  DemandForwardingBridge
> - Caught an exception processing local command
> org.apache.activemq.transport.InactivityIOException: Channel was inactive
> for too long: /10.247.32.82:61115
>        at
> org.apache.activemq.transport.InactivityMonitor.oneway(InactivityMonitor.java:225)
>        at
> org.apache.activemq.transport.TransportFilter.oneway(TransportFilter.java:83)
>        at
> org.apache.activemq.transport.WireFormatNegotiator.oneway(WireFormatNegotiator.java:100)
>        at
> org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:40)
>        at
> org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)
>        at
> org.apache.activemq.network.DemandForwardingBridgeSupport.serviceLocalCommand(DemandForwardingBridgeSupport.java:647)
>        at
> org.apache.activemq.network.DemandForwardingBridgeSupport$1.onCommand(DemandForwardingBridgeSupport.java:147)
>        at
> org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:104)
>        at
> org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:68)
>        at
> org.apache.activemq.transport.vm.VMTransport.iterate(VMTransport.java:205)
>        at
> org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:98)
>        at
> org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:36)
>
> I've attached both ActiveMQ.xml config files, any help much appreciated!
>
> Thanks
>
> Ross
>
> http://www.nabble.com/file/p24531057/hk_activemq.xml hk_activemq.xml
> http://www.nabble.com/file/p24531057/lille_activemq.xml lille_activemq.xml
>
> --
> View this message in context: http://www.nabble.com/Channel-was-inactive-for-too-long-tp24531057p24531057.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>



-- 
http://blog.garytully.com

Open Source Integration
http://fusesource.com

Mime
View raw message