ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » WMB 6.0.2 - IA9O SOAP Extract Node Failures

Post new topic  Reply to topic Goto page 1, 2  Next
 WMB 6.0.2 - IA9O SOAP Extract Node Failures « View previous topic :: View next topic » 
Author Message
AviD
PostPosted: Mon Apr 09, 2007 12:32 pm    Post subject: WMB 6.0.2 - IA9O SOAP Extract Node Failures Reply with quote

Acolyte

Joined: 06 Apr 2004
Posts: 62

Hey all, we are experiencing an issue with the IA90 Support Pac SOAP Extract Nodes in WMB 6.0.2.

It appears after variable timeframes (1 day to 2+ weeks), all SOAP extract nodes in flows in a given Execution group will start to fail with the following error:

Quote:
Unhandled exception in plugin method,java.lang.RuntimeException,com.ibm.broker.soap.SoapExtractNode,initialiseAttributes,SoapExtractNode.java,114



The only workaround I've found is to stop, remove, and redeploy the BARs into the execution group again. Simply stopping and restarting them does not work.


Has anyone else experienced this issue, or know the cause?
I'll be opening a PMR shortly with IBM, but thought I'd check to see if anyone here has seen this before.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Mon Apr 09, 2007 12:35 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

I think you need to be at the 6.0.0.3 version of the runtime?
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
AviD
PostPosted: Mon Apr 09, 2007 12:41 pm    Post subject: Reply with quote

Acolyte

Joined: 06 Apr 2004
Posts: 62

We are at...

Quote:
WebSphere Message Brokers Toolkit - Message Broker

Version: 6.0.2
Build id: 20061201_1308


And

Quote:

$ mqsiservice -v
BIPv600 en US
ucnv Console CCSID 819 dft ucnv CCSID 819
ICUW ISO-8859-1 ICUA ISO-8859-1

BIP8996I: Version: 6003
BIP8997I: Product: WebSphere Message Brokers
BIP8998I: CMVC Level: S600-CSD03 DH600-L60821.1
BIP8999I: Build Type: Production

BIP8071I: Successful command completion.



Note, the SOAP Extract Node in each flow works fine for some time, then it randomly starts failing with that error until all flows in the Execution group using it are stopped, removed, and redeployed. Almost as if the flows are going stale in respect to the node.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Mon Apr 09, 2007 1:08 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Well, that definitely shouldn't happen, and probably does need a PMR opened.

Are you sure that the failures are "random", not for example coincident with a deploy of some kind", or a system change of some kind?
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
AviD
PostPosted: Wed Apr 11, 2007 7:19 am    Post subject: Reply with quote

Acolyte

Joined: 06 Apr 2004
Posts: 62

Jeff:

I am not positive they are random, but I am unaware of any system changes taken at that time.

I'll contact the admins and try to track any changes down...

I'm working on gathering the info for the PMR opened.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Tue Apr 17, 2007 9:04 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Can you tell me the PMR# for this? Is there a fix available?
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
AviD
PostPosted: Wed Apr 25, 2007 8:00 am    Post subject: Reply with quote

Acolyte

Joined: 06 Apr 2004
Posts: 62

Jeff, sorry for the delay, lot going on...and this issue hasn't resurfaced yet.
No word from IBM on identifying the cause or a fix.

The issue is documented in PMR 75132 344 000.

Not sure how to proceed given we can't reproduce the error.
Back to top
View user's profile Send private message
TonyD
PostPosted: Sun May 06, 2007 8:53 pm    Post subject: Reply with quote

Knight

Joined: 15 May 2001
Posts: 540
Location: New Zealand

Any update on this? ... I have also experienced it several times, most recently today:

Code:

2007-05-07 11:13:29.346481~75310928   RecoverableException  BIP2230E: Error detected whilst processing a message in node 'mfCCtoGIS_EventRoutingService.SOAPExtract'.
                                       The message broker detected an error whilst processing a message in node 'mfCCtoGIS_EventRoutingService.SOAPExtract'. An exception has been thrown to cut short the processing of the message.
                                       See the following messages for details of the error.
2007-05-07 11:13:29.346597~75310928   RecoverableException  BIP4367E: The method ''evaluate'' in Java node ''SOAPExtract'' has thrown the following exception: 'java.lang.RuntimeException: Unsupported token - ?'.
                                       The method ''evaluate'' of the Java node has thrown an exception. Examine previous error messages for details of the cause of the problem.
                                       This error is generated by the Java node API.  It can occur in a Java Compute node or a Java user-defined node. If the node is a user-defined node, contact the node provider for further details.
