You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Monteiro Jean-Louis <je...@atosorigin.com> on 2008/08/27 14:03:56 UTC

ActiveMQ bottleneck

Hi again,


I've done some tests with MDB and ActiveMQ.

I identified a bottleneck on ActiveMQ. The class is org.apache.activemq.management.CountStatisticImpl
As you can see, this class is used for JMX statistics. But, even if management system property is not set, this class is used.

Some methods of this class call "updateSampleTime();"
Here is the definition of this method:
protected synchronized void updateSampleTime() {
   lastSampleTime = System.currentTimeMillis();
}

First it's synchonized and then it does a native (system) call which is very bad for performances (system CPU usage).
I've checked trunk (5.x) version and it seems to be patched.

So what can we do ?
--> go to 5.x version ?
--> add a patch to the current 4.1.1 version ?

Kind regards,
Jean-Louis MONTEIRO

________________________________

Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? du groupe Atos Origin ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Re: ActiveMQ bottleneck

Posted by Jean-Louis MONTEIRO <je...@atosorigin.com>.
David,

Looks like only a 4.1.2 is available on the SVN repository. Unfortunately,
no fix has been applied.
I will look for a 4.1.3 from JIRA and check it.

Regards,
Jean-Louis


David Blevins wrote:
> 
> 
> On Aug 27, 2008, at 5:03 AM, Monteiro Jean-Louis wrote:
> 
> Looks like there was a 4.1.2 released in April, wonder if that still  
> has it.
> 
> Also looks like there's a 4.1.3 version in their JIRA so if it is we  
> should definitely get a patch for that.
> 
> We could try the upgrade route but I'm not sure of the Java EE 5 TCK  
> status of 5.x.
> 
> 
> -David
> 
> 
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/ActiveMQ-bottleneck-tp19183913p19250032.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.


Re: ActiveMQ bottleneck

Posted by David Blevins <da...@visi.com>.
On Aug 27, 2008, at 5:03 AM, Monteiro Jean-Louis wrote:

> Hi again,
>
>
> I've done some tests with MDB and ActiveMQ.
>
> I identified a bottleneck on ActiveMQ. The class is  
> org.apache.activemq.management.CountStatisticImpl
> As you can see, this class is used for JMX statistics. But, even if  
> management system property is not set, this class is used.
>
> Some methods of this class call "updateSampleTime();"
> Here is the definition of this method:
> protected synchronized void updateSampleTime() {
>   lastSampleTime = System.currentTimeMillis();
> }
>
> First it's synchonized and then it does a native (system) call which  
> is very bad for performances (system CPU usage).
> I've checked trunk (5.x) version and it seems to be patched.
>
> So what can we do ?
> --> go to 5.x version ?
> --> add a patch to the current 4.1.1 version ?
>

Looks like there was a 4.1.2 released in April, wonder if that still  
has it.

Also looks like there's a 4.1.3 version in their JIRA so if it is we  
should definitely get a patch for that.

We could try the upgrade route but I'm not sure of the Java EE 5 TCK  
status of 5.x.


-David