Messages stucked at SM58

Hi,
We have lot of entries stucked in sm58 of our production server. Even after trying Execute LUW/LUWS, these are not processing. Tcode SM50 have most of the dialogue process in waiting status.most of the entries stucked are for WF-Batch user and the user is not locked.
Thanks in advance.
Sudhir

Hi Vijay/Nipun,
Thanks for your replies.I have tried everything like unlocking the queue and refreshing them but nothing worked.This was all performance related problem.Finally we got to know that our target system response was slow, As soon as the target SAP R/3 system got quicker at response, all entries processed within a minute or two.
Thanks again.
Sudhir

Similar Messages

Message stucks in SM58

Hi,
i'm trying to send an ALEAUD from XI to IDES (R/3 4.6C). It stucks in SM58: "Screen output without connection to user", what is obvisiously a message from R/3. Do somebody know that error?
Regards,
Udo

Check it out...
https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe">Handle Acknoledgements for IDoc</a>
From...
Yallabandi.

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

Error sending IDoc from ERP to PI 7.4 Java Only (stuck in SM58)

Hi specialists
I'm trying to send an IDoc to our new PI 7.4 Java Only.
Because of some authorization issues I changed the RFC Destination <blabla> on PI (nwa) pointing to the ERP system.
Now the IDoc is stuck in SM58 (tRFC queue) and I get this error message:
The IDoc Destination <blabla> was changed. Refresh the destination instance with
Meldungsnr. SR053
Anyone able to tell me where to do this refresh? I'm new to PI 7.4 Java Only and could not find useful answers on SCN and other internet sources.
Thanks a lot in advance for any hints.
Renaud

Hi Iñaki
Great document btw... didn't stumble uppon this before. Thanks.
I carefully went through it but nothing I tried helped.
The RFC destination (PI -> ERP) is working fine.
The resource adapter (inboundRA) is configured correctly. I can confirm, that the connection test of the RFC-Destination inside ERP (ERP -> PI) is successful.
BUT still: sending an IDoc from ERP to PI fails with this message in SM58:
The IDoc Destination <destinationName> was changed. Refresh the destination instance with
Meldungsnr. SR053
This seems to happen every time after one changes some settings in the destination specified in the inboundRA property "destinationName".
So my question still is: how / where do I refresh this destination instance on a PI 7.4 Java Stack Only??? I mean without having to restart the whole PI instance...
Best regards
Renaud

ABAP Outbound Proxy: some messages stuck in CRM system

Hi all,
we've a strange issue with a ABAP Outbound proxy we've generated in our CRM 5.0 system (asynchronous interface).
Sometimes messages stuck in the CRM system. They are in status 'Scheduled' (green flag) in SXMB_MONI in the CRM system. When I have a look at the corresponding queue, there's no message within. Status in SMQ1 and SMQ2 is fine, too. All queues are registered. When I reprocess such a message manually in SXMB_MONI in CRM with the restart button, they're sent fine to XI.
Please note: it's NOT a general issue with that outbound proxy. In most cases the messages are sent immediately, just in some cases the messages stuck and I don't know why.
Is it possible to restart such messages automatically? I just know the report RSXMB_RESTART_MESSAGES, but that one just restarts messages in Error status. But the ones we have aren't in error status so they cannot be selected with that report.
Any idea where could be the problem / we should check?
BR
Holger

On which SP r u working correctly. May be an SP upgrade could help.
Regards,
Prateek

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

TNEF Issue - Winmail.dat or messages stuck in submission queue

Hi guys,
I've looked around the forums and have found people that have had submission queue issues when they set TNEF to $null or $false, and have found that the unified answer is to set TNEF to $true.
I also see folks having issues with recipients in remote domains receiving winmail.dat files in some instances (with a .pdf or .xls file attached) if TNEF is set to $true.
I have both issues. If I set TNEF to $true, I encounter the winmail.dat file problem. If I set TNEF to $false or $null, I encounter the submission queue issue (submission queue states "A transient storage failure occured", and users get a queue
expiration bounce). Neither of these states are acceptable. I cannot have messages stuck in the queue only to be expired, and I cannot have recipients in remote domains failing to receive attachments in emails.
Does anyone have a possible workaround that might resolve this particular situation? It seems that this has been an issue in Exch 2010.
Current Environment Configuration:
I am running Exchange 2013 SP1 Standard on both of my CAS/MBX servers, running on Server 2012 R2 patched to the latest updates. I have an inbound spam filter, but mail outbound is not filtered, therefore the spam filter on our side should not play a role.
I do have not made any changes to the exchange default malware filter either. Other than this issue, mail is flowing correctly and as expected.

