| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Consumer issue processing the msgs in sequence |
« View previous topic :: View next topic » |
| Author |
Message
|
| mqbrks |
 Posted: Wed Jul 12, 2017 10:40 am Post subject: Consumer issue processing the msgs in sequence |
 |
|
Voyager
Joined: 17 Jan 2012
Posts: 75
|
Hi All,
I am not sure if this is the right forum that knows a possible solution for current problem.
We have a application where the Source would be sending the files and IIB would be processing those files and sending the msgs to Target Queue.
The Target Application (MDB running on Weblogic) consumes the msgs on Queue on the logical sequence . Due to some organization changes we have cloning of the application and the new target application is pointing to new queues like IIB.
The only difference from the old and new MDB (Message Driven Bean on Weblogic) is the .bindings
The target application (previous one) consumes all the msgs in the group on queue.
where was the target application (new one) consumes just the first message in the group, even though the messages exist on queue, it complains saying
No new message with seqNumber=2 and times out after a min.
Any insights would be really appreciated. If you have any additional questions, pls let me know. |
|
| Back to top |
|
 |
| mqbrks |
| Posted: Thu Jul 13, 2017 4:24 am Post subject: |
|
|
Voyager
Joined: 17 Jan 2012
Posts: 75
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jul 13, 2017 5:17 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You said that the behavior is different with different .bindings files.
That seems odd to me. But I haven't done any troubleshooting on your environment.
Perhaps the remainder of the messages in the group are not available yet, or have not been committed, or are arriving out of sequence, such that the second message takes longer than 60 seconds to arrive.
But again, I haven't done any troubleshooting on your environment.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| mqbrks |
| Posted: Thu Jul 13, 2017 6:37 am Post subject: |
|
|
Voyager
Joined: 17 Jan 2012
Posts: 75
|
Thank you mqjeff for your reply! Here are the details, if it gives a better idea.
Applications are being cloned as part of Organization Change.
This is the whole route.
Source - IIB -> Local IIB QMgr -> Farm Qmgr - > Target Application.
Existing Application/Route
IIB Version 10.0.0.3
QMgr Version - 8.0.0.4
Farm Qmgr Version - 7.5
The target application is consuming all the messages in the above scenario.
Cloned Application
Source - IIB -> Local IIB QMgr -> Farm Qmgr - > Target Application.
Old Application
IIB Version 10.0.0.8
QMgr Version - 8.0.0.4
Farm Qmgr Version - 8.0.0.4
The messages are stuck on the queues and not able to be consumed by application.
Again the same messages if exported to a file and placed on same queue, the consumer is able to processes all the messages.
Do you think the way of putting the messages differs or the MQ Version on Farm could create a problem ? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jul 13, 2017 6:53 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
The biggest difference is in the version / release of your farm queue managers.
This may not be trivial as now you have authinfo and channel auth records in the mix....
Have you thought about checking the qmgr log for errors??
Have fun 
_________________
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
|
|
|
|
