| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| jco error at SAP side WMB flow |
« View previous topic :: View next topic » |
| Author |
Message
|
| punky |
 Posted: Wed Jan 30, 2013 1:38 am Post subject: |
 |
|
Apprentice
Joined: 26 May 2011
Posts: 44
Location: India
|
Hi All,
I had a finding from the system log for this issue.
| Quote: |
Jan 28 01:20:45 rbitbmr5 user:err|error WebSphere Broker v7002[9699562]: (RBITBRKA.ESB_EG_02)[13653]BIP2628E: Exception condition detected on input node 'com.abc.crm.services.MF_CRM_BPPublishFromCRM.BPPublishFromCRM.Input'. : RBITBRKA.92807a65-2b01-0000-0080-f2aea027a948: /build/S700_P/src/DataFlowEngine/TemplateNodes/ImbCallableTemplateNode.cpp: 1201: Java_com_ibm_broker_plugin_MbCallableTemplateNode__1failMessage: ComIbmSAPInputNode: com/abc/crm/services/MF_CRM_BPPublishFromCRM#FCMComposite_1_7
Jan 28 01:20:45 rbitbmr5 user:info WebSphere Broker v7002[9699562]: (RBITBRKA.ESB_EG_02)[13653]BIP3455E: Adapter input node 'BPPublishFromCRM.Input' in message flow 'com.abc.crm.services.MF_CRM_BPPublishFromCRM' encountered an error when trying to determine the operation name. : RBITBRKA.92807a65-2b01-0000-0080-f2aea027a948: MbErrorHandler.java: 137: getMethodName: :
Jan 28 01:20:45 rbitbmr5 user:info WebSphere Broker v7002[9699562]: (RBITBRKA.ESB_EG_02)[13653]BIP3450E: An adapter error occurred during the processing of a message. The adapter error message is 'For the IDoc type Z_MD_BUPA_INB_REL_SAVE_M01, operation key=Z_MD_BUPA_INB_MAIN_SAVE_M not found using the application-specific information {Create={MsgType=Z_MD_BUPA_INB_REL_SAVE_M, MsgCode=, MsgFunction=}} verify apropriate combination of MsgType,MsgCode, MsgFunction is set in SapZMdBupaInbRelSaveM01, application-specific information.: RBITBRKA.92807a65-2b01-0000-0080-f2aea027a948: MbErrorHandler.java: 286: throwableToMbException: :
Jan 28 01:20:45 rbitbmr5 user:info WebSphere Broker v7002[9699562]: (RBITBRKA.ESB_EG_02)[13653]BIP3453E: Adapter input node 'com.abc.crm.services.MF_CRM_BPPublishFromCRM' failed to process an event called 'SapZMdBupaInbRelSaveM01' from adapter component 'BPPublishFromCRM.inadapter'. : RBITBRKA.92807a65-2b01-0000-0080-f2aea027a948: /build/S700_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 723: MbMessageEndpoint.failureProcessing: :
Jan 28 01:21:19 rbitbmr5 user:info syslog: ifconfig -a
Jan 28 01:21:47 rbitbmr5 user:err|error WebSphere Broker v7002[9699562]: (RBITBRKA.ESB_EG_02)[13653]BIP2628E: Exception condition detected on input node 'com.abc.crm.services.MF_CRM_BPPublishFromCRM.BPPublishFromCRM.Input'. : RBITBRKA.92807a65-2b01-0000-0080-f2aea027a948: /build/S700_P/src/DataFlowEngine/TemplateNodes/ImbCallableTemplateNode.cpp: 1201: Java_com_ibm_broker_plugin_MbCallableTemplateNode__1failMessage: ComIbmSAPInputNode: com/abc/crm/services/MF_CRM_BPPublishFromCRM#FCMComposite_1_7
Jan 28 01:21:47 rbitbmr5 user:info WebSphere Broker v7002[9699562]: (RBITBRKA.ESB_EG_02)[13653]BIP3455E: Adapter input node 'BPPublishFromCRM.Input' in message flow 'com.abc.crm.services.MF_CRM_BPPublishFromCRM' encountered an error when trying to determine the operation name. : RBITBRKA.92807a65-2b01-0000-0080-f2aea027a948: MbErrorHandler.java: 137: getMethodName: :
Jan 28 01:21:47 rbitbmr5 user:info WebSphere Broker v7002[9699562]: (RBITBRKA.ESB_EG_02)[13653]BIP3450E: An adapter error occurred during the processing of a message. The adapter error message is 'For the IDoc type Z_MD_BUPA_INB_MAIN_SAVE_M01, operation key=Z_MD_BUPA_INB_REL_SAVE_M not found using the application-specific information {Create={MsgType=Z_MD_BUPA_INB_MAIN_SAVE_M, MsgCode=, MsgFunction=}} verify apropriate combination of MsgType,MsgCode, MsgFunction is set in SapZMdBupaInbMainSaveM01, application-specific information.: RBITBRKA.92807a65-2b01-0000-0080-f2aea027a948: MbErrorHandler.java: 286: throwableToMbException: :
Jan 28 01:21:47 rbitbmr5 user:info WebSphere Broker v7002[9699562]: (RBITBRKA.ESB_EG_02)[13653]BIP3453E: Adapter input node 'com.abc.crm.services.MF_CRM_BPPublishFromCRM' failed to process an event called 'SapZMdBupaInbMainSaveM01' from adapter component 'BPPublishFromCRM.inadapter'. : RBITBRKA.92807a65-2b01-0000-0080-f2aea027a948:/build/S700_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 723: MbMessageEndpoint.failureProcessing: :
|
The adapter (in inbound mode) is configured to a single RFC, which has data for three different types of IDOCS (multiple IDOCS scenario).
The version of adapter checked from ra.xml is 7.0.0.3
Below is the detail:
IDOC Type: Z_MD_BUPA_INB_REL_SAVE_M01
Message type: Z_MD_BUPA_INB_REL_SAVE_M
IDOC Type: Z_MD_BUPA_INB_MAIN_SAVE_M01
Message type: Z_MD_BUPA_INB_MAIN_SAVE_M
IDOC Type: BUPA_HIERARCHY_INBOUND_SAVE_01
Message type: BUPA_HIERARCHY_INBOUND_SAVE_M
From the system log, it is observed that the adapter is getting confused with the Message types for data coming in for different IDOC types.
| Quote: |
For the IDoc type Z_MD_BUPA_INB_REL_SAVE_M01, operation key=Z_MD_BUPA_INB_MAIN_SAVE_M not found using the application-specific information {Create={MsgType=Z_MD_BUPA_INB_REL_SAVE_M, MsgCode=, MsgFunction=}}
|
| Quote: |
'For the IDoc type Z_MD_BUPA_INB_MAIN_SAVE_M01, operation key=Z_MD_BUPA_INB_REL_SAVE_M not found using the application-specific information {Create={MsgType=Z_MD_BUPA_INB_MAIN_SAVE_M, MsgCode=, MsgFunction=}}
|
Please advice if someone has faced this before.
Best Regards,
Punky |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Wed Jan 30, 2013 5:18 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Why haven't you applied 7.0.0.5? Why are you on 7.0.0.3? Don't forget both toolkit and runtime need to be updated.
http://www-01.ibm.com/support/docview.wss?uid=swg24033276
| Quote: |
APAR IV12663 WebSphere Message Broker Toolkit V6.1 SAP node propagation fails due to adapter component mismatch with message set
117822 Update adapter level to V7005 for Toolkit V7005
117649 SAP V7003 ifix 14 missing transport and the ext folder |
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Mangesh Gadhave |
| Posted: Fri Jun 07, 2013 4:22 am Post subject: |
|
|
Newbie
Joined: 07 Jun 2013
Posts: 1
|
Hi Punky,
I am getting exactly the same error in system logs while receiving Idocs from SAP. I have two different set of Idocs in one MessageSet. Its working for one of them bit not for the other.
Did you find the solution for this yet?
Regards,
Mangesh |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
