Skip to Content
avatar image
Former Member

PI JMS Sender Communication channel issue

Hi guys ,

My scenario is JMS to Proxy .

Third party which is sending the messages in JMS queue has said that PI is not picking the messages as a result few messages are getting timed out .

But on PI side I don't see any error or failed messages at communication channel level .

I don't see any issue at JMS sender communication channel .

Parameter for Error handling settings seems good to me :

1. Wait after message error(msecs) - 10000

2. Wait after reconnect(msecs) - 10000

We are accessing JMS provider over JNDI .

Any inputs ?

Thanks  ,

PD

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    Dec 06, 2013 at 09:54 AM

    If you stop and start the adapter do the messages get picked up?

    If so, one solution that we implemented was to put a scheduling on the adapter to start and stop every X min/hours.

    This is kind of a known issue when it comes to JNDI based connections.

    You could also check if the latest JMS jars are being used

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 06, 2013 at 10:24 AM

    Hi Priyanka

    JMS is little bit complex as compared with other adapters. There are two layers of connection

    1. MQ on third party side

    2. MQ on SAP PI side

    Normally they placed their message in their queue and if MQ set up is correct it will come to MQ in sap side and from there PI adapter picks it up.

    So please check the below

    1. check the connection is working between 3rd party MQ and SAP MQ. You can work with MQ team for that.

    2. You can install Hermes or MQ visual edit and configure your sap side MQ, so that you can goes to queue and check whether messages stuck there or not.

    Add comment
    10|10000 characters needed characters exceeded

  • Dec 06, 2013 at 01:57 PM
    Add comment
    10|10000 characters needed characters exceeded