Sync/Async - JMS receiver comm. channel not processing

[Former Member]

I have a Sync/Async scenario (without bpm) in PI 7.11:

RFC -> PI -> JMS

whereby the JMS receiver comm. channel does not fully process the message.

More specifically, the RFC sender comm. channel gets a message in and passes the message to the JMS channel, but that JMS channel within the RWB comm. channel log only shows the entry:

- Message processing started

The odd twist to this is that when we bring the PI server down, then back up again, (or wait a period of time, still trying to determine this period) the FIRST message attempt does successfully get processed, i.e. the first message on that JMS receiver comm. channel RWB log shows as:

- Channel successfully processed the message: 08499236-387c-11e0-b002-000025bab2c2

- Stored the correlation ID 08499236-387c-11e0-b002-000025bab2c2 of the request JMS message: ID:c3e2d840d4d8d4f24040404040404040c754dc12d8b54ec6 correponding to the XI message: 08499236-387c-11e0-b002-000025bab2c2

- Message processing started

(but then because of an issue on the target system, no response comes back, so then we'll additionally get the log entry:

- Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: no message received

)

Any suggestions appreciated on what I can check here to try and figure this out. Possibly because the first message eventually errors out, it is stopping the other subsequent msgs from getting processed...

When I check the audit logs of a 'success' msg vs. a not-successful msg, the success msg has an entry (and subsequent entries) of:

...

14.02.2011 12:50:19 Information Transform: transforming the payload ...

14.02.2011 12:50:19 Information Transform: successfully transformed

14.02.2011 12:50:19 Information ROB: entering RequestOnewayBean

14.02.2011 12:50:19 Information ROB: forwarding the request message

14.02.2011 12:50:19 Information ROB: leaving RequestOnewayBean

14.02.2011 12:50:19 Information JMS Message was forwarded to the JMS provider succesfully."

14.02.2011 12:50:19 Information XMB Message as Binary was forwarded to the SAP XI JMS service succesfully.

14.02.2011 12:50:19 Information WRB: entering WaitResponseBean

14.02.2011 12:50:19 Information WRB: retrieving the message for 08499236-387c-11e0-b002-000025bab2c2 ...

...

wheras the non-success msg shows only:

...

14.02.2011 12:55:30 Information Transform: transforming the payload ...

14.02.2011 12:55:30 Information Transform: successfully transformed

14.02.2011 12:55:30 Information ROB: entering RequestOnewayBean

14.02.2011 12:55:30 Information ROB: forwarding the request message

14.02.2011 12:55:30 Information ROB: leaving RequestOnewayBean

...

So, we can see that the message is not "forwarded to the JMS provider..." in the non-success case.

And also the sxi_monitor shows these messages with a status of "Log version".

Keith

[siddhesh_pathak4]

Hello,

I know its long time that this you have faced. By any chance do you know the resolution for this?

Thanks,

Siddhesh

[Former Member]

Hi Siddhesh - yes that was a while back and am trying to remember the resolution.  I have implemented sync/async bridges (as well as async/sync bridges) successfully, so I don't mind checking your settings, particularly I am interested in the settings within the Module tab of the JMS receiver.  I can then compare to mine if you'd like.  Also if you can let me know what underlying queuing system in that target system (e.g. MQSeries?) that would be great.

Regards,

Keith