The failover transport doesn't rely on the inactivity monitor. The
inactivity monitor serves to detect (and prevent, if you enable keepalive)
disconnections due to inactivity sooner than the disconnection detection
that's built into the TCP protocol itself (subject to settings on the
socket, which might be influenced by settings on the OSes on both ends),
but sooner or later the disconnection will be detected and the failover
protocol will re-establish the connection.

Tim

On Jun 28, 2017 8:36 PM, "boppana" <lakshmi.bopp...@uk.bp.com> wrote:

> Thanks for your suggestions, I will keep my log level as INFO.
>
> I have one last question
>
> Ø  If I  disable inactivity Monitor in my subscriber  i.e.
> "&nested.useInactivityMonitor=false&nested.wireFormat.maxInactivityDuration=0",
> So in this case if connection breaks down then still my fail over will work
> right? Or failover will work only if I enable inactivity monitor?
> I mean does failover is dependent on my useInactivityMonitor settings?
>
> My complete Url is
> url = "failover://(ssl://"
>                            + SubParams.getPropertyVal(
> SubParams.SUBSCRIBER_EMS_SERVER)
>                            + ":"
>                            + SubParams.getPropertyVal(
> SubParams.SUBSCRIBER_EMS_PORT)
>                            + ")?jms.useCompression=true&
> maxReconnectDelay="
>                            + SubParams
>                                          .getIntVal(SubParams.
> SUBSCRIBER_EMS_CONNECT_ATTEMPT_DELAY)
>                            + "&timeout="
>                            + SubParams
>                                          .getIntVal(SubParams.
> SUBSCRIBER_EMS_CONNECT_ATTEMPT_TIMEOUT)
>                            + "&maxReconnectAttempts="
>                            + SubParams
>                                          .getIntVal(SubParams.
> SUBSCRIBER_EMS_CONNECT_ATTEMPT_COUNT)
>                            + "&nested.useInactivityMonitor=
> false&nested.wireFormat.maxInactivityDuration=0";
>
>
>
> Regards,
> Lakshmi Prasad Boppana
> Developer
>
> From: Tim Bain [via ActiveMQ] [mailto:ml+s2283324n4728044...@n4.nabble.com
> ]
> Sent: 29 June 2017 10:48
> To: Boppana, Lakshmi Prasad (INFOSYS)
> Subject: RE: My Subscriber is reconnecting after every 5 mins
>
> 1. You would turn your Log4J logging level down from DEBUG to a reasonable
> level like WARN or maybe INFO. Why do you have it at DEBUG, anyway?
>
> 2. That option (and lots more) are documented at
> http://activemq.apache.org/tcp-transport-reference.html. Note that you'll
> need to prefix the option with "nested." like you did for
> useInactivityMonitor, to pass the options from the failover transport into
> the ssl transport.
>
> Tim
>
> On Jun 28, 2017 8:00 AM, "boppana" <[hidden 
> email]</user/SendEmail.jtp?type=node&node=4728044&i=0>>
> wrote:
>
> > If I enable inactivity monitor(i.e. removing wireFormat.
> > maxInactivityDuration=0&useInactivityMonitor=false from url) then am
> > getting following Acctivity monitor log entries and my log file is filled
> > with all these messages for almost every 2 seconds.
> >
> > 1.How to get rid of these entries in logs?
> > 2.You mentioned that "enable keepalive on the TCP transport", where I can
> > do this?is this something configured only at my subscriber end or at MAQ
> > server end or publisher? Also can u let me know how to set up this
> > keepAlive?
> >
> >
> > 28 Jun 2017 21:55:20,445 [ActiveMQ InactivityMonitor ReadCheckTimer]
> DEBUG
> > org.apache.activemq.transport.AbstractInactivityMonitor - A receive is
> in
> > progress, skipping read check.
> > 28 Jun 2017 21:55:20,445 [ActiveMQ InactivityMonitor WriteCheckTimer]
> > DEBUG org.apache.activemq.transport.AbstractInactivityMonitor - ssl://
> > il3-broker-a-il-core-int-06.apps.test-a.0341.o2.
> > we1.csl.cd2.bp.com/10.165.5.103:443 message sent since last write check,
> > resetting flag.
> > 28 Jun 2017 21:55:23,593 [ActiveMQ InactivityMonitor ReadCheckTimer]
> DEBUG
> > org.apache.activemq.transport.AbstractInactivityMonitor - A receive is
> in
> > progress, skipping read check.
> > 28 Jun 2017 21:55:23,593 [ActiveMQ InactivityMonitor WriteCheckTimer]
> > DEBUG org.apache.activemq.transport.AbstractInactivityMonitor - ssl://
> > il3-broker-a-il-core-int-06.apps.test-a.0341.o2.
> > we1.csl.cd2.bp.com/10.165.5.103:443 message sent since last write check,
> > resetting flag.
> > 28 Jun 2017 21:55:24,487 [ActiveMQ InactivityMonitor ReadCheckTimer]
> DEBUG
> > org.apache.activemq.transport.AbstractInactivityMonitor - A receive is
> in
> > progress, skipping read check.
> > 28 Jun 2017 21:55:24,487 [ActiveMQ InactivityMonitor WriteCheckTimer]
> > DEBUG org.apache.activemq.transport.AbstractInactivityMonitor - ssl://
> > il3-broker-a-il-core-int-06.apps.test-a.0341.o2.
> > we1.csl.cd2.bp.com/10.165.5.103:443 message sent since last write check,
> > resetting flag.
> > 28 Jun 2017 21:55:30,445 [ActiveMQ InactivityMonitor WriteCheckTimer]
> > DEBUG org.apache.activemq.transport.AbstractInactivityMonitor -
> > WriteChecker: 10000ms elapsed since last write check.
> > 28 Jun 2017 21:55:30,445 [ActiveMQ InactivityMonitor WriteCheckTimer]
> > DEBUG org.apache.activemq.transport.AbstractInactivityMonitor - ssl://
> > il3-broker-a-il-core-int-06.apps.test-a.0341.o2.
> > we1.csl.cd2.bp.com/10.165.5.103:443 no message sent since last write
> > check, sending a KeepAliveInfo
> > 28 Jun 2017 21:55:30,448 [ActiveMQ InactivityMonitor Worker] DEBUG
> > org.apache.activemq.transport.AbstractInactivityMonitor - Running
> > WriteCheck[tcp://10.165.5.103:443]
> > 28 Jun 2017 21:55:33,593 [ActiveMQ InactivityMonitor WriteCheckTimer]
> > DEBUG org.apache.activemq.transport.AbstractInactivityMonitor -
> > WriteChecker: 10000ms elapsed since last write check.
> > 28 Jun 2017 21:55:33,593 [ActiveMQ InactivityMonitor WriteCheckTimer]
> > DEBUG org.apache.activemq.transport.AbstractInactivityMonitor - ssl://
> > il3-broker-a-il-core-int-06.apps.test-a.0341.o2.
> > we1.csl.cd2.bp.com/10.165.5.103:443 no message sent since last write
> > check, sending a KeepAliveInfo
> > 28 Jun 2017 21:55:33,597 [ActiveMQ InactivityMonitor Worker] DEBUG
> > org.apache.activemq.transport.AbstractInactivityMonitor - Running
> > WriteCheck[tcp://10.165.5.103:443]
> >
> >
> >
> > From: Tim Bain [via ActiveMQ] [mailto:[hidden
> email]</user/SendEmail.jtp?type=node&node=4728044&i=1>
> > ]
> > Sent: 28 June 2017 20:32
> > To: Boppana, Lakshmi Prasad (INFOSYS)
> > Subject: RE: My Subscriber is reconnecting after every 5 mins
> >
> > It looks like you're disabling the inactivity monitor (
> > useInactivityMonitor=false
> > <http://il3-broker-a-il-core-int-06.apps.test-a.0341.o2.
> > we1.csl.cd2.bp.com:443/?wireFormat.maxInactivityDuration=0&
> > useInactivityMonitor=false>)
> > but
> > not enabling TCP keepalive, so I'd expect your TCP sockets to time out
> due
> > to inactivity after some amount of time, and five minutes sounds like a
> > plausible duration.
> >
> > If that's indeed what's going on, and if you want this to stop happening,
> > either enable the inactivity monitor or enable keepalive on the TCP
> > transport. Or don't, and just keep things as they are, since you haven't
> > said that there's anything that doesn't actually work, you just have
> extra
> > noise in the logs. Either way works.
> >
> > Tim
> >
> > On Jun 28, 2017 4:30 AM, "boppana" <[hidden email]</user/SendEmail.jtp?
> type=node&node=4727996&i=0>>
> > wrote:
> >
> > > Below are my logs
> > > 28 Jun 2017 14:15:28,042 [ActiveMQ Transport:
> ssl://il3-broker-a-il-core-
> > > int-06.apps.test-a.0341.o2.we1.csl.cd2.bp.com/10.165.5.202:443] DEBUG
> > > org.apache.activemq.transport.failover.FailoverTransport - ssl://
> > > il3-broker-a-il-core-int-06.apps.test-a.0341.o2.we1.csl.cd2.bp.com:443
> ?
> > > wireFormat.maxInactivityDuration=0&useInactivityMonitor=false
> > > handleTransportFailure: java.io.EOFException
> > > java.io.EOFException
> > >                 at java.io.DataInputStream.
> readInt(DataInputStream.java:
> > > 392)
> > >                 at org.apache.activemq.openwire.
> > OpenWireFormat.unmarshal(
> > > OpenWireFormat.java:258)
> > >                 at org.apache.activemq.transport.
> > > tcp.TcpTransport.readCommand(TcpTransport.java:221)
> > >                 at org.apache.activemq.transport.
> tcp.TcpTransport.doRun(
> > > TcpTransport.java:213)
> > >                 at org.apache.activemq.transport.tcp.TcpTransport.run(
> > > TcpTransport.java:196)
> > >                 at java.lang.Thread.run(Thread.java:745)
> > > 28 Jun 2017 14:15:28,045 [ActiveMQ Transport:
> ssl://il3-broker-a-il-core-
> > > int-06.apps.test-a.0341.o2.we1.csl.cd2.bp.com/10.165.5.202:443] DEBUG
> > > org.apache.activemq.transport.tcp.TcpTransport - Stopping transport
> > ssl://
> > > il3-broker-a-il-core-int-06.apps.test-a.0341.o2.
> > > we1.csl.cd2.bp.com/10.165.5.202:443
> > > 28 Jun 2017 14:15:28,046 [ActiveMQ Transport:
> ssl://il3-broker-a-il-core-
> > > int-06.apps.test-a.0341.o2.we1.csl.cd2.bp.com/10.165.5.202:443] DEBUG
> > > org.apache.activemq.thread.TaskRunnerFactory - Initialized
> > > TaskRunnerFactory[ActiveMQ Task] using ExecutorService:
> > > java.util.concurrent.ThreadPoolExecutor@30567156[
> Running<mailto<mailto:java.util.concurrent.ThreadPoolExecutor@30567156[
> Running%3cmailto>:
> > java.util.concurrent.ThreadPoolExecutor@30567156[Running<mailto:
> java.util.concurrent.ThreadPoolExecutor@30567156[Running>>, pool size = 0,
> > > active threads = 0, queued tasks = 0, completed tasks = 0]
> > > 28 Jun 2017 14:15:28,048 [ActiveMQ Transport:
> ssl://il3-broker-a-il-core-
> > > int-06.apps.test-a.0341.o2.we1.csl.cd2.bp.com/10.165.5.202:443] DEBUG
> > > org.apache.activemq.thread.TaskRunnerFactory - Execute[ActiveMQ Task]
> > > runnable: org.apache.activemq.transport.tcp.TcpTransport$1@4f8c8801<<
> mailto:org.apache.activemq.transport.tcp.TcpTransport$1@4f8c8801%3c>
> > mailto:org.apache.activemq.transport.tcp.TcpTransport$1@4f8c8801>
> > > 28 Jun 2017 14:15:28,048 [ActiveMQ Transport:
> ssl://il3-broker-a-il-core-
> > > int-06.apps.test-a.0341.o2.we1.csl.cd2.bp.com/10.165.5.202:443] DEBUG
> > > org.apache.activemq.thread.TaskRunnerFactory - Created thread[ActiveMQ
> > > Task-1]: Thread[ActiveMQ Task-1,5,main]
> > > 28 Jun 2017 14:15:28,049 [ActiveMQ Task-1] DEBUG
> > > org.apache.activemq.transport.tcp.TcpTransport - Closing socket
> > > e2bcb15[TLS_RSA_WITH_AES_128_CBC_SHA256: Socket[addr=il3-broker-a-il-
> > > core-int-06.apps.test-a.0341.o2.we1.csl.cd2.bp.com/10.165.
> > > 5.202,port=443,localport=64955]]
> > > 28 Jun 2017 14:15:28,049 [ActiveMQ Task-1] DEBUG
> > > org.apache.activemq.transport.tcp.TcpTransport - Closed socket
> > > e2bcb15[TLS_RSA_WITH_AES_128_CBC_SHA256: Socket[addr=il3-broker-a-il-
> > > core-int-06.apps.test-a.0341.o2.we1.csl.cd2.bp.com/10.165.
> > > 5.202,port=443,localport=64955]]
> > > 28 Jun 2017 14:15:28,051 [ActiveMQ Transport:
> ssl://il3-broker-a-il-core-
> > > int-06.apps.test-a.0341.o2.we1.csl.cd2.bp.com/10.165.5.202:443] DEBUG
> > > org.apache.activemq.util.ThreadPoolUtils - Forcing shutdown of
> > > ExecutorService: java.util.concurrent.ThreadPoolExecutor@30567156<
> mailto:java.util.concurrent.ThreadPoolExecutor@30567156>[
> > Running<mailto:java.util.concurrent.ThreadPoolExecutor@30567156
> [Running>,
> > > pool size = 1, active threads = 0, queued tasks = 0, completed tasks =
> 1]
> > > 28 Jun 2017 14:15:28,051 [ActiveMQ Transport:
> ssl://il3-broker-a-il-core-
> > > int-06.apps.test-a.0341.o2.we1.csl.cd2.bp.com/10.165.5.202:443] DEBUG
> > > org.apache.activemq.util.ThreadPoolUtils - Shutdown of
> ExecutorService:
> > > java.util.concurrent.ThreadPoolExecutor@30567156[
> Terminated<mailto<mailto:java.util.concurrent.ThreadPoolExecutor@30567156[
> Terminated%3cmailto>:
> > java.util.concurrent.ThreadPoolExecutor@30567156[Terminated<mailto:
> java.util.concurrent.ThreadPoolExecutor@30567156[Terminated>>, pool size =
> > > 0, active threads = 0, queued tasks = 0, completed tasks = 1] is
> > shutdown:
> > > true and terminated: false.
> > > 28 Jun 2017 14:15:28,052 [ActiveMQ Transport:
> ssl://il3-broker-a-il-core-
> > > int-06.apps.test-a.0341.o2.we1.csl.cd2.bp.com/10.165.5.202:443] WARN
> > > org.apache.activemq.transport.failover.FailoverTransport - Transport
> > > (ssl://il3-broker-a-il-core-int-06.apps.test-a.0341.o2.
> > > we1.csl.cd2.bp.com/10.165.5.202:443) failed, attempting to
> automatically
> > > reconnect
> > > java.io.EOFException
> > >                 at java.io.DataInputStream.
> readInt(DataInputStream.java:
> > > 392)
> > >                 at org.apache.activemq.openwire.
> > OpenWireFormat.unmarshal(
> > > OpenWireFormat.java:258)
> > >                 at org.apache.activemq.transport.
> > > tcp.TcpTransport.readCommand(TcpTransport.java:221)
> > >                 at org.apache.activemq.transport.
> tcp.TcpTransport.doRun(
> > > TcpTransport.java:213)
> > >                 at org.apache.activemq.transport.tcp.TcpTransport.run(
> > > TcpTransport.java:196)
> > >                 at java.lang.Thread.run(Thread.java:745)
> > > 28 Jun 2017 14:15:28,056 [ActiveMQ Transport:
> ssl://il3-broker-a-il-core-
> > > int-06.apps.test-a.0341.o2.we1.csl.cd2.bp.com/10.165.5.202:443] DEBUG
> > > org.apache.activemq.ActiveMQConnection - transport interrupted -
> > > processing required, dispatchers: 1
> > > 28 Jun 2017 14:15:28,056 [ActiveMQ Transport:
> ssl://il3-broker-a-il-core-
> > > int-06.apps.test-a.0341.o2.we1.csl.cd2.bp.com/10.165.5.202:443] DEBUG
> > > org.apache.activemq.ActiveMQConnection - notified failover transport
> > > (unconnected) of pending interruption processing for:
> > > ID:IVCSW70007257-V-64954-1498630226763-1:1
> > > 28 Jun 2017 14:15:28,056 [ActiveMQ Transport:
> ssl://il3-broker-a-il-core-
> > > int-06.apps.test-a.0341.o2.we1.csl.cd2.bp.com/10.165.5.202:443] DEBUG
> > > org.apache.activemq.thread.TaskRunnerFactory - Created thread[ActiveMQ
> > > Task-3]: Thread[ActiveMQ Task-3,5,main]
> > > 28 Jun 2017 14:15:28,058 [ActiveMQConnection[ID:IVCSW70007257-V-64954-
> > 1498630226763-1:1]
> > > Scheduler] DEBUG org.apache.activemq.ActiveMQMessageConsumer -
> > > ID:IVCSW70007257-V-64954-1498630226763-1:1:1:1 clearing unconsumed
> list
> > > (0) on transport interrupt
> > > 28 Jun 2017 14:15:28,058 [ActiveMQConnection[ID:IVCSW70007257-V-64954-
> > 1498630226763-1:1]
> > > Scheduler] DEBUG org.apache.activemq.ActiveMQConnection -
> > > transportInterruptionProcessingComplete: 0
> for:ID:IVCSW70007257-V-64954-
> > > 1498630226763-1:1
> > > 28 Jun 2017 14:15:28,058 [ActiveMQConnection[ID:IVCSW70007257-V-64954-
> > 1498630226763-1:1]
> > > Scheduler] DEBUG org.apache.activemq.ActiveMQConnection - notified
> > > failover transport (unconnected) of interruption completion for:
> > > ID:IVCSW70007257-V-64954-1498630226763-1:1
> > > 28 Jun 2017 14:15:28,059 [ActiveMQ Task-3] DEBUG
> > > org.apache.activemq.thread.PooledTaskRunner - Running task iteration
> 0 -
> > > org.apache.activemq.transport.failover.FailoverTransport$2@
> > 7dc9eb54<mailto:org.apache.activemq.transport.failover.FailoverTransport
> <mailto:org.apache.activemq.transport.failover.FailoverTransport%20%0b>>
> $2@7dc9eb54>
> > > 28 Jun 2017 14:15:28,059 [ActiveMQ Task-3] DEBUG
> > > org.apache.activemq.transport.failover.FailoverTransport - urlList
> > > connectionList:[ssl://il3-broker-a-il-core-int-06.apps.
> > > test-a.0341.o2.we1.csl.cd2.bp.com:443], from:
> > [ssl://il3-broker-a-il-core-
> > > int-06.apps.test-a.0341.o2.we1.csl.cd2.bp.com:443]
> > > 28 Jun 2017 14:15:28,059 [ActiveMQ Task-3] DEBUG
> > > org.apache.activemq.transport.failover.FailoverTransport - Waiting 10
> ms
> > > before attempting connection.
> > > 28 Jun 2017 14:15:28,071 [ActiveMQ Task-3] DEBUG
> > > org.apache.activemq.transport.failover.FailoverTransport - Attempting
> > > 0th  connect to: ssl://il3-broker-a-il-core-
> int-06.apps.test-a.0341.o2.
> > > we1.csl.cd2.bp.com:443?wireFormat.maxInactivityDuration=0&
> > > useInactivityMonitor=false
> > > 28 Jun 2017 14:15:28,168 [ActiveMQ Task-3] DEBUG
> > > org.apache.activemq.transport.WireFormatNegotiator - Sending:
> > > WireFormatInfo { version=10, properties={TcpNoDelayEnabled=true,
> > > SizePrefixDisabled=false, CacheSize=1024, StackTraceEnabled=true,
> > > CacheEnabled=true, TightEncodingEnabled=true, MaxFrameSize=
> > 9223372036854775807,
> > > MaxInactivityDuration=0, MaxInactivityDurationInitalDelay=10000},
> > > magic=[A,c,t,i,v,e,M,Q]}
> > > 28 Jun 2017 14:15:28,168 [ActiveMQ Transport:
> ssl://il3-broker-a-il-core-
> > > int-06.apps.test-a.0341.o2.we1.csl.cd2.bp.com/10.165.5.103:443] DEBUG
> > > org.apache.activemq.transport.tcp.TcpTransport - TCP consumer thread
> for
> > > ssl://il3-broker-a-il-core-int-06.apps.test-a.0341.o2.
> > > we1.csl.cd2.bp.com/10.165.5.103:443 starting
> > > 28 Jun 2017 14:15:28,251 [ActiveMQ Transport:
> ssl://il3-broker-a-il-core-
> > > int-06.apps.test-a.0341.o2.we1.csl.cd2.bp.com/10.165.5.103:443] DEBUG
> > > org.apache.activemq.transport.WireFormatNegotiator - Received
> > WireFormat:
> > > WireFormatInfo { version=10, properties={TcpNoDelayEnabled=true,
> > > SizePrefixDisabled=false, CacheSize=1024, StackTraceEnabled=true,
> > > CacheEnabled=true, TightEncodingEnabled=true, MaxFrameSize=104857600,
> > > MaxInactivityDuration=30000, MaxInactivityDurationInitalDelay=10000},
> > > magic=[A,c,t,i,v,e,M,Q]}
> > > 28 Jun 2017 14:15:28,252 [ActiveMQ Transport:
> ssl://il3-broker-a-il-core-
> > > int-06.apps.test-a.0341.o2.we1.csl.cd2.bp.com/10.165.5.103:443] DEBUG
> > > org.apache.activemq.transport.WireFormatNegotiator - ssl://
> > > il3-broker-a-il-core-int-06.apps.test-a.0341.o2.
> > > we1.csl.cd2.bp.com/10.165.5.103:443 before negotiation:
> > > OpenWireFormat{version=10, cacheEnabled=false, stackTraceEnabled=false,
> > > tightEncodingEnabled=false, sizePrefixDisabled=false, maxFrameSize=
> > > 9223372036854775807}
> > > 28 Jun 2017 14:15:28,252 [ActiveMQ Transport:
> ssl://il3-broker-a-il-core-
> > > int-06.apps.test-a.0341.o2.we1.csl.cd2.bp.com/10.165.5.103:443] DEBUG
> > > org.apache.activemq.transport.WireFormatNegotiator - ssl://
> > > il3-broker-a-il-core-int-06.apps.test-a.0341.o2.
> > > we1.csl.cd2.bp.com/10.165.5.103:443 after negotiation:
> > > OpenWireFormat{version=10, cacheEnabled=true, stackTraceEnabled=true,
> > > tightEncodingEnabled=true, sizePrefixDisabled=false,
> > maxFrameSize=104857600}
> > > 28 Jun 2017 14:15:28,253 [ActiveMQ Task-3] DEBUG
> > org.apache.activemq.state.ConnectionStateTracker
> > > - conn: ID:IVCSW70007257-V-64954-1498630226763-1:1
> > > 28 Jun 2017 14:15:28,253 [ActiveMQ Task-3] DEBUG
> > org.apache.activemq.state.ConnectionStateTracker
> > > - session: ID:IVCSW70007257-V-64954-1498630226763-1:1:-1
> > > 28 Jun 2017 14:15:28,254 [ActiveMQ Task-3] DEBUG
> > org.apache.activemq.state.ConnectionStateTracker
> > > - consumer: ID:IVCSW70007257-V-64954-1498630226763-1:1:-1:1
> > > 28 Jun 2017 14:15:28,255 [ActiveMQ Task-3] DEBUG
> > org.apache.activemq.state.ConnectionStateTracker
> > > - session: ID:IVCSW70007257-V-64954-1498630226763-1:1:1
> > > 28 Jun 2017 14:15:28,255 [ActiveMQ Task-3] DEBUG
> > org.apache.activemq.state.ConnectionStateTracker
> > > - consumer: ID:IVCSW70007257-V-64954-1498630226763-1:1:1:1
> > > 28 Jun 2017 14:15:28,255 [ActiveMQ Task-3] DEBUG
> > > org.apache.activemq.transport.failover.FailoverTransport - Connection
> > > established
> > > 28 Jun 2017 14:15:28,256 [ActiveMQ Task-3] INFO
> > > org.apache.activemq.transport.failover.FailoverTransport -
> Successfully
> > > reconnected to ssl://il3-broker-a-il-core-int-06.apps.test-a.0341.o2.
> > > we1.csl.cd2.bp.com:443?wireFormat.maxInactivityDuration=0&
> > > useInactivityMonitor=false
> > > 28 Jun 2017 14:15:28,256 [ActiveMQ Task-3] DEBUG
> > > org.apache.activemq.thread.TaskRunnerFactory - Created thread[ActiveMQ
> > > Task-4]: Thread[ActiveMQ Task-4,5,main]
> > > 28
> > >
> > >
> > >
> > > From: jkorab [via ActiveMQ] [mailto:[hidden
> email]</user/SendEmail.jtp?
> > type=node&node=4727996&i=1>]
> > > Sent: 28 June 2017 18:10
> > > To: Boppana, Lakshmi Prasad (INFOSYS)
> > > Subject: Re: My Subscriber is reconnecting after every 5 mins
> > >
> > > Hi,
> > > What do the ActiveMQ logs say at that time?
> > > Jakub
> > >
> > > On Wed, Jun 28, 2017 at 7:07 AM, boppana [via ActiveMQ] <[hidden
> > > email]</user/SendEmail.jtp?type=node&node=4727990&i=0>> wrote:
> > > Hi Team,
> > > Iam as a subscriber using following url for connecting my AMQ broker
> > > url = "failover://(ssl://"
> > >                                 + SubParams.getPropertyVal(
> > > SubParams.SUBSCRIBER_EMS_SERVER)
> > >                                 + ":"
> > >                                 + SubParams.getPropertyVal(
> > > SubParams.SUBSCRIBER_EMS_PORT)
> > >                                 + ")?jms.useCompression=true&
> > > maxReconnectDelay="
> > >                                 + SubParams
> > >                                                 .getIntVal(SubParams.
> > > SUBSCRIBER_EMS_CONNECT_ATTEMPT_DELAY)
> > >                                 + "&timeout="
> > >                                 + SubParams
> > >                                                 .getIntVal(SubParams.
> > > SUBSCRIBER_EMS_CONNECT_ATTEMPT_TIMEOUT)
> > >                                 + "&maxReconnectAttempts="
> > >                                 + SubParams
> > >                                                 .getIntVal(SubParams.
> > > SUBSCRIBER_EMS_CONNECT_ATTEMPT_COUNT)
> > >                                 + "&nested.useInactivityMonitor=
> > > false&nested.wireFormat.maxInactivityDuration=0";
> > >
> > > If publisher is not publishing any messages then after 5 mins my
> > > subscriber is going down and again as I mentioned failover its able to
> > > successfully reconnect.But why its always going down after every 5 mins
> > and
> > > how can I avoid this?
> > > Am getting below error when subscriber is going down
> > >
> > > [ActiveMQ Transport: ssl://il3-broker-a-il-core-
> > > int-06.apps.test-a.0341.o2.we1.csl.cd2.bp.com/10.165.5.202:443<
> > > http://il3-broker-a-il-core-int-06.apps.test-a.
> > > 0341.o2.we1.csl.cd2.bp.com/10.165.5.202:443>] DEBUG
> > > org.apache.activemq.transport.failover.FailoverTransport - ssl://
> > > il3-broker-a-il-core-int-06.apps.test-a.0341.o2.we1.csl.cd2.bp.com:443
> ?
> > > wireFormat.maxInactivityDuration=0&useInactivityMonitor=false<htt
> > > p://il3-broker-a-il-core-int-06.apps.test-a.0341.o2.we1.
> > > csl.cd2.bp.com:443?wireFormat.maxInactivityDuration=0&
> > > useInactivityMonitor=false> handleTransportFailure:
> java.io.EOFException
> > > java.io.EOFException
> > >         at java.io.DataInputStream.readInt(DataInputStream.java:392)
> > >         at org.apache.activemq.openwire.OpenWireFormat.unmarshal(
> > > OpenWireFormat.java:258)
> > >         at org.apache.activemq.transport.tcp.TcpTransport.readCommand(
> > > TcpTransport.java:221)
> > >         at org.apache.activemq.transport.tcp.TcpTransport.doRun(
> > > TcpTransport.java:213)
> > >         at org.apache.activemq.transport.tcp.TcpTransport.run(
> > > TcpTransport.java:196)
> > >         at java.lang.Thread.run(Thread.java:745)
> > >
> > > ________________________________
> > > If you reply to this email, your message will be added to the
> discussion
> > > below:
> > > http://activemq.2283324.n4.nabble.com/My-Subscriber-is-
> > > reconnecting-after-every-5-mins-tp4727982.html
> > > To unsubscribe from ActiveMQ - User, click here.
> > > NAML<http://activemq.2283324.n4.nabble.com/template/
> > > NamlServlet.jtp?macro=macro_viewer&id=instant_html%
> > > 21nabble%3Aemail.naml&base=nabble.naml.namespaces.
> > > BasicNamespace-nabble.view.web.template.NabbleNamespace-
> > > nabble.view.web.template.NodeNamespace&breadcrumbs=
> > > notify_subscribers%21nabble%3Aemail.naml-instant_emails%
> > > 21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
> > >
> > >
> > > ________________________________
> > > If you reply to this email, your message will be added to the
> discussion
> > > below:
> > > http://activemq.2283324.n4.nabble.com/My-Subscriber-is-
> > > reconnecting-after-every-5-mins-tp4727982p4727990.html
> > > To start a new topic under ActiveMQ - User, email
> > > [hidden email]</user/SendEmail.jtp?type=node&node=4727996&i=2><mailto:
> > ml+
> > <mailto:ml+%20%0b>> [hidden email]</user/SendEmail.jtp?
> > type=node&node=4727996&i=3>>
> > > To unsubscribe from My Subscriber is reconnecting after every 5 mins,
> > > click here<http://activemq.2283324.n4.nabble.com/template/
> > > NamlServlet.jtp?macro=unsubscribe_by_code&node=4727982&code=
> > > bGFrc2htaS5ib3BwYW5hQHVrLmJwLmNvbXw0NzI3OTgyfDQyNDk4NzEwNw==>.
> > > NAML<http://activemq.2283324.n4.nabble.com/template/
> > > NamlServlet.jtp?macro=macro_viewer&id=instant_html%
> > > 21nabble%3Aemail.naml&base=nabble.naml.namespaces.
> > > BasicNamespace-nabble.view.web.template.NabbleNamespace-
> > > nabble.view.web.template.NodeNamespace&breadcrumbs=
> > > notify_subscribers%21nabble%3Aemail.naml-instant_emails%
> > > 21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
> > >
> > >
> > >
> > >
> > > --
> > > View this message in context: http://activemq.2283324.n4.
> > > nabble.com/My-Subscriber-is-reconnecting-after-every-5-
> > > mins-tp4727982p4727991.html
> > > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> >
> > ________________________________
> > If you reply to this email, your message will be added to the discussion
> > below:
> > http://activemq.2283324.n4.nabble.com/My-Subscriber-is-
> > reconnecting-after-every-5-mins-tp4727982p4727996.html
> > To start a new topic under ActiveMQ - User, email
> > [hidden email]</user/SendEmail.jtp?type=node&node=4728044&i=2><mailto:
> ml+
> <mailto:ml+%20%0b>> [hidden email]</user/SendEmail.jtp?
> type=node&node=4728044&i=3>>
> > To unsubscribe from My Subscriber is reconnecting after every 5 mins,
> > click here<http://activemq.2283324.n4.nabble.com/template/
> > NamlServlet.jtp?macro=unsubscribe_by_code&node=4727982&code=
> > bGFrc2htaS5ib3BwYW5hQHVrLmJwLmNvbXw0NzI3OTgyfDQyNDk4NzEwNw==>.
> > NAML<http://activemq.2283324.n4.nabble.com/template/
> > NamlServlet.jtp?macro=macro_viewer&id=instant_html%
> > 21nabble%3Aemail.naml&base=nabble.naml.namespaces.
> > BasicNamespace-nabble.view.web.template.NabbleNamespace-
> > nabble.view.web.template.NodeNamespace&breadcrumbs=
> > notify_subscribers%21nabble%3Aemail.naml-instant_emails%
> > 21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
> >
> >
> >
> >
> > --
> > View this message in context: http://activemq.2283324.n4.
> > nabble.com/My-Subscriber-is-reconnecting-after-every-5-
> > mins-tp4727982p4728000.html
> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
> ________________________________
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/My-Subscriber-is-
> reconnecting-after-every-5-mins-tp4727982p4728044.html
> To start a new topic under ActiveMQ - User, email
> ml+s2283324n2341805...@n4.nabble.com<mailto:ml+
> s2283324n2341805...@n4.nabble.com>
> To unsubscribe from My Subscriber is reconnecting after every 5 mins,
> click here<http://activemq.2283324.n4.nabble.com/template/
> NamlServlet.jtp?macro=unsubscribe_by_code&node=4727982&code=
> bGFrc2htaS5ib3BwYW5hQHVrLmJwLmNvbXw0NzI3OTgyfDQyNDk4NzEwNw==>.
> NAML<http://activemq.2283324.n4.nabble.com/template/
> NamlServlet.jtp?macro=macro_viewer&id=instant_html%
> 21nabble%3Aemail.naml&base=nabble.naml.namespaces.
> BasicNamespace-nabble.view.web.template.NabbleNamespace-
> nabble.view.web.template.NodeNamespace&breadcrumbs=
> notify_subscribers%21nabble%3Aemail.naml-instant_emails%
> 21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/My-Subscriber-is-reconnecting-after-every-5-
> mins-tp4727982p4728045.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to