"To be delivered" status in RWB -- Any solution?

[Former Member]

Hi all,

IDoc to File scenario.

The status is staying at "To be delivered" and not moving anywhere from there.

What might be the problem. I even restarted the Java stack still it has the same problem.

Any suggestions??

Thanks

Deepthi

[Former Member]

Thank you Kenny for the links. It helped us to understand about the distribution of threads in Adapter framework.

The main problem is 2 months back we tested few FTPS connections which are not successfull and they keeps trying to connect and they all stayed in the status "Delivering" and "To be delivered" status.

There are around 200 messages like this and these messages are strucked in Messaging queue and not allowing the remaining messages to process.

I manually cancelled all those "To be delivered" messages and changed to working IP address for all the "Delivering" status.

Now the Messaging queue got cleared and messages starts flowing normally.

[kenny_scott]

Hi Deepthi,

in addition to the SDN blogs check the CSS note -

[#937159 XI Adapter Engine is stuck|http://service.sap.com/sap/support/notes/937159]

if all Adapter Engine Adapters are stuck,

e.g.,

ensure that there are enough JEE Application Threads available (350 recommended for XI/PI)

Regards

Kenny

[kenny_scott]

Hi Deepthi,

the following blogs should help

[XI/PI File and JDBC Receiver Adapter performance and availability improvements|https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/12338] [original link is broken] [original link is broken] [original link is broken];

[Messaging System queue properties after XI 3.0 SP19 / XI 7.0SP11|https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/7141] [original link is broken] [original link is broken] [original link is broken];

Regards

Kenny

[Former Member]

Hi Deepthi ,

Check the settings at Visual Admin !!

In J2EE Visual Administrator --> messaging.connections

Messaging System parameters needs to be set to:

Send.maxConsumers=10

Recv.maxConsumers=10

Call.maxConsumers=20

Rqst.maxConsumers=20

BTW , would like to know about your server info ?

Regards ,

[Former Member]

Hi,

Even I have faced the same issue,it was because of the OS related issue.Due to some problem in the OS it was not allowing to write files in the specified folder.

Thanks,

Tiny

[former_member732072]

Hi Deepthi,

Also do have a look at the following forum as it is very informative. It has a similar issue as yours.

and

Best Regards

[shivhare]

Hi,

check entrty in queue with the help of SMQ1 and SMQ2 and remove all entry and agin sent IDOC . if java instance is running it should be process.

Thanks,

Amit

[Former Member]

Hi Amit,

There are no entries in SMQ2.

The message is successfully processed in Integration Engine and pushed to Adapter engine.

Success Message successfully received by messaging system. Profile: XI URL: http://xi-dev.intranet.Com.:50000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER

Success Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.

Success Message successfully put into the queue.

the status stayed at " To be delivered" and not processing anything further.

Now I found that this is happening for all the outbound messages. All the inbound messages are working perfectly.

Any suggestions?

Thanks

Deepthi

[Former Member]

Hey

We had the exact same problem and had to open a OSS message with SAP.

I am not really sure if they have released the Note with the solution or not but it would be worth contacting them.

They will ask you to make some setting changes in Visual admin.

Thanks

Aamir

[Former Member]

HI,

If there are no entries in SMQ1/SMQ2, then can check the Adapter Engine. Probably the message may not be reached till Integration Engine. In RWB, you may find the status as delivering...!!!

Check the solution & root cause given by Agasthuri Doss ...

Thanks

Swarup

[shivhare]

Check adapter specific setting in integration directory

and alos check thread

Thanks

Amit

Edited by: Amit Shivhare on Sep 24, 2009 9:57 AM