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 » SAP IDOC (inadapter) error while processing to Broker

Post new topic  Reply to topic
 SAP IDOC (inadapter) error while processing to Broker « View previous topic :: View next topic » 
Author Message
am040383
PostPosted: Wed Nov 13, 2013 3:25 am    Post subject: SAP IDOC (inadapter) error while processing to Broker Reply with quote

Newbie

Joined: 30 Jul 2009
Posts: 5
Hi have received the below error while SAP sends IDOC message to the broker.
Please Advise It is working in our SIT broker but not in INT broker, though the same code is running. I am suspecting may be some version mismatch is there. Please help

Error Details:

Nov 6 23:12:16 rintbmr4 user:info WebSphere Broker v7005[10879028]: (RINTBRKA.ESB_EG_01)[42410]BIP3442E: An exception occurred in adapter node 'MaterialMaster_Operations', which is using adapter component 'MaterialMaster.inadapter'.. : RINTBRKA.4e438364-3001-0000-0080-9347468b63bb: MbErrorHandler.java: 137: createMessage: :
Nov 6 23:12:16 rintbmr4 user:info WebSphere Broker v7005[10879028]: (RINTBRKA.ESB_EG_01)[42410]BIP3450E: An adapter error occurred during the processing of a message. The adapter error message is 'com.sap.conn.jco.JCoException: (1000) com.ibm.despi.exception.DESPIException: java.lang.NullPointerException: com.ibm.despi.exception.DESPIException: com.ibm.despi.exception.DESPIException: java.lang.NullPointerException com.ibm.despi.exception.DESPIException: com.ibm.despi.exception.DESPIException: java.lang.NullPointerException: RINTBRKA.4e438364-3001-0000-0080-9347468b63bb: MbErrorHandler.java: 286: throwableToMbException: :
Nov 6 23:12:16 rintbmr4 user:info WebSphere Broker v7005[10879028]: (RINTBRKA.ESB_EG_01)[42410]BIP3453E: Adapter input node 'com.nol.fnca.services.MF_FNCA_MaterialMaster_V2' failed to process an event called 'SapMatmas05Zmatmas05' from adapter component 'MaterialMaster.inadapter'. : RINTBRKA.4e438364-3001-0000-0080-9347468b63bb: /build/S700_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 723: MbMessageEndpoint.failureProcessing: :
Nov 6 23:12:16 rintbmr4 user:err|error WebSphere Broker v7005[10879028]: (RINTBRKA.ESB_EG_01)[41896]BIP2628E: Exception condition detected on input node 'com.nol.fnca.services.MF_FNCA_MaterialMaster_V2.MaterialMaster_Operations'. : RINTBRKA.4e438364-3001-0000-0080-9347468b63bb: /build/S700_P/src/DataFlowEngine/TemplateNodes/ImbCallableTemplateNode.cpp: 1203: Java_com_ibm_broker_plugin_MbCallableTemplateNode__1failMessage: ComIbmSAPInputNode: com/nol/fnca/services/MF_FNCA_MaterialMaster_V2#FCMComposite_1_4
Nov 6 23:12:16 rintbmr4 user:info WebSphere Broker v7005[10879028]: (RINTBRKA.ESB_EG_01)[41896]BIP3442E: An exception occurred in adapter node 'MaterialMaster_Operations', which is using adapter component 'MaterialMaster.inadapter'.. : RINTBRKA.4e438364-3001-0000-0080-9347468b63bb: MbErrorHandler.java: 137: createMessage: :
Nov 6 23:12:16 rintbmr4 user:info WebSphere Broker v7005[10879028]: (RINTBRKA.ESB_EG_01)[41896]BIP3450E: An adapter error occurred during the processing of a message. The adapter error message is 'com.sap.conn.jco.JCoException: (1000) com.ibm.despi.exception.DESPIException: java.lang.NullPointerException: com.ibm.despi.exception.DESPIException: com.ibm.despi.exception.DESPIException: java.lang.NullPointerException com.ibm.despi.exception.DESPIException: com.ibm.despi.exception.DESPIException: java.lang.NullPointerException: RINTBRKA.4e438364-3001-0000-0080-9347468b63bb: MbErrorHandler.java: 286: throwableToMbException: :
Nov 6 23:12:16 rintbmr4 user:info WebSphere Broker v7005[10879028]: (RINTBRKA.ESB_EG_01)[41896]BIP3453E: Adapter input node 'com.nol.fnca.services.MF_FNCA_MaterialMaster_V2' failed to process an event called 'SapMatmas05Zmatmas05' from adapter component 'MaterialMaster.inadapter'. : RINTBRKA.4e438364-3001-0000-0080-9347468b63bb: /build/S700_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 723: MbMessageEndpoint.failureProcessing: :
Nov 6 23:12:17 rintbmr4 user:err|error WebSphere Broker v7005[10879028]: (RINTBRKA.ESB_EG_01)[11312]BIP2628E: Exception condition detected on input node 'com.nol.fnca.services.MF_FNCA_MaterialMaster_V2.MaterialMaster_Operations'. : RINTBRKA.4e438364-3001-0000-0080-9347468b63bb: /build/S700_P/src/DataFlowEngine/TemplateNodes/ImbCallableTemplateNode.cpp: 1203: Java_com_ibm_broker_plugin_MbCallableTemplateNode__1failMessage: ComIbmSAPInputNode: com/nol/fnca/services/MF_FNCA_MaterialMaster_V2#FCMComposite_1_4
Nov 6 23:12:17 rintbmr4 user:info WebSphere Broker v7005[10879028]: (RINTBRKA.ESB_EG_01)[11312]BIP3442E: An exception occurred in adapter node 'MaterialMaster_Operations', which is using adapter component 'MaterialMaster.inadapter'.. : RINTBRKA.4e438364-3001-0000-0080-9347468b63bb: MbErrorHandler.java: 137: createMessage: :
Nov 6 23:12:17 rintbmr4 user:info WebSphere Broker v7005[10879028]: (RINTBRKA.ESB_EG_01)[11312]BIP3450E: An adapter error occurred during the processing of a message. The adapter error message is 'com.sap.conn.jco.JCoException: (1000) com.ibm.despi.exception.DESPIException: java.lang.NullPointerException: com.ibm.despi.exception.DESPIException: com.ibm.despi.exception.DESPIException: java.lang.NullPointerException com.ibm.despi.exception.DESPIException: com.ibm.despi.exception.DESPIException: java.lang.NullPointerException: RINTBRKA.4e438364-3001-0000-0080-9347468b63bb: MbErrorHandler.java: 286: throwableToMbException: :
Nov 6 23:12:17 rintbmr4 user:info WebSphere Broker v7005[10879028]: (RINTBRKA.ESB_EG_01)[11312]BIP3453E: Adapter input node 'com.nol.fnca.services.MF_FNCA_MaterialMaster_V2' failed to process an event called 'SapMatmas05Zmatmas05' from adapter component 'MaterialMaster.inadapter'. : RINTBRKA.4e438364-3001-0000-0080-9347468b63bb: /build/S700_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 723: MbMessageEndpoint.failureProcessing: :
Back to top
View user's profile Send private message
am040383
PostPosted: Wed Nov 13, 2013 9:14 pm    Post subject: Reply with quote

