Messages stucked in moni with queue status as "RUNNING"

Hi All,
Few of messages stucked in moni with queue status as "RUNNING" from the past 6 to 7 hours. all the stucked messages running on same dialog instance app server 03 (ucobpi03_PIP_03). i checked PIP appserver its working fine.
Can any one please expalin me how to clean the queues..is there any effect of other queues ?
Thanks,
Siva.

Hi,
it can be due to multiple reasons....
check the interface logic built ...it can be either due to this or can be of large volume of data...
Also check the queues have been registered or not...
HTH
Rajesh

Similar Messages

Monitoring EOIO Messages stuck in AE with HOLD status?

Hi Gurus,
Scenario: IDOC -- > XI (Message split) - - > (HTTP/File)
Some times messages to File adapter are stuck in Adapter Engine with status "HOLD". Found the root cause and un-checked "Maintain order at runtime" in interface determination.
How to get alert if the EOIO messages are stuck in AE with status "HOLD"?
Please help.

Hi,
HOLD status
This is an EOIO message whose predecessor was not processed successfully yet. The status is retained until all predecessors are delivered successfully. If a predecessor has the "System error" status and is restarted, all successors are also restarted provided that the delivery of the predecessor is successful.
If a predecessor has the "canceled with errors" status, further processing is not possible in systems before Support Package 11 for the adapter framework and Support Package 10 for the adapter framework core patch 02. In higher version systems, the status of predecessors can only be set to "canceled with errors" in a manual way. Successors that have the "Holding" status can be restarted after you have set the "canceled with errors" status (see related note 811864).
Regards,
Sreenivas

Message stuck in Adapter Engine queue with status "Delivering"

Hi All,
I have a File to File EOIO scenario. The messages are sucessfully delivered from IE to AE. All entries have a chequered flag in SXMB_MONI. No messages are stuck in IE queue (SMQ2). But the message is stuck in AE queue with status "Delivering". I can not resend or cancel the message coz the status is "delivering".
The reason it is in "delivering" status is due to some config error that I made in Communication Channel FTP parameters. Now it is corrected. But how do I deal with this message now?
Restart of server is not an option here. Is there are place I can delete the message from AE queue?
Thanks
Jaishankar

You can see the queues status (and number of stuck entries etc) through the link:
http://<host>:<port>/MessagingSystem/monitor/systemStatus.jsp
There, you can maintain the queues.
There is also a link for the EOIO Sequence Monitor:
http://<host>:<port>/MessagingSystem/monitor/sequenceMonitor.jsp
There you can see the stuck messages and maintain these.
Make sure to handle the proper message IDs.
All of these are acessible through the Messaging System main page:
http://<host>:<port>/MessagingSystem/
Regards,
Henrique.

Messages stuck in TO BE DELIVERED status

Hi !
Suddenly, whenever a message has to use the File Adapter, no mather which communication channel is to be used, the message is stuck with the "TO BE DELIVERED" status.
These messages, all have SUCCESSFUL status in the SXMB_MONI. The problem is in adapter engine. ALL have NO errors in their Audit Log. Because the problem is in adapter engine/framework, obviously queues at SMQR/SMQ1/SMQ2 are emtpy. ALL have QoS = EO (no eoio queue is used, NO predecessor messages are stuck with system error).
This occurs no mather which adapter is the sender (RFC, File, etc.)
The audit log is:
2008-04-10 16:59:34
Success
Message successfully received by messaging system. Profile: XI URL: http://xxxxxxx:yyyyy/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
2008-04-10 16:59:34
Success
Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2008-04-10 16:59:34
Success
Message successfully put into the queue.
If we try to resend the message using the "resend" button in RWB, the message keeps in the TBDL state and the only difference is a new "success" entry in the audit log saying that:}
"Success | Admin action: Trying to redeliver message".
We already refreshed the cache and restarted the Java stack.
Any clues?
Thanks !
Regards,
Matias.

