activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Geurt Schimmel <GSchim...@schubergphilis.com>
Subject Re: InactivityMonitor=false not working ?
Date Wed, 29 Jan 2014 07:39:21 GMT
That did the trick.

Thanks Gary !

Geurt

Sent from my iPhone

> On 28 jan. 2014, at 22:20, "Gary Tully" <gary.tully@gmail.com> wrote:
> 
> I think you need:
> <networkConnector name="BrokerLinktoXxxmlog4" userName="system"
> password="${activemq.password}"
> uri="static:(ssl://xxxmlog4:61616?useInactivityMonitor=false)?useJmx=true"
> duplex="true">
> 
> 
>> On 27 January 2014 23:11, Geurt Schimmel <GSchimmel@schubergphilis.com> wrote:
>> Dear all,
>> 
>> In a network-of-brokers with 2 MQ instances (both ActiveMQ 5.9), I've configured
'ssl://0.0.0.0:61616?transport.useInactivityMonitor=false&amp;...' on both machines.
>> 
>> The connection is set up from host xxxmlog3 with
>> 
>> <networkConnector name="BrokerLinktoXxxmlog4" userName="system" password="${activemq.password}"
uri="static:(ssl://xxxmlog4:61616)?useJmx=true" duplex="true">
>> 
>> However - numerous messages about shutting down due to a remote error (alternating
with establishing the connection):
>> 
>> 2014-01-27 23:13:54,412 | WARN  | Network connection between vm://localhost#3396
and ssl://xxxmlog4/192.168.251.116:61616 shutdown due to a remote error: org.apache.activemq.transport.InactivityIOException:
Channel was inactive for too (>30000) long: tcp://192.168.251.116:61616 | org.apache.activemq.network.DemandForwardingBridgeSupport
| ActiveMQ InactivityMonitor Worker
>> 
>> Apparently,  'useInactivityMonitor=false' doesn't seem to have any effect.  Tried
adding 'wireFormat.maxInactivityDuration=0' to the networkconnector, but same behaviour: not
working.
>> 
>> Thanks,
>> Geurt
> 
> 
> 
> -- 
> http://redhat.com
> http://blog.garytully.com

Mime
View raw message