Newbie

Joined: 30 Jul 2009
Posts: 5
Hi Masters,

Anyone have any view on this?
Back to top
View user's profile Send private message
mapa
PostPosted: Thu Nov 14, 2013 9:32 am    Post subject: Reply with quote

Master

Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden
My guess is that the IDOC definition in the SAP systems (I assume you are going against two different SAP systems) are not the same or you aren't using the same SAP Adapter in SIT and INT.

(You can also check the answers in the other SAP question currently active.)

It is also very similar to
BIP3453E BIP3450E in WMB SAP connectivity sample failures
Back to top
View user's profile Send private message Visit poster's website
am040383
PostPosted: Mon Nov 18, 2013 4:19 am    Post subject: Reply with quote

Newbie

Joined: 30 Jul 2009
Posts: 5
Hi mapa,

NO. IDOC definition and SAP Adapter, both are the same in the INT and SIT env.

I am still searching the resolution for this issue
Back to top
View user's profile Send private message
mapa
PostPosted: Mon Nov 18, 2013 6:35 am    Post subject: Reply with quote

Master

Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden
What version is it then?
Look in the Toolkit ResourceAdapters folder.

When you say that it is the same code running, is it the exact same artifact (bar-file) that you have deployed?

Or do you have the same source and then create new bar-file that you deploy (that in theory should be the exact same but not necessarily so depending upon a number of factors)? (If so, create a new workspace and rebuild it, then deploy).