Hi,
Statuses such as HOLDING or FAILED usually happen only for delivery semantics EOIO (exactly once in order) or BE (best effort means Asynchronous). TO_BE_DELIVERED occurs while the message is put into the Messaging System receive queue. This is done via the Messaging System receive servlet:
http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>/<PROTOCOL>
The MS returns HTTP 200 to the Integration Server only if this was executed successfully. In this example scenario, status TO_BE_DELIVERED should not appear since we assume that the IS has called the servlet successfully.
The status is updated from TO_BE_DELIVERED to DELIVERING when the message has popped out of the receive queue and the event handler lookup was successful, so there is a small gap where TO_BE_DELIVERED could remain in the message monitor, although it was delivered from IS successfully.
Regards,
Srini

Messages stuck in SMQ2 Inbound Queue.

Scenario: File->XI->Proxy
When I put 50 files at the same time in a directory, channel is configured Exactly Once in Order and we have created queue with the name GATQUEUE. The messages are picked up from directory and sent one by one to BPM process. 31 messages out of 50 poccesed succesfully but 19 of them get stuck in the queue always. Though GATQUEUE is released lately but they are stuck in 'XBQO$PE_WS90000013' queue. This is seen in SMQ2 Inbound Queue.
Could you please tell me how to release this message which are already stuck and what bit of configuration required so that it works for 1000s of files/messages at a time?
Thanks
K

Hi Kiran,
Just add the below parameter in XI tcode : SXMB_ADM
Execure Integration Engine and Configuration.
Click on Specific Configuration, go to change mode
Click on New entries
Category : MONITOR
Parameter :QRFC_RESTART_ALLOWED
Current Value : 1
Save.
Regards,
Venu.

Sales order stuck in interface with line status shipped in transaction form

Hi All
Can anyone tell me the reason for the sales orders getting stuck in the interface with line status Shipped in the shipping transaction form.
I ran the Interface trip stop -SRS and mode All for this delivery Id. I checked the log file of it. The error showing in the log file is ORA-20001; ORA-20120 none of the Registers have Balances greater or equal to the excisable amount -> 350 or education cess amount ->7.
Please tell me the set up where to check the register balances and how to proceed with this order. can we manually update the registers if required to process this order.
Thanks in advance
Prem.

Hi,
HOLD status
This is an EOIO message whose predecessor was not processed successfully yet. The status is retained until all predecessors are delivered successfully. If a predecessor has the "System error" status and is restarted, all successors are also restarted provided that the delivery of the predecessor is successful.
If a predecessor has the "canceled with errors" status, further processing is not possible in systems before Support Package 11 for the adapter framework and Support Package 10 for the adapter framework core patch 02. In higher version systems, the status of predecessors can only be set to "canceled with errors" in a manual way. Successors that have the "Holding" status can be restarted after you have set the "canceled with errors" status (see related note 811864).
Regards,
Sreenivas

Message stucked at O/B queue in ECC

Dear All,
We have a scenario - Purchase Order Data posted from ECC to SRM system through PI using Proxy.
Problem is when the message is triggered from ECC, it was stucked up at O/B queue in ECC in MCEXO2 queue and the entry was not found in SXMB_MONI in ECC.
Could you please suggest us resolution.
Thanks & Regards,
Soumya.

Dear All,
In SMQ1, select the Q, Unlock & Activate. When we click on activate system issues the message u201CLUWs in status NOSEND must be picked up by the application u2013Message No :: SR082 u201C.
What does that mean ? Can anybody suggest What are we missing ?
Regards,
Soumya.

How to check the messages stuck up in the queues.

hi experts,
i have implemented the message queues in the EOIO form. if any message is stuck up in the inbound or the outbound queue. where would i will be able to check it.
i have the answers of checking it up in SXMB_MONI and runtime workbench.
is there any other way where i can get info about where the message has stuck up
regards,
Alpa.

