cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Message getting stuck in Queue

Former Member
0 Likes
4,312

Dear Freinds,

One of our interface is from Asyn JDBC -> Asyn Proxy. During execution we found the messages are getting stuck in R/3 side. Even we tried deleting those and again activated, but still the problem persits.

How to resolve . Reply ASAP.

Thanks & Regards

K.Ramesh

View Entire Topic
aashish_sinha
Active Contributor
0 Likes

Hi,

You can use the transactions SMQ1 and SMQ2 to clear the inbound and outbound messages in the ABAP stack. You can run this transactions in your XI server and clear the stuck up messages.

but you have registred the queues ?

TCODE -> SXMB_ADM -> register queues

regards

Aashish Sinha

Former Member
0 Likes

Hi,

We have done whatever you have mentioned above. But still the issue persists.

Need soultions friends.

Thanks

Ramesh

Former Member
0 Likes

Hi

1. Goto sxmb_adm

2. De-activate the Queues

3. Activate the Queues

4. Register the Queues

Regards,

Krishna

Former Member
0 Likes

Hi Ramesh,

I too got the same problem recently.

you can solve it by

1) restrict the size of the paylaod by breaking it to smaller chunks

or

2) If you are pickiing all records in to payload, check with your business people if they support delta run.

so that for intial run you will load whole file containing all records, after that you will run interface only with changed/update values.

Let me know how it goes.

Former Member
0 Likes

Hi Ramesh,

Just make sure that you have deleted all the Messages those strucked in the queues before activating the Queues.

1)Just goto SMQ2 and delete all the entries if u dont require these messages

2)Goto SMQR and select all and Delete all the queues

3)Goto SXMB_ADM -Manage Queues-Just Register and dont say any Activation and all

Now trigger the message angain and check whether it is strucked or not

Regards

Seshagiri

Former Member
0 Likes

Hi Sheshagiri,

We have followed the steps mentioned steps but still we are getting the same error. Please tell us how to solve this issue.

Thanks

Ramesh