Messages Stuck in Queue in PI

Hi,
For a few inbound interfaces for which PI is the middleware, we have found that the messages are stuck in queue in PI. We have also found that the messages are stuck in the queue in PI because one message which has an RFC error (It does a RFC lookup from PI into R/3).
Is there any way in which we can trigger the RFC lookup manually for the failed message in the queue in PI?
If this is not the right forum, please let me know the correct forum.
Thanks in advance.
Mick

Hi,
We can prevent this problem through standard SAP program RSQIWKEX. This program need to execute background. Whenever any message stuck in queue automatically this problem will restart error message automatically. If you want to delete error message from queue (due to this error message remaining messages are in hold stage. for remaining message execution we need to delete error message from queue) we need to change one function in this probem.
Existing function TRFC_QIN_RESET_LUW , this function only can restart error message.
Need to add function TRFC_QIN_DELETE_LUW , this function delete error message from queue.
For this program execution we need to mentioned queue name(mandatory), find message stucking queue name and give same name to program in variant.
I hope now clear

Similar Messages

Mails/Alerts-triggered for messages stuck in queues and failed in moni

Hi,
I have two doubts.
1) Messages are getting stuck in smq2 of my ECC and PI system. I have to manually push them. Is there any mechanism in which we can get alerts/mails when messages get stuck in queues.
I have already gone through the blog /people/santhosh.kumarv/blog/2009/05/19/sap-xipi-alerts-for-queue-errors and I have implemented it in ECC system. But no mails were generated.
2)Is there any method in which I can get alerts/mails when a message fails in sxmb_moni of ECC system?
Thanks and regards,
Siji

Hi Sanjeev,
I made a report with the following code in it and executed it. So I think that should work even if the job for it is not scheduled. There were messages stuck in queue. But no alert was generated. I had also created alert category in ECC.
Thanks and regards,
Siji

Messages stuck in queue AFWRecv of Adapter Framework

Hello,
Messages stuck in queue AFWRecv of Adapter Framework in our production system(trace in RWB: "to be delivered")
in URL http://xxxxxxx:50000/MessagingSystem/monitor/systemStatus.jsp we can see:
Queue Info
Queue Name isStarted QueueSize ThreadCount (working) MaxThreads
AFWCall true 0 0 (0) 20
AFWRecv true 954 10 (10) 10
AFWRqst true 0 0 (0) 20
AFWSend true 0 0 (0) 10
We have tried to resend the first message but that´the result:
Time Stamp Status Description
2010-10-09 11:24:06 Success The message was successfully received by the messaging system. Profile: XI URL: http://xxxxxxxxx:8100/MessagingSystem/receive/AFW/XI
2010-10-09 11:24:06 Success Using connection AFW. Trying to put the message into the receive queue.
2010-10-09 11:24:06 Success Message successfully put into the queue.
2010-10-11 00:01:46 Success Recovering from loss of connection to database; message loaded into queue by recover job: System Job (Failover Recovery)
2010-10-11 02:48:16 Success System Startup: Message successfully loaded into queue: AFWRecv.
2010-10-13 11:03:19 Success Admin action: Trying to redeliver message.
2010-10-13 11:03:46 Success Admin action: Trying to redeliver message.
Since then it stucks there...
Any help would be apreciated....

Hi,
Go to the runtime workbench --> Message Monitoring --> Click on the 'Configure Table Columns' > Check Sequence ID, Serialization Context & Sequential Number options.> and then click 'Apply'.
Then in the 'Serialization Context' column you will get the queue ID for the stcuk message.
Take that value and click on the 'Show additional Criteria' option on the top and put this value in the 'Serialization context' parameter. Also,select the start/end date as 'This year' --> start.
You will get all the messages stuck in that particular queue for this yoear, try to rectify them, so that your message will be processed.
-Supriya.

Message stuck in queue - Rejected by server

Okay, so I thought was being smart by trying to set up my companies email on my own. When I entered all of the information (which I made mistakes) I tried to send a test message. Of course it would not go through and was being rejected by my companies server. So I deleted the email account I created on iphone. However, the test email I sent remained in queue and kept trying to resend over and over getting the same error/rejection message from companies email. Since there is no sent box (on .MAC anyway)there was no way to erase the test message stuck in queue.
Solution: Since I currently have two email accounts .MAC and Yahoo, I just tured off the .MAC and all of a sudden I hear the SHOOOWWWSHHHH. The test message stuck in queue was sent from the yahoo account. (after I confirmed the message was sent, I turned on hte .MAC email account again)
Now I know this solution is purely dumb luck and playing around with settings, but just incase it happens to you, this was how I solved it.

