| Author |
Message
|
| kash3338 |
 Posted: Wed Jun 08, 2011 7:13 am Post subject: Throw error to Syslog with TimeoutNotification |
 |
|
Shaman
Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India
|
Hi,
We have a flow which has Timeout Notification node set to Automatic mode. This flow is used to poll a DB on regular intervals. With the Timeout Notification node, the error handling functionality is like, if the catch terminal is not connected, the error is written to syslog and the node keeps retrying.
We do not want this retry to occurm but we want the error to be trown to the syslog. How can this scenario be handled? We stopped the retry by connecting the catch terminal, but then the error is not trown to syslog. But we need the error in syslog, but without the retry.
Is there any better solution to acheive this?
Message Broker version: 6.1 |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Wed Jun 08, 2011 8:41 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Put a TryCatch node after the Timer node and before the compute/DB node?
Then any exception won't be rolled back to the TimerNode.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| kash3338 |
| Posted: Wed Jun 08, 2011 9:30 am Post subject: |
|
|
Shaman
Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India
|
| smdavies99 wrote: |
| Put a TryCatch node after the Timer node and before the compute/DB node? |
Then will I be able to get the error in syslog? My aim is to both stop the retry in the timer node as well as to get the error in syslog. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Jun 08, 2011 9:46 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Connect your normal error handling code to the Catch Terminal of the try-Catch node.
(I am assuming that standard error code will cause an error to appear in the event log)
There are a few what I call prime nodes(1) that exhibit this sort of behaviour in an error case where some nodes would handle the rollback & backout correctly.
The collector node is one such case although I understand that its errant behaviour has been sorted out in the latest fixpacks (6.1.0.9 & 7.0.0.2)
(1) Nodes where a thread starts. eg MQInput SOAPInput JMSInput TimerNode FileInputNode & the second part of the Collector Node. There are more but I hope you get what I'm on about.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| kash3338 |
| Posted: Thu Jun 09, 2011 12:42 am Post subject: |
|
|
Shaman
Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India
|
| smdavies99 wrote: |
Connect your normal error handling code to the Catch Terminal of the try-Catch node.
(I am assuming that standard error code will cause an error to appear in the event log) |
I have a error handling code attached to the catch terminal of the Try-Catch node. But this does not cause the error to appear in syslog. Is there any way i can do this? I need the error to appear in syslog but there should not be any retry. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jun 09, 2011 1:51 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
|
|
