cancel
Showing results for 
Search instead for 
Did you mean: 

Messages are in "To Be Deleivered ". State

Former Member
0 Kudos

Dear Experts,

We are getting the following error in RWB ,Adapter monitoring which made All the messages are in "TO BE DELIVERED" status.

Please suggest any ideas to resolve the same which can be rewarded accordingly...

Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection *** after 60 attempts.

(Details: Code: MS.APP.LISTENER.NOTFOUND)

Thanks,

Kiran.

Accepted Solutions (1)

Accepted Solutions (1)

SudhirT
Active Contributor
0 Kudos

Hi Kiran,

Check SAP Note 1138724. if that is your problem.

Thanks!

Answers (8)

Answers (8)

Former Member
0 Kudos

Hi Kiran,

Check the Inbound and Outbound Queues in you target system SMQ1 and SMQ2. Delete them and check again it should be working.

Thanks,

Sudhir

agasthuri_doss
Active Contributor
0 Kudos

Hi,

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. We can 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 make sure the right password

Cheers

Agasthuri Doss

Former Member
0 Kudos

Dear Seshagiri,

CPA Cache and the Server Restart was done earlier but the problem still exists.

Thanks,

Kiran.

Former Member
0 Kudos

Hi,

I faced same kinda error with my IDOC - Soap scenario

Later I realized part of target URL was missing.

It was also showed up a check flag in MONI, but in RWB, there was holding... later turned to system error ... error message.

If you are using Soap Recv CC, do the following:

Check each of the receiver CC parameters

target url and action.

logon authorizations

re create the CC and try.

If you are still experiencing the same problems,

pick payload from PI and send it to target via XML Spy or WS Navigator.

regards,

venkat.

Edited by: Venkat Anusuri on Sep 8, 2008 5:36 PM

Former Member
0 Kudos

Dear All Experts ,

Thanks for your valuable suggestions..The problem was solved by increating Messaging .Connection = Curret value +15 in Visual Admin.The messages are running fine now.

Thanks,

Kiran.

Former Member
0 Kudos

Dear kiran

i am also facing the same problem

how do you increase the messgae conections?

Regards

Buddhike

Former Member
0 Kudos

Hi Guna Ranjan,

Please note that the Adapter engine was refreshed and even Java Node was re-started. But still no use.

Thyanks,

Kiran.

Former Member
0 Kudos

Dear Seshagiri,

The messages are in "To be Delivered " state ad not in "Holding " state and it's showing success in MONI but not in RWB.

The outbound(XI--> Partner) messages are not processing fine but the inbound messages are processing fine.

Thanks,

Kiran.

Former Member
0 Kudos

Hi,

The reason for this is messages were struck up at Adapter engine that why the message were processed at IE and strucked at AE.

Reffer the Blog which i suggested and also do CPACache

REgards

Seshagiri

former_member192295
Active Contributor
0 Kudos

Hi,

It is due to one of message was stuck in queue that why remaining messages are getting to be delivered state, refresh adapter engine and check it, it will work.

Former Member
0 Kudos

Hi

check the RWB message monitoring ,there you will find the cause of the Error.the cause may be your mapping or etc.

Regard's

Chetan Ahuja

Former Member
0 Kudos

Please see the more error information as follows ..

==== Events on Server ******** ====

Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection RNIF11_http://sap.com/xi/XI/System after 60 attempts.

(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)

Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection SFTP_http://seeburger.com/xi after 60 attempts.

(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)

Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection Split997_http://seeburger.com/xi after 60 attempts.

(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)

Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection RFC_http://sap.com/xi/XI/System after 60 attempts.

(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)

Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection JDBC_http://sap.com/xi/XI/System after 60 attempts.

(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)

Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection RNIF_http://sap.com/xi/XI/System after 60 attempts.

(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)

Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection SOAP_http://sap.com/xi/XI/System after 60 attempts.

(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)

Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection Marketplace_http://sap.com/xi/XI/System after 60 attempts.

(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)

Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection CIDX_http://sap.com/xi/XI/System after 60 attempts.

(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)

Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection AS2_http://seeburger.com/xi after 60 attempts.

(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)

Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection BC_http://sap.com/xi/XI/System after 60 attempts.

(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)

Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection JMS_http://sap.com/xi/XI/System after 60 attempts.

(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)

Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection Mail_http://sap.com/xi/XI/System after 60 attempts.

(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)

Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection File_http://sap.com/xi/XI/System after 60 attempts.

(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)

Adapter Engine, message: Fatal Message listener localejbs/RNIFMessageListener could not be created for connection RNIFAdapter after 60 attempts.

(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:26)

Adapter Engine, message: Fatal Message listener localejbs/MarketPlaceAdapterListener could not be created for connection MPA after 60 attempts.

Thanks,

Kiran.

Former Member
0 Kudos

Hi,

Check this

Regards

Seshagiri