aspose file tools
The moose likes EJB and other Java EE Technologies and the fly likes Messaging solution for parallel processing Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login


Win a copy of The Mikado Method this week in the Agile and other Processes forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Reply Bookmark "Messaging solution for parallel processing" Watch "Messaging solution for parallel processing" New topic
Author

Messaging solution for parallel processing

Kedar Dixit
Ranch Hand

Joined: Apr 22, 2003
Posts: 43
Hi,
I am looking for a solution to implement a messaging solution for asynchronous processing of rules.

I initially thought of using JMS, but a Proof Of Concept revealed that only sequential processing is possible with single session listener. The requirement is to have parallel processing.
Is there a way to configure this in JMS?

As a solution to this I also thought of using Message Driven Beans (MDBs). However, there are issues of duplicate messages getting processed at the same time leading to locking/concurrency issues. We need to keep a track of what is getting currently processed so that we can schedule the processing of duplicate message.

Could someone please suggest best solutions for the above scenario? Some good pointers/sample code will help me immensely. Please respond at your earliest convenience.

Thanks,
[ February 29, 2008: Message edited by: Bear Bibeault ]

Sun Certified Programmer for Java 1.4<br />SCWCD 1.4 (in progress)<br /> <br />Life is a movie and you are the star. Give it a happy ending!
Kedar Dixit
Ranch Hand

Joined: Apr 22, 2003
Posts: 43
Anyone? Any help would be really appreciated!
Thanks,
Kedar
Jesus Angeles
Ranch Hand

Joined: Feb 26, 2005
Posts: 2036
Originally posted by Kedar Dixit:


As a solution to this I also thought of using Message Driven Beans (MDBs). However, there are issues of duplicate messages getting processed at the same time leading to locking/concurrency issues. We need to keep a track of what is getting currently processed so that we can schedule the processing of duplicate message.



What do you mean by 'duplicate messages'? There is a possibility that you will send duplicate messages? Or you are worried that 2 MDBs will process a single message?
 
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to run our stuff on 16 servers instead of 3.
 
subject: Messaging solution for parallel processing
 
Similar Threads
WebShpere MQ : JMS API Vs IBM Message Queue Interface
Distributed processing and workflow pattern
JMS queries
Message driven bean instance pool and concurrent proceesing
MDB one at a time