SXMB_MONI message fail causing Queue struck at SMQ2

Hi All,
If mapping error occured in SXMB_MONI, corresponding entry will be struck up in SMQ2 and saying that SYSFAIL.
When i drill down this into further, it is saying that Mapping error.
Because of this all messages coming later also getting strucked in this queue.
Why is this happening and what to do for not to get struck further messages
Regards

Hi Hetal,
>>Create a job which will restart message after some time if it is stuck because of connection problem or something, then queue will be clear.
It's because of Mapping problem, even though we schedule a job to restart, it won't resolve. again it comes into same error.
@Prateej:
>>Could you check the QoS for the following entry in SXMB_MONI? Is it EOIO ?
QOS is Exactly Once
@Madu:
>>This is the standard behavior of PI. When some message will fail in Integration Engine(either because of Receiver not found or mapping error),some of remaining message(not all messages) which will come in the same queue of failed message will stuck.
You can not predict which messages will stuck and which messages will not stuck.
YES, you are right.
>>If you are having some important interface, which you want to divert the messages in other queue. You apply exactly once in order in sender channel for other interfaces so that these messages will not stuck in SMQ2.
For me all are Important Interfaces only. I can't prioritize
I think the better solution is Monitor failed messages in MONI every day and if it is failed because of Mapping error means, we can delete that entry from SMQ2.because for mapping related errors we don't require that message to restart again.
so that nothing will be queued after wards.
Regards

Similar Messages

BPE crash - Trying to remove work item and SXMB_MONI message that caused it

Hi,
I have a file to IDOC scenario with BPE. We have had a large file that was picked up by XI in error, but the adapter engine did process the XML conversion successfully. This message was sent to the BPE but due to the message size, the BPE crashed. Currently the work flow that caused the crash is in started status in report RSWF_XI_SWPC - continue workflow after system crash. and we have a message in SXMB_MONI for this workflow that is still in status outbound to PE "message being sent". We would like to remove or cancel the workflow and the message in XI. I have searched around for the best way to do this in this situation but have not found anything. We cannot cancel the message in SXMB_MONI due to the status it is currently in. Can we:
1. stop and start BPM to resolve the issue or
2. some how change the status of the workflow to error so the message in SXMB_MONI can be cancelled.
3. Should we just leave the work item and messge as is, because it is not affecting anything else in XI.
Any help would be apprecieated.
thanks.
Jamie
Edited by: Jamie Bullen on Jan 22, 2008 4:04 PM

Hi,
Thanks for your reply. I'm pretty sure I can delete the work item from SWWL but I don't think the outbound status of the message is SXMB_MONI will change once this is done.
thanks.
Jamie

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

3 Messages getting struck in SMQ2 at same time with difference in seconds

