JBoss MQ in JBoss 5.1.0?

[andreas_back]

Hello!

The following facts are well known:

• JBoss MQ is the default messaging server up to JBoss 4.2.3.
• JBoss Messaging is the default messaging server in JBoss 5.1.0.
• HornetQ is the default messaging server from JBoss 6.0 M3 onwards and can be used with JBoss 5.1.0.

But is it possible to use JBoss MQ with JBoss 5.1.0 and which steps are necessary to make JBoss MQ running under JBoss 5.1.0?

Thanks for any help.

Greetings

Andreas

[andreas_back]

Hello!

The release notes for JBoss 5.0 state: "JBossMQ has been removed from the distribution and is no longer supported in AS5. JBoss Messaging Service is now the default JMS provider."

Does this imply that it is technically really no option to use JBossMQ under JBoss 5.1.0? Or is it just not supported?

Well, to some extend, JBoss 5.1.0.GA is not supported either.

This would imply that we have to change some of our application logic while migrating to JBoss 5.1.0 because JBoss MQ and JBoss Messaging are behaving differently in the case of a client crash, see https://community.jboss.org/thread/151962

Greetings,

Andreas

[henk53]

Although I'm not specifically interested in using JBoss MQ in JBoss 5.1.0, I am trying to understand how all these different JMS providers and JCA connection factories work, so I'm interested in the answer to this as well.

[emrehe]

yes, i am asking the same question too, but no answers till now

[wdfink]

Hi Andreas,

to use JBossMQ will have also other impacts, it use the old TxManager. It will be a difficult part to use in JB5.1 because of TxHandling.

As I know your application a bit ;-) I recommend to spend the effort for the migration to JBM, it will also good to use only EJB standard this will make the further migration to Hornet easy.

Also JBM is better for cluster and failover.

[emrehe]

does JBM mean JBoss Messaging?

[andreas_back]

Hello Wolf-Dieter,

you are quite active on the forum!

Of course we migrated to JBoss Messaging, in the first step. But, since the application has really slow consumers - as you might remember - and JBoss Messaging has not the possiblity to set the client window size to 0, we were forced to migrate to HornetQ.

Let me put it in this words, we had the opportunity to help to improve the quality of HornetQ ...

But we are now quite satisfied with HornetQ and will go productive with it!

With best regards,

Andreas

[wdfink]

Yes indeed, common abbreviation.

[emrehe]

Wolf-Dieter, thanks for your answer!

do you have any guide materials about migration from jbossmq to jboss messaging?

[emrehe]

Andreas,

how about the answer of your question: "Does this imply that it is technically really no option to use JBossMQ under JBoss 5.1.0? Or is it just not supported?"

is it possible to configure jbossmq on jboss 5.1, like i copy the lib from jboss 4.0.3 to jboss 5.1?

[wdfink]

No,

but is was simple, internal access must only JEE conform.

We use SpyTopic because we run clustered and an access to Topic at the node where the MQ-singleton is not started wll fail.

This reference to *.mq.*.Spy* classes will fail during compile if you use the JBoss 5.1 jars for compiler.

Also you have to do a little configuration for JBM.

And you have to set the unique JMS ServerPeerId via command line option for each instance.

[andreas_back]

Hello emre he!

The point is that I still can not answer the question that you have quoted.

But if you look at it from a practical point of view using a GA version does imply that there is no support contract and therefore no one who is payed for answering a specific question.

And if there is a project with a strict timeline then from a practical point of view

*      not knowing if something is possible or not

is similar to

*     not knowing actually how to do it.

So from a practical point of view for the project that has been mentioned it was simply not a way to go because

*          I could not find out how to do it (in a resonable timeframe)

*          and nobody told me how to do it.

Or to put it simple: To use JBossMQ under JBoss 5.1.0.GA is simply not supported by

*     a tutorial,

*     a documentation,

*     even an automatic script that installs it

With best regards,

Andreas

[andreas_back]

Hello emre he,

yes, the migration from JBossMQ to JBoss Messaging is simple, but double check that JBoss Messaging really satisfies your requirements. There are subtil differences, one for the slow consumers has already mentioned by me.

0therwise you might prefer a direct migration to HornetQ. But for HornetQ you shall have a close look at the user forum/Jira to see if some of the minor bugs that are discussed there might affect your application.

Well, or simpy use a supported version from jboss.com ...

With best regards,

Andreas

[emrehe]

Thanks Andreas,

Yes as you said i have not found any solid proof to prove if we can apply jbossmq on jboss 5.1.

i will try to migrate it to jboss messaging.

with the perspective request, i can only use jboss 5.1 not jboss 6.x :-( so i am afraid i can not research the HornetQ.

but as you said: "one for the slow consumers has already mentioned by me.", does that mean jboss messaging has the potential performance issue at server side?

Best regards,

Emre

[andreas_back]

Hello emre he,

have a look at

http://community.jboss.org/message/439661#439661

It just says the JBoss Messaging always prefetches one message into the client. Normally, this does not matter.

But if you have jobs that have a long processing time and have several consumers on the same queue then some consumers could be idle and the prefetched message in one client still waits for the long job to finish. In this case there are obviously long wainting times and a poor utilization of the system.

HornetQ (as ActiveMQ) has a solution to this. JBossMQ does not have the problem at all because it does no prefetching.

With best regards,

Andreas