| Author |
Message
|
| northwilks |
 Posted: Wed Aug 20, 2014 12:54 pm Post subject: Unable to parse Message from SAP into Data Object after 7007 |
 |
|
Novice
Joined: 11 Feb 2013
Posts: 13
|
Overview
Using WMB to interface between SAP and parters (via MQ)
Currently in process of moving from WMB 7.0.0.5 to 7.0.0.7
This was done conbined with a WMQ patch level 7.0.1.12 we have to do. And being installed together.
We have completed our Development and Test installation.
Production scheduled in near future.
BUT We found that message leaving SAP into WMB are failing in WMB ONLY on Dev and Test.
It appears it started the day of the WMB fix 7.0.0.7 install/MQ install
In WMB I have a generic passthrough inadapter running. Has been worked fine for months.
Based on WMB pattern supplied. This is still working
The message flows that handle the message specific Queues are now failing for SOME of the messages.
ALL PRODUCTION msg flows are still working (at 7.0.0.5)
My local broker (still 7.0.0.5) also works.
Dev and Test (at 7.0.0.7) both have specific messages that fail
In the MQ input node I have the properties set for input parsing to include (same across boxes)
msg domain: Data Object
msg set: (msg specifc)
msg type: (,msg specific)
msg format: SAP ALE IDoc
Specific messages fail, others are okay. They are in different execution groups. (Not 100% verified)
I am able to run debug and stop flow after input node.
For the failing message, it appears that they can not be parsed into the Data Object format.
The good messages parse fine. The properties on the both Good and Fail seem the same. Same for MQMD
tree. Message have similiar information in SAP.
I logged part of the error message and get this:
Error BIP4395 Text ( Unhandled exception in plugin method ) SubText( -java.lang.NoClassDefFoundError-
java.lang.J9VMInternals-verifyImpl-J9VMInternals.java
Have not found anything I can understand in my searches of the BIP code or message
Do not know enough about java to understand it.
Verified SAP_JCO were all the same.
Same for Queue Definition.
Same bar file to all boxes.
We are planning to roll back the Development System to 7.0.0.5 to determine if the install of 7.0.0.7.
This seems to be the only thing that has changed exepting the MQ fixpack.
Any suggestions on what else I can check or other methods to identify the problem? |
|
| Back to top |
|
 |
| northwilks |
| Posted: Thu Aug 21, 2014 3:48 pm Post subject: Got it working, still not sure what cause the fail. |
|
|
Novice
Joined: 11 Feb 2013
Posts: 13
|
Here is an update.
I figure out how to get it working again. But if anyone can explain why this now acts the way it does, I would appreciate it. Or a better solution?
Big thing I noticed about failing and working messages, they are in different Execution group..... and the difference between EG? the ones the fail are IN TO WMB ONLY. which means NO adapter, since adapters are generic and in different EG. Since the adapter is definitely tied to the Java engine, maybe that's it??? maybe it has code that the parser needs to parse SAP Data objects.
So I took one failing Execution Groups and added an outadapter... just a random one. Even though NO part of the flow uses it. But I just tossed it in the bar file. Surprised! the all started working! |
|
| Back to top |
|
|
| northwilks |
| Posted: Wed Sep 03, 2014 7:51 am Post subject: Additional information: Reported problem IT01691 |
|
|
Novice
Joined: 11 Feb 2013
Posts: 13
|
I found a reported problem IT01691 which indicates this will be fixed in fix pack 7.0.0.8 but offers no interim/local fix.
Also, if Broker is stopped and restarted, these flow will begin to fail. Even though they already contained the additional adapter node.
The bar files need to be re-deployed before the message flows will begin to work again. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Sep 03, 2014 7:53 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| If there's a published APAR, you can open a PMR and get an iFix. |
|
| Back to top |
|
|
| northwilks |
| Posted: Wed Sep 03, 2014 8:17 am Post subject: |
|
|
Novice
Joined: 11 Feb 2013
Posts: 13
|
| Thanks. I will try that now. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Sep 03, 2014 9:13 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
you might also want to start planning your move to IIB. WMB 7 will be out of support in about 12 months.... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| northwilks |
| Posted: Wed Sep 03, 2014 9:39 am Post subject: |
|
|
Novice
Joined: 11 Feb 2013
Posts: 13
|
Ouch. Thank you for pointing that out.
Are there resources to help plan that migration? Hopefully no change to existing function. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Sep 03, 2014 10:39 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| northwilks wrote: |
| Are there resources to help plan that migration? |
Yes.
| northwilks wrote: |
| Hopefully no change to existing function. |
Aside from the changes one normally sees between 2 major versions of IBM software....
WMBv7 artifacts should run in IIBv9, i.e. you can deploy v7 bar files to v9 in the same way you can deploy v6.0 bar files to v7. You may find the source code and development enviroment somewhat different, with consequent changes to your development practices, design choices, etc, etc, etc.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| northwilks |
| Posted: Tue Sep 09, 2014 8:10 am Post subject: Issue resolved. |
|
|
Novice
Joined: 11 Feb 2013
Posts: 13
|
I opened a PMR as suggested and received an iFix. We just finished deploying to development and it worked as expected. Test and Prod will wait for Oct.
Thanks to all for your guidance. |
|
| Back to top |
|
|
|
|
