| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Strange Subscriber application problem |
« View previous topic :: View next topic » |
| Author |
Message
|
| cadenza |
 Posted: Tue Jun 28, 2005 11:17 pm Post subject: Strange Subscriber application problem |
 |
|
Apprentice
Joined: 01 Jun 2004
Posts: 48
|
Hi,
A subscriber application is picking up 3 different types of messages from a single queue.
Msg A: MQRFH format
Frequency of arrival: HIGH
Msg B: MQRFH format
Frequency of arrival: One per day
Msg C: MQRFH2 format
Frequency of arrival: Medium
The Message Delivery Sequence of the queue is set as Priority.
The downstream application team has reported that while processing Msg A there is no problem observed. However once the application receives a Msg C, it cannot process any further messages of type A.
It has been observed that the messages of type A accumulate in the queue itself after they process any messages of type C.
It is only known that the downstream application uses Java-MQ for connecting to the queue.
Any ideas??? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Jun 29, 2005 2:01 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
What do they do with message type C?
Is it a poison message for them ? ex:
process msg type B
process msg type C -- rollback
process next msg -- type C (see rollback) -- rollback
process next msg -- type C (see rollback) -- rollback...
and so on.
So they never get to the next message as they reprocess message C over and over again...
Application logic error.
Enjoy  |
|
| Back to top |
|
|
| bower5932 |
| Posted: Wed Jun 29, 2005 4:00 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| If it is being rolled back, you should be able to run amqsbcg against the queue and see the backout count increasing. |
|
| Back to top |
|
|
| cadenza |
| Posted: Wed Jun 29, 2005 9:03 pm Post subject: |
|
|
Apprentice
Joined: 01 Jun 2004
Posts: 48
|
Hi,
They are consuming these messages for their own needs.
However the problem has been solved .... it occured because the messages of type A and B had a higher priority value than message C.
When the priority of the messages of type A and B were made to 0 as of C, the subscriber started processing them normally.
Thanks for all your help. |
|
| 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
|
|
|
|
