cancel
Showing results for 
Search instead for 
Did you mean: 

Adapter Engine - "To Be Delivered"

Former Member
0 Kudos

Hi Guys,

I was hoping someone might be able to help. We have allot of messages in out Adapter engine which is stuck in to be delivered. Nothing is failing and the comm channel monitor is fine. Seems like the messages are just processing very slowly. It's been queuing up for a week now and stands at 7000 messages. On R/3, SMQ2 the messages also times out. We tried to restart the system also the java engine with doesn't seem to help.

Any ideas what I can do?

Thanks,

Jan

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Jan ,

First check in SMq2 and ensure all your quue is in running state if any has system failure then try to check whats the error and if the message is not necessary just cancel them . Secondly Sometimes the messages get struck in "Delivering" State in RWB when you dont specify any time out paramaters in the channel. Sometimes it does not auto process

You have a service there called "SAP XI AF Messaging". Just stop and start it. Then XI will automatically process the message to success or failure state

Regards,

Saurabh

Answers (3)

Answers (3)

Shabarish_Nair
Active Contributor
0 Kudos

can you also check the database level.

Confirm if the DB and table space are not high in PI

Former Member
0 Kudos

awesome! it's working now. I have no Idea what triggered it again. I restarted all messages, queues and cash and for some reason it started processing.

Former Member
0 Kudos

Hi,

Can you try this:

goto sxmb-adm->manage queues->deregister all the available queues-> then register the queues.

Regards,

Souvik

rajasekhar_reddy14
Active Contributor
0 Kudos

Hi,

Tell me what kind if interfaces? 7000 messages belong to same adapter or different.

this kind of issue very serious ,so you have to analys how thread allocation working for adapter.

Regards,

Raj

Former Member
0 Kudos

Hi,

It's different interfaces but all messages. They just queue up on the adapter side. It's mostly File -> IDOC interfaces.

We did manage to get it going for a good 30min where it came down to 5000 messages but now it's stuck again...

[Screen Print|http://www.photostand.co.za/images/h9fbfh1e4gxmbxmjuzpq.jpg]

rajasekhar_reddy14
Active Contributor
0 Kudos

after chekcing your sceena shot,i I think messages delivering to Target system.it mioght take some time.

if all messages got strucked then it is serious issue.

Former Member
0 Kudos

yeah it's pretty serious as it's our production system Suppose we'll log a call to sap since no one here knows whats causing this.

rajasekhar_reddy14
Active Contributor
0 Kudos

let me explain ,

Every adapter had predefined open connections by defulat 5 to handle parllel requests,if your interface is going handle more messages at one shot then def it will take some more time deliver messages to target system.

even you can check the how many number of conection is using whil checking

Copeonent monitporing-->adapyter engine->engine status.

some times you have to invreate the value to required number.

refer below blog

/people/kenny.scott/blog/2008/12/05/xipi-file-and-jdbc-receiver-adapter-performance-and-availability-improvements

Regards,

Raj