JMS in websphere 8.0 - V5 default messaging provider vs WebSphere MQ messaging provider

Question

I want to implement a system to add tasks to a queue and then process them later. Since JMS is made for such type of requirements I'd like to use it. I have websphere 8 and I don't know which JMS provider should I use V5 default messaging provider or WebSphere MQ messaging provider .

My requirement is simple so I plan on having the Producer and Consumer in same EAR .

Also, Is JMS for my requirement is an overkill?

Answer 1

You should use Default messaging provider , the one you didn't mention.

The WebSphere MQ provider is used when you have external WebSphere MQ server, and V5 default messaging provider is used only while migrating from very old WebSphere version.

JMS is usually used when you want to 'queue` some processing, not necessary postpone it in time. As you usually listen(wait) for incoming messages for example using MDB, and process them automatically once they are available. So in your case once you put message in the queue, it would be picked up and processed right away, unless you will have some waiting logic, and get(read) the message from the queue on demand, not automatically.

If you want to schedule tasks, better combination might be database and timer beans rather than JMS. But again, depends on requirements, JMS is also fine.