| Author |
Message
|
| mrgate |
 Posted: Mon Jun 29, 2009 5:21 am Post subject: logs for message flows |
 |
|
Centurion
Joined: 28 Feb 2007
Posts: 141
Location: India
|
Hi All,
Currently we are working on Message Broker V6.1.4, Websphere MQ V7.0 on AIX 5.3.
We have a message flow deployed on production environment.
1) Ours message flows functionality is retrieve from queue, do necessary computation using compute node and insert into database.
2) There is an exception handling mechanism in such a way that it will retrieve necessary error and write to error queue and throw error using throw node so that message will be sent to mqinput node and message will be written to backout queue. so, everytime when a message was retrieved from input, if error occurs, it will be sent to both error queue and backout queue.
3) Two days back, there was a situation in such a way that message was sent to backout queue and message was not sent to error queue. We have one reason that when error occurs in error handling path, it will be sent to backout queue and not to error queue.
4) We can have flow level trace using mqsichangetrace,mqsireadlog and mqsiformatlog commands, but this happened before two days and customer is asking for root cause today.
5) May I know whether any solution is there for getting root cause other than trace settings. Is there any logs for getting detailed information of message flow that happened before two days.
_________________
MQSeries terrorist |
|
| Back to top |
|
 |
| WMBDEV1 |
| Posted: Mon Jun 29, 2009 6:10 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
| It depends how fatal the error was. There may be clues in system logs which i'm guessing here may be something along the lines of /var/adm/messages so someone please feel free to correct me. |
|
| Back to top |
|
|
| gs |
| Posted: Mon Jun 29, 2009 1:14 pm Post subject: |
|
|
Master
Joined: 31 May 2007
Posts: 254
Location: Sweden
|
| WMBDEV1 wrote: |
| It depends how fatal the error was. There may be clues in system logs which i'm guessing here may be something along the lines of /var/adm/messages so someone please feel free to correct me. |
I second that. The errors should have been output to the syslog. You could also look at the execution group's stdout/stderr. |
|
| Back to top |
|
|
| mrgate |
| Posted: Mon Jun 29, 2009 11:00 pm Post subject: |
|
|
Centurion
Joined: 28 Feb 2007
Posts: 141
Location: India
|
| gs wrote: |
| I second that. The errors should have been output to the syslog. You could also look at the execution group's stdout/stderr. |
Hi, may I know the exact path of execution group's stdout/stderr.
_________________
MQSeries terrorist |
|
| Back to top |
|
|
| gs |
| Posted: Mon Jun 29, 2009 11:42 pm Post subject: |
|
|
Master
Joined: 31 May 2007
Posts: 254
Location: Sweden
|
| mrgate wrote: |
| Hi, may I know the exact path of execution group's stdout/stderr. |
Have you tried "stdout stderr" as a search query in the wmb infocenter? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jun 30, 2009 4:54 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It's entirely possible, and not too hard, to build a message flow that will never log anything, no matter what goes wrong.
Ignore standard error/standard out.
Revisit the design of your flow, and ensure that you take steps to log errors, or at least take steps not to prevent exceptions from reaching the input node. |
|
| Back to top |
|
|
|
|
