This week's book giveaway is in the Java 8 forum.
We're giving away four copies of Java 8 in Action and have Raoul-Gabriel Urma, Mario Fusco, and Alan Mycroft on-line!
See this thread for details.
The moose likes Websphere and the fly likes Messaging issues in Websphere Application Server 7.0.0 - onMessage() called several times Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Java 8 in Action this week in the Java 8 forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "Messaging issues in Websphere Application Server 7.0.0 - onMessage() called several times" Watch "Messaging issues in Websphere Application Server 7.0.0 - onMessage() called several times" New topic
Author

Messaging issues in Websphere Application Server 7.0.0 - onMessage() called several times

Kumar Gaurav
Ranch Hand

Joined: Apr 08, 2008
Posts: 108
Hi,

We are working with MDBs in EJB3 on WAS 7.0.0.

We have messaging requirements for which we have configured 4 Queues. We are using Default Messaging Provider embedded within WAS and used Activation Specifications and JCA Adapter for the same.

The issue with the configured MDB is , for each message sent by the application the corresponding MDB is spawned 5 times and therefore the corresponding job is triggered 5 times. i.e. I can see the onMessage() is called 5 times in the logs.Though the message is sent only once.

We have the default value set for the “failure retry count” property which is 5. When we change this to 1 , then only one MDB is spawned and the job runs only once and is completed successfully. But we want to keep the “failure retry count” value 5 to handle failover.

Any pointers would be of great help.


Thanks.

Regards,
Gaurav
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Messaging issues in Websphere Application Server 7.0.0 - onMessage() called several times
 
Similar Threads
EJB timeout issue
Strange behaviour of MDB and EJB
How to recover input message from JMS queue after transaction rolled back
How to kick start the DLQ
Container Managed Transactions with an MDB