cancel
Showing results for 
Search instead for 
Did you mean: 

Empty response when retrieving synchonous response-message from MQ-queue

Former Member
0 Kudos

We retrieve a synchronous message from SAP/GRC to XI and forward this to an external webservice via MQ. Our infrastructure doesnu2019t allow direct communication from XI to the external website. We need to put it on a MQ-queue which forwards the message to DataPower. DataPower (IBM) handles the actual webservice call. We use the sync/async bridge in the JMS-adapter to handle correlation between the request and response.

The problem is that when the JMS-adapter picks the response-message it is empty! This means that our interface-mapping is failing. When stopping the adapter we can analyze the payload and it looks fine at the MQ-queue. In runtime workbench I can see the following log:

2009-03-23 19:01:26 Success Message successfully received by messaging system. Profile: XI URL: http://d36sap79.corpusers.net:56200/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER

2009-03-23 19:01:26 Success Using connection JMS_http://sap.com/xi/XI/System. Trying to put the message into the request queue.

2009-03-23 19:01:26 Success Message successfully put into the queue.

2009-03-23 19:01:26 Success The message was successfully retrieved from the request queue.

2009-03-23 19:01:26 Success The message status set to DLNG.

2009-03-23 19:01:26 Success Delivering to channel: Receiver_NFE_SRVSC_MQ

2009-03-23 19:01:26 Success MP: Entering module processor

2009-03-23 19:01:26 Success MP: Processing local module localejbs/AF_Modules/RequestOnewayBean

2009-03-23 19:01:26 Success ROB: entering RequestOnewayBean

2009-03-23 19:01:26 Success ROB: forwarding the request message

2009-03-23 19:01:26 Success ROB: leaving RequestOnewayBean

2009-03-23 19:01:26 Success MP: Processing local module localejbs/AF_Modules/MessageTransformBean

2009-03-23 19:01:26 Success Transform: using Transform.Class: com.sap.aii.messaging.adapter.XSLTConversion

2009-03-23 19:01:26 Success Transform: transforming the payload ...

2009-03-23 19:01:26 Success Transform: successfully transformed

2009-03-23 19:01:26 Success MP: Processing local module localejbs/SAP XI JMS Adapter/ConvertMessageToBinary

2009-03-23 19:01:26 Success MP: Processing local module localejbs/SAP XI JMS Adapter/SendBinarytoXIJMSService

2009-03-23 19:01:26 Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException

2009-03-23 19:01:26 Error Exception caught by adapter framework: null

2009-03-23 19:01:26 Error Delivery of the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException. Setting message to status failed.

2009-03-23 19:01:26 Error The message status set to FAIL.

2009-03-23 19:01:26 Error Returning synchronous error message to calling application: com.sap.aii.af.ra.ms.api.RecoverableException.

Whats happening? Why is my responsemessage it empty?

Can somebody please help?

Kind regards

/Helé

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

If I get it right the MQ queue gives a response message back to XI. The message looks okay on MQ queue, but in XI it's empty.

So I guess the problem must be within the channel that picks it from MQ queue. Did you configure any modules in it that might screw up the content? Is the the message empty as soon as it arrives in XI adapter engine? Pls. check in RWB Monitoring or End-to-End monitoring.

Do you have other channels that pick up messages from that or another MQ queue which do not show such an error? Are they configured exactly the same way?

Regards,

Kai

Former Member
0 Kudos

The problem is solved.

There were two different issues.

1. We needed to configure the channel as "JMS-compliant". Otherwise it couldnt handle the JMS-headers/CorrelationID:s in a correct way.

2. We forgot to add a "Sender Agreement" (hm careless...). Once added it started to work.

It is still a question why I didn't got more proper error-messages though...

Former Member
0 Kudos

Glad you solved it ;o)

Yeah - sometimes the JMS error messages are not too exact... Hope this will get better with MQ7

Cheers,

Kai