Message is getting struck in outbound queue

Hi All,
I am doing a simple FILE to FILE scenario . The message is getting struck in SMQ2 (inbound queue). If i go to inbound queue and manually UNLOCK the queue entry then only the message is getting delivered . This is a new installation and we are on PI 7.0 .Please let me know if we have to so some configuration .

Hi !
Check if your queues are registered in the SMQS transaction (for outbound queues) or SMQR (inbound). Go there, then enter the queues you need or reactivate them. They should be activated to process the message automatically whenever they receive something.
Try this:
http://help.sap.com/saphelp_nw2004s/helpdata/en/96/8412417301ee6fe10000000a1550b0/frameset.htm
Regards,
Matias.

Similar Messages

Message should get generated in outbound program when idoc is posted in ot

Dear All,
Can anyone please tell me,how i can send response back to the idoc program.
Requirement: Outbound program will generate an idoc and when it gets posted in the other server a message should appear that idoc was posted in other server...
Now can anyone tell me how i can do this,i mean message should get generated in outbound program when idoc is posted in other server..
warm regards
Sajid

hi,
Go through the following thread
iDoc - XI - iDoc with Acknowledgement
Regards
Mudit

Need to raise an Alert for huge Volume of messages struck in the queue

Dear All,
I have a query which is mentioned below.
The Partners send huge number of volume of messages at a time to PI Server and due to this reason,the messages are getting struck up in the inbound/outbound queue.Everytime the user manually check for the struck up messages and reprocess it.
Example: One Partner sends 50,000 number of ORDERS at a time.
Now an alert needs to be raised for those messages which got struck up ( i.e. messages on hold and "not failed") in the queue.
Please share your inputs /suggestion.
Warm Regards
B.Dheepa

Hi,
Else you can implement the Logic in this blog
XI : How to Re-Process failed XI Messages Automatically
You can Schedule the Strandard Reports to release automatically the Strucked messages in Queues
Regards
Seshagiri

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

QRFC outbound queue

Hello all,
In the outbound queue of a R3/ECC system, I find messages with status as "Message edited in the target system".
What could be reason for this and what is the work around to solve this problem ?

Hi,
Did you get resolutoin to your problem here? We have BI queues in ECC which have been running just fine for over a year now and out of no where this just started happening to one of our LO extraction processes in ECC. We have raised our issue to SAP but at this point can not find any notes pertaining to this type of message being in a ECC outbound queue for BI.
thanks

How to clear outbound Queue in SXMB_MONI

HI Experts,
Unable to process the file in SXMB_MONI as a result the files are getting strucked with the QUEUE and now how to clear this queues for processsing the file...
and another i have configure the server with 611 client but while executing the client of the server is showing 001 and we didn't observe initially as it is working fine but when we observed now it is found
is this has an impact..
do we need to do any other certain configurations at the Server end..
regards,
Kishore

> There is no URL in SXMB_ADM, how to provide an url there, and even before we didn't get this problem as the files are successfully processsing for the past 3 months in PDN, and now we are getting this problem.
>
Hello,
I have understood your problem but you are not following the steps which we are mentioning here.
For your above problem you need to follow ONLY step no1 & 2 mentioned in the blog since steps are common for acitvating the proxy and thats way you are getting confused that why I am asking you to follow that blog.
In the blog step 1 will simply help you creat the RFC destination.
Step 2 will help you to use the above RFC destinaiton as an url.
In opionion if you resolve this problem first then it will be easier to solve your queue problem.
Please let me know if you need more help/clarification in this regard i will help you.
Regards,
Sarvesh

URGENT------Two Messages Fired Simultaneously get struck in Queue

Hi,
I am using WebLogic 8.1. In my application, I am using Message Driven Bean which listens to a Queue and when a message is found, it calls a web-service client to do further processing. There are two problems I am facing:-
1.) When there is any error from web-service, the message still keeps pending in Queue. If count gets high, the application slows down. Is there any way that if further processing fails, message gets destroyed from queue.
2.) When more than one Messages are fired simultaneously in Queue, they somehow get stuck up and no calls to web-service is made. They remain in pending state in Queue. How to do proper settings so that as many as many as 10 messages are getting handled simultaneously.
Any help will be greatly appreciated.....Can anybody tell me how to cofigure my queue / tune it for better performance.
Thanks

