SMQ2 Queue status stay 'Ready'

hi all,
    In our R3 system, all the queue was stuck in 'Ready' status.
    We found something strange that if increasing the diag process number from 18 to 25, the queue will be running well. But in SM50, we found many diag process are free.
    Can some body tell me why?
     Regards,
     Terry

Hi
We got it.
In our system, the value of the parameter <rdisp/rfc_min_wait_dia_wp> is 20 while the number of dialog work processes is 18.There are no dialog work processes available for RFC requests.
Regards,
Terry

Similar Messages

Middleware - SMQ2 -queue status is 'READY'

Hi Expert,
What is missing regarding queue settings, if we have the following phenomenon:
After having any transactions e.g. business partner change or replication in CRM, queue is created with READY status. It is processed if I manually activate.
Thanks in advance.
Rgds,
Anett

Hi Raj,
Thanks for the hints.
One point is not clear yet, what blocks the queue permanently?
It is done via program, but not clear why.
(If I start manually everything is right.)
A

Queue Status in SMQ2 = RUNNING, but Stuck.

I have a queue that sometimes gets stuck in SMQ2 in status RUNNING (for no apparent reason).
If I activating the queue manually (as suggested in
http://help.sap.com/saphelp_nw04/helpdata/en/d9/b9f2407b937e7fe10000000a1550b0/frameset.htm)
usually solves the problem.
Therefore, this queue processes messages 24x7 and cannot get stuck for more than 5 minutes.
Question n1)Is there a way I can do this automatically (scheduling a JOB) (itu2019s a specific queue, that is only used for this single process)?
Question n2) Sometimes, after activating the queue again, the message continues in status RUNNING, and the only solution is to delete the message and activating the queue manually (when I do this, after processing every message in the queue, when new messages begin to arrive, the queue goes to status READY for a LONG time.) Does anyone knows whats going on?
obs.: The message is ALWAYS processed successfully, and there is no problem to process it 2 times. The only thing that cannot happen is STOP the process.
Thank you.
At.,
Bernardo Tavares Braga

1) I already registered all the queue through sxmb_adm - didn't change anything.
2) This queue is on SAP PI/XI, but the message goes to SAP ECC.
Since the process is executed, what I think happens is that the message updates SAP ECC, but somehow it doesn't give a return to SAP PI/XI.
So SAP PI/XI thinks its still executing.
Pinangshuk, the MONITOR QRFC_RESTART_ALLOWED is set to value 1(in the Integration Engine configuration - sxmb_admin)
Also, this enables the restart of stuck queues manually. Is there a way to do this automatically?

In Bound queue status in SMQ2

Hi All,
i've created a customer in CRM and saved it.
i've filled all the mandatory fields and it should replicate to ECC.
i've checked in SMW01, BUPA_MAIN BDoc is in intermediate state ,then i went to SMQ2 in CRM to check the queue status it is in READY status then upon unlocking the queue and refreshing it moved to RUNNING status and cleared from the inbound queue.....then upon refreshing the SMW01 ,BDoc BUPA_MAIN moved from intermediate state to send to receiver status and customer replicated to ECC.
My query is whenever i create any CUSTOMER/LEAD the queue in SMQ2 should go to RUNNING status and get processed automatically, every time i'm clearing the queue in SMQ2 and refreshing the SMW01 to reliacate the customer to ECC.
Please suggest me if any configuration change i've to do for the automatic queue clearence.
i've cleared all the queues in SMQ2 , there are no queues in wait/failed Status.
Thanks,
Syam

Hi Rohit Sharma,
Thanks for the help it solved my query.
I have one more query ,
Now the customer replicated to ECC without manual clearence of the queue.
even though the customer replicated to ECC i have the BDoc state of the BUPA_MAIN BDoc type as 'Sent to receivers (not all have confirmed)' with yellow light.
BDoc state should change to 'Confirmed (fully processed)' upon successful replication to ECC like BUS_TRANS_MSG for Lead.
Please suggest on any configuration change has to be done for the above query.
Thanks
Syam