Hi,
you could use transactions SMQ1 and SMQ2.
For more information:
XI Asynchronous Message Processing: Understanding XI Queues -Part I
http://help.sap.com/saphelp_nw04/helpdata/en/7b/94553b4d53273de10000000a114084/frameset.htm
Regards
Patrick
Edited by: Patrick Koehnen on Oct 22, 2008 2:51 PM

WSRM messages stuck in PI with HTTP code:403 forbidden

Hi Guys,
We have interface from FILE to WS where file is being sent from third party system to ECC in which we are facing issue.
This service uses HTTPS protocol and while creating the binding in ECC SOAMANAGER we have used communication security as "SSL over HTTP" whereelse in HTTP portocol "none" is selected.
I have tested the wsdl url in browser and is working fine but while sending the message it throwing HTTP code: 403 forbidden error.
Can you help me to resolve this issue?
Thanks
Aki

HI,
I have tested the wsdl url in browser and is working fine but while sending the message it throwing HTTP code: 403 forbidden error.
Can you help me to resolve this issue?
     HTTP code: 403 forbidden error might occur The server understood the request, but is refusing to fulfill it
     Path sap/xi/engine not active
             u2022 HTTP 403 during cache refresh of the adapter framework - Refer SAP Note -751856
             u2022 Because of Inactive Services in ICF u2013Go to SICF transaction and activate the services. Refer SAP Note -517484
             u2022 Error in RWB/Message Monitoring- because of J2EE roles u2013 Refer SAP Note -796726
            u2022 Error in SOAP Adapter - "403 Forbidden" from the adapter's servlet. u2013Because of the URL is incorrect or the adapter is not              correctly deployed.
regards,
ganesh.

Stuck in To Be Delivered Status in Message Monitoring - Adapter Engine

Hi,
I have messages stuck in To Be Delivered status in Messages Monitoring. When i checked the Audito Logs, there are NO LOGS. I resent the message and now the logs indicated in the Audit Logs is:
2014-03-26 08:39:10
Information
The message was successfully received by the messaging system. Protocol: XI URL: http://<host>:<port>/MessagingSystem/receive/AFW/XI Credential (User): PIIXXXX
2014-03-26 08:39:10
Information
Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2014-03-26 08:39:10
Information
Message successfully put into the queue.
2014-03-26 08:52:48
Information
Admin action: Trying to redeliver message.
The connection between the receiver is ok, does this have something to do with the Communication Channels?
Please help.
thank you.

Hi Eng Swee,
there are messages that were cancelled yesterday and the status is 'Terminated With Errors'
this is what is indicated in the Audit Logs
2014-03-26 02:38:47
Information
Admin action: Trying to fail message.
2014-03-26 02:38:47
Error
The message status was set to FAIL.
2014-03-26 02:38:47
Information
Admin action: The message was successfully set to status failed.
2014-03-26 02:38:47
Error
Asynchronous error detected: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Message failed by admin.. Trying to report it.
2014-03-26 02:38:47
Error
Asynchronous error reported.
Is this the reason why the messages are stuck?
thank you!

Messages stuck in Java Queues

I am running PI7.0 SP10 on a MCOD system running ECC6.0 and EP.
We had an issue last week on our Production system where the Java Stack went down, and when the system came back up, we cleared the issues in SMQ1, SMQ2 and SM58 and now we have over two hundred messages stuck in the java queues.
There is nothing locked in SM13, in sxmb_moni all the messgaes are successfully processed... In the RWB the status of the messages are "To be delivered".
I have tried reactivating the adapters but this has not worked.
The queues can be seen in the http://host.fqdn:5<SYSNO>00/MessagingSystem/monitor/systemStatus.jsp
specifically : File_http://sap.com/xi/XI/SystemRecv
and
SOAP_http://sap.com/xi/XI/SystemRecv
where the "isStarted" is set to false, where all the others are true...
How can I go about starting these and processing the backlog of messages??
I have searched OSS, SDN and SAPFans but had not luck!
I have subsequently done a full cache refresh and CPACache refresh but this has not helped.
There are no locked users (XI/PI users) holding this up!