Check the status of your multi-thread. Sometimes it might be because of the multi-thread implementation neither JMS nor the application server.

Middleware problem -Outbound queue is stuck in SAP R/3 system with message

Hi Middleware gurus ,
We are stuck with a serious issue . We are trying to download Business partners from SAP R/3 4.6c system to SAP CRM 5.2 system using CRM Middleware
Previously we did a successful Initial download of 2 Business partners from SAP R/3 to CRM . Their BP numbers in CRM are 001 and 002 . The Delta load is working fine for the both the BPs which are already downloaded
Now , the real problem is when we are trying to download a new Business partner . When we set the Filter ( BP no 003 ) in MW adaptor object CUSTOMER_MAIN and start the Initial load again , we see that the Outbound queue is getting stuck with message STOP .
There are two queues generated in SAP R/3 system with names MASS_CRM_CUSTOME and R3AD_CUSTOME . The status for both the queues is STOP and when go for details it mentions sapsuck ..SAPMSSY1 -Message no. SR 053.
Even we checked the txn SMW01, the Bdocs message is "Recived ( Intermediate state) " for Bdoc type BUPA_MAIN.
We really dont as to why the Initial load worked fine with 2 BPs and later when want to do more BP Initial Load the Outbound queue is getting stuck
Also , by unlocking the 2nd queue R3AD_CUSTOME we are able to release it , but the first queue MASS_CRM_CUSTOME* is stuck
Please help us urgently
Regards
Dinesh and Ritvij
Email : [email protected]
Mobile -+91=9704933315

Hi Praveen and other Middleware gurus,
We checked on this . Actually the RFC is used for connecting to SAP R/3 system.
We also raised an OSS message on this and found a reply that in transaction CRMM_BUPA_MAP, we can map the required BP . But the SAP support guy recived an error received the error:
An RFC link is not maintained in the Middleware
Message no. CRM_BUPA_MAPPING051
We have set the RFC link , but still the problem continues!!!
Please help further..
Regards
Dinesh and Ritvij

Client proxy message strucked in ECC queues

Hi All,
I am working on Proxy interface. My interface is like below
ECC 6----
>PI (7.1) -
>File
I had done the entire configuration in ECC and PI for proxy activation. While testing the interface in ECC system messages processed successfully, but the message strucked in queues (SMQ2) in ECC system. If run the queue manually the message processed successfully to the PI.
Can you please tell any more configurations required?
Regards,
Ramesh

Hi,
The queue used for Proxy call is not registerd in ECC system. You need to register the queue to process successfully.
you will get the name of Queue from SMQ2 t-code and register it with t-code SMQR.
Thanks
Swarup
Edited by: Swarup Sawant on Aug 24, 2009 8:03 AM

Struck up with R3AD_* Queues in SMQ1(Outbound Queue in ECC Side)

Hi ,
I am using CRM Middleware for replicating business partner(BP) from CRM to ECC
and material from ECC to CRM.
BP and Materials are replicating well.
My Issue is,
while checking queues in SMQ1 (Outbound Queue in ECC Side), i am getting many queues are pending also
status as "SYSFAIL".
QUEUE Names are R3AD_000000123,R3AD_000000139,R3AD_000000141... R3AD_*,etc..
I tried to unlock the queues and activated, afterthat also queue status is "SYSFAIL". Then i checked in CRM side
Transaction Code SMW01,
BDOC Details:
BDOC State Description: Information no processing.
BDOC Type :BUS_TRANS_MSG.
ERROR Message:
a.Processing of document with GUID 4E57E4A5108162A7E10000000A0BE02A is canceled.
b.Business transaction type ZEQQ does not exist.
c.Validation error occurred: Module CRM_DOWNLOAD_BTMBDOC_VAL, BDoc type BUS_TRANS_MSG.
Thanks and Regards,
Ravi A

Maintain a filter in ECC go to Tcode SM30 , then go to table/view and enter CRMRFCPAR click maintain and enter
User CRM
Object Name SALESDOCUMENT
Destination xxxxxxxxxxxx
Load Type delta download
Queue Name
Queue Name
BAPINAME
INFO
InQueue Flag X
Send XML
CRM Release 700
Logical system xxxxxxxxxxx
this will stop the flow of ecc sales documents to crm
this will also stop Bdcos in SMW01
Please let me know if this helped

