• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • paul wheaton
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
  • Devaka Cooray
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
  • Himai Minh
Bartenders:

MDB Poison message

 
Ranch Hand
Posts: 80
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all,
What does WebSphere do if a message delivered to an MDB fails multiple times? (i.e. fails more than the maximum retry setting) I assume it must store it somewhere for an admin to look at. Where is this and what tools are available to process / review them?
I want to use a MDB to process credit card orders and don't want to worry about lost messages. Of course I will use CMT s.t. if the MDB fails the message will be returned to the queue, but I am worried about poisoned messages.
Thanks!
--Dave.
 
Ranch Hand
Posts: 118
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi.
My experience on this is dependant on how they fail.
If you throw an exception during your processing of the messages, the WAS will likely just shut down the listener port on the server.
This will leave the messages on the queue and WAS will attempt to process them once again when you open up the listener port.
/Peter
 
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Peter,

We are developing an application and we are facing a problem. I am using using WAS 5.1 and MQ simulator. I am sending email messages using JMS. I have configured the Queue and Queue connection factory as well as Listener port. Most of the time the code works fine but sometime the listener get stopped and we have to start it again.

We do not want to start out Listener again and again to send message. On java ranch you have suggested that exception in code could make Listener port stop working.

My onMessage method is as follows:-



It is using emailutility class for sending message. Here what changed I should do for not stopping Listener port?


with regards
Jai
[ December 01, 2004: Message edited by: jai deep ]
 
reply
    Bookmark Topic Watch Topic
  • New Topic