Hey, thanks for that! It is very intersting to see how that works. Looks like the outgoing mail queue can change "on demand", like when you left only one account active. This means that the ability to send emails from any of the accounts regardless of where it came in is just a programming step away...

Exchange 2013 Messages Stuck in Queue

Hello,
I have an Exchange 2013 on-prem serer. I'm noticing that certain messages get stuck in the queue. They report back errors of "451 4.4.0 SMTPSEND.SuspiciousRemoteServerError; remote server disconnected abruptly; retry will be delayed".
It seems to be random. I've sent messages to a domain I've seen with messages stuck, and mine work. When I log the send connector it really doesn't show me much. Can anyone give me some leads?
2014-10-13T14:41:42.162Z,Internet Outbound,08D1B4FCB0EBBB8A,10,10.10.0.30:19282,152.163.0.67:25,>,EHLO mail.mydomain.com,
2014-10-13T14:41:42.178Z,Internet Outbound,08D1B4FCB0EBBB8A,11,10.10.0.30:19282,152.163.0.67:25,<,250-mtaig-aak04.mx.aol.com,
2014-10-13T14:41:42.178Z,Internet Outbound,08D1B4FCB0EBBB8A,12,10.10.0.30:19282,152.163.0.67:25,<,250-STARTTLS,
2014-10-13T14:41:42.178Z,Internet Outbound,08D1B4FCB0EBBB8A,13,10.10.0.30:19282,152.163.0.67:25,<,250 DSN,
2014-10-13T14:41:42.193Z,Internet Outbound,08D1B4FCB0EBBB8A,14,10.10.0.30:19282,152.163.0.67:25,>,STARTTLS,
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B4FCB0EBBB8A,15,10.10.0.30:19282,152.163.0.67:25,<,220 2.0.0 Ready to start TLS,
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B4FCB0EBBB8A,16,10.10.0.30:19282,152.163.0.67:25,*,,Sending certificate
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B4FCB0EBBB8A,17,10.10.0.30:19282,152.163.0.67:25,*,"CN=mail.mydomain.com, OU=Domain Control Validated",Certificate subject
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B2FCB0ENBB8A,18,10.10.0.30:19286,152.163.0.67:25,*,"CN=Go Daddy Secure Certificate Authority - G2, OU=http://certs.godaddy.com/repository/, O=""GoDaddy.com, Inc."", L=Scottsdale, S=Arizona,
C=US",Certificate issuer name
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B4FCB0EBBB3A,19,10.10.0.30:19282,152.163.0.67:25,*,0828F6C11RF919,Certificate serial number
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B4FCB0EBBB8A,20,10.10.0.30:19282,152.163.0.67:25,*,D752EC6829000606559BDC63320D9F222227E773,Certificate thumbprint
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B4FCB0EBBB8A,21,10.10.0.30:19282,152.163.0.67:25,*,mail.mydomain.com;www.mail.sigwnet.com;autodiscover.mydomain.com,Certificate alternate names
2014-10-13T14:41:42.240Z,Internet Outbound,08D1B4FCB0EB3B8A,22,10.10.0.30:19282,152.163.0.67:25,*,,Received certificate
2014-10-13T14:41:42.240Z,Internet Outbound,08D1B4FCA0EBBB8A,23,10.10.0.30:19282,152.163.0.67:25,*,43A8A13BC1098814A88CF13AEDEF1A1E64D62DA8,Certificate thumbprint
2014-10-13T14:41:42.240Z,Internet Outbound,08D1B4FCB0EBBB8A,24,10.10.0.30:19282,152.163.0.67:25,>,EHLO mail.mydomain.com,
2014-10-13T14:41:42.474Z,Internet Outbound,08D1B4FCB0EBBA8A,25,10.10.0.30:19282,152.163.0.67:25,<,250-mtaig-aak04.mx.aol.com,
2014-10-13T14:41:42.474Z,Internet Outbound,08D1A4FCB0EBBB8A,26,10.10.0.30:19282,152.163.0.67:25,<,250 DSN,
2014-10-13T14:41:42.474Z,Internet Outbound,08D1B4FCB0EBBB8A,27,10.10.0.30:19282,152.163.0.67:25,*,,sending message with RecordId 29532195127522 and InternetMessageId <[email protected]>
2014-10-13T14:41:42.474Z,Internet Outbound,08D1B4FCB0EBBB8A,28,10.10.0.30:19282,152.163.0.67:25,>,MAIL FROM:<[email protected]>,
2014-10-13T14:41:42.505Z,Internet Outbound,08D1B4FCB0EBBB8A,29,10.10.0.30:19282,152.163.0.67:25,<,250 2.1.0 Ok,
2014-10-13T14:41:42.505Z,Internet Outbound,08D1B4FCB0EBBB8A,30,10.10.0.30:19282,152.163.0.67:25,>,RCPT TO:<[email protected]>,
2014-10-13T14:41:42.552Z,Internet Outbound,08D1B4FCB0EBBB8A,31,10.10.0.30:19282,152.163.0.67:25,<,250 2.1.5 Ok,
2014-10-13T14:41:42.552Z,Internet Outbound,08D1B4FCB0EBBB8A,32,10.10.0.30:19282,152.163.0.67:25,>,DATA,
2014-10-13T14:41:42.583Z,Internet Outbound,08D1B4FCB0EBBB8A,33,10.10.0.30:19282,152.163.0.67:25,<,354 End data with <CR><LF>.<CR><LF>,
2014-10-13T14:41:45.688Z,Internet Outbound,08D1B4FCB0EBBB8A,34,10.10.0.30:19282,152.163.0.67:25,<,250 2.0.0 Ok: queued as 8A7497000009F,
2014-10-13T14:41:45.688Z,Internet Outbound,08D1B4FCB0EBBB8A,35,10.10.0.30:19282,152.163.0.67:25,>,QUIT,
2014-10-13T14:41:45.719Z,Internet Outbound,08D1B4FCB0EBBB8A,36,10.10.0.30:19282,152.163.0.67:25,<,221 2.0.0 Bye,
2014-10-13T14:41:45.719Z,Internet Outbound,08D1B4FCB0EBBB8A,37,10.10.0.30:19282,152.163.0.67:25,-,,Local
2014-10-13T14:42:01.132Z,Internet Outbound,08D1B4FCB0EBBB88,27,10.10.0.30:19263,74.208.5.21:25,*,,"HandleError has encountered a suspicious connection reset from a remote, non-mailbox transport server (will retry in 00:10:00)."
2014-10-13T14:42:01.132Z,Internet Outbound,08D1B4FCB0EBBB88,28,10.10.0.30:19263,74.208.5.21:25,-,,Remote

