cancel
Showing results for 
Search instead for 
Did you mean: 

Messages 'To Be Delivered'

Former Member
0 Kudos

Hello,

the messages in rwb are status 'To be delivered',..i had read other threads and we had applied the follow:

1. Status: TO_BE_DELIVERED

Which means that the message was successfully delivered from Integration Server point of view and it states that the messages is initially handed over to the Messaging System.

TO_BE_DELIVERED occurs while the message is put into the Messaging System receive queue.

Solution:

This is done via the Messaging System receive servlet:

http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>;

/<PROTOCOL>

Only if this was executed successfully the Messaging System returns HTTP 200 to the Integration Server and the Status TO_BE_DELIVERED moves to DELIVERING

1. Try logging into Sap GUI with two users: XIAPPLUSER & XIAFUSER

to see if they are blocked

2. check the messages:

AdapterFramework

com.sap.aii.adapterframework.serviceuser.language

com.sap.aii.adapterframework.serviceuser.name = XIAFUSER

com.sap.aii.adapterframework.serviceuser.pwd

ApplicationSystem

com.sap.aii.applicationsystem.serviceuser.language

com.sap.aii.applicationsystem.serviceuser.name = XIAPPLUSER

com.sap.aii.applicationsystem.serviceuser.pwd

in the exchange profile to make sure the right passwords

however, the messages continue in 'To be delivered'

thanks very much, is very important for us solved this problem asap

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

Pls provide the message log - this might help determine if a delivery attempt ever made.

Former Member
0 Kudos

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

However to avoid this problem in future, please add pool waiting time and task time out 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

0 Kudos

Hi, Silvia

Does this problem afect only to FTP receiver message?

If yes, see note 821267, pont 45. Receiver File Adapter stuck while using temporary file.

Regards,

Carme.

Former Member
0 Kudos

Hi Tanaya,

the queues are emty.

Former Member
0 Kudos

Go through this..

Otherwise restart the J2EE server.

Regards,

Sarvesh

Former Member
0 Kudos

Hi,

Did you check the corresponding queues in runtime workbench?

If already any message is stuck in that queue, you need to first process it.

Then only these message will be processed.

-Tanaya.