| Author |
Message
|
| Inisah |
 Posted: Thu May 29, 2014 8:20 am Post subject: What does uncommitted message in input queue of a flow mean? |
 |
|
Apprentice
Joined: 21 Mar 2014
Posts: 44
|
We see uncommitted messages in the input queue of a flow. IPPROCS of the flow is 1 and we see that the flow is up and running. How do we further check and resolve what the issue is?
MQ Ver : 7.5.0.2
MB : 7 |
|
| Back to top |
|
 |
| zpat |
| Posted: Thu May 29, 2014 9:30 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Sounds like your flow is not committing the message MQGET and is hanging or waiting for something else.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| Inisah |
| Posted: Thu May 29, 2014 9:35 am Post subject: |
|
|
Apprentice
Joined: 21 Mar 2014
Posts: 44
|
| How do we check if any issue with the flow. This flow was already existing and not changed since years |
|
| Back to top |
|
|
| pvnkumar |
| Posted: Wed Jun 11, 2014 10:30 pm Post subject: |
|
|
Novice
Joined: 26 May 2008
Posts: 16
|
check your syslog which should show some information if something wrong with the flow.
you can also stop and start your flow and verify if it picks up messages in the queue.
if issue still persists, you can enable a trace and finoud out whats happening within the flow. |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Jun 11, 2014 11:45 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
It means the flow has MQinput node transaction mode = yes (or auto with persistent message) but is not committing properly.
Does the flow wait for anything (like a web service response)? Does it roll back the message (check the DLQ)?
Calling Java modules (or anything non-WMB) is a good way to hang a flow.
Try removing the flow's calls to external code or external systems and see if the flow now works, then replace them one at a time until it stops working - then fix it.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
|
|
