activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <tb...@alumni.duke.edu>
Subject Re: ActiveMQ InactivityMonitor Weird Issue
Date Sat, 13 Feb 2016 17:45:51 GMT
The log line says that it's been very little time since we sent the
previous message, so if you're seeing it many times in a row it means
you're sending lots of messages in rapid succession.  Which will probably
result in high network utilization.

Why are you running Log4J at DEBUG?  You should run at INFO unless there's
a specific problem you're trying to debug.

Tim
On Jan 28, 2016 7:19 AM, "karthikrk" <karthi_bbb@yahoo.co.in> wrote:

> Hi All,
>
> We are facing strange issue in one of our customer place.
>
> We are using ActiveMQ v 5.11.1
>
> Our broker uri in the 'active.xml' file is as below:-
>
> /<"ssl://
> 0.0.0.0:50020?maximumConnections=10000&wireformat.maxFrameSize=104857600
> ">/
>
> Our client side uri is as below:-
>
> /ConnectionFactory connectionFactory = new
>
> ActiveMQConnectionFactory("ssl://queueIpAddress:queuePortNumber?wireFormat.cacheEnabled=false&wireFormat.tightEncodingEnabled=true&wireFormat.maxInactivityDuration=30000")
>
> connection = connectionFactory.createConnection()/
>
> The 'InactivityMonitor' is working as expected. But some times we have
> observed that the below message in the log file
>
> 2015-12-10 16:12:10,410 [DEBUG] (InactivityMonitor) – 0 ms elapsed since
> last write check.
> 2015-12-10 16:12:10,410 [DEBUG] (InactivityMonitor) – 0 ms elapsed since
> last write check.
> 2015-12-10 16:12:10,410 [DEBUG] (InactivityMonitor) – 0 ms elapsed since
> last write check.
> 2015-12-10 16:12:10,410 [DEBUG] (InactivityMonitor) – 0 ms elapsed since
> last write check.
> 2015-12-10 16:12:10,411 [DEBUG] (InactivityMonitor) – 1 ms elapsed since
> last write check.
> 2015-12-10 16:12:10,412 [DEBUG] (InactivityMonitor) – 2 ms elapsed since
> last write check.
> 2015-12-10 16:12:10,412 [DEBUG] (InactivityMonitor) – 1 ms elapsed since
> last write check.
> 2015-12-10 16:12:10,412 [DEBUG] (InactivityMonitor) – 0 ms elapsed since
> last write check.
> 2015-12-10 16:12:10,412 [DEBUG] (InactivityMonitor) – 0 ms elapsed since
> last write check.
> 2015-12-10 16:12:10,412 [DEBUG] (InactivityMonitor) – 0 ms elapsed since
> last write check.
> 2015-12-10 16:12:10,412 [DEBUG] (InactivityMonitor) – 0 ms elapsed since
> last write check.
> 2015-12-10 16:12:10,412 [DEBUG] (InactivityMonitor) – 0 ms elapsed since
> last write check..
>
> The above message is printed continuously in the log file and the log file
> grows very fast within few seconds. We want to understand in what scenario
> this will happen?
>
> *At the same time we have observed that the bandwidth usage is very high in
> the network during this time.*
>
> We did not find any clue why suddenly happening like this and this is very
> critical for us to resolve.This issue is happening very rarely but the
> impact is very high because of high bandwidth usage.
>
>
> Thanks in advance!!
>
> --Karthik
>
>
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-InactivityMonitor-Weird-Issue-tp4706558.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message