Using JBoss with SonicMQ as JMS Server

[edelarosa]

Hi,

Has anyone tried configuring JBoss 3.2.3 with SonicMQ V5 as JMS Server?
I plan to have my MDB (EARed) contained and run by JBoss but using SonicMQ
as the JMS Server.

I just can't drop JBoss because of proven performance, but the speed and volume
of messages (5 million/day) that my application requires couldn't live with
JBossMQ alone. I always got stuck with JMS Exception, particularly with
OutOfMemoryException, when the amount of messages reach 150K.

It would be great if someone could provide me hint on how to set them both
(JBossMQ+SonicMQ) to allow load balancing most especially during peak hour.

Thanks you.

[adrian.brock]

It's strange but when I search on google the top two links look very useful to me.
http://www.google.com/search?hl=en&ie=UTF-8&oe=UTF-8&q=sonicmq+jboss&btnG=Google+Search
Maybe you didn't find them helpful?

Regards,
Adrian

[adrian.brock]

You probably put the same amount of effort into configuring jbossmq?

I've seen jbossmq cope with a little under 1 million persistent messages an hour.
Of course it depends upon the size of your messages.

Regards,
Adrian

[edelarosa]

Hi Adrian,

It's strange but when I search on google the top two links look very useful to me.
http://www.google.com/search?hl=en&ie=UTF-8&oe=UTF-8&q=sonicmq+jboss&btnG=Google+Search
Maybe you didn't find them helpful?

Regards,
Adrian

Actually, I'm into a process of evaluating different JMS provider to coulpe with JBoss
and I probably made my inquiry a bit quick of posting without Googling. So, thanks a
lot for the above link, I believe they'll be very useful to me too.

You probably put the same amount of effort into configuring jbossmq?

I've seen jbossmq cope with a little under 1 million persistent messages an hour.
Of course it depends upon the size of your messages.

Regars,
Ardian

Yup, you're right. We expect an ObjectMessage with Hashtable in it, among others.
Surely, the message varies with unpredictable size depending on the contents of
the Hashtable generated by different transactions. This could be one leading to
JMS enigma when bombarded with volume of messages in a very short period of
time.

Regards,

Eduardo Dela Rosa

[ivelin.ivanov]

You might find these links useful as well:
http://theserverside.com/news/thread.tss?thread_id=24614
http://jboss.org/wiki/Wiki.jsp?page=JBossMQ

Ivelin