Queue is getting struck for every delta change in CRM 5.0

Hi Middleware gurus,
The queues are getting struck with status 'READY' for each of these following scenarios:
1. Individual new sales order upload from CRM to R/3 (CRM - SMQ1)
2. Individual sales order delta changes upload from CRM to R/3 (CRM - SMQ1)
3. Individual new materials donloaded into CRM from R/3 (CRM - SMQ1)
4. Material delta change download from R/3 to CRM (CRM - SMQ2)
5. Knowledgebase delta changes download from R/3 to CRM (CRM - SMQ2)
I have to manually release the queue everytime, so that the changes can be uploaded. Am I missing something?
By the way individual new sales order created in R/3 and delta changes on R/3 orders are getting replicated into CRM without any problem.
Thanks,
Kishore

Hi Kishore,
We had similar issue before. Do not use the replication scenarios X,Y or Z. You have use the scenario A which will solve your problem for sales order replication issues. Please refer to the note 705200. For rest of issues make sure in both the systems the queue scheduler is running. If not running actively then register the each queue in both the systems using SMQS and SMQR. If still the issue is not solved then let me know.
Award points, if the issue is solved
Cheers,
Paul Kondaveeti

Message getting stuck in XBQO queue - Time limit exceeded

Hi All,
We have a BPM scenario in our project (on PI 7.0 SP18), where bundle of PEXR2002 Payment IDocs are received as a single flat file. This file is then consumed by the BPM, to split the message into multiple payments using Java Mapping.
However, when we get an IDoc file of size greater than 5 MB (more than 500 IDocs), the message gets stuck in XBQO queue and eventually giving a SYSFAIL with the message "Time limit exceeded". Could you please let us know if you have encountered a similar issue and are aware of a possible solution.
Any pointers to this will be really appreciated.
Thanks & Regards,
ROSIE SASIDHARAN

H Rosie,
1) Goto SXMB_ADM-> Integration Engine Configuration->Parameter EO_MSG_SIZE_LIMIT->possible values 0 - 2,097,151 (KB)
The parameter EO_MSG_SIZE_LIMIT enables serial processing of messages of a particular size. This applies for messages with the quality of service Exactly Once (EO). If the message is larger than the parameter value, the message is processed in a separate queue.
2) Goto SXMB_ADM-> Integration Engine Configuration->Parameter HTTP_TIMEOUT->possible values n Seconds, where n is a whole number.
The parameter Specifies the timeout for HTTP connections (time between two data packages at line level). This value overrides the system profile parameter icm/server_port_n (for example, icm/server_port_0 : PROT=HTTP, PORT=50044, TIMEOUT=900). If you do not set the parameter HTTP_TIMEOUT or if you set the parameter to 0, then the setting for the system profile parameter is used.
See SAP Note 335162 for sysfail issue....
Hope these will help u....
Regds,
Pinangshuk.

MDB messages dont get processed from Queues when involving a remote Topic in transaction

Using WLS 6.1 SP4 on winXP Pro boxes, I have come across a peculiar problem:
          I have several MDBs that process ObjectMessages from queues and forward their payload (wrapped in another new ObjectMessage) to other queues, all of which are located within the same WLS server.
          Right now I'm adding a new MDB that gets messages from a remote Topic with a durable subscription, and forwards the payload to local queues after some processing.
          When the Topic is local as well, there is no problem. But when the Topic is set up in a remote machine, only the MDB that has the remote durable subscription works the way it should. It receives the remote message and forwards it to the corresponding local queue. But then the messages in those local queues dont get processed. The 'Messages Received' count rises and the 'Messages' count stays at 0, as if the messages had been correctly processed and acknowledged, but no onMessage() method is called besides the one from the MDB that has the durable subscription to the remote Topic (I can tell because there's no further processing from the queue those messages get put in). It's as if those messages were simply received and acknowledged without being passed to other MDBs by WLS.
          * All queue MDBs use Required container-managed transaction management and auto-acknowledge
          * All queue MDBs have default durability for their queue subscriptions
          * The topic MDB has a durable subscription stored in a filestore
          * Lookup of the remote Topic is done via JNDI
          Since the processing and forwarding of messages occurs the way it should when everything is local, I am inclined to believe one of two things:
          a) There's some issue with the way WLS treats messages (or even just payloads) when they come from a remote server
          b) WLS is doing something I'm not aware of when propagating a transaction that begins with the delivery of a message from a remote JMS Topic when it involves further forwarding of messages in local JMS Queues.
          Any help will be appreciated.
          regards,
          .munir estevane