Do a JCO trace on the inbound adapters in both environments and compare.

For some versions the only way to see the real exceptions for outbound BAPI calls is to actually do a service trace on the EG. Normally overkill but if you are desperate it might be worth it. Something you will have to do anyway if you need to do a PMR.

Maybe someone else has a better idea?
Back to top
View user's profile Send private message Visit poster's website
am040383
PostPosted: Thu Nov 21, 2013 12:15 am    Post subject: Reply with quote

Newbie

Joined: 30 Jul 2009
Posts: 5
Hi

Now we understood that, this is because of SAP server up-gradation issue.

Those environment got upgraded, we are receiving the error.

Now, what I do, I am now recreate the Inbound Adapter and import all the Message Set newly and deploy to the broker. Now I am getting the below error in my trace node which is connected to my SAP Input Failure terminal.

Please help.

----------------
( ['MQROOT' : 0x1237425f0]
(0x01000000:Name):RecoverableException = (
(0x03000000:NameValue):File = 'MbErrorHandler.java' (CHARACTER)
(0x03000000:NameValue):Line = 137 (INTEGER)
(0x03000000:NameValue):Function = 'getMethodName' (CHARACTER)
(0x03000000:NameValue):Type = '' (CHARACTER)
(0x03000000:NameValue):Name = '' (CHARACTER)
(0x03000000:NameValue):Label = '' (CHARACTER)
(0x03000000:NameValue):Catalog = 'BIPmsgs' (CHARACTER)
(0x03000000:NameValue):Severity = 0 (INTEGER)
(0x03000000:NameValue):Number = 3455 (INTEGER)
(0x03000000:NameValue):Text = 'Selector excpetion caught from generateEISFunctionname' (CHARACTER)
(0x01000000:Name ):Insert = (
(0x03000000:NameValue):Type = 5 (INTEGER)
(0x03000000:NameValue):Text = 'MaterialMaster_Operations' (CHARACTER)
)
(0x01000000:Name ):Insert = (
(0x03000000:NameValue):Type = 5 (INTEGER)
(0x03000000:NameValue):Text = 'com.nol.fnca.services.MF_FNCA_MaterialMaster_V2' (CHARACTER)
)
(0x01000000:Name ):RecoverableException = (
(0x03000000:NameValue):File = 'MbErrorHandler.java' (CHARACTER)
(0x03000000:NameValue):Line = 286 (INTEGER)
(0x03000000:NameValue):Function = 'throwableToMbException' (CHARACTER)
(0x03000000:NameValue):Type = '' (CHARACTER)
(0x03000000:NameValue):Name = '' (CHARACTER)
(0x03000000:NameValue):Label = '' (CHARACTER)
(0x03000000:NameValue):Catalog = 'BIPmsgs' (CHARACTER)
(0x03000000:NameValue):Severity = 0 (INTEGER)
(0x03000000:NameValue):Number = 3450 (INTEGER)
(0x03000000:NameValue):Text = 'Selector excpetion caught from generateEISFunctionname' (CHARACTER)
(0x01000000:Name ):Insert = (
(0x03000000:NameValue):Type = 5 (INTEGER)
(0x03000000:NameValue):Text = 'java.lang.RuntimeException: org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Feature 'IDocVersion' not found. (http:///temp.xml, 3, 21)
org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Feature 'IDocVersion' not found. (http:///temp.xml, 3, 21)
Feature 'IDocVersion' not found. (http:///temp.xml, 3, 21)
Feature 'IDocVersion' not found. (http:///temp.xml, 3, 21)
' (CHARACTER)
)
)
)
)
Back to top
View user's profile Send private message
marko.pitkanen
PostPosted: Thu Nov 21, 2013 11:09 pm    Post subject: Reply with quote

Chevalier

Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
Hi,

My advice for you am040383 is that you should rise now PMR and reach official help with this "IDocVersion not found" exception.

--
Marko
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » SAP IDOC (inadapter) error while processing to Broker
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.