SMQ2 queue is blocked and messages are in u201Cwaitingu201D status in RWB

Hello,
A SMQ2 queue is blocked with XXX data and these messages are in u201Cwaitingu201D state in RWB.
What could be the reason?
Im sure its not because of the space because all the messages which flow after that was there in the directory.
Regards,
Mathangi

Hi Mathangi,
double click on the queue and click on the first message which will direct to MONI
--> check what exactly the error is and try to resolve the error accordingly
if you are unable to do that
Right click on the first message and save LUV it will be saved in SMQ3
then unlock the queue and execute again it will process successfully..
later you can process the message which is saved
Regards,
Naveen

** 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

Sysfail locks smq2 queue

Hi,
We are live with our PI7.1 system as of 11/6 and are seeing serious issues when a data error causes a sysfail for a SMQ2 queue. At this point the queue is locked for further processing. We have monitors setup which page us for this situation. However, we really need to prevent the queue from locking so other messages are sent even when one item is in sysfail status.
Notes 813209 and 1118297 do not seem to offer any help is this situation.
Is there a way to prevent the queue from locking due to sysfail status messages?
Any help is greatly appreciated.
Regards,
Rick Taylor

Rick,
Check out this blog..
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417500)ID1371322850DB11715461650132929943End?blog=/pub/wlg/2728
"For automatic qRfc failure recovery, schedule the report RSQIWKEX to run periodically. This report enables automatically resets the queues. "
I remember there is a way to put error messages in different queue so that current queue wont b lock anymore...I'll check and let you know.
Hope this will help.
Thanks,
Nilesh

SMQ2 Queue sys.failed

HI all,
In CRM system SMQ2 queue name R3AD_ACCOUNTING is getting system failed.
When iam trying to unlock,activate and Execute those queue entries(5677) its not working i am getting the Message that FUNCTIONAL MODULE DOES NOT EXIT for this iam deleting the queue entries one by one after checking each one.
This queues are coming from R3 because of sale/service billing document post. when i check in SMW01 i didnt get any information related to this queue.
Is it any other way to solve this issue. How to resolve ?
Do the needful..
regards,
shoki.

HI,
when i check the queue entries i got the Functional module BAPI_CRM_SAVE,and queue name R3AD_ACCOUNTING, STATUS TEXT says that " Bdoc status failed,Bdoc not found".
system doesn't have dump errors too.
I came to know that when ever you get the message "Function module not found for this exception" for Queue entries we can delete that queue entry, but the problem is i have so many entries, Its not possible check one by one and delete?
sould i delete this all entries at once? Is it any solution?
Thanks,
shoki

MCEX12 Extraction Queue Status

Hi Experts
We are using MCEX12 Extraction Queue in our project
Many a times the status of this queue turns to WAITUPDATE
Thus the V# jobs do not extract data to delta Queue
Then i have to make the status to ready and run the v3 jobs manually
What could be the reason of the Status of the Queue changing to WAITUPDATE?
Regards
Akshay Chonkar

Hi
Check Note 869628 - Constant WAITUPDA in SMQ1 and performance optimization
and also 980221.
Hope it helps

Queue goes into 'READY' state

Hi All,
I'm using the 'TRFC_SET_QIN_PROPERTIES' function module with the qin_name parameter.
The problem I'm facing is that, most of the times, my function module entry goes into the queue - but the queue is in 'READY' state. I have to manually go to SMQ2 and make a change to put the queue into 'RUNNING' state.
Is there a way to automatically set the queue to 'RUNNNING' state when i insert an entry into the queue? Or, is there a seperate API that can do this task for me?
Regards,
Ram

Hello Jeff, the agents on an active call will not count for the Not Ready state. When receiving the call (ringing) they will be placed in Reserved state; while the call is connected they will be in Talking state and after the call ends they could be placed in Work state for a while.
HTH
Pablo

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

CCR -Queue Status "SYSFAIL"

