on 12-05-2007 4:08 PM
Hi everybody
Sometimes I get this alert in the CCMS-> Transactional RFC and Queued RFC -> Inbound Queues->Int. Server Outbound Messages (XBQ0*)->Blocked queues:
Blocked inbound queue XBQ0$PE_W.... status RETRY...........
I can not get the isssue because it happend when nobody is monitoring the XI system. I want to see what happen at this time but I do not how to do it. When I see the inbound queues in the SMQ2 is empty. Could tell me someboy how to get the issue in a trace or log file?
The system works fine normally but it happens sometimes.
thanks in advanced.
i m not 100% sure but i guess you would also get a dump in ST22 in case of queue failure
just give the user as * and check for any ABAP dumps there
Thanx
Aamir
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Gerardo Mondragon
this issue is not very strange when some queue has very heavy load then for time being messages are queued in the queue and it throws exception and ccms alert is generated. after some time when the queue gets processed all the messsages you will not find any error
if you find error RETRY status in SMQ2 then right click in the last column and execute LUW
it will get processed and queues will be fine
then in RZ 20 you can complete alert
thanks
Sandeep Shrama
PS; if helpful reward points
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thanks for your awnser.
When I monitor the blocked queue this one is empty because after some retries the XI proces the message and clear the queue. Then I can not see what happen.
What I wonder is could I watch somewhere what was the reason the queue was blocked or why this particular message caused the issue? Is there a log or trace file in the XI system to watch ?
Many Thanks.
User | Count |
---|---|
86 | |
10 | |
10 | |
10 | |
7 | |
6 | |
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.