Queue's have to be unlocked again and again in ECC

[Former Member]

Hi All,

We are facing a issue in ECC, that when ever a new message comes in ECC, the queue gets locked and we have to unlock it again and again. The queue gets into Ready state and they have to be unlocked using unlock button on top in SMQR TXN.

I have tried selecting all queues and regestring them again but it doesn't help.

please advice.

XIer

[VijayKonam]

Did you check if the ABAP code is putting any short dumps in ST22? In such cases the Qs are stopped. Just a thought.

VJ

[former_member183906]

queues are locked when the load to the processor is hight..and the second task is in queue while first one is processing at that time..secodn process will be locked after some time..extent

1) clear the queues in SMQ2,first try to activate them,if that doesn't work them delete them

2)You may need to re-register your queues.

Follow SXMB_ADM -> Manage Queues -> Deregister Queues

Afterwards, re-register the queues and activate from the same screen

3)Only use SMQ1 (outbound queues) and SMQ2 (inbound queues) if re-registering doesn't fix it. You will need to give the queues sometime to get activated so be patient.

4)From SXMB_MONI go to Queue ID of the message, a click here shall take you to qRFC monitor.

if the messages are stuck, you should see an entry indicating number of messages stuck in the queue.

a double click on the entry shall take you to detailed list.

if the messages are stuck because of any error (other than queue not registered etc for e.g. a message failure) then the first message shall show you that.

if indeed you find a message stuck in the queue then the way is to delete the stuck message (DONT DO THIS IN PRODUCTION SERVER without being sure of what does this mean for that particular process !!) and unlock the queue from previous screen.

5)Go to smq2 and execute F8. Then it should come as Nothing was Selected.

If any queues are present then open a queue.if the status is SYS ERROR check the entries,right click on the status text and give save LUW.This brings queue to READY. .

GoTo-> Qin Scheduler: check for the scheduler status to be inactive->Edit-> Activate Scheduler: status frm inactive to starting to wait.Now the queue will be RUNNING.U can see the entries in the queue moving.

Now go to SMQ3, right click on the queue and give Restore LUW.

6)this basically means tht message is waiting in the queue.

in sxmb_moni go to queue Id column and double click on the entry .It will take u to SMQ2.Check the status of the queue

If its SYSFAIL or STOP then double click on it and try to correct the error.After correcting the error send the message again.Also check whether the Queeu is Registred in transaction SMQR.

7)Select your queue form the sxmb_moni, you will reacht he QRFC monitor.

Here you will see some lock figures on the , Select on the 'Unlock Queues'. Activate your queues once again.

This is if your data is correct and queue is stuck. You should only delete the queue if it has errored out due to incorrect data and you need to urgenetly process the rest of the data in the queue.

If you drill down one step more than selct the error message and on the menu select edit-->Save LUW.

AND

Due to connection failure or some other system failure the queue will stop...

If once any failure in the queue then after posting msg also stop...

so that we need to run the 3 reports in Xi system..

it will automate the queue process if any error accure ...

If periodicaly u ill run this reports then the reports will Automate your failure messages ..

Trfc- RSQIWKEX

Qrfc – RSARFCEX

OtherErrors- RSXMB_RESTART_MESSAGES...

[Former Member]

Hi,

Do you want the messages to flow into R/3 from XI in order.

if not might be you could remve maintain order at runtime in interface dt in ID.

what is the quality of service ur using.

Plz let us know more about ur scenario so that experts will be able to advise you.

thanks and regards

ahmed