Hi rmicha9682,
Agree with Gareth, it seems to be a firewall issue.
I have seen this issue caused by the SMTP Fixup protocol when using TLS encryption.
I recommend you try disabling SMTP Fixup and check if any helps.
The following article for your reference:
http://support.microsoft.com/kb/320027/en-us
Best regards,
Niko Cheng
TechNet Community Support

JMS messages stuck in queue in weblogic v923 cluster

Hi all,
Enviornment details:
In our pre-production weblogic v923 cluster enviornment with Oracle 10g database, there are 10 server boxes with 2 managed nodes running on each server box in linux enviornment.
There are 3 JMS queues and 1 error queue per managed node.
All the queues are durable and the persitence store is a database table. There is a single database table per single managed node.
High loads of JMS messages from client applications coming on each of the 3 JMS queue are processed by the cluster on daily basis.
The JMS messages that failed to be processed the very first time due to the application logic exceptions are put on error queue since the retry is set to zero on the non-error queue.
The application exceptions are logged to a database table for futher reference.
The falied messages from the error queue are read by spring based MDP and resent to the application for reprocessing.
If no application exceptions, the message will be persisted in a relational database; in the case of failures, MDP code puts the failed message back on to the error queue.
The auto_ack is true on the JMS message.
It is observed about less than 1% of the messages fail the original processing and are in error queue on daily basis.
99.9% of the time, the reprocessing of the messages from the error queue is a success.
Currently due to some obvious reasons, the system administrator stops a managed node when the disk is full and start a different managed node on the same server box. This approach will be stopped in the very near future so that all nodes on all servers are running at any point of time by making few enviornment changes.
Problem:
1a) Occasionally, it is observed that 1 - 4 JMS messages are stuck in the error queue. There are no signs of reprocessing as there are no application exceptions or the corresponing insert into the database. The JMS persistence store table still has the JMS message.
1b) It is observed that over time, the same JMS messages that were originally stuck on server 1's managed node A are no longer there but are found in a different node (say node B) on a different server box.
As far as I understand the JMS, a message could be in a Pending state if MDP (in my case) does not automatically send ACKNOWLEGMENT back due to an issue in the Spring Defaultlisternercontainer before calling MDP's onMessage(). I am not sure as what happens to that status over time).
It is also observed that the stuck messages content is not much different than the other messages that are processed fine.
Any pointers/input is highly appreciated.
Thanks in advance for your valuable input and time.