Dear all,
While doing CCR i am getting the error with queue status as "SYSFAIL" in inbound queues of APO, When displyed the same saying " Enter Purchase Group" When displayed data from LUW in binary code shows material as semifinished material is it right?
I am unable to find out the material for which it shows this error, This error apperaed first time.
Please help me out How can i trace this error.
Regards,
Amol

Hi,
What says the application log (SLG1)
You can look there by the "TID of First LUW" entry and search by "External ID" field in SLG1.
Usually from there you can get order number, material number, plant and some other useful data. Does it bring more light?
btw. "Enter Purch. Group" error usually is seen in the inbound queue, when the purchasing group of the material master is not maintained. See SNP2 tab of the material master - it should be filled.
br,
Mikhail

Server Admin doesn't show Print Queue status

When I look at my print queues (all 17) under Server Admin, it shows queue name, # of jobs, shared via (IPP & SMB), and printer kind (HP LJ 1022n and HP LJ P2015). It has a column for status, but this is always 100% empty/blank. Also, if I go to the Jobs tab, then I can pick "Jobs on Queue" for all the queues, but the line below for "Queue Status" is again always blank.
Is there something I can do to get this info to show up in Server Admin? I know that CUPS knows the printer status, as I can go to localhost:631 and see the status in the Printers list and the Jobs list.
It isn't life threatening. It is just annoying to have to go to the web page when Server Admin -almost- gets me everything I need to diagnose a teacher's printing problem remotely.

Hi Keith
You could always consult the Print Service logs. If you set the logging levels to Debug or Debug2 you should get everything. You have to be a bit careful with this as the log can get quite large. Other than that I don’t know of anything that is available out of the box.
There may be others that can suggest a 3rd party solution that gives you the appropriate feedback you are looking for. Opening port 631 should not be that much of risk I would have thought?
Tony

BW Queue Status Stopped: SXMB_MONI

Hi
I am passing data from XI to BW into a Data Source via Inbound Proxy. The problem is for some of my messages I get the status as Green Flag(Queue Status- Stop)in SXMB_MONI.
That means all those Messages are not posted to Data source even though they are successfully transferred from XI.
If I manually try to restart them. It says that the message are already scheduled in Queue. But in Queue there is no entry.
Should I regenerate my proxy? Even though out of 10 I still have 6 successful Messages and rest 4 as Queue status stopped.
Can anyone suggest what can be the problem?
Regards
Swetank

Hi,
is there any trasaction in BW where you can register your Queues. somthing like sxmb_Adm--> register Queues...
B'cos this was the same problem that i encountered when i was using another client(105) in XI-IS when executing server proxies. Then the queues in the client system were not registered.
so check if there is any place in BW system where you can register the queues.
cheers,
Siva maranani.

Queue Status is showing Stopped

Folks,
I am trying to pass IDOCS from XI and the Queue Status is showing Stopped . I am using two receivers.
Please let me know how to start the queue.
Manish

Still the queue is showing stooped , here is the trace ,
<i><b> <Trace level="1" type="B" name="IDX_INBOUND_XMB" />
- 
<Trace level="1" type="T">User: XIAPPL</Trace>
<Trace level="1" type="T">Language: E</Trace>
<Trace level="1" type="T">Correct Version from 2 to 3: 3.X-Data to 4.x-Data</Trace>
<Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>
<Trace level="1" type="T">IDoc-Inbound-Handling</Trace>
<Trace level="1" type="T">Syntax-Check-Flag</Trace>
<Trace level="1" type="T">IDoc-Tunnel-Flag</Trace>
<Trace level="1" type="T">Queueid</Trace>
- <Trace level="1" type="B" name="IDX_IDOC_TO_XML">
<Trace level="1" type="T">Get the Metadata for port SAPST4</Trace>
<Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
</Trace>
<Trace level="1" type="T">Set Receiver Routing-object</Trace>
<Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>
<Trace level="1" type="T">COMMIT is expected by application !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" /></b></i>
Can anybody let me know what is the problem

SMQ2 Queue status stay 'Ready'

Similar Messages

Maybe you are looking for