Ok,
It seems to be ok, the return can be http 200 or http 500.
The Soap and File are destinations, ok.
The messages are with status "delivering" on rwb... really, increasing the number of threads will not solve this...
I don't have access to visual admin (only basis team can access it here). I thought it could be something wrong with destination (but you already checked it)... so, the only thing can be done is to find in visual admin somewhere about system properties, conection parameters searching for something wrong there... here are our parameters if you would like to find something (sorry for the size of message)...
AFW.Call.maxConsumers 10
AFW.Recv.maxConsumers 5
AFW.Rqst.maxConsumers 10
AFW.Send.maxConsumers 5
BC_http://sap.com/xi/XI/System.Call.maxConsumers 20
BC_http://sap.com/xi/XI/System.Recv.maxConsumers 10
BC_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
BC_http://sap.com/xi/XI/System.Send.maxConsumers 10
BcAdapter.Call.maxConsumers 10
BcAdapter.Recv.maxConsumers 5
BcAdapter.Rqst.maxConsumers 10
BcAdapter.Send.maxConsumers 5
CIDXAdapter.Call.maxConsumers 10
CIDXAdapter.Recv.maxConsumers 5
CIDXAdapter.Rqst.maxConsumers 10
CIDXAdapter.Send.maxConsumers 5
CIDX_http://sap.com/xi/XI/System.Call.maxConsumers 20
CIDX_http://sap.com/xi/XI/System.Recv.maxConsumers 10
CIDX_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
CIDX_http://sap.com/xi/XI/System.Send.maxConsumers 10
EOIO.lockTimeout 5
File_http://sap.com/xi/XI/System.Call.maxConsumers 20
File_http://sap.com/xi/XI/System.Recv.maxConsumers 10
File_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
File_http://sap.com/xi/XI/System.Send.maxConsumers 10
JDBC_http://sap.com/xi/XI/System.Call.maxConsumers 20
JDBC_http://sap.com/xi/XI/System.Recv.maxConsumers 10
JDBC_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
JDBC_http://sap.com/xi/XI/System.Send.maxConsumers 10
JMS_http://sap.com/xi/XI/System.Call.maxConsumers 20
JMS_http://sap.com/xi/XI/System.Recv.maxConsumers 10
JMS_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
JMS_http://sap.com/xi/XI/System.Send.maxConsumers 10
JPR.Call.maxConsumers 10
JPR.Recv.maxConsumers 5
JPR.Rqst.maxConsumers 10
JPR.Send.maxConsumers 5
MPA.Call.maxConsumers 10
MPA.Recv.maxConsumers 5
MPA.Rqst.maxConsumers 10
MPA.Send.maxConsumers 5
Mail_http://sap.com/xi/XI/System.Call.maxConsumers 20
Mail_http://sap.com/xi/XI/System.Recv.maxConsumers 10
Mail_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
Mail_http://sap.com/xi/XI/System.Send.maxConsumers 10
Marketplace_http://sap.com/xi/XI/System.Call.maxConsumers 20
Marketplace_http://sap.com/xi/XI/System.Recv.maxConsumers 10
Marketplace_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
Marketplace_http://sap.com/xi/XI/System.Send.maxConsumers 10
RFC_http://sap.com/xi/XI/System.Call.maxConsumers 20
RFC_http://sap.com/xi/XI/System.Recv.maxConsumers 10
RFC_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
RFC_http://sap.com/xi/XI/System.Send.maxConsumers 10
RNIF11Adapter.Call.maxConsumers 20
RNIF11Adapter.Recv.maxConsumers 10
RNIF11Adapter.Rqst.maxConsumers 20
RNIF11Adapter.Send.maxConsumers 10
RNIF11_http://sap.com/xi/XI/System.Call.maxConsumers 20
RNIF11_http://sap.com/xi/XI/System.Recv.maxConsumers 10
RNIF11_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
RNIF11_http://sap.com/xi/XI/System.Send.maxConsumers 10
RNIFAdapter.Call.maxConsumers 10
RNIFAdapter.Recv.maxConsumers 5
RNIFAdapter.Rqst.maxConsumers 10
RNIFAdapter.Send.maxConsumers 5
RNIF_http://sap.com/xi/XI/System.Call.maxConsumers 20
RNIF_http://sap.com/xi/XI/System.Recv.maxConsumers 10
RNIF_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
RNIF_http://sap.com/xi/XI/System.Send.maxConsumers 10
SOAP_http://sap.com/xi/XI/System.Call.maxConsumers 20
SOAP_http://sap.com/xi/XI/System.Recv.maxConsumers 10
SOAP_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
SOAP_http://sap.com/xi/XI/System.Send.maxConsumers 10
bulkCommit.threshold 100
cluster.timeout 60000
connection.0.ackListener null
connection.0.exceptionListener localejbs/AFWListener
connection.0.jms.messageSelector null
connection.0.jms.profile null
connection.0.jms.provider null
connection.0.jms.queue null
connection.0.messageListener localejbs/AFWListener
connection.0.name AFW
connection.0.pollAttempts 60
connection.0.pollInterval 60000
connection.1.ackListener localejbs/MarketPlaceAdapterListener
connection.1.exceptionListener localejbs/MarketPlaceAdapterListener
connection.1.jms.messageSelector null
connection.1.jms.profile null
connection.1.jms.provider null
connection.1.jms.queue null
connection.1.messageListener localejbs/MarketPlaceAdapterListener
connection.1.name MPA
connection.1.pollAttempts 60
connection.1.pollInterval 60000
connection.2.ackListener null
connection.2.exceptionListener localejbs/JPR
connection.2.jms.messageSelector null
connection.2.jms.profile null
connection.2.jms.provider null
connection.2.jms.queue null
connection.2.messageListener localejbs/JPR
connection.2.name JPR
connection.2.pollAttempts 60
connection.2.pollInterval 60000
connection.3.ackListener null
connection.3.exceptionListener localejbs/RNIFMessageListener
connection.3.jms.messageSelector null
connection.3.jms.profile null
connection.3.jms.provider null
connection.3.jms.queue null
connection.3.messageListener localejbs/RNIFMessageListener
connection.3.name RNIFAdapter
connection.3.pollAttempts 60
connection.3.pollInterval 60000
connection.4.ackListener null
connection.4.exceptionListener localejbs/CIDXMessageListener
connection.4.jms.messageSelector null
connection.4.jms.profile null
connection.4.jms.provider null
connection.4.jms.queue null
connection.4.messageListener localejbs/CIDXMessageListener
connection.4.name CIDXAdapter
connection.4.pollAttempts 60
connection.4.pollInterval 60000
connection.5.ackListener localejbs/BcAdapterListener
connection.5.exceptionListener localejbs/BcAdapterListener
connection.5.jms.messageSelector null
connection.5.jms.profile null
connection.5.jms.provider null
connection.5.jms.queue null
connection.5.messageListener localejbs/BcAdapterListener
connection.5.name BcAdapter
connection.5.pollAttempts 60
connection.5.pollInterval 60000
connection.6.ackListener null
connection.6.exceptionListener localejbs/TestListener
connection.6.jms.messageSelector null
connection.6.jms.profile null
connection.6.jms.provider null
connection.6.jms.queue null
connection.6.messageListener localejbs/TestListener
connection.6.name test
connection.6.pollAttempts 60
connection.6.pollInterval 60000
connection.7.ackListener null
connection.7.exceptionListener localejbs/RNIF11MessageListener
connection.7.jms.messageSelector null
connection.7.jms.profile null
connection.7.jms.provider null
connection.7.jms.queue null
connection.7.messageListener localejbs/RNIF11MessageListener
connection.7.name RNIF11Adapter
connection.7.pollAttempts 60
connection.7.pollInterval 60000
connections (name=AFW, messageListener=localejbs/AFWListener, exceptionListener=localejbs/AFWListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=MPA, messageListener=localejbs/MarketPlaceAdapterListener, exceptionListener=localejbs/MarketPlaceAdapterListener, ackListener=localejbs/MarketPlaceAdapterListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=JPR, messageListener=localejbs/JPR, exceptionListener=localejbs/JPR, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=RNIFAdapter, messageListener=localejbs/RNIFMessageListener, exceptionListener=localejbs/RNIFMessageListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=CIDXAdapter, messageListener=localejbs/CIDXMessageListener, exceptionListener=localejbs/CIDXMessageListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=BcAdapter, messageListener=localejbs/BcAdapterListener, exceptionListener=localejbs/BcAdapterListener, ackListener=localejbs/BcAdapterListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=test, messageListener=localejbs/TestListener, exceptionListener=localejbs/TestListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=10, Recv.maxConsumers=10, Call.maxConsumers=20, Rqst.maxConsumers=20)(name=RNIF11Adapter, messageListener=localejbs/RNIF11MessageListener, exceptionListener=localejbs/RNIF11MessageListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=10, Recv.maxConsumers=10, Call.maxConsumers=20, Rqst.maxConsumers=20)
debug HTTP
failover.reassignOnNodeLoss true
initial.delay 0
jdbc.autoConfigure false
jdbc.datasource jdbc/SAP/BC_XI_AF_MSG
jdbc.dbProductName ORACLE
jdbc.substituteEmptyString true
jdbc.supportsOpenSQL true
jdbc.supportsScrollableResultSet false
jms.0.dmq SonicMQ.deadMessage
jms.0.messageLengthKey message_length
jms.0.password ********
jms.0.provider
jms.0.url
jms.0.username
monitoring.displayDefault fromParty, toParty, status, timesFailedRetries, sentRecvTime
persistMessageRemover.checkInterval 1440
proxy.password ********
proxy.user
reassignCheck.waitTime 30
ssl.httpsHandler iaik.protocol.https.Handler
ssl.securityProvider iaik.security.provider.IAIK
ssl.serverNameCheck false
ssl.trustedCACerts.viewName TrustedCAs
startup.delay 0
syncMessageRemover.checkInterval 60
syncMessageRemover.messageCount 1000
syncMessageRemover.removeBody true
system.deafaultMaxConsumersPerQueue 10
system.failNonDelivered false
system.message.lazyRead true
system.node 23654950
system.queueConsumerThreadPoolSize 0
system.statusLog System,Send,Recv,Call,Rqst
system.transactionManager ts
test.Call.maxConsumers 20
test.Recv.maxConsumers 10
test.Rqst.maxConsumers 20
test.Send.maxConsumers 10
throughputStatistics enabled
regards
roberti

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.

