| Author |
Message
|
| Gralgrathor |
 Posted: Mon Jan 30, 2017 8:26 am Post subject: Exception does not trigger SAP Input node failure terminal |
 |
|
Master
Joined: 23 Jul 2009
Posts: 297
|
Tested with IIB 10.0.0.5 and 7 on Windows7 and AIX.
If I receive a message on the SAP Input node, generate an exception, then again generate an exception on the Catch-leg, I expect the retry mechanism on the SAP Input node to be triggered, which is set to Fail, and the input message to be put on the failure terminal of the SAP input node.
However, nothing appears on the failure terminal of the input node, no matter what settings and properties I change.
If I step through the flow using the debugger, the exception on the Output-leg is detected, triggering the message to be put on the Catch-terminal. A compute node on the Catch-leg then does a THROW, and the debugger shows a red exclamation mark on the input node. Stepping forward does not result in a message on the Fail-leg, however, but causes the debugger to start waiting for the next input message.
I've run a couple of system traces, but they don't tell me much more than the user traces and the debugger: an exception is detected in the Catch-leg, and then - nothing.
Does anybody have similar problems with SAP Input nodes? Does anybody have a suggestion for a possible solution, or something I might try to get closer to the cause of the problem?
Thanks in advance!
_________________
A measure of wheat for a penny, and three measures of barley for a penny; and see thou hurt not the oil and the wine. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue Jan 31, 2017 5:19 am Post subject: Re: Exception does not trigger SAP Input node failure termin |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Gralgrathor wrote: |
Tested with IIB 10.0.0.5 and 7 on Windows7 and AIX.
If I receive a message on the SAP Input node, generate an exception, then again generate an exception on the Catch-leg, I expect the retry mechanism on the SAP Input node to be triggered, which is set to Fail, and the input message to be put on the failure terminal of the SAP input node.
However, nothing appears on the failure terminal of the input node, no matter what settings and properties I change.
If I step through the flow using the debugger, the exception on the Output-leg is detected, triggering the message to be put on the Catch-terminal. A compute node on the Catch-leg then does a THROW, and the debugger shows a red exclamation mark on the input node. Stepping forward does not result in a message on the Fail-leg, however, but causes the debugger to start waiting for the next input message.
I've run a couple of system traces, but they don't tell me much more than the user traces and the debugger: an exception is detected in the Catch-leg, and then - nothing.
Does anybody have similar problems with SAP Input nodes? Does anybody have a suggestion for a possible solution, or something I might try to get closer to the cause of the problem?
Thanks in advance! |
Think about how the message on the failure node would work with SAP's message / IDOC system. Check out the status and information on the IDOC in SAP. You'll notice that the IDOC has been marked with an error code for it's status and there might be an error message as you would see in the exception tree.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Gralgrathor |
| Posted: Tue Jan 31, 2017 6:54 am Post subject: Re: Exception does not trigger SAP Input node failure termin |
|
|
Master
Joined: 23 Jul 2009
Posts: 297
|
| fjb_saper wrote: |
| You'll notice that the IDOC has been marked with an error code |
That would have been acceptable. Unfortunately, SAP registers the Idoc as having been successfully delivered to its partner.
_________________
A measure of wheat for a penny, and three measures of barley for a penny; and see thou hurt not the oil and the wine. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jan 31, 2017 7:02 am Post subject: Re: Exception does not trigger SAP Input node failure termin |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Gralgrathor wrote: |
| fjb_saper wrote: |
| You'll notice that the IDOC has been marked with an error code |
That would have been acceptable. Unfortunately, SAP registers the Idoc as having been successfully delivered to its partner. |
what happens if the failure terminal is not linked to anything?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Gralgrathor |
| Posted: Tue Jan 31, 2017 8:12 am Post subject: Re: Exception does not trigger SAP Input node failure termin |
|
|
Master
Joined: 23 Jul 2009
Posts: 297
|
| fjb_saper wrote: |
| what happens if the failure terminal is not linked to anything? |
Same thing.
_________________
A measure of wheat for a penny, and three measures of barley for a penny; and see thou hurt not the oil and the wine. |
|
| Back to top |
|
|
| wietse_de_vries |
| Posted: Wed Feb 01, 2017 3:38 am Post subject: |
|
|
Newbie
Joined: 01 Jul 2009
Posts: 2
|
Calling the failure terminal in the SAP input node works in version 8 of WMB in case of an failure/rollback somewhere down the flow.
Ik have tested this in version 10.0.0.3 and it works. Now with version 10.0.0.5 is doesn't work.
Why a Failure terminal if "by deisgn" it is never called?
This looks like a bug in 10.0.0.5 |
|
| Back to top |
|
|
| Gralgrathor |
| Posted: Wed Feb 01, 2017 3:57 am Post subject: |
|
|
Master
Joined: 23 Jul 2009
Posts: 297
|
| wietse_de_vries wrote: |
| Why a Failure terminal if "by deisgn" it is never called? |
Perhaps for aesthetic reasons?
_________________
A measure of wheat for a penny, and three measures of barley for a penny; and see thou hurt not the oil and the wine. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Feb 01, 2017 5:46 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| wietse_de_vries wrote: |
Calling the failure terminal in the SAP input node works in version 8 of WMB in case of an failure/rollback somewhere down the flow.
Ik have tested this in version 10.0.0.3 and it works. Now with version 10.0.0.5 is doesn't work.
Why a Failure terminal if "by deisgn" it is never called?
This looks like a bug in 10.0.0.5 |
How does it work int 10.0.0.7 ?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Gralgrathor |
| Posted: Wed Feb 01, 2017 5:54 am Post subject: |
|
|
Master
Joined: 23 Jul 2009
Posts: 297
|
| fjb_saper wrote: |
| How does it work int 10.0.0.7 ? |
Same behaviour. The only thing I haven't done yet (besides dating a supermodel - in both cases I'm still working on it, in between emergencies) is building a 10.0.0.3/4 environment and checking if that works. I've seen this flow work in other environments, but I cannot say with absolute certainty that it's the upgrade from 10.0.0.4 to 5 that killed it, since this flow was deployed only after the upgrade to 10.0.0.5.
- edit -
Correction: I *do* know this worked before the upgrade; there are failed Idocs on queues connected to the failure terminals of this flow that date before the upgrade.
_________________
A measure of wheat for a penny, and three measures of barley for a penny; and see thou hurt not the oil and the wine.
Last edited by Gralgrathor on Wed Feb 01, 2017 6:06 am; edited 1 time in total |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Feb 01, 2017 5:57 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Open a PMR. Get the latest IFix for the component and check if it works...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
