|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Integrating Broker & mySAP issue |
« View previous topic :: View next topic » |
Author |
Message
|
kirankinnu |
Posted: Mon May 14, 2007 7:02 am Post subject: Integrating Broker & mySAP issue |
|
|
 Centurion
Joined: 12 Jun 2004 Posts: 128 Location: Chicago, IL
|
Hi,
I configured the mySAP adapter and was able to connect to SAP. I want to make a BAPI call and am expecting a response in the RESPONSE queue. I extracted the meta data with ODA. I imported the BO into a message set and configured the cfg file correspondingly. When I tried to run the flow and sent the message to REQUEST queue, the message is getting to FAULT queue and in the trace file I am seeing this error."JMS Message was not of the type (Text, Object)" I am validating the message that I am sending to the request queue. What might be the possible reason for this error. Please advice on this.
Thanks,
Kiran |
|
Back to top |
|
 |
kirankinnu |
Posted: Mon May 14, 2007 9:31 am Post subject: |
|
|
 Centurion
Joined: 12 Jun 2004 Posts: 128 Location: Chicago, IL
|
This Is the exact error I am getting:
JMS Message class: jms_bytes
JMSType: null JMSDeliveryMode: 1
JMSExpiration: 0
JMSPriority: 0
JMSMessageID: ID:414d5120514d475238202020202020201c8843462004ab0c
JMSTimestamp: 1178917745560
JMSCorrelationID:null
JMSDestination: null
JMSReplyTo: null
JMSRedelivered: false
status:-1
resubmitTo:null
description:JMS Message was not of the type (Text, Object) expected. Writing it to the fault queue.
keys:null
The JMSType is null. It should refer to the forat & message set that we define in the cfg file. What changes do I need to make for this to apply.
Thanks
Kiran |
|
Back to top |
|
 |
kirankinnu |
Posted: Mon May 14, 2007 11:50 am Post subject: |
|
|
 Centurion
Joined: 12 Jun 2004 Posts: 128 Location: Chicago, IL
|
Once I set the RFH2 header properly, it was working fine. |
|
Back to top |
|
 |
VivekMeshram |
Posted: Thu Jul 12, 2007 11:51 pm Post subject: JDBC Adaptor problem - |
|
|
 Voyager
Joined: 25 Mar 2002 Posts: 83
|
Hi kiran -
We are having the same problem with JDBC adaptor. When an application writes a message into JDBC Request queue - JDBC adaptor not able to process the message and throwing the following error message. The message sent to JDBC FAULT queue. We tried moving message from FAULT to REQUEST queue…still no luck…any idea why this is happening...
JDBC Trace Log:
JMS Message class: jms_bytes
JMSType: mcd://mrm/OJ2QEA8002001/MS_EAI_ASBO_SG_IN_SG?format=CwXML
JMSDeliveryMode: 2
JMSExpiration: 0
JMSPriority: 0
JMSMessageID: ID:414d51204d51525a3839333220202020468dd9f220e8c903
JMSTimestamp: 1184312656240
JMSCorrelationID:null
JMSDestination: null
JMSReplyTo: null
JMSRedelivered: false
status:-1
resubmitTo:null
description:JMS Message was not of the type (Text, Object) expected. Writing it to the fault queue.
keys:null
Integer encoding: 1, Floating point encoding 256. |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Jul 13, 2007 2:13 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Quote: |
description:JMS Message was not of the type (Text, Object) expected. Writing it to the fault queue. |
This is quite clear.
The format field of your RFH header has a content that is not valid for the message.
See further:
Quote: |
JMS Message class: jms_bytes |
You are expecting a jms_text or jms_object message but receiving a jms_bytes message.
Set your sender to send the message correctly...  _________________ MQ & Broker admin |
|
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
|
|
|
|