Messages stuck in queue AFWRecv of Adapter Framework

[Former Member]

Hello,

Messages stuck in queue AFWRecv of Adapter Framework in our production system(trace in RWB: "to be delivered")

in URL http://xxxxxxx:50000/MessagingSystem/monitor/systemStatus.jsp we can see:

Queue Info

Queue Name isStarted QueueSize ThreadCount (working) MaxThreads

AFWCall true 0 0 (0) 20

AFWRecv true 954 10 (10) 10

AFWRqst true 0 0 (0) 20

AFWSend true 0 0 (0) 10

We have tried to resend the first message but that´the result:

Time Stamp Status Description

2010-10-09 11:24:06 Success The message was successfully received by the messaging system. Profile: XI URL: http://xxxxxxxxx:8100/MessagingSystem/receive/AFW/XI

2010-10-09 11:24:06 Success Using connection AFW. Trying to put the message into the receive queue.

2010-10-09 11:24:06 Success Message successfully put into the queue.

2010-10-11 00:01:46 Success Recovering from loss of connection to database; message loaded into queue by recover job: System Job (Failover Recovery)

2010-10-11 02:48:16 Success System Startup: Message successfully loaded into queue: AFWRecv.

2010-10-13 11:03:19 Success Admin action: Trying to redeliver message.

2010-10-13 11:03:46 Success Admin action: Trying to redeliver message.

Since then it stucks there...

Any help would be apreciated....

[Former Member · Accepted solution]

you can check the service "Locking Adapter" in the Visual Admin (click on refresh inside their). If you see lock entries which are fairly old I'd suggest to delete the oldest one and monitor if things are getting through

you should only delete entries starting with $XI* in the name column!

Nesimi

Edited by: Nesimi Buelbuel on Oct 13, 2010 2:55 PM

[Former Member]

Hello,

Please haw can I check that?

Thanks in advance,

[Former Member]

Hi Filipe,

As you are looking for the inbound messages, goto SMQ2 transaction. It will list out all the queues.

Click on the Queue, then click on Display selection.

Check the below link:

http://help.sap.com/saphelp_nw04/helpdata/EN/49/e3fb40ef74f823e10000000a155106/content.htm

Thanks,

Edited by: Hareenkumar on Oct 13, 2010 2:30 PM

[Former Member]

Hi,

Go to the runtime workbench --> Message Monitoring --> Click on the 'Configure Table Columns' > Check Sequence ID, Serialization Context & Sequential Number options.> and then click 'Apply'.

Then in the 'Serialization Context' column you will get the queue ID for the stcuk message.

Take that value and click on the 'Show additional Criteria' option on the top and put this value in the 'Serialization context' parameter. Also,select the start/end date as 'This year' --> start.

You will get all the messages stuck in that particular queue for this yoear, try to rectify them, so that your message will be processed.

-Supriya.

[former_member4985]

Hi there,

If you can reprocess the messages fine after a J2EE restart, I believe

that it's related to threads missing.

You can increase the value of the parameter "MaxThreadCount" to '350' or higher.

Also, what are the number of threads assigned/working?

Regards,

Caio Cagnani

[Former Member]

Hi,

Check in the adapter engine in the queue wherein your messages are stuck, that queue can have other old messages stuck

already and hence your message are not getting delivered.

You have to clear that queue first, for that chech the entire queue for any messages stuck in it.

-Supriya.