PI RWB-Messages stuck in Delivering Status

Hi Experts,
PI 7.1
Scenario: Proxy to Mail (Outbound)
QOs: Exactly Once in Order
We are facing problem while sending messages to receiver.
Messages are stuck in Delivering status and the messages followed by them are going into holding status.
Messages in Delivering status has no audit logs.
Issue has started couple of months back. We took restart initially to rectify the barrier but it is happening again. This is repetitive issue and we are looking for permanent fix. Restart is not preferred resolution as it is a production system. Please suggest how can we overcome it? It would be a great help.

Hi Hardik
I've blogged about this issue recently. Please check out the blog:-
http://scn.sap.com/community/pi-and-soa-middleware/blog/2014/03/27/handling-and-preventing-messages-stuck-in-to-be-delivered-status
Rgds
Eng Swee

JMS messages stuck as Pending messages

          Hi.
          I am trying to write an application to process huge amounts of data. I try to
          process around 1,000, 000 messages [java objects] using a single queue and 8 MDB.
          The strange thing is that in the end there are always 10 messages stuck in the
          pending message category.
          I can also observe that a weblogic thread is stuck. [can see it in the console]
          The stuck thread current description is something like "Connectio27.Session28".
          I have tried to use the QueueConnectionFactory from a EJB using resource reference
          instead of fetching it directly. Even this has not helped. I guess the problem
          is that while loading the messages onto the queues, one of the threads gets stuck
          somewhere.
          I am sing MDB's for processing. There doesnot seem to be any problems on the MDB
          side.
          If I reboot the server the 10 messages get processed successfully.
          Any ideas will be highly appreciated.
          -Sharma


