| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| SAP Adapter error |
« View previous topic :: View next topic » |
| Author |
Message
|
| marnick |
 Posted: Wed Mar 04, 2009 1:39 pm Post subject: SAP Adapter error |
 |
|
Novice
Joined: 26 Oct 2006
Posts: 10
|
Hi!
I'm working with these built-in adapters for the first time.
I followed the IBM docs for configuring these - I copied the sapjco libraries to the server (Unix) and also configured the adapters in WMB Toolkit.
I tried to develop two flows (one for inbound messages and another for outbound messages). Whenever I try to deploy the "inbound" flow (SAPInput node), I get a timeout and a javacore dump. The outbound flow get deployed, but when I put a message to the flow and it gets to the SAPRequest node it rolls back to the input queue.
I see no errors in the trace, but I also noted that I get a javacore dump.
Here's the trace:
| Code: |
Timestamps are formatted in local time, 180 minutes before GMT.
Trace written by version ; formatter version 6100
2009-02-28 14:55:56.170803~12346720 UserTrace BIP4040I: The Execution Group ''dmedina'' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2009-02-28 14:55:56.171756~12346720 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' connected to queue manager ''GOYAQM1''. The MQCC was '0' and the MQRC was '0'.
2009-02-28 14:55:56.171791~12346720 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' on queue manager ''GOYAQM1''.
2009-02-28 14:56:12.499305~00464224 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'SapCustomerOutboundMFlow.SAP_CUSTOMER_INQ'.
2009-02-28 14:56:12.505825~00464224 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'SapCustomerOutboundMFlow.SAP_CUSTOMER_INQ' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2009-02-28 14:56:12.505883~00464224 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'SapCustomerOutboundMFlow.SAP_CUSTOMER_INQ' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2009-02-28 14:56:12.506845~00464224 UserTrace BIP6061I: Parser type ''XMLNSC'' created on behalf of node 'SapCustomerOutboundMFlow.SAP_CUSTOMER_INQ' to handle portion of incoming message of length '705' bytes beginning at offset '364'. Parser type selected based on value ''XMLNSC'' from previous parser.
2009-02-28 14:56:12.540107~00464224 UserTrace BIP3447I: A message using method binding ''createSapCustomerWrapper'' has been received in adapter request node ''SAP Request: Create'' in message flow ''SapCustomerOutboundMFlow''.
2009-02-28 14:56:13.424612~00464224 UserTrace BIP3484E: ''Trace SAP logon configuration values*****''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2009-02-28 14:56:13.427032~00464224 UserTrace BIP3484E: ''UserName=MQUSER''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2009-02-28 14:56:13.428990~00464224 UserTrace BIP3484E: ''Password=******''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2009-02-28 14:56:13.430980~00464224 UserTrace BIP3484E: ''Language=EN''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2009-02-28 14:56:13.433951~00464224 UserTrace BIP3484E: ''Codepage=1100''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2009-02-28 14:56:13.436077~00464224 UserTrace BIP3484E: ''Client=800''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2009-02-28 14:56:13.438031~00464224 UserTrace BIP3484E: ''ApplicationServerHost=172.16.1.57''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2009-02-28 14:56:13.440036~00464224 UserTrace BIP3484E: ''SystemNumber=00''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2009-02-28 14:56:13.441978~00464224 UserTrace BIP3484E: ''GatewayHost=172.16.1.57''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2009-02-28 14:56:13.444019~00464224 UserTrace BIP3484E: ''GatewayService=sapgw00''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2009-02-28 14:56:13.446013~00464224 UserTrace BIP3484E: ''LogonGroup=''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2009-02-28 14:56:13.447978~00464224 UserTrace BIP3484E: ''SAPSystemID=''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2009-02-28 14:56:13.449976~00464224 UserTrace BIP3484E: ''MessageServerHost=''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2009-02-28 14:56:13.452013~00464224 UserTrace BIP3484E: ''RFCTraceOn=true''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2009-02-28 14:56:13.454363~00464224 UserTrace BIP3484E: ''RFCTraceLevel=1 (SAP JCo Java API logging)''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2009-02-28 14:56:13.456594~00464224 UserTrace BIP3484E: ''RFCTracePath=C:\Archivos de programa\IBM\WMBT610''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2009-02-28 14:56:13.458773~00464224 UserTrace BIP3484E: ''ABAPDebug=false''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2009-02-28 14:56:13.461167~00464224 UserTrace BIP3484E: ''END of Trace SAP logon configuration values*****''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2009-02-28 14:56:57.828315~08907136 Information BIP3501I: The execution group ''dmedina'' on broker ''GOYABR1'' has SAP adapter components deployed to it which are being used in at least one message flow.
This execution group is running WebSphere Adapter SAP nodes.
None
2009-02-28 14:57:09.655072~26178912 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2009-02-28 14:57:09.808439~26178912 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2009-02-28 14:57:09.809505~26178912 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2009-02-28 14:57:09.810399~26178912 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '169' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
2009-02-28 14:57:10.479789~26178912 UserTrace BIP7080I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node with Subscription Point '''' has received a message of type 'Publish'.
The Publication Node with Subscription Point '''' has started processing a message.
No user action required.
2009-02-28 14:57:10.498283~26178912 UserTrace BIP7081I: The Publication Node has matched '1' subscriptions to topic ''$SYS/Broker/GOYABR1/Status/ExecutionGroup/dmedina'' for subscription point ''''.
The Publication Node has matched subscriptions for the current publication and topic.
No user action required.
2009-02-28 14:57:10.498424~26178912 UserTrace BIP7082I: Node 'PubSubControlMsgFlow.MatchingNode': Publishing to destination 'GOYAQM1:SYSTEM.BROKER.ADMIN.REPLY:4366674d677253756233' for user 'wbiadmin'.
A publication destination is being added to the list of destinations to 'GOYAQM1:SYSTEM.BROKER.ADMIN.REPLY:4366674d677253756233' for user 'wbiadmin'.
No user action required.
2009-02-28 14:57:10.498891~26178912 UserTrace BIP7085I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node has propagated a message to its output terminal for subscription point ''''.
The Publication Node has propagated the current message to its output terminal.
No user action required.
2009-02-28 14:57:10.602357~26178912 UserTrace BIP2638I: The MQ output node 'PubSubControlMsgFlow.ListOutputNoSyncNode' attempted to write a message to queue ''SYSTEM.BROKER.ADMIN.REPLY'' connected to queue manager ''GOYAQM1''. The MQCC was '0' and the MQRC was '0'.
2009-02-28 14:57:10.602416~26178912 UserTrace BIP2622I: Message successfully output by output node 'PubSubControlMsgFlow.ListOutputNoSyncNode' to queue ''SYSTEM.BROKER.ADMIN.REPLY'' on queue manager ''GOYAQM1''.
2009-02-28 14:57:10.604332~26178912 UserTrace BIP4040I: The Execution Group ''dmedina'' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2009-02-28 14:57:10.617774~26178912 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' connected to queue manager ''GOYAQM1''. The MQCC was '0' and the MQRC was '0'.
2009-02-28 14:57:10.617809~26178912 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' on queue manager ''GOYAQM1''.
2009-02-28 14:57:10.898876~13485408 Error BIP2648E: Message backed out to a queue; node 'SapCustomerOutboundMFlow.SAP_CUSTOMER_INQ'.
Node 'SapCustomerOutboundMFlow.SAP_CUSTOMER_INQ' has received a message which has previously been backed out one or more times because of a processing error in the main path of the message flow. The failure terminal is not attached, so the message broker is putting the message directly to the requeue or dead letter backout queue associated with this node. The MQMD 'backoutCount' of the message now equals the 'backoutThreshold' defined for the WebSphere MQ input queue.
Examine previous messages and the message flow to determine why the message is being backed out. Correct this situation if possible. Perform any local error recovery processing required.
2009-02-28 14:57:10.925320~13485408 UserTrace BIP2638I: The MQ output node 'SapCustomerOutboundMFlow.SAP_CUSTOMER_INQ' attempted to write a message to queue ''SYSTEM.DEAD.LETTER.QUEUE'' connected to queue manager ''GOYAQM1''. The MQCC was '0' and the MQRC was '0'.
2009-02-28 14:57:10.925357~13485408 UserTrace BIP2615I: The WebSphere MQ input node 'SapCustomerOutboundMFlow.SAP_CUSTOMER_INQ' has backed out the message to the backout requeue or the dead letter queue.
Message backout processing has been invoked, and the message has either been backed out by being written to the backout requeue or dead letter queue, as determined by the WebSphere MQ queue manager and queue configuration.
No user action required.
2009-02-28 14:59:08.036535~26178912 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2009-02-28 14:59:08.036700~26178912 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2009-02-28 14:59:08.037410~26178912 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2009-02-28 14:59:08.037534~26178912 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '230' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
Threads encountered in this trace:
-1208907136 -1500464224 -1512346720 -1513485408 -1526178912
|
I'm using WebSphere Message Broker 6.1.0
Have any clues? I have no idea of what's going on...
Marnick. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Wed Mar 04, 2009 2:16 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
For starters
| Quote: |
2009-02-28 14:57:10.898876~13485408 Error BIP2648E: Message backed out to a queue; node 'SapCustomerOutboundMFlow.SAP_CUSTOMER_INQ'.
Node 'SapCustomerOutboundMFlow.SAP_CUSTOMER_INQ' has received a message which has previously been backed out one or more times because of a processing error in the main path of the message flow. The failure terminal is not attached, so the message broker is putting the message directly to the requeue or dead letter backout queue associated with this node. The MQMD 'backoutCount' of the message now equals the 'backoutThreshold' defined for the WebSphere MQ input queue.
Examine previous messages and the message flow to determine why the message is being backed out. Correct this situation if possible. Perform any local error recovery processing required. |
your flow does not seem to have any comprehensive error handling. In fact almost none.
A good thing to do is to have this so that you can see the whole of the exceptionlist on the trace using a TraceNode set to output ${ExceptionList}
Does the WMQ Queue used for the message input have a BOQ defined? If it does not then you risk getting a poisoned message etc etc etc This is all Broker SOP.(IMHO)
In my experience getting a broker system to talk to SAP is a bit of a nightmare and without a proper system to capture the errors on the Broker and in SAP itself you end up going quietly mad. Then you a have a "Doh" moment and it all works.
What is the SAP System saying when you try to run this flow?
Does it log anything?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| marnick |
| Posted: Thu Mar 05, 2009 5:59 am Post subject: |
|
|
Novice
Joined: 26 Oct 2006
Posts: 10
|
| smdavies99 wrote: |
For starters
your flow does not seem to have any comprehensive error handling. In fact almost none.
A good thing to do is to have this so that you can see the whole of the exceptionlist on the trace using a TraceNode set to output ${ExceptionList}
Does the WMQ Queue used for the message input have a BOQ defined? If it does not then you risk getting a poisoned message etc etc etc This is all Broker SOP.(IMHO)
In my experience getting a broker system to talk to SAP is a bit of a nightmare and without a proper system to capture the errors on the Broker and in SAP itself you end up going quietly mad. Then you a have a "Doh" moment and it all works.
What is the SAP System saying when you try to run this flow?
Does it log anything? |
Hi:
Thanks for your answer.
I placed a trycatch node before the SAP Request node and a trace node with the exceptionlist in the catch terminal, but I get the same trace, without any exception. In one opportunity the Sap was down and then I saw the exception, but when SAP it´s running I can not see any error.
I looked in the stdout and stderr logs and I found this:
stdout:
| Code: |
2009-03-01 02:49:27.348277 Execution group started. UUID is: '91a973d1-1f01-0000-0080-e11575c52204'. Broker is: GOYABR1
This method is deprecated (WBIResourceAdapterMetadata(Object obj, boolean supportsLocalTx)). It will not read version information from a file. Use WBIResourceAdapterMetadata(String name, String vendor, String version, boolean supportsLocalTx) |
stderr:
| Code: |
2009-03-01 02:49:27.348277 Execution group started. UUID is: '91a973d1-1f01-0000-0080-e11575c52204'. Broker is: GOYABR1
Unhandled exception
Type=Segmentation error vmState=0x00000000
J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000001
Handler1=00CD6368 Handler2=00BBB84F InaccessibleAddress=4B53B700
EDI=0B53B700 ESI=0FFFFDFF EAX=0FFFFEFF EBX=00AB6FD4
ECX=09D69930 EDX=90000000
EIP=00AA6049 ES=0000007B DS=0000007B ESP=098E60F4
EFlags=00210292 CS=00000073 SS=0000007B EBP=098E6210
Module=/lib/ld-linux.so.2
Module_base_address=00AA0000
Target=2_30_20070420_12448_lHdSMR (Linux 2.6.9-55.ELsmp)
CPU=x86 (1 logical CPUs) (0xdee13000 RAM)
JVMDUMP006I Processing Dump Event "gpf", detail "" - Please Wait.
JVMDUMP007I JVM Requesting System Dump using '/home/wbiadmin/core.20090301.025111.9074.dmp'
JVMDUMP010I System Dump written to /home/wbiadmin/core.20090301.025111.9074.dmp
JVMDUMP007I JVM Requesting Snap Dump using '/home/wbiadmin/Snap0002.20090301.025111.9074.trc'
JVMDUMP010I Snap Dump written to /home/wbiadmin/Snap0002.20090301.025111.9074.trc
JVMDUMP007I JVM Requesting Java Dump using '/home/wbiadmin/javacore.20090301.025111.9074.txt'
JVMDUMP010I Java Dump written to /home/wbiadmin/javacore.20090301.025111.9074.txt
JVMDUMP013I Processed Dump Event "gpf", detail "". |
I also checked in SAP and does not log anything. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
