cancel
Showing results for 
Search instead for 
Did you mean: 

PI queue issue when communication channel is stopped.

gopalkrishna_baliga
Participant
0 Kudos

Hi Experts

   I have a Proxy to JMS scenario. Message flows from SAP CRM to PI via Proxy and then to Biztalk via JMS receiver channel.

   When I stop the JMS channel ideally I expected that the message should have stuck in SMQ2 queue. And later when I start the channel I can resend the message from SMQ2. However I don't see any message in queue. When i check RWB or config and monitoring, I see the message in error.

  I cannot resend the error message also.

  Is this a normal behavior? What could be wrong?

  I feel PI will try to resend 3 times and if it still fails then it should put the message in queue in error or schedule state. Later we should be able to see the messages in SMQ2. Or queue should automatically reprocess from SMQ2 by the system jobs to process the queues.

  I am using PI7.31.

Thanks

Gopal

Accepted Solutions (0)

Answers (3)

Answers (3)

rodrigoalejandro_pertierr
Active Contributor
0 Kudos

one the inteface process successfully in Abap Stack,i mean,if you see the Flag White and Black, then the message is passed to the Integration Server to be processed and convert the XML document to the format that the backend is specting..

So, if the message is in the Java Stack you cannot see the message in the MSQ2.

take a look to this picture, i Think is more clear than words.

former_member182004
Contributor
0 Kudos

Hi Gopal,

I recommend you trying to make the interface via AAE (not using the IE, ABAP Stack).

It has a better performance and in your scenario it is possible.

Here's the guide:  http://scn.sap.com/docs/DOC-16242

Regards,

  Juan

ambrish_mishra
Active Contributor
0 Kudos

HI Gopal,

The message are not in SMQ2 since they passed IE successfully. They will error out in adapter engine which is right.

However, you should be able to resend the message through RWB after you start the channel. Select the first message in queue and resend and try to clear the queue manually.

Normally there are jobs scheduled by basis in production to resend the messages in error in IE and adapter level. These jobs may not be running in your environment.

Hope it helps!

Ambrish