Is the durable subscriber forwarder rolling back its transactions?
          That would cause the behavior you describe (eg the message gets
          placed in the queue, but is never made visible). What do
          the pending counts on the destination queue look like?
          Munir Estevane wrote:
          > Using WLS 6.1 SP4 on winXP Pro boxes, I have come across a peculiar problem:
          >
          > I have several MDBs that process ObjectMessages from queues and forward their payload (wrapped in another new ObjectMessage) to other queues, all of which are located within the same WLS server.
          > Right now I'm adding a new MDB that gets messages from a remote Topic with a durable subscription, and forwards the payload to local queues after some processing.
          >
          > When the Topic is local as well, there is no problem. But when the Topic is set up in a remote machine, only the MDB that has the remote durable subscription works the way it should. It receives the remote message and forwards it to the corresponding local queue. But then the messages in those local queues dont get processed. The 'Messages Received' count rises and the 'Messages' count stays at 0, as if the messages had been correctly processed and acknowledged, but no onMessage() method is called besides the one from the MDB that has the durable subscription to the remote Topic (I can tell because there's no further processing from the queue those messages get put in). It's as if those messages were simply received and acknowledged without being passed to other MDBs by WLS.
          >
          > * All queue MDBs use Required container-managed transaction management and auto-acknowledge
          > * All queue MDBs have default durability for their queue subscriptions
          > * The topic MDB has a durable subscription stored in a filestore
          > * Lookup of the remote Topic is done via JNDI
          >
          > Since the processing and forwarding of messages occurs the way it should when everything is local, I am inclined to believe one of two things:
          > a) There's some issue with the way WLS treats messages (or even just payloads) when they come from a remote server
          > b) WLS is doing something I'm not aware of when propagating a transaction that begins with the delivery of a message from a remote JMS Topic when it involves further forwarding of messages in local JMS Queues.
          >
          > Any help will be appreciated.
          >
          > regards,
          > .munir estevane

***Raising Alerts When the message is struck in the Queue

Hi Experts,
Is there any way of Raising Alerts When the message is struck in the Queue I want to notify the user if the message is struck in Queue(smq1,smq2).Please let me know the same.
Thanks,
Srinivasa

hi
you can trigger alert for any of the component failure.
for this u nees the ccms configuration.
than you need to configure in RZ20 and RZ21.
steps.
1. create alert category in ALRTCATDEF
2.enter long text
3. add fixed recepient.
4.go to RZ21.
5. select display overview for method
6. serch for method CCMS_Send_Alert_to_ALM.
7. copy the method and create ur own Z method.
8. open ur method.
9. under control tab select ONLY IN CENTRAL SYSTEM TRIGGERED BY CCMS AGENTS.
10. in parameter tab give ur alert cat created before.
11.under release tab select AUTO REACTION METHOD.
12. go to RZ20.
13. a list of system will be displyed select ur own xi system
14. now select the queue name for which u want to trigger alert.
15.goto property button and double click.
16. go to method tab and click on method assigment.
17. goto method radio button and assigne the method u created in RZ21.
done.....enjoy....
u can check the log in slg1 tcode
regards,
navneet

Reg:Outbound Queues are strucked in CRM

Hi All,
After Extracting Data from CRM source system,the rercords are still displaying in the outbound queues of the CRM Source system.what might be the issue?In outbound queues the status is NOSEND or is it maintaining one more copy of the records.what happens manually if the queues are deleted.if any queues are deleted the posting to BI is stopped.If any data is missed by deleting the queues ,shall we recover the data back.what are the steps to schedule the those jobs in BI.
Thanks & Regards,
MD.Kalim.

Hello,
I would check the customizing in SPRO. It seems that your System is customized to distribute billing numbers.
My guess is
Customer Relationship Management
Billing
Country-Specific Functions
Official Document Numbering
Transfer Official Document Numbers to Accounting Documents
Check whether there is an entry somewhere there forcing the System to behave the way it does.
Lutz

Message is getting struck in outbound queue

Similar Messages

Maybe you are looking for