cancel
Showing results for 
Search instead for 
Did you mean: 

sysfail queue: queue stopped

Former Member
0 Kudos

i have some scenarios runnnig in my system, some scenarios are failing due to queue STOP,

when i click the queue name from the MONI, it shows that three queues namely XBTI007, XBTI003, XBTI004 are in SYSFAIL status,

when i cllick those queues, i find some 1000 entries in each of the queue,

the topmost entry shows that qRFC SXMS_ASYNC_EXEC failed due to

reason: COMMIT/ROLLBACK error on "DEFAULT" database connection...

there are many scenarios getiing stuck but i could find that the a particular scenarios qRFC execution lead to the error,

but since all the scenarios are getting stuck ....

wat action can i take....

if i select the entry with sysfail status and activate the queue, will it hamper something...

will data loss happen??

pls help...its in production system

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello Sudeep,

qRFC - Exactly Once in Order..

So that is why if theres an error in a message all the message which comes after that will be stuck.

If you activate the queue - data loss wont happen .

Moreover only activating the queue might not solve the problem.

Regards,

Sumit

Former Member
0 Kudos

hi sumit,

why different scenarios occupy same queue ??

and why SMQ2? and why not SMQ1......whats the difference between both...

and did u ever encounter error such as

COMMIT/ROLLBACK error in DEFAULT database connection

Former Member
0 Kudos

Dhar,

SMQ2 is for outbound queue and SMQ1 is inbound queue. If you are getting the messages into XI then check in SMQ1 for any errors in XI and if you are sending out from XI then see SMQ2. Check this help for some more information on this:

http://help.sap.com/saphelp_nw04/helpdata/en/76/e12041c877f623e10000000a155106/content.htm

Regards,

---Satish

Former Member
0 Kudos

Isn't SMQ1 for Outbound and SMQ2 for Inbound

Answers (1)

Answers (1)

Former Member
0 Kudos

Dhar,

If you are using JDBC receiver communication channel then try enabling Database ‘Auto-Commit’ and give a try. Also please check this weblog:

/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically

After enabling this property try to restart all this messages and give a try.

Regards,

---Satish