if you waited for a minute or so between each threaddump, it definitly
          sounds like an issue around the database query not returning or there is too
          much data being returned.
          sree
          "Ghanshyam Sharma" <[email protected]> wrote in message
          news:40e2d9d6$1@mktnews1...
          >
          > Hmm, I didnt wait too much between thread dumps. Probably a minute or two.
          >
          > Let me check the oracle stuff.
          >
          > Thanks a Lot.
          >
          > -Sharma
          >
          > "sree bodapati" <iwillreply@thenewsgroups> wrote:
          > >Threaddumps dont seem to show much except for it looks like both execute
          > >thread 13 and 12 are stuck reading from oracle , you may want to see
          > >what
          > >query is being sent to oracle by instrumenting you MDB code see that
          > >query
          > >properly returns. The threads are runnable but they dont seem to move
          > >, what
          > >was the duration between each thread dump ?
          > >
          > >/
          > >sree
          > >
          > >
          > >"Ghanshyam Sharma" <[email protected]> wrote in message
          > >news:40e2ce39$1@mktnews1...
          > >>
          > >> Hi Tom.
          > >>
          > >> I am attaching a thread dump of the server on windows, when I have
          > >20
          > >messages
          > >> stuck as pending with MDB's having not-supported transaction attribute.
          > >>
          > >> I hope this helps in debugging the problem. Please let me know if
          > >something is
          > >> needed.
          > >>
          > >> Thanks everyone.
          > >> -Sharma
          > >>
          > >>
          > >> Tom Barnes
          >
          ><[email protected].bea.com>
          > >> wrote:
          > >> >As I wrote below, a thread-dump of the WL Server that hosts
          > >> >the stuck MDB might help explain things.
          > >> >
          > >> >Sharma wrote:
          > >> >
          > >> >> Hm, this is confirmed. I pumped in one million messages a few time
          > >> >with and without
          > >> >> file stores to differe the performance, but every time I get a clean
          > >> >slate :)
          > >> >>
          > >> >> Looks like having required transaction attribute somehow removes
          > >this
          > >> >problem.
          > >> >>
          > >> >>
          > >> >> But still I do not understand why messages were getting stuck with
          > >> >not-supported
          > >> >> attribute. Tom is it possible to understand this. The
          > >phenomenon/Reason
          > >> >behind
          > >> >> this may show up somewhere else :)
          > >> >>
          > >> >> -Sharma
          > >> >>
          > >> >> Tom Barnes
          >
          ><[email protected].bea.com>
          > >> >> wrote:
          > >> >>
          > >> >>>The default is no transactions. I also find it curious
          > >> >>>that this helps. I wonder if tx timeouts are helping here...
          > >> >>>
          > >> >>>Sharma wrote:
          > >> >>>
          > >> >>>
          > >> >>>>Surprisingly I could process all one million messages if I
          configure
          > >> >>>
          > >> >>>the MDB's
          > >> >>>
          > >> >>>>as folowing.
          > >> >>>>
          > >> >>>>Default-transaction=required
          > >> >>>>Transaction-typr=container
          > >> >>>>
          > >> >>>>When I was getting the problem, I had nothing for these settings.
          > >> >I
          > >> >>>
          > >> >>>do not know
          > >> >>>
          > >> >>>>what is the default, probably Not-supported ???
          > >> >>>>
          > >> >>>>Let me try my testing a few times and than confirm to you guys.
          > >> >>>>
          > >> >>>>Tom Barnes
          >
          ><[email protected].bea.com>
          > >> >>>>wrote:
          > >> >>>>
          > >> >>>>
          > >> >>>>>Since you narrowed the problem down to the MDB side, can
          > >> >>>>>post a thread dump of the server when it is stuck? That
          > >> >>>>>might help diagnose the problem.
          > >> >>>>>
          > >> >>>>>Ghanshyam Sharma wrote:
          > >> >>>>>
          > >> >>>>>
          > >> >>>>>
          > >> >>>>>>Infact The thread which is stuck is not the loader/message
          producer
          > >> >>>>>
          > >> >>>>>thread. It
          > >> >>>>>
          > >> >>>>>
          > >> >>>>>>is a thread handling message driven beans. My producers end up
          > >populating
          > >> >>>>>
          > >> >>>>>the
          > >> >>>>>
          > >> >>>>>
          > >> >>>>>>JMS correctly.
          > >> >>>>>>
          > >> >>>>>>This is 81sp02.
          > >> >>>>>>-Sharma
          > >> >>>>>>
          > >> >>>>>>"Ghanshyam Sharma" <[email protected]> wrote:
          > >> >>>>>>
          > >> >>>>>>
          > >> >>>>>>
          > >> >>>>>>>Hi.
          > >> >>>>>>>
          > >> >>>>>>>I am trying to write an application to process huge amounts
          > >of
          > >> >data.
          > >> >>>>>>>I try to
          > >> >>>>>>>process around 1,000, 000 messages [java objects] using a single
          > >> >>>
          > >> >>>queue
          > >> >>>
          > >> >>>>>>>and 8 MDB.
          > >> >>>>>>>The strange thing is that in the end there are always 10
          messages
          > >> >>>
          > >> >>>stuck
          > >> >>>
          > >> >>>>>>>in the
          > >> >>>>>>>pending message category.
          > >> >>>>>>>
          > >> >>>>>>>I can also observe that a weblogic thread is stuck. [can see
          > >it
          > >> >in
          > >> >>>>>
          > >> >>>>>the
          > >> >>>>>
          > >> >>>>>
          > >> >>>>>>>console]
          > >> >>>>>>>The stuck thread current description is something like
          > >"Connectio27.Session28".
          > >> >>>>>>>
          > >> >>>>>>>I have tried to use the QueueConnectionFactory from a EJB using
          > >> >resource
          > >> >>>>>>>reference
          > >> >>>>>>>instead of fetching it directly. Even this has not helped. I
          > >guess
          > >> >>>>>
          > >> >>>>>the
          > >> >>>>>
          > >> >>>>>
          > >> >>>>>>>problem
          > >> >>>>>>>is that while loading the messages onto the queues, one of the
          > >> >threads
          > >> >>>>>>>gets stuck
          > >> >>>>>>>somewhere.
          > >> >>>>>>>
          > >> >>>>>>>I am sing MDB's for processing. There doesnot seem to be any
          > >problems
          > >> >>>>>>>on the MDB
          > >> >>>>>>>side.
          > >> >>>>>>>
          > >> >>>>>>>If I reboot the server the 10 messages get processed
          successfully.
          > >> >>>>>>>
          > >> >>>>>>>Any ideas will be highly appreciated.
          > >> >>>>>>>-Sharma
          > >> >>>>>>
          > >> >>>>>>
          > >> >>
          > >> >
          > >>
          > >
          > >
          >

Trigger Alert E-Mail When messages were in To Be delivered Status

Hello all,
Is it possible to trigger an Alert E-mail if a message struck up in 'To be delivered' status ??
I Know this status is not an error status with AE to trigger alert automatically. We are facing this problem often and when we restart XI AF messaging system, all messages were processed.
We would like to know if messages were struck up with that status more than 15mins.
Any thoughts??
Regards

Hi,
Standard Alert Frame work will not support sending an Alert for To Be delivered status.
you have to do some work around,
check below blog and apply this design
/people/shweta.walaskar2/blog/2011/05/12/trigger-alerts-for-messages-in-to-be-delivered-status-monitoring-adapter-queue-lock
Regards,
Raj

Messages stucked in moni with queue status as "RUNNING"

Similar Messages

Maybe you are looking for