You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Geurt Schimmel <GS...@schubergphilis.com> on 2014/01/28 00:11:21 UTC

InactivityMonitor=false not working ?

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

Re: InactivityMonitor=false not working ?

Posted by artnaseef <ar...@artnaseef.com>.
Could it be "socket.useInactivityMonitor=false"?

Looking in transport/tcp/TcpTransportFactory.java:

        Map<String, Object> socketOptions =
IntrospectionSupport.extractProperties(options, "socket.");

        ...

        boolean useInactivityMonitor = "true".equals(getOption(options,
"useInactivityMonitor", "true"));




--
View this message in context: http://activemq.2283324.n4.nabble.com/InactivityMonitor-false-not-working-tp4676860p4676928.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: InactivityMonitor=false not working ?

Posted by Geurt Schimmel <GS...@schubergphilis.com>.
That did the trick.

Thanks Gary !

Geurt

Sent from my iPhone

> On 28 jan. 2014, at 22:20, "Gary Tully" <ga...@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 <GS...@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

Re: InactivityMonitor=false not working ?

Posted by Gary Tully <ga...@gmail.com>.
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 <GS...@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