e good to know if there's any solution to this. Was thinking
> of upgrading to 5.10 but it seems the same problem happens there.
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Broker-Hangs-after-some-time-or-does-nothing-tp4677506p4683707.h
there.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Broker-Hangs-after-some-time-or-does-nothing-tp4677506p4683707.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
ing to do with
> network connections? Any help would be appreciated.
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Broker-Hangs-after-some-time-or-does-nothing-tp4677506p4681166.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
from prod. I
am not able to reproduce this in QA or DEV. Is this something to do with
network connections? Any help would be appreciated.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Broker-Hangs-after-some-time-or-does-nothing-tp4677506p4681166.html
Sent from the ActiveMQ
;>>> so
>>>> >> that
>>>> >> consumption never blocks due to producer-flow-control. In that
>>>> >> scenario,
>>>> >> deadlocks won't happen because consumers can always consume.
>>>> >>
>>>> &
second. Actually, more complicated possibilities
>>> exist
>>> >> as
>>> >> well.
>>> >>
>>> >> Your best bet is to never consume and produce on the same connection
>>> so
>>> >> that
>>> >> consumpt
> consumption never blocks due to producer-flow-control. In that
>> >> scenario,
>> >> deadlocks won't happen because consumers can always consume.
>> >>
>> >> Back to stack traces - if the consuming threads are blocked waiting
to
> >> obtain a lock while producing threads hold that lock, that could
> >> indicate
> >> the problem.
> >>
> >> Anyway, slow consumption is quite often the cause of broker hangs, so
> >> looking for slow consumption and understanding speedi
umption (or
>> slowing production) is important. If the broker JVM becomes completely
>> unresponsive, try connecting jconsole or visualvm before the broker
>> hangs
>> and then watch memory. If the JVM is running out of Heap or Permgen
>> space,
>> that would explain the hung b
> and then watch memory. If the JVM is running out of Heap or Permgen space,
> that would explain the hung broker.
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Broker-Hangs-after-some-time-or-does-nothing-tp4677506p4677656.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
broker JVM becomes completely
unresponsive, try connecting jconsole or visualvm before the broker hangs
and then watch memory. If the JVM is running out of Heap or Permgen space,
that would explain the hung broker.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Broker-Hangs-
irag
> >> >
> >> >
> >> > On Wed, Feb 5, 2014 at 8:07 PM, artnaseef wrote:
> >> >
> >> >> There are many things to check.
> >> >>
>
mean
>> the
>> >> broker or something else?
>> >>
>> >> Troubleshooting steps:
>> >> * When flow stops, check the broker for active client connections via
>> >> the
>> >> webconsole or JMX.
>> >> * Check consumer a
ransport is being used, be sure to use a
> >> ConnectionListener and TransportListener to receive notifications of
> >> lost
> >> connection to the broker. Note that you should get a log message if the
> >> failover transport loses connection, so this may not be necessary.
t; lost
>> connection to the broker. Note that you should get a log message if the
>> failover transport loses connection, so this may not be necessary.
>> * Check broker JVM memory (especially Heap and PermGen)
>>
>> Also, if the broker is running out of memory due t
ry due to having too many
> messages
> (i.e. slow consumer problem), that could cause the broker to stop
> functioning.
>
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Broker-Hangs-after-some-time-or-does-nothing-tp4677506p4677512.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
Ah, it's possible to change the subject. Got it.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Broker-Hangs-after-some-time-or-does-nothing-tp4677506p4677514.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
context:
http://activemq.2283324.n4.nabble.com/Broker-Hangs-after-some-time-or-does-nothing-tp4677506p4677512.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
I am using Activemq-5.10.SNAPSHOT and implementing with replicated leveldb.
After few messages consumer stop processing messages. Messages just stay on
queue. nothing happens. Client cannot send anymore messges. I dont see any
exception on client side. I dont see any exception on server logs.
I s
19 matches
Mail list logo