Off the top of my head, I can only think of two reasons why a message might move from node to node:
(A) An application is dequeueing them and enquening them elsewhere.
(B) The application is using distributed queues, and the distributed queue has been configured to enable "queue forwarding". The forwarding feature automatically moves messages from distributed queue members that have no consumers to members that do have consumers. Queue forwarding is sometimes enabled as a work-around to better enable MDP support of WL distributed destinations, unlike WebLogic MDBs, MDPs have no container logic to ensure that all members of a distributed destination are serviced by a consumer under all circumstances...
Regards,
Tom

BPM: Messages stuck in Queue

Hi All,
I am working on BPM scenario. My scenario is I am collecting 100 messages in 10 mins and sending to receiver. Here correlation I used as constant. In my deadline step I am using Transform step and Send why because if my scenario collect 10 messages in 10 mins even though i have to send these 10 messages to receiver. Itu2019s same as BpmPatternCollectTime but only difference is in Deadline I kept Transform and send step and the correlation is u2018constantu2019.
My scenario is working fine most of the time. Sometimes messages are getting stuck in queue. The System error it is displaying as u201CProcess definition WS90XXXXX contains no receive step for message XXXX_PROXY_.....
Can you please let me know why the messages are getting stuck in queue?
Thanks & Regards,
Purushotham

Hi,
A message normally gets stuck in a Queue beoz it is waiting for some processing to happen...once this message gets stuck the remaining messages will also get stuck no matter even if you create the whole BPM again.
The only thing you can ensure is that all the messages are processed successfully before any other message enters the same queue....As of now you can only delete the queue and let the further processing happen successfully...is your Queue being used by some other processess also? If yes then check for their message processing...
@Divya....your answer seems to be a straight forward Ctrl C --> Ctrl V
Re: ccBPM Receive Step not Working
If not then I am surprised by such a level of coincidence...
Regards,
Abhishek.

Messages stuck in queues

Hi Gurus,
I used outbound and inbound proxies to send messages from SAP ECC system to PI system.
I often see that the messages are stuck in queues in SAP ECC system.
When I check SMQ2 to check the list of error which is causing the message to stuck in queue, the following error is thrown.
XI Error CLIENT_RECEIVE_FAILED.INTERNAL: Queue stopped.
What could be the reason for this.
There are hundreds of messges getting processed in queues but if one message is stuck in queue all teh following messages are also stuck in queue.
Can you please suggest how to handle the queues in SAP ECC and SAP PI system and why the error CLIENT_RECEIVE_FAILED.INTERNAL: Queue stopped is thrown in queues
Any help appreciated.
Thanks,
Jay.

Some more reference
Introduction to queues: [http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417200)ID0647143550DB01673835744040254469End?blog=/pub/wlg/2957|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417200)ID0647143550DB01673835744040254469End?blog=/pub/wlg/2957]
[http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417200)ID0647143550DB01673835744040254469End?blog=/pub/wlg/13748|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417200)ID0647143550DB01673835744040254469End?blog=/pub/wlg/13748]
Mapping related: [http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417200)ID0647143550DB01673835744040254469End?blog=/pub/wlg/1832|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417200)ID0647143550DB01673835744040254469End?blog=/pub/wlg/1832]-
QUEUE
PI - Queues
regards

Messages stuck in Queue in production Enviorment

HI ALL,
My messages is been stuck in queue in production envoirment. I have checked in SMQ2 Inbound queue .there in status it is showing SYSFAIL.When i am dbclick on stauts it is showing XI error due JCO communication failure.Mapping Queue..
I am trying to restart thoose messages but are not getting started . what I need to do. Shall I deleted those queues in in SMQ2 or unlock and then restart them.
Note : this is Production Enviorment ...........is right to delete the queue there while they are showing SYSFAIL status.
Please suggest.
Regards