2007-05-07 11:13:29.346618~75310928   RecoverableException  BIP4395E: Java exception: ''java.lang.RuntimeException''; thrown from class name: ''com.ibm.broker.soap.SoapExtractNode'', method name: ''initialiseAttributes'', file: ''SoapExtractNode.java'', line: '114'
                                       The message contains that data associated with a Java exception.


: and this is the SOAP envelope that was passed to the node:

Code:

<soapenv:Envelope xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><CreateUpdateEventResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="C:\EQC\XML\XSD\EQC Event Schemas\CreateUpdateGISEventResponse.xsd" senderRefID="33"><ResponseHeader><TransactionIdentifier>String</TransactionIdentifier><Timestamp>2001-12-17T09:30:47-05:00</Timestamp></ResponseHeader><CreateUpdateEventStatus><giscommit>true</giscommit><eventID>EVT/200705/0013</eventID></CreateUpdateEventStatus></CreateUpdateEventResponse></soapenv:Body></soapenv:Envelope>


Like you I found that a redeploy cured the problem, but this will not be a satisfactory workaround when we go to Production! It is probably happened a dozen times in my setup, in several different message flows, for no apparent reason
Back to top
View user's profile Send private message Send e-mail
TonyD
PostPosted: Tue May 29, 2007 9:32 pm    Post subject: Reply with quote

Knight

Joined: 15 May 2001
Posts: 540
Location: New Zealand

Just had this happen again on two successive days, again fixed by a redeploy, but required tracing etc. in order to determine why the flow was failing to complete.
AviD, did you ever get any response to your PMR? Otherwise I might construct a simple flow, run it for a while until it exhibits the same error and then raise a PMR and ask the change team to also run it for a while until it fails.
If we cannot get a resolution on this we will have to scrap using the SOAPExtract node.
Back to top
View user's profile Send private message Send e-mail
jefflowrey
PostPosted: Wed May 30, 2007 3:53 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

There is a fix available.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
TonyD
PostPosted: Wed May 30, 2007 1:13 pm    Post subject: Reply with quote

Knight

Joined: 15 May 2001
Posts: 540
Location: New Zealand

Goodness, how did you know that?! Found it (IY98621: IA90 / UNHANDLED EXCEPTION IN PLUGIN) but it is only a week old! Thanks are in order yet again!
Back to top
View user's profile Send private message Send e-mail
jefflowrey
PostPosted: Wed May 30, 2007 1:34 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

I had to open a PMR on this myself, and got a fix.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
AviD
PostPosted: Tue Jun 26, 2007 8:04 am    Post subject: Reply with quote

Acolyte

Joined: 06 Apr 2004
Posts: 62

Thanks guys, I should have put a reminder on this topic.

We haven't experienced the issue until recently again and I'm testing out the fixed SupportPac.

Glad I wasn't just going insane with the Support Pac and others experienced it too!
Back to top
View user's profile Send private message
AviD
PostPosted: Wed Jun 27, 2007 6:46 am    Post subject: Reply with quote

Acolyte

Joined: 06 Apr 2004
Posts: 62

Just a follow-up question...

When you install an updated Support Pac, do you need to delete and recreate the nodes that are part of that Support Pac?

i.e. The instructions for the updated IA9O Support Pac include the mqsisoap.par update to the broker (server) and also say to install the SP via Rational on the Toolkit.

Once I've done that (actually had to rollback the old IA9O and then install the new IA9O)...do I need to delete and recreate the SOAP Nodes? Or does the installation automatically update them?

In general, I'm not sure.

Specifically with this Support Pac, I have a feeling the Nodes didn't change at all, just the processing on the broker (mqsisoap.par) did...so it may not matter...but I'd like to know generally speaking what can be expected when a given updated Support Pac is installed.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Jun 27, 2007 7:08 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

It's my understanding that the Tooling was unchanged by this particular fix - so all you really needed to do was update the mqsisoap.par in the Runtime.

Either way, you should not have to delete and re-add your nodes. If you do need to do this, though, the Toolkit or the Runtime will be pretty clear about it. Either the Toolkit will show a very generic icon (likely with a red x) for the nodes in the Flow, or the runtime will throw errors about not being able to find the corresponding LIL for the node.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page 1, 2  Next Page 1 of 2

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » WMB 6.0.2 - IA9O SOAP Extract Node Failures
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.