Messages stucked with status "To be Delivered" and "Delivering"

[Former Member]

Hi experts,

Some messages in our PI production stucked with status To be Delivered" and "Delivering" after we applied support packages in RP1- ECC 6.0 production system. The messages which failed has sender service RP1 (ECC prodcution) but at the time some of message with the same sender service RP1 has been successfull too.

We tried to resend the messages and cancelled them but "the messages cant be cancelled or resend". No queues in smq1 or smq2. What we can do now? This is critical scenario.

Thanks.

Regards,

Thava

[Former Member · Accepted solution]

Thavachelvi ,

Kindly go through this ..

Regards ,

[Former Member]

Hi All,

Yes the sender interface which was ECC system was slow at the time and teh messages which hang "deleivering" was very huge". So, what I did waschanging some parameters :

Parameters which was changed:

Max concurrency for R_JDBC_SAPHUB changed to 10 from 5.

"messaging.system.queueParallelism.maxReceivers" changed from 0 to 2.

MaxThreadCount = 350. previously 150

Thanks.

Regards,

Thava

[Former Member]

This happens during "fraction of second" when the adapter tries to deliver a message & has problem with the channel. After the "fraction of second", the channel is all Good. Hence the subsequent msg's got delivered. Msg's with "Delivering or To-be-delivered" cannot be cancelled.

We had to restart the java instance when we had the same problem.

This is a SAP bug & you have raised a OSS message to SAP. (Hopefully this gets resovled by some new pathch.)..

Regards,

Siva Maranani

[Former Member]

The instant solution for the issue is restart of J2EE Server.

However to avoid this problem in future, please add pool waiting time in advanced mode parameters of communication channel.

If this issue is occouring for JDBC messages, please check JDBC Driver version.

Also check consumer thread count in visual admin.

Send.MaxConsumers (direction AFW -> IS asynchronous) -

Recv.MaxConsumers (direction IS -> AFW asynchronous) -

Call.MaxConsumers (direction AFW -> IS synchronous) -

Rqst.MaxConsumers (direction IS -> AFW synchronous) -

This should be appropriate as per your server configuration.

Warm Regards,

Gouri

[Former Member]

Thavachelvi ,

May be helpful to you :

http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=%28J2EE3417500%29ID1417584150DB2005594672404240420...

Regards ,

[Former Member]

HI,

If you have check everything and still not getting any success then, In this case you have to restart your J2EE server and then your messages will be delivered.

Other solution is to restart the the service under "server->services->SAP XI AF Messaging" in Visual Admin but sometime it create problem for other messages and in that case you have to restart the J2EE server. So the best solution is to restart the server itself.

[former_member5086]

Hi Thava,

We have had this issue with ftp target scenario.

In our case, it would appears after have restarted our system.

And this issue is caused by a XI*tmp file created in target directory because we have parametrized "create temporary file" in our target communication channel.

Before stop XI system, one message is processing and TMP file is created . If this message doesn't finish after than, when we restart XI system they can not create tmp file (it exist) and message remains in "Delivering" status. All message for the same sender service , interface and receiver service would be enqueued in "to be delivered".

Perharps is this your case?

Can you verify if a tmp file exist in your target directory?

Regards,

[Former Member]

Hi,

I faced some times this issues in production server.

This messages are showing in RWB> Message Monitoring> Delivering Status.

This type of messages are not reached to target directory,Because of some issues from target server like huge messages are flows or Sever are slow or Down like this.

After some time the messages are flowing either successfully or throws error like System error.

U may be find out after time.

Thank you.

Sateesh