Thanks for bringing this up.
I'll let the MQ and performance people answer this, but I think I like
the conclusion:
"When overloaded with messages, JBoss MQ and JBoss messaging suffered
failures that brought the whole application server down. OpenMQ, in
contrast, prevented the client from sending any more messages once the
message queue reached a size limit. This behaviour protected the
application server from failure."
-Alexis
On Jul 23, 2008, at 14:34, Legolas wood wrote:
> Hi
> Today I saw something interesting which shows that Glassfish MQ is the
> slowest MQ when compared with Jboss MQ and Jboss messaging.
> http://www.c2b2.co.uk/iPoint/ipoint?SelectedPage=69&110ArticleID=17
>
> Maybe you find it interesting too.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>