| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Websphere Default Messaging problem - MDB is not triggered |
« View previous topic :: View next topic » |
| Author |
Message
|
| kaustav_chakraborty |
 Posted: Wed Jul 30, 2008 1:16 pm Post subject: Websphere Default Messaging problem - MDB is not triggered |
 |
|
Newbie
Joined: 30 Jul 2008
Posts: 2
|
Hi,
Our client is having multiple applications where the message is transferred asynchronously using Websphere 6 Default Messaging provider. It works fine most of the time, but very recently we have found that some of the messages put into the queue are not triggering the MDB. Most of the cases we have found that 2 messages are sent into the queue at a time & one of them are being able to trigger MDB onMessage() & getting processed successfully while the other one are not triggering MDB at all & staying in the queue for infinite time. May be the message is staying in the queue because the message expiry interval is set to infinite. In the run time the message is seen in the queue. At the day end if we restart the server then those messages are coming out & triggering the MDB successfully. We are not at all being able to understand why this problem is taking place in the queue. We are feeling so much helpless & after all we have to resolve the issue soon because client is asking for it everyday. Please anyone help me in this regard.
[NB : In the queue setup, we are using one Bus, 3 queue associated with it, 1 connection factory, 3 Activation Spec. Also we have noticed that when this problem is happening, the system is not having huge traffic at that point of time, so it is not the case of memory shortage also]
Thanks,
Kaustav |
|
| Back to top |
|
 |
| kaustav_chakraborty |
| Posted: Wed Jul 30, 2008 1:24 pm Post subject: Websphere Default Messaging problem - MDB is not triggered |
|
|
Newbie
Joined: 30 Jul 2008
Posts: 2
|
| Just to add with the earlier post, our operating system is Sun Solaris, & java version is 1.4. If you need to know the queue configuration settings or any other settings then I can provide that. |
|
| Back to top |
|
|
| Jinny |
| Posted: Tue Aug 05, 2008 11:25 pm Post subject: |
|
|
Novice
Joined: 30 Jul 2008
Posts: 16
|
Check queue status that IPPROCS attribute.
if another application open the queue, trigger event did not working.
And , show me the Q attribute, and queue status.
then We help you more easily. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Aug 06, 2008 8:12 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Make sure as well that the message is in a gettable state (committed). Browse the message using some tool and make sure you disconnect the queue. Make sure your pool size is big enough. For every MDB on a queue you need max instances of MDB + 1 connections...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
