Client Proxy - Message waiting in queue

Hi all,
I have a client proxy in R3 that sends information to XI. I see in XSMB_MONI a green flag, but in the field "status queue" appears a yellow triangle with the message "Message waiting in queue".
In Runtime Workbench I don't see any message.
Any help? I have to activate the queue?
Regards,

Hi,
Have u registered the queue in R3? If not....
1.Go to SXMB_ADM(R/3)
2. Go to Manage Queues and then
3. Register All Queues.
<a href="/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically Failed Messages</a>
Regards
San

Similar Messages

Message waiting in queue

Hi guys,
Im trying to connecting XI (integration server) to R/3 (Application sys) using ABAP proxy.
When the message enters in XBTO2___0002 (inbound queue) it cant leave there!!!
Queue status is: a yellow triangle Message waiting in queue.
I dont have any error messages, only this statusI dont know what happens!
Anybody could help me?
Thanks in advance,
Ricardo.

Hi Ricardo,
Try registering queues again...it worked for me for the same problem.
sxmb_Adm->mange queues->register queues..
Regards
Anand
Message was edited by: Anand Torgal

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

Client proxy message not reaching to XI system

Hi
I have done one scenario from CRM to FILE. When i am executing the client proxy through my zprogram its executing without any errors. I have checked in SXMB_MONI of CRD system i can see the messages but they are not with successful flag or not with error flag. But in XI system (SXMB_MONI) i didnt find any messages. Could you please tell me what's the problem is?
Regards
Sowmya

Sowmya,
As you are not getting any message in SXMB_MONI, there can be following possibilities:
1. There can be some problem in proxy configuration on your CRM system. Please check with your BASIS team that steps give in this blog are properly followed:
How do you activate ABAP Proxies?
2. Make sure that in
SXMB_ADM --->integration engine config -
>change specific attributes....
The RUNTIME parameter is defined LOGGING and TRACE_LEVEL and the value is 1.
3. Make sure the queues are registered in Tx: SMQR.
Further, I do not think that COMMIT statement or anything like that is missing as in that case you should have got a message in SXMB_MONI with a green flag stating that "Commit statement is missing".

ABAP Client proxy message not reaching AAE

Hi Experts,
I am facing a strange issue in one of my proxy interfaces. ABAP client Proxy is used to post message to AAE in SAP PI 7.3. The messages are being generated and pushed out of ECC successfully. I can see them in the SXMB_MONI t-code with checkered flag. These messages are reaching the Integartion Engine instaed of the Adapter Engine.
I have configured the following:
1. Sender / Receiver ID in SXMSIF:
2. Configured the corresponding Runtime parameter in SXMB_ADM
I have few other such ABAp client proxy i/f's which work fine and their message are being sent to the Adapter engine. Howveere, only this one interface is posing a problem. What can be the issue?
Please advice.
Thanks in advance.
Elizabeth.

Hi Elizabeth,
It will be great if you could please let me know all the user profile configured in userID of Logon&Security tab of SM59 for connecting ECC system to post the message via AAE.
I have used
SAP_XI_APPL_SERV_USER
SAP_XI_DEVELOPER_J2EE and
SAP_XI_IS_SERV_USER
profiles in my UserID for Basic authentication.
Currently I am doing the same scenario what you have done with integrated configuration.The message is getting failed in ECC with 403 Forbidden error.
Please help me.
Thanks
Ray...

Message waiting in queueu0085

Hi all,
During message process some messages stop in some queues with the message time limit exceeded and obstruct other messages to be processed. I need to delete the first queue entry to process the remaining messages. I dont want delete the block entry because one message is lost
I would like to know how I can fix this issue preventing an elimination of messages.
Thanks in advance,
Ricardo.

Hi,
Go through these links:
Message waiting in queue
Messages in BPM with Status Waiting
Message Queue in XI is stuck
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Hope these will be of help.
Regards,
Divija.

Waiting in QUEUE - client Proxy