I also see folks having issues with recipients in remote domains receiving winmail.dat files in some instances (with a .pdf or .xls file attached) if TNEF is set to $true.
Hi,
According to your description, my understanding is that all the remote domain's recipients would receive winmail.dat files when you send the message to them if TNEF is set to $true, right?
The Winmail.dat file is used to preserve Rich Text formatting. Outlook uses it when sending a Rich Text-formatted message. During transport, the content of the message may be changed, preventing the receiving client from being able to read the formatting
instructions. In other cases, the receiving client does not use or recognize the winmail.dat file.
I recommend that you refer to the following article to solve the issue:
http://support.microsoft.com/kb/278061
Method 1: Change the default message format
The sender can change the format of the email messages that they send by using the following steps:
On the Tools menu, click Options, and then click
Mail Format.
In Compose in this message format, click to select Plain Text, and then click
OK.
NOTE: To send to certain recipients that use RTF format and others recipients that use plain text format, the sender must set the option for the recipient in either the Personal Address Book or the recipient's contact record.
Method 2: Modify the recipient's entry in the Personal Address Book
The sender can use the following steps to remove the RTF format from the recipient attribute in the Personal Address Book:
On the Tools menu, click Address Book.
In Show Names From, click the Personal Address Book.
Select the addressee that you want to set as plain text, and then click
Properties on the File menu.
In the SMTP-General tab, click to clear the Always send to this recipient in Microsoft Exchange rich text format check box, and then click
OK.
Method 3: Change the specific contact format
The sender can use the following steps to set plain text in the recipient's contact record:
Open the recipient's record in the Contacts folder.
Double-click the recipient's e-mail address.
In the E-Mail Properties dialog box, click Send Plain Text only under
Internet Format.
Method 4: Set the Outlook Rich Text Format Internet e-mail setting
In Outlook 2003 and Outlook 2007, click Options on the Tools menu.
Click the Mail Format tab.
Click Internet Format.
Under Outlook Rich Text options, click either Convert to HTML format or
Convert to Plain Text format.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support
Niko,
The Winmail.dat issue is only part of the problem, as described in my original post. For these messages (which it's a different set of messages every time, and it's becoming impossible for me to track them all down), if I set exchange or outlook to encode
the message in Rich Text, the message gets encoded and sent to the recipient. Some of our recipients will reject the message because it is rich text, others receive a winmail.dat file.
However, if I set exchange to not encode messages (TNEF= $false or $null), the message becomes stuck in the submission queue and eventually times out with an error resembling "Storage Transient Failure".

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

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

JDBC Driver: Messages stuck in processing started at rwb

Hi,
I have ABAP Proxy (7.1 EHP1) -> JDBC (MS SQL Server) scenario.
I'm trying to do INSERT_UPDATE. The interfases works fine for the first 5 messages. If I check the DB I see rows inserted correctly, but the first five messages stucks in processing started, and the others JDBC messages stuck in Pending to be delivered The interfase is developed as asynchron, i'm not affraid in the response.
I tryed to do just an INSERT, send just one message, or change the isolation level. But the messages continues stucking in processing started status.
One of the lasts possibilities is transform the interface to sync or increase the max number of threads of queue "JDBC_http://sap.com/xi/XI/SystemRecv" via ConfigTool. But I can't stop the j2ee stack until next weekend.
The audit Log:
- The message was successfully received by the messaging system. Protocol: XI URL: http://sapdev:51000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
- Using connection JDBC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
- Message successfully put into the queue.
- The message was successfully retrieved from the receive queue.
- The message status was set to DLNG.
- Delivering to channel: CC_C0400_IM01_MES_INTEG
- JDBC Adapter Receiver processing started, required QoS ExactlyOnce
- JDBC Adapter Receiver Channel CC_C0400_IM01_MES_INTEG: processing started; party / service XXXXXXXXX_DES.
- INSERT INTO XXXXXXXXXX_TST (CodArticulo, Descripcion, EAN13, Vidautil, bolsasporestuche, estuchesporcaja, estuchesporpalet, gxu, UNISTK) VALUES (XXXXXX, XXXXXXXXX, , 270 , 1, 0 , 0.000 , 1000 , KG)
Maybe is a problem in DB side, but the experience tell me that is more inestable a SAP PI than MS SQL Server
Any Idea?
P.S. In the same PI is coexisting diferents JDBC interfaces that works fine. I have tried to use their channels but still stucking.
And this is not my first PI :P