Hi all,
Three EOIO messages with Queue name QBTJ.......................(same Queue id for 3days)
that is day1 QBTJ(message (a) queue id=day2 QBTJ queue id=day3 QBTJ queue id
day1 QBTJ(message (b) queue id=day2 QBTJ queue id=day3 QBTJ queue id
day1 QBTJ(message (c) queue id=day2 QBTJ queue id=day3 QBTJ queue id
.These are getting struck in smq2 at same times (compared the timings 3 days).the time at which these messages are getting struck are same with the difference in seconds.
Other than these 3 different times ,these messages are moving with out strucking in SMQ2.
I have two questions here
1)what could be the reason for only these three messages are getting struck in smq2
2)is there any parameter which could be set in SXMB_ABMIN to unlock the queue automatically with out going to smq2 and manually unlocking.
Please do not send nonrelavent blogs
Thanks,
Srinivasa

Hello,
you can schedule the report RSQIWKEX in your XI system. This report does automatically unlock all queues.
See the blog for more details.
regards,
Björn

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

Putting message into send queue failed

Putting message into send queue failed, due to: com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id 8fd8ebf2-14dc-498c-26d4-fa83a612df8f(OUTBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: Violation of PRIMARY KEY constraint 'PK__BC_MSG_DUP_CHECK__0CB1C3F7'. Cannot insert duplicate key in object 'SAPPIQDB.BC_MSG_DUP_CHECK'..
I get the above error for one of my interface.
The scenario is simple lift and shift using integrated scenario.
I am unable to figure out reason for the above error.
Regards,
Lalit Mohan Gupta.

Hi Lalit Mohan Gupta,
It seems like you have a problem with duplicate Message IDs (GUID). This can happen if you do not let SAP PI generate the message ID for the message being processed, but is relying on an external system to provide you with the message ID.
In any case. I don't think you will succeed with getting the message processed, because of the duplicate message ID constraint in SAP PI. But you need to be aware that depending on how your SAP PI has been setup to handle archiving/deletion of messages in Java-stack, you could potentially run into the situation, where SAP PI removes the initial message from its database and by that enables processing of the duplicate message ID.
Best regards,
Jacob

** Message being processed - Queue status green colour

Hi Friends,
Many messages in our SXMB_MONI shows green color in the queue id column. It shows 'Message being processed'. All messages are in queue, still they are not delivered. Processing takes more hours. These messages are not EOIO queue. While we check this thru SMQ1 and SMQ2 it shows 'Running'. So, what could be the problem ...?
Kindly help friends, to solve this issue. (Points rewarded for helpful answer)
Kind Regards,
Jeg P.

HI,
QUEUE STATUS RUNNING BASICALLY MEANS THT
The first LUW of this queue is currently being processed. If a queue in this status hangs for more than 30 minutes, this may mean that the work process responsible for processing this LUW has been terminated. In this case you can activate this queue again. Note that activating a queue in status RUNNING may cause a LUW to be executed several times if this LUW is still being processed in the target system at that time. We therefore recommend a waiting time of at least 30 minutes before you reactivate the queue.
HOPE THIS WILL SOLVE THE PROBLEM
PLZ REWARDS POINTS
VIKAS

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

BPM wait step : RWB"To Be Delivered status": SXMB_MONI"Message being sent"

Hi All,
I have a BPM interface running fine since 1 year.
In this BPM I have wait step for 5 minutes.
But yesterday message is stopped on wait and not proceeding ahead.
I checked XML is good as per mapping. and in runtime wirk bench message is still in "To Be Delivered status"
and in SXMB_MONI message column Outbound Status still showing "Message being sent" even after 12 hours.(wait is only 5 minutes). And below is the trace of last message.
Please guide how to handle or restart this message. in SMQ1 & SMQ2 there are no queues showing:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface Request_SI</Trace>
<Trace level="1" type="T">select interface namespace https://www.XXXXX.com/YYYY</Trace>
<Trace level="1" type="T">--start determination of receiver interface action</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface Request_SI</Trace>
<Trace level="1" type="T">select interface namespace https://www.XXXXX.com/YYYY</Trace>
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
</SAP:Trace>
Regards

Solved, few BASIS jobs were inactive in transaction code "SWF_XI_CUSTOMIZING".

Error"XI Error CLIENT_RECEIVE_FAILED.INTERNAL: Queue sto" in SMQ2

Hi,
When i am trying to test my JDBC to ABAP Server proxy i am getting the error(XI Error CLIENT_RECEIVE_FAILED.INTERNAL: Queue sto) in SMQ2 please advice me what could be the problem?
Regards,
Bhoj

Hello better you apply LUW on each and every message in SMQ, queues. Else activate and inactivate the messages in the queue by sxmb_adm -> managequeues -> deregisterqueues -> registerqueues -> activate queue.
And also do if any messages are failed follow the blog to resend the failed messages,
XI : How to Re-Process failed XI Messages Automatically

Error in sxmb_moni : message scheduled

hi,
   in sxmb_moni , i get the status messasage "scheduled".
my queue status is "message waiting in queue".
my receiver field is empty.
      can somebody help me to solve this problem.
thanks in advance,
      disney

Hi,
If u want to manually unlock then u need to go to transaction SMQR,SMQ1,SMQ2 for queue management. There u have to select the queue and activated all entries.
SMQ1 qRFC Monitor for the outbound queue You use this transaction to monitor the status of the LUWs in the outbound queue and restart any hanging queues manually.
SMQ2 qRFC Monitor for the inbound queue. You use this transaction to monitor the status of the LUWs in the outbound queue.
U may schedule the report RSQOWKEX (Outbound Queues) and RSQIWKEX (Inbound Queues) to restart the queues automatically.
After that please register the queues via t.code sxmb_adm where u have an option manage ques.
Once you register the queues, they default activated.
Regards,
Pradeep A.

Messages failed in

Hello All,
Around 400 messages failed in Outbound queue of IE in SAP PI. All these messages are going towards SAP.
The reason behind the failure is connection issues with the SAP.
Question is, Is it possible to resend all these messages from PI once SAP is availble?
Regards,
Moorthy

Hi Dasika,
You can resend the messages from Runtime workbench , or SXMB_MONI also (there is an option to resend manually), if the number of message is large , you can shedule a batch job.
Could you please look at this blog /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically if it helps you .
please refer similar posts
Collect and Resend messages when SAP(R/3) is unavailable
During SAP outages,XI unable to send the IDoc to SAP System.
Regards,
srinivas
Edited by: Srinivas on Apr 2, 2010 9:56 AM

** How to stop a particular queue completely in SMQ2 tcodes

Hi,
I have nearly 6000 messages in various queues in SMQ2 tcode (Inbound queues). For example,
XBTO1_0001    1875
XBTO1_0002    2335
XBTO1_0002    1770
Messages are processed slowly. When we tried to stop a queue, only one message is stopped in the queue. Instead we want to stop complete 1 queue. Then, we feel that remaining queues will work fase. So, how to do this ...?
Kind Regards,
Jeg P.

Hi,
1) Why the queue XBTZ is not displayed in SMQR tcode ? (But, it is* displayed in SMQ2)
--->are you sure that the queue XBTZ* is active. Because in SMQr you could see the queues which are active and are already registered.
Re register the queues and make it active.
Try to make the ragistration of queue "XBTZ*" in SMQR.
Press directly Registration tab and rgister the queue then deactivate it.
http://help.sap.com/saphelp_nw04/helpdata/en/59/d9fa40ee14f26fe10000000a1550b0/frameset.htm
Go to SMQR and check the Scheduler Status i.e first line of the Screen. If it is Wait or any other status, then make sure that all Queues are registered.
Also.
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
2) If we 'Deregister' the queue, any effect will come for the new messages ?
If we Deregister the queue then the queue is no longer processed.
http://help.sap.com/saphelp_nw04/helpdata/en/29/595f3ca0dd9770e10000000a114084/frameset.htm
thanks
Swarup