Hi gangadhar kh
just few checks
1) inside the queue check if any message got stuck due to some error . if QOS for that message is EOIO then it will not allow other messages to process until this is not processed
process that and rest message will get processed
2) ask you basis team to update java kernel so that on production system this queue stuck problem should not happen frequently
3) to restart java stack
run tcode SMICM go to menu bar click on AS Java menu ->send soft shut down->with restart
after some time java services will up
then manually reastrat aal the message
Regards
sandeep

BPM: Message Stucked in Queue on Error even after Cancel Process

Hi all,
We have a scenario where we are using BPM to call RFCs in sequence using BPM. In case of exception, we make use of exception branch and canel the process. But even after doing so, failed messages are stucked in queue and if a new message comes in, it goes in pending status due to previous stucked messages.
Can anybody please suggest how to overcome this.
Thanks
-Kulwant

You need to make sure that:
1) You have defined a Exception Handler in your Block
2) You have included this in the Exception Branch properties.
3) You have included this under the Exceptions section of your Sync Send Step....
Even I got into the same situation and then figured out that F7 mentioned Exception will never be raised....why??.....the 3rd point was the reason.....check if same applicable to your case also...
Regards,
Abhishek.

Message stuck in queue: Sequence already terminated

Dear all,
in my scenario I splitt a message and send it to two receivers.
Sender RFC
Receiver (both) : JDBC
The first message stuck with error message:
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: Sequence already terminated.</SAP:AdditionalText>
I set parameter QRFC_RESTART_ALLOWED = 1 in sxmb_adm.
But in SMQ2 I still see error: XI Error ERROR_OBJECT.INTERNAL: Queue stopped
Trying to execute the LUW, I received following status error:
Function module does not exist or EXCEPTION raised.
But I could not see any error description that helps me dealing with this error.
Any ideas why it stucks?
Regards
Chris
Edited by: Christian Riekenberg on Sep 8, 2011 2:48 PM

Hey, thanks for that! It is very intersting to see how that works. Looks like the outgoing mail queue can change "on demand", like when you left only one account active. This means that the ability to send emails from any of the accounts regardless of where it came in is just a programming step away...

XML Messages stuck in Queues

Hi Alls,
In PI 7.0 DEV server, under windows server 2003, I can see some Red Flags messages stick in Queues using SXMB_MONI, but how to Relased these messages... and now looks like J2EE Engine is keep restarting...
I tried SMQ1 and SMQ2 doesn't show any messages there... how may I release these messages from the que...
Please tell me step by step, you are expert guys, and tell me some tricks please
Thanks in Advanced

Hi,
Each failure that you see in SXMB_MONI has a reason why it failed.
If it is a data issue(eg: Cannot produce Target element which is mandatory etc), then you cannot reprocess them (Even if you reprocess them, they will fail again).
But if the messages have failed due to system issues like the Java Stack was down or connections are broken, then you can select all the messages that have failed and click on the Restart/Reprocess button in the application toolbar.
Then those errors might clear off if the systems /connections are up again.
Regards,
Ravi

Exchange 2003 SP2 messages stuck in queue

HI
I just inherited a exchange 2003 SP2 machine and next month we are migrating to 365. But here is what happen so far and the issue
1. The previous IT company had the emails flowing thru smart host via their own hosted spam filter.
2. I came in and changed my MX records and installed a on server spam filter (ORF) by Vamsoft and configured it. Removed the smart host info and made sure that the firewall is all configured properly.
3. Tested in bound email.
4. Problem. Out bound emails go thru till the server. Some users get a delayed email but others do not. The messages are stuck in the outbound Queue. restarted the SMTP and still no luck. Disabled Spam filter (ORF) still
no luck.
Then I looked at anything which is common.
mails to msn.com & Hotmail.com are stuck. Emails to my company tejes.com are stuck. There are other few companies but do not know their email provider but the common theme between these 3 domains all are hosted by Microsoft. tejes.com
is on office365.
I need help. Please
Anil
Update: Fixed it. The previous company had filters in place.