I am executing client proxy. If I set the the execution mode to 'D', I have no issues, but If I set the execution mode to 'B' for my outbound queues (EO ), the queue is not executed. Message is set to 'READY' status (status text 'transaction recorded).
If i go and set the execution mode on the queue to 'D', the message is processed immediatly. This problem happens only when I am trying to execute with remote user id .
Any ideas?

Hi,
Check out for any dead lock.
Regards
Agasthuri Doss

Pending Messages waiting for Client Acknowledgement

          Hi,
          I have tried to search the Internet for an answer to this question but failed.
          Any clue???
          I have setup a queue on BEA WLS 7.4. I have four consumers which connect concurrently
          to dequeue messages. Each of the consumers serve as a proxy to other clients
          waiting for the messages.
          The proxy application (consumer) is developed such that it will send the client_acknowledge
          to the Q manager after it finishes processing the received message and sends it
          successfully to the external client.
          I noticed that in some exceptional cases which I cannot reproduce, the proxy application
          would fail to send the message to client and therefore wouldn't send the client_acknowldege.
          Although I tried to catch all possible exceptions, i cannot catch this single
          exception that causes my proxy to continue processing the messages in a proper
          way. The problem is that I end up with some Pending Messages on the queue which
          cannot be available to other consumers and would stay that way till the consumer
          that was attempting to dequeue it is killed.
          Isn't there any way to configure an expiry period for this client_acknowledge
          wait state??? In other words, is it possible to configure a time after which
          the JMS provider would no longer be waiting for the client_acknowledge and sends
          the pending message back to the Q in a state that makes it available to other
          consumers.


Sorry. Once a message has been received in "CLIENT_ACKNOWLEDGE" mode, it
          remains pending and unavailable to other consumers until either the consumer
          is closed, acknowledge is called, or the client disconnects.
          Have you tried using a transacted session? In that case, the transaction
          will time out eventually, which will roll back the transaction and make the
          message visible again. You can control the length of this timeout using the
          "TransactionTimeout" parameter on the JMS connection factory.
          greg
          "Muhannad" <[email protected]> wrote in message
          news:[email protected]...
          >
          > Hi,
          > I have tried to search the Internet for an answer to this question but
          failed.
          > Any clue???
          >
          > I have setup a queue on BEA WLS 7.4. I have four consumers which connect
          concurrently
          > to dequeue messages. Each of the consumers serve as a proxy to other
          clients
          > waiting for the messages.
          >
          > The proxy application (consumer) is developed such that it will send the
          client_acknowledge
          > to the Q manager after it finishes processing the received message and
          sends it
          > successfully to the external client.
          >
          > I noticed that in some exceptional cases which I cannot reproduce, the
          proxy application
          > would fail to send the message to client and therefore wouldn't send the
          client_acknowldege.
          > Although I tried to catch all possible exceptions, i cannot catch this
          single
          > exception that causes my proxy to continue processing the messages in a
          proper
          > way. The problem is that I end up with some Pending Messages on the queue
          which
          > cannot be available to other consumers and would stay that way till the
          consumer
          > that was attempting to dequeue it is killed.
          >
          > Isn't there any way to configure an expiry period for this
          client_acknowledge
          > wait state??? In other words, is it possible to configure a time after
          which
          > the JMS provider would no longer be waiting for the client_acknowledge and
          sends
          > the pending message back to the Q in a state that makes it available to
          other
          > consumers.

ABAP Client Proxy from ECC 6.0 to XI message irregular recieving

Hi Gurus
Any one has come across issue whereby the ECC 6 system trigger ABAP Client proxy to SAP PI 7.0. The first time the PI is able to recieve it in the SXI_MONITOR. But subsequent trigger from the ECC 6.0 system the SAP ABAP program to trigger the Client Proxy, the PI seem to lost connectivity and did not recieve any message. This is pretty strange and hopefully someone in SDN and enlighten me.
Thanks
Regards
On behalf of malcolm

Hi Santosh
I went to SMQR and register the queue, but it still did not reflect the locked queue when i trigger the ECC 6 to SAP PI 7.0. The green flag - schedule still appear in the SXMB_MONI queue. But i am quite puzzle as why the ABAP client proxy after sending message the first time and second time, the third time it stuck? And also it is not practical to everytime go to the SMQ1 or SMQ2 to unlock the queue. I don't think it a good solution for solving my problem, it is just a temporary solution.

Async ABAP Client Proxy Queuing

Hi all,
We've successfully set up an asynchronous ABAP client proxy on a WAS 6.20 instance to connect to our XI 3.0 box. Our concern is if XI is down the messages won't get queued up for delivery. As I understand it, failed messages won't get queued up for delivery if a delivery error occurs. Is this correct? If queuing is not possible with a standard WAS 6.20 installation, what options do we have to make queuing possible?
Many thanks,
--jtb

I believe queuing should be supported on a WAS 6.20 system so long as you have installed APPINT 200_620 (XI 2.0 add-on), SL 6. You need level 6 in order to communicate with XI 3.0 (or at least that's how I understand it). This above mentioned add-on is a basically the ABAP side of a 2.0 integration server. In our scenario we set the role of the business with the 2.0 add-on as an application server.

Proxy messages not processed in PI 7.1 pipeline coming from local client

Dear experts,
We have recently installed a PI7.1 system with two clients:
200 - Integration Server
250 - Local Integration Engine
Now, when we send proxy messages from the 250 client to the 200 client,
the messages are not processed in the integration server. The message
does arrive as we can see in SXMB_MONI, but there is no receiver determination
or what-so-ever executed. In SXMB_MONI we can see that only the SENDER
pipeline is executed.
Proxy messages from 6.20 and 7.0 systems to IS are properly processed.
Ofcourse the 250 client is defined as an application system in the integation engine
configuration (SXMB_ADM).
regards,
Jeroen

In SXMB_MONI we can see that only the SENDER pipeline is executed.
Yes. Even if no receivers are configured the data from sender to XI should be visible in sxmb_moni.
Check smq1 at XI. There could be some problem with the technical system for client 250.
Regards,
Prateek

Messages waiting indefinetely in queue -- how to purge

Hi All,
I have around 900 messages in the outbound queue waiting in the past 2 days .
Is there any way to purge sceduled messages in the Queue (SMQ1,SMQ2)?
My messages are indefinetely growing in the message queue without processing. I understand I need to configure a background job for that.
Which transaction code should i use to schedule Backgound job for Messages ( not BPM) ?
Is there any way I can purge these messages from the queue before they get processed by XI?
if yes please let me know the way.
Because of this a scenario I run today is scheduled in the queue after 3 days and my receiver is unable to get the message.
Regards,
Meher

Hi All,
Thanks All for helping me.
Initiated a search for all the messages waiting on all the Queues.
Status of all the messages shows : <b>To Be Delivered</b>
Messages were processed successfully till some date. we have a system down after that.
From then on messages are not being processed.
Am I missing in the job configuration for the Queues.
Queue status is displayed as Ready ( no errors)
Regards,
Meher
This is not a production environment.

Fault message handling in abap client proxy

Hi experts,
i have scenario like this SAPECC---XI---WEBservice
i was decided to using the ABAP CLIENT proxy in sender side and soap adapter communication in receiver side
i will be get the wsdl file form client
problem is i am in bit of confusion like am i need to create fault message for this asychronous scenario?
how can i create the fault message for this scenario(that WSDL) and how the abaperwill handle those error
thanks in advance

Hi.
You can use fault message but it won´t return a error to your ABAP Proxy because your interface is ASSYNC. The fault message generated will stop in Adapter Engine.
If you need a return of the error, you have to change your interface to Sync mode.
To get more information, follow the link below:
Fault Message Type
http://help.sap.com/saphelp_nwpi711/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm
Best Regards.
Bruno

Http- XI-Proxy. Message stays in queue.

http->XI-Proxy async scenario. Message stays in queue in targret system.
(see screenshort at http://wapman.ru/screen.png).
When i click the name of queue and start processing manually, then everything works. Why message is not process automaticaly?

also you can register the Q's thru SMQR in XI box
regds
Prabhu

ABAP client proxy send message fialed

I developed one ABAP client proxy to send msg. status in SXMB_MONI is error.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
After I test it in RWB,I'm sure that IR and ID is right. Then what's wrong?

> There are two scenarios with the same outbound interface.Is it the problem?
>
> ABAP proxy send message, and then there are two route.
Yes this could be the reason, because at the time of Receiver Determination it tries to send the message to both the interface. Are both the scenario Proxy to XI??
Try to change the Message Interface in IR and accordingly change in ID also and then try.
Regards,
Sarvesh
Edited by: Sarvesh Singh on Oct 17, 2008 2:24 PM

Client Proxy - Message waiting in queue

Similar Messages

Maybe you are looking for