Fail to Queue to SG

Hello,
I am working on a new scipt and attempting to queue calls to a skill group, however they are failing the queue to skill group node.
In the CVP logs I see an invitation rejected message with 404 not found.
Would this be caused by a missing route in CUPS or CVP?
Thanks!

Hi Candese,
I hope you have configured the agent IP extension as "7006570" in CUCM. However, as you are using "000" as sigdigits,the SIP INVITE from CUSP to CUCM would be "0007006570".
Which does not exist in CUCM and its is sending back "404 not found" SIP error.
Strip the "000" in the SIP trunk to fix it by setting the incoming digits parameter on the CUCM SIP trunk to "7".
HTH
Regards,
Thammaya Gupta K.

Error while trying to pick message from weblogic queue

Hi,
We are getting the following error while trying to connect to pick up a message from weblogic queue.
We are suing oracle soa suite 10.1.3.1 and weblogic 8.1
the bad part is that, this error is not documented anywhere and couldn't get much help on this.
Would appreciate any suggestions / pointers on this.
Let me know if any further information is required.
invoke failed
org.collaxa.thirdparty.apache.wsif.WSIFException: file:/E:/product/10.1.3.1/OracleAS_4/bpel/domains/default/tmp/.bpel_OTOCBPELProcess_1.0_78fcf080ec2bd7495aebfb5373e76116.tmp/readmsg.wsdl [ Consume_Message_ptt::Consume_Message(opaque) ] - WSIF JCA Execute of operation 'Consume_Message' failed due to: ERRJMS_IX_WRONG_SPEC.
Outbound interaction invoked with incorrect InteractionSpec.
; nested exception is:
ORABPEL-12115
ERRJMS_IX_WRONG_SPEC.
Outbound interaction invoked with incorrect InteractionSpec.
---------------------------------------------------

Hi!
I am facing a similar issue, does someone have an idea ?
<remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="code"><code>null</code>
</part><part name="detail"><detail>null</detail>
</part><part name="summary"><summary>file:/opt/oracle/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_TestReceiveMessage_BPEL_1.0_e00fd88d454889b871183d0d92dc9f7d.tmp/plReceiveMessage.wsdl [ Consume_Message_ptt::Consume_Message(TestPushMessage_BPELProcessRequest) ] - WSIF JCA Execute of operation 'Consume_Message' failed due to: ERRJMS_IX_WRONG_SPEC.
Outbound interaction invoked with incorrect InteractionSpec.
; nested exception is:
ORABPEL-12115
ERRJMS_IX_WRONG_SPEC.
Outbound interaction invoked with incorrect InteractionSpec.
Please examine the log file to determine the problem.
</summary>
</part></remoteFault>
Thanks,
romain.

SXMB_MONI message fail causing Queue struck at SMQ2

Similar Messages

Maybe you are looking for