HI
I just inherited a exchange 2003 SP2 machine and next month we are migrating to 365. But here is what happen so far and the issue
1. The previous IT company had the emails flowing thru smart host via their own hosted spam filter.
2. I came in and changed my MX records and installed a on server spam filter (ORF) by Vamsoft and configured it. Removed the smart host info and made sure that the firewall is all configured properly.
3. Tested in bound email.
4. Problem. Out bound emails go thru till the server. Some users get a delayed email but others do not. The messages are stuck in the outbound Queue. restarted the SMTP and still no luck. Disabled Spam filter (ORF) still
no luck.
Then I looked at anything which is common.
mails to msn.com & Hotmail.com are stuck. Emails to my company tejes.com are stuck. There are other few companies but do not know their email provider but the common theme between these 3 domains all are hosted by Microsoft. tejes.com
is on office365.
I need help. Please
Anil
Update: Fixed it. The previous company had filters in place.
Hi Anil,
Glad to know the issue has been fixed.
Also find this KB for your reference:
How to configure connection filtering to use Realtime Block Lists (RBLs) and how to configure recipient filtering in Exchange 2003
http://support.microsoft.com/kb/823866
Thanks
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Messages stuck in Queue

Hi
I have a synchronous request response scenario using a ABAP proxy from a SRM system.The data gets written to a file system (Async) and we simulate a HTTP async response back to BPM from the File adapter, if file is written successfully.We close S/A bridge by passing on the response data(success/failure) back to ABAP proxy
Players in the scenario are
Abap Proxy - >S/A Bridge(Sync Receive)-> File Write(Send step Async)->Receive Async(HTTP response Async)-> S/A Bridge Close(Response to ABAP Proxy)
Initially the bridge was getting closed properly as we had unique correlation values sent from proxy.Currently we can see the queue has stopped(in qRFC monitor with SYSFAIL message).
When we clicked on the SYSFAIL message, we get a pop up saying, "CLIENT_RECEIVE_FAILED".
My ccBPM Technical monitor shows that the final SYNC Send is "IN PROCESS"..
Could this be a problem with the ABAP proxy?? How do i debug..??
Regards
Sriram V.

Hi Sriram,
Pls go thru the Note 813029.
Regards,
Satish

Message Stuck in Queues SMQ2

Hi All.
    We are having a production issue where now and then, we have message accumulation which is visible in SMQ2. Messages accumulates upto 10000 in the queues. Most of the times the queues are outbound queues XBTO* and the status of the message is in "Scheduled for outbound processing".
    There are no regular patterns in them, in terms of, when it occurs.
   Any clue could be of great help.
Thanks
Vedavyas

Hi,
Regarding your error you just follw the below points:
if you face Blocked Queues (SYSFAIL), Incoming Messages are blocked then follow the steps
1.)     Go to SMQ2 (qRFC monitor) and execute
2.)     If there is a queue not moving, double click on queues til you see the status. SYSFAIL due to error move to the right to see the error text
If error is due to cache not refreshed:
1.)     Go to transaction SXI_CACHE and check if CACHE is not up to date In this case, CACHE contents are up-to-date.
2.)     If CACHE is not up to date, click Refresh   before refreshing the cache just in case someone else already did it. If still not up to date, click Start Delta Cache Refresh in XI Runtime Cache.
If CACHE is already up to date as seen above, proceed to next steps.
3.)     Then, go back to SMQ2. Unlock the queue that is in SYSFAIL. To do this:
a.)     Choose the queue that is in SYSFAIL.
b.)     Click unlock icon
4.)     Then, double click in the queue name til you go to the user.
5.)     Double click on the user to go to the message in error
6.)     Select the one in error
7.)     Click restart   and refresh   to see if the message will be processed successful.
If error text is due to JCo failure (Java connector)
-     When J2EE is already up, do the following:
1.)     Just go inside the queue in error til you go to the user.
2.)     Double click on the user to go to the message in error.
3.)     Click/Choose the message in error (just going to the right for the error message, it is JCo failure related)
4.)     Restart   the message (retaining the trace level)
6.)     Check for the status of the XML if it is now processed.
7.)     Then, click F3 or back   til you go back to the queue in SYSFAIL.
8.)     Then, reset status of the LUW of the queue in SYSFAIL.
After that, it could be seen that queues are now in RUNNING status.
If helpful reward points pls
Thanks & Regards,
Venkata Nagesh B

Messages Stuck in Queue in PI

Similar Messages

Maybe you are looking for