on 06-12-2013 1:31 PM
Hi,
I saw that in our client we have lot of interfaces stock in a queue. I access the transaction smq2 to verify this but I want to verify first the name of the interfaces before to re-process it again. Exist a way to verify the name of the interface without accessing one by one to verify this?
Thanks!
Carlos
Hi Carlos,
you can select in SXMB_MONI by status "recorded for outbound processing".
Actually it makes no sense. Only asynchronous message would stuck there. And the qos "Exacly Once" is defined to be queued, so there is nothing special if they are delivered later.
Just solve the error reason (e.g. by deleting the blocking message) und unlock the following ones; the queue will be processed. An explicit restart is not necessary.
/Udo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Udo,
Thanks for your response.
I send you here some screen shots for better understanding. I'm little confuse about this issue.. If I delete the first line presented in the second screen I know that the others stocked interfaces are going to process it again right or I'm wrong? I don't want to insert old data in the system only if is needed.
Regards,
Carlos
Hi Carlos,
>>>If I delete the first line presented in the second screen I know that the others stocked interfaces are going to process it again right or I'm wrong?
right
>>>I don't want to insert old data in the system only if is needed.
As i mentioned before the data are not inside (under normal circumstances). Aynchronous means: Exactly Once, so the sender has sent them only once.
/Udo
Hi All,
can't we take a help from runtime workbench to check how many messages for particular interface?
Regards,
Muniyappan.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In the queue of your previous screenshot, can you go to the top message that is having an issue in SXMB_MONI. Are you able to determine the issue with that message? If you can resolve the issue and reprocess the message the rest of your queue should process normally.
You were asking about old data, the records below the one that is in an error state have not been processed yet. They have only been recorded to process. If you delete the stuck LUW, that particular record should not reprocess. Although you should be able to manually reprocess in SXMB_MONI.
Typically all of the messages in a particular queue are going to be from the same interface. Even if you delete the first LUW, from my experience you are going to get an error on the second one in that same list. Unless the root cause of the message failure has been resolved before you reset the status or delete the stuck LUW.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.