Hi Xavier,
have a look at the documentation of this option:
db.autoCommit=NO|YES
Use this parameter to deactivate the logical unit of work required by the JDBC adapter to guarantee that the data in the database is consistent. This option is required for JDBC drivers that do not support transactions. To avoid data inconsistencies in the database when the logical unit of work is deactivated, ensure that multiple database transactions cannot access the database simultaneously.
The default value is NO.
Do not set this parameter to YES if the JDBC driver supports transactions, that is, if the system does not display a corresponding error message during normal operation.
Netweaver Documentation
I'm sure MS SQL Server JDBC Driver is able to support transactions. By default the whole message will be treated as one transaction against the database.
Regards
Sven

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

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

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.

Messages Stuck In Outbox Vanished Into Thin Air

I sent a bunch of important messages to my e-mail when browsing Safari, but for some reason they weren't going through and were stuck in my outbox.Now all of a sudden all those messages are nowhere to be found in my mailbox, and I know I didn't delete them.Would an update wipe them all out?Is there any way to recover them?I don't understand why all of a sudden they are gone.I have looked everywhere for them.

I had an excellent Apple support agent named Luis who helped out. Re-installed the account partially. Discovered that there is in fact a bug in Yosemite. The mail client in mac will not save the outgoing server address and confusion amongst different mail account happens, added to outbox messages stuck. Hopefully Apple will correct bug in later OS X version. Case number 753401346

Messages stuck in "Retry" in Submission Queue - Exchange 2013

Hello,
We have 2013 Exchange consisting of 2 CASs and 2 MBX servers spanning two locations via VPN, 1 of each server in each location. We are hosting exchange for an outside domain, and have just transferred them into our organization within the last month. There
are two users who consistently have messages stuck in the "Retry" status in the submission queue. Not all of their messages, but usually 2-4 are stuck and eventually kicked back to them.
I have read other forums about a potential issue with conversion to RTF. I have forced the queues empty and attempted this fix, but within a week the users had messages stuck again.
Has anybody run into this and possibly found a fix?

Thank you for all your replies.
It appears this issue has been resolved. At first I made the following change:
Get-RemoteDomain | Set-RemoteDomain -TNEFEnabled $False
Restarted Transport services on both mailbox DB Servers and the messages remained in the queue and more messages were getting stuck.
Then I made this change:
Get-RemoteDomain | Set-RemoteDomain -TNEFEnabled $True
Restarted Transport services on both mailbox DB Servers and the messages cleared from the queues and it seems no more messages are getting stuck as they were before.
I also changed the message timeout from 2 days to 2 hours. I'd rather know sooner than later that a message was stuck. I plan to continue monitoring this.
Thanks again.
Stop Stop Stop, this isn't a solution! Every single post I run into this answer, but it is a real crappy "solution". Simple: there is no solution yet, if everyone take this for an answer there will never we a good answer! This is a work around,
we got mails stucked in the queue for 2 months and it start with no reason. We have every update, enough disk space etc. Settinf the remote domain to true brings you the problem with Apple users and Gmail, hotmail etc. They will receive an email.dat or no
attachment when you send HTML mail. The False or Null is a future that make mail HTML so you can use signatures, pictures etc. It always worked, now only for 2 days and we must reboot again. Set de Remote domain to true we have problems with customers who
doens't receive their email correct!.
Microsoft please solve this problem and stop making crappy excuses or crappy workarounds, a solution is what we need!!!

Messages stucked at SM58

Similar Messages

Maybe you are looking for