| Author |
Message
|
| arun_dguy |
 Posted: Mon Aug 21, 2006 4:09 am Post subject: Execution Groups abend |
 |
|
Novice
Joined: 21 Aug 2006
Posts: 10
|
Hi All,
I would like to know the possible reasons for the execution groups to abend. One thing i know is that due to memory leak it will abend. Could anyone please explain me on the other issues. |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Mon Aug 21, 2006 4:28 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
Hello,
I would like to know the possible reasons for someone to die. One thing i know is that due to heart attack (caused by silly questions) you can die. Could anyone please explain me on the other issues.
(sorry, could not resist).
_________________
Regards, Butcher |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Aug 21, 2006 4:44 am Post subject: Re: Execution Groups abend |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| arun_dguy wrote: |
Hi All,
I would like to know the possible reasons for the execution groups to abend. One thing i know is that due to memory leak it will abend. Could anyone please explain me on the other issues. |
Is this a philosphical question or do you have an actual abend? If so, please post details including error messages, platform, package level (including CSDs) & circumstances of abend.
If not, try the messages manual. There's an error message for every problem, though not necessarially a distinct one.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| arun_dguy |
| Posted: Mon Aug 21, 2006 11:37 pm Post subject: |
|
|
Novice
Joined: 21 Aug 2006
Posts: 10
|
We had a abend in the servers. Please see below the errors and let me know if you could find out anyissues. Since this is the first time i was not able to frame the question properly. Sorry.
Aug 3 04:46:45 appma001 WMQIv210[352588]:
(PHXLGP11.PHXLGEG11)[7197]BIP4362E: Java plug-in node error:
[com.amex.emi.CASCustomNodeMessages:0E]Exception : parseResursively
Exception : String index out of range: 169. :
PHXLGP11.a7675bea-0701-0000-0080-c2a7b408d712: : 0:
com.amex.emi.CASCustomNode: parseResursively: :
Aug 3 04:46:45 appma001 WMQIv210[352588]:
(PHXLGP11.PHXLGEG11)[7197]BIP4362E: Java plug-in node error:
[com.amex.emi.CASCustomNodeMessages:0E]Exception : parseResursively
Exception : . : PHXLGP11.a7675bea-0701-0000-0080-c2a7b408d712: : 0:
com.amex.emi.CASCustomNode: parseResursively: :
Aug 3 04:46:45 appma001 WMQIv210[352588]:
(PHXLGP11.PHXLGEG11)[7197]BIP4362E: Java plug-in node error:
[com.amex.emi.CASCustomNodeMessages:0E]Exception : parseCasReplyStream
StringIndexOutOfBoundsException : String index out of range: 169. :
PHXLGP11.a7675bea-0701-0000-0080-c2a7b408d712: : 0:
com.amex.emi.CASCustomNode: parseCasReplyStream: :
Aug 3 04:46:45 appma001 WMQIv210[352588]:
(PHXLGP11.PHXLGEG11)[7197]BIP4362E: Java plug-in node error:
[com.amex.emi.CASCustomNodeMessages:0E]Exception : evaluate Error in
evaluate : String index out of range: 169. :
PHXLGP11.a7675bea-0701-0000-0080-c2a7b408d712: : 0:
com.amex.emi.CASCustomNode: evaluate: :
Aug 3 04:46:45 appma001 WMQIv210[352588]:
(PHXLGP11.PHXLGEG11)[7197]BIP4362E: Java plug-in node error:
[com.amex.emi.CASCustomNodeMessages:0E]Exception : evaluate Exception :
. : PHXLGP11.a7675bea-0701-0000-0080-c2a7b408d712: : 0:
com.amex.emi.CASCustomNode: evaluate: :
Aug 3 04:46:45 appma001 WMQIv210[352588]:
(PHXLGP11.PHXLGEG11)[7197]BIP4362E: Java plug-in node error:
[com.amex.emi.CASCustomNodeMessages:0E]Exception : evaluate Exception
Rolling back!!!. : PHXLGP11.a7675bea-0701-0000-0080-c2a7b408d712: : 0:
com.amex.emi.CASCustomNode: evaluate: :
Aug 3 04:46:45 appma001 WMQIv210[352588]:
(PHXLGP11.PHXLGEG11)[7197]BIP2628E: Exception condition detected on
input node 'PHXLG_GETCASDATA_REPLY.PHXLG.GETCASDATA.MQSI.REPLY'. :
PHXLGP11.a7675bea-0701-0000-0080-c2a7b408d712:
/build/S210_P/src/DataFlowEngine/ImbMqInputNode.cpp: 1462:
ImbMqInputNode::readQueue: ComIbmMQInputNode:
b0396498-fd00-0000-0080-9307aadb86c2
Aug 3 04:46:45 appma001 WMQIv210[352588]:
(PHXLGP11.PHXLGEG11)[7197]BIP2230E: Error detected whilst processing a
message in node 'PHXLG_GETCASDATA_REPLY.CAS_X_Custom'. :
PHXLGP11.a7675bea-0701-0000-0080-c2a7b408d712:
/build/S210_P/src/DataFlowEngine/PluginInterface/ImbJniNode.cpp: 851:
ImbJniNode::evaluate: ComIbmJniNode:
a2a34991-fe00-0000-0080-9307aadb86c2
Aug 3 04:46:45 appma001 WMQIv210[352588]:
(PHXLGP11.PHXLGEG11)[7197]BIP4367E: The method 'evaluate' in Java node
'CAS_X_Custom' has thrown the following exception:
java.lang.NullPointerException. :
PHXLGP11.a7675bea-0701-0000-0080-c2a7b408d712:
/build/S210_P/src/DataFlowEngine/PluginInterface/com_ibm_broker_plugin_CMbService.cpp:
1486: throwableToNativeException: :
Aug 3 04:48:59 appma001 WMQIv210[352588]:
(PHXLGP11.PHXLGEG11)[7197]BIP4362E: Java plug-in node error:
[com.amex.emi.CASCustomNodeMessages:0E]Exception : parseResursively
Exception : String index out of range: 2871. :
PHXLGP11.a7675bea-0701-0000-0080-c2a7b408d712: : 0:
com.amex.emi.CASCustomNode: parseResursively: :
Aug 3 04:48:59 appma001 WMQIv210[352588]:
(PHXLGP11.PHXLGEG11)[7197]BIP4362E: Java plug-in node error:
[com.amex.emi.CASCustomNodeMessages:0E]Exception : parseCasReplyStream
StringIndexOutOfBoundsException : String index out of range: 2871. :
PHXLGP11.a7675bea-0701-0000-0080-c2a7b408d712: : 0:
com.amex.emi.CASCustomNode: parseCasReplyStream: :
Aug 3 04:48:59 appma001 WMQIv210[352588]:
(PHXLGP11.PHXLGEG11)[7197]BIP4362E: Java plug-in node error:
[com.amex.emi.CASCustomNodeMessages:0E]Exception : evaluate Error in
evaluate : String index out of range: 2871. :
PHXLGP11.a7675bea-0701-0000-0080-c2a7b408d712: : 0:
com.amex.emi.CASCustomNode: evaluate: :
Aug 3 08:12:44 appma001 WMQIv210[352588]:
(PHXLGP11.PHXLGEG11)[7197]BIP2228E: Severe error:
/build/S210_P/src/CommonServices/Unix/ImbAbend.cpp 478 signal received
Abend file: /var/wmqi/errors/PHXLGP11.PHXLGEG11.352588.7197.abend
action: abort |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Aug 22, 2006 2:14 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Your custom plugin node is not able to handle the data you are giving it correctly.
Likely this means you're giving it bad data.
It also means that the custom plugin is not written properly to gracefully handle this bad data - and is instead handling this bad data UNGracefully.
Contact the authors of the plugin, and work with them to resolve this issue.
If you are the author of the plugin - then spend some more time reading the error message you just posted. It's fairly clear what's happening.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| arun_dguy |
| Posted: Tue Aug 22, 2006 2:52 am Post subject: |
|
|
Novice
Joined: 21 Aug 2006
Posts: 10
|
| The error logs that i updated above is for the failure of only two messages. I don't think that only these 2 message failure would have resulted to the execution group abend. I suspect there is something else other than this failure that lead to this abend for which we dont have any logs. Please let me know your thoughts in this. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Aug 22, 2006 3:07 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| arun_dguy wrote: |
| Please let me know your thoughts in this. |
My thoughts are that the plug-in node is abending and bringing down the execution group. It's perfectly feasable if the node throws an unhandled abend up to the execution group, which then "handles" it by logging the failure and going down.
Additional evidence is provided by the fact that it's a transient abend. If there was a systemic problem with the execution group you'd expect a recurrent problem. This is more likely to be data releated, data related abends within a standard node are unlikely to bring the group down as there is a mechanism for dealing with them.
Certainly the plug-in abend is the place to start looking for the problem. Even if it turns out not to be the cause of the execution group problem, it shouldn't be doing what it's doing. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
