activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Commented] (AMQ-4417) Unbalanced usage Exception in Valve.decrement
Date Mon, 01 Apr 2013 14:13:16 GMT


Timothy Bish commented on AMQ-4417:

5.4.2 is quite old, perhaps move to a newer version as the VMTransport among other things
has had much done to improve it since then.
> Unbalanced usage Exception in Valve.decrement
> ---------------------------------------------
>                 Key: AMQ-4417
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.4.2
>            Reporter: Vincent Baudry
> One of our production node running ActiveMQ shows a permanent error log every milisecond
> Exception in thread "VMTransport" java.lang.IllegalStateException: Unbalanced usage:
> at org.apache.activemq.thread.Valve.decrement( 
> at org.apache.activemq.transport.vm.VMTransport.iterate( 
> at org.apache.activemq.thread.PooledTaskRunner.runTask( 
> at org.apache.activemq.thread.PooledTaskRunner$ 
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(

> at java.util.concurrent.ThreadPoolExecutor$ 
> at 
> The value behind unbalanced usage keeping moving but globally getting decremented over
> We are for now unable to see the side effect on the app, which is still running, except
the CPU usage going through the roof, probably because of this constant logging.
> As the log doesn't have a root in our code, it's hard to understand what's gone wrong
initially, and if it might be linked to our usage of ActiveMQ.
> I've read the source code but can't understand why the valve usage int has gone initially
negative. But it seems to me that when it has gone once negative, the only way to have the
broker work fine again is to restart the server to reinitialize this value (as all subsequent
iterate() / increment() calls will throw/catch an exception due to usage negative value and
finally hit the decrement() method ).
> As we don't have a scenario to reproduce the bug, I don't expect you to find a solution
to it right now, but I wanted to file it in case anyone encounter the same bug and has the
way to reproduce it.
> And also I would be glad to have answers to the following questions, if possible :
> - Do you have any clues concerning this issue ? Things I could investigate further ?
> - Doest it seem normal to you that my exception log starts in a then plugged
to the PooledTaskRunner mechanism ?
> - What kind of ActiveMQ tasks run using this PooledTaskRunner / VmTransport.iterate()
mechanism ? All AMQ tasks ? Only enqueueing/dequeueing tasks ? Internal tasks ?
> - Is it possible that some enqueueing/dequeueing tasks still work fine when in this state
? Is this faulty valve not shared by all producers connecting to the broker via vm:// ?
> To give you a little technical context, we use this broker with a spring producer using
Spring JmsTemplate through vm://transport

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message