Queue Monitor Wait

Database: 10.1.0.2
The event of "Queue Monitor Wait" in STATS$SYSTEM_EVENT
is tens of times of others' event.
aq_tm_processes is already set to 1 in init.ora
How to improve it?
Thanks

v$system_event shows cumulative values since the last instance startup. You need to install statspack and get delta values to find out which events are causing problems.

Similar Messages

Queue Monitor and Inbound Adapter Tabs in RWB are empty

Hi,
When we process messages in PI and want to see some monitoring data in the RWB we found that some screens do not show data. (PI 7.10)
RWB --> Message Monitoring --> Integration Engineselect a message --> Details
Then we get a new popup with 5 tabs:
1. Mesage Data: OK
2 Message Content: OK
3. Inbound Adapter: when I log in an empty screen is shown
4. Queue Monitor: when I log in an empty screen is shown
5. end-to-end Monitoring : ends in Java dump
I've looked into sap help and OSS, but I can't find any hints.
Somebody any suggestions
Thanks in advance
Ron

Hi Gokhan,
Our technical consultants are having a look into the sap note.
We have activated end-to-end montioring and now you'll see in the message monitor of the RWB that end-to-end monitoring is available.
You activate it with RWB --> configuration
Hope this clarifies it.
Best regards
Ron

Queues monitoring

Hi Experts,
Please explain ARFCRSTATE table like --
What are the contents that it carry?
What runtime information we can get from this table?
We are in the process of optimising our monitoring activities and one of the major part is queues monitoring. We are now refreshing each and every time the inbound queues to check whether there are any messages stuck in them. We are now trying to develop a program so that if the messages are stuck in queues we will be informed like an Alert through mails or something else. After searching a lot in the forums i came to know that the above table carrys the run time information about queues. but when checked i didn't find any useful information.
Are there any pre configured programs or tables or anything in sap for this queue monitoring stuff?
If so please give the details.
Thanks in advance.

You can also configure CCMS alerts to monitor inbound/ outbound queues.
Check the below blog and find more, can help you on queue monitoring:
http://www.sdn.sap.com/irj/scn/weblogs?blog=/cs/user/create/cs_msg%3fx-lr=cs_disc%2f2131%26x-lr2=wlg%2f2777%26page=
--Div

JMS Queue monitoring

Hi everyone,
is there any way to monitor a jms queue with its contained messages ? i'm talking about a tool like the jmx console in jboss - the JMS Adapter and JMS Notification in the Visual Admin only provide some properties.
Any suggestions ?

Hi,
In short what you want (sending email in case message has stayed too long time in the queue), is NOT possible directly. That's not a standard feature by the JMS spec.
What is possible is the is so-called dead messages, once the acknowledgment fails the predefined number of times then the messages will be redirected to a special queue. From there the messages can be exported by telnet.
Check SAP note 777930 for more info. Btw, it might be a good idea to get familiar with that note, otherwise if the external server let's say always throws an exception while processing the message, it will be moved to this special queue and unless someone issues the appropriate telnet commands, nobody will understand about this.
However if you disable this feature, that will mean that the message will be delivered endlessly, causing CPU load. Not nice if you have doubts in your external listeners.
Now about the queue monitoring :
You could create manually a periodic task (EJB timers in J2EE 1.4 which is covered in the prerelease of the next server version, or if you are using Netweaver 04s or 04s than perhaps java.util.Timer) that will periodically open a JMS browser, check the messages in the queue, if they have stayed too long time (>100 seconds for example ?) or if the queue is too big (>100 messages) you can send manually the email alert that something has went wrong. By usage of the JAVA API that should be simple
Another thing you can do is that inside your external listeners and the onMessage method, you could check manually the number of times the message is redelivered, if it is above some threshold (i.e . if it is 3, that means the SAP server has delivered the message 3 times , since the listener have rejected it 2 times already),then you can send the email via the standard java API. The delivery count can be retrieved by using the standard optional property JMSXDeliveryCount from the message.
HTH
Peter

Advanced queues are waiting in ready status and do not process

Advanced queues are waiting in ready status and do not process.
There are no Db locks.
DB 11.2.0.2.0

Hi,
With this information it is not possible to get appropriate answer in the forum.
By the way you checked alert log file.
Check the below link also:
http://www.cs.umbc.edu/portal/help/oracle8/server.815/a68005/03_adq2f.htm
Best regards,
Rafi.
http://rafioracledba.blogspot.com/

Monitor wait events thru OEM

Hi,
We have OEM (10.2.0.5) and how to monitor wait events thru OEM and where do we find them? I checked under performance tab and couldn't find.

Go to: Database Instance > Server Tab > Statistics Management > Automatic Workload Repository
Click "Run AWR Report" for any time period you want. It looks like Statspack report and has all the wait events in that period.
Another way is to Go to Performance Tab > Top Activity and click on a session in Top Sessions. It has a summary of waits for that session. You can change the drop down "Show Aggregated Data" to "Show Raw Data" to see breakdown of waits for the session.

Queue Monitoring

Hi Experts,
I got this error in SAP Queue Monitoring anyone explain me
Error:The assert condition was violated
Also give me some link to understand the Queue monitoring in SAP.
Regards,
Manigandan

Hi Manigandan,
I got this error in SAP Queue Monitoring anyone explain me
Error:The assert condition was violated
Check this thread: http://scn.sap.com/thread/1240651
Also give me some link to understand the Queue monitoring in SAP.
If you use SCN search you can find links like these:
http://scn.sap.com/docs/DOC-16526
Outside of this comminuty: http://www.****************/Tutorials/XI/XMLMessageQueues/Monitor.htm
Regards.

Queues stuck in DB-Queue Monitor .

Hi,
I have B1if with some scenarios in my system, but i have a problem with Queue stuck.
Under DB-Queue Monitor, i have the stuck queues, Q.INB_IQ_INTQ_ASYN_QS.0010000000 > sap.B1SysSLDSync > message(<SLDModify sysid="0010000112" company="SBO_DEPOSITO_NILDO" task="delete" /> ).
I have checked and all IPO-Steps are active.
Any solution????
[]'s

Hi Priyanka,
To clear the no send status entry, go to R3AS, select the object say for BP (Bupa_main) press enter and then execute, then open R3AM1 enter object name as Bupa_main and select Running and done and execute.
Now you can open SMQ2 and click on each entry with nosend status and then click on activate queue in the top toolbar, this shld change the status to running and then click on refresh.
The following is the list of Queue extensions that are used in CRM, all the queues start with these extensions:
<b>Outbound queues</b>
CDB*     Start queues for loads CRM -> CDB
CRM_SITE*     Load queues for Mobile Clients
CSA*     Send queues of CRM Server Applications
EXT*     Start queues for loads CRM -> Ext.
R3AI/R*     Start queues for loads from ERP Backend system
R3AU*     Load queues CRM -> ERP Backend system
<b>Inbound queues</b>
CRI*     Initial load queues CRM -> CDB
CRM_SITE*      Load queues from Mobile Clients
R3A*     Load queues ERP Backend -> CRM
CSA*     Send inbound queues of CRM Server Applications
Hope this answers ur query.
Regards,
Amit
Message was edited by:
        Amit Singh

Queue monitoring in Solman through CCMS

Hi All,
Can some one please help me to know how Queue monitoring(SMQ1 and SMQ2 in ECC system) is possible through CCMs.
Would be thank ful if somebody can provides me steps as to how we can configure queue monitoring.
Thanks You all in advance.
Regards,
Prerna

Hi Prerna,
Please go through the below SAP Note and a link which will help you to configure Queue Monitoring in CCMS.
441269 - Setting up tRFC/qRFC monitoring in the alert monitor
http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/03/25/michals-pi-tips-component-based-message-alerting
Let me know if You face any more Issues for the same.
Thanks
Ajitabh

Why XBTO* is visible in inbound queues monitor if it is an outbound queue

Hi all,
why XBTO* is visible in inbound queues monitor if it is an outbound queue?
Any help will be really appreciated.
Regards,
Ivá

Similar question...
XBTO and XBTS Queues

Tuxedo process IPC queue monitoring

Hi
This question is aimed mostly at Oracle techies who have experience supporting Tuxedo sites.
We've been developing on Tuxedo for a couple of years now and are about to go live with a Tuxedo based transactional system.
Throughout the development and testing phase it has become pretty apparent to us that we need to be able to keep an eye on IPC request queues for processes running under Tuxedo.
For example, we have 10 instances of server "A" running within Tuxedo. As long as these ten instances can cope with the load, we are getting good end-to-end response times. When we overload the system whereby our requests start being queued up on IPC queues for these processes, quite predictably our end-to-end response times go up. We would like to get an early warning when situations like this occur.
Sometimes there are obvious reasons for this behaviour (i.e. we're sending more requests per seconds than our application can cope with) and at other times, it is a degradation in performance of a downstream process (e.g. database query taking longer and longer to return as time goes by) that is causing our requests to start backlogging. It is this latter scenario that we would like to be alerted to before our clients ring us up to tell us that our service is not performing as well as it should.
However, there seems to be a distinct lack of importance placed on server request queue monitoring within Tuxedo infrastructure and API set. Perhaps we are missing something obvious?
We would like to be able to have a more proactive monitoring and reporting facility in place to help us observe queuing behaviour. It seems that there are two ways to obtain any queuing diagnostics:
1) Use a shell script to call tmadmin/pq from time to time to take snapshots or use OS commands to monitor IPC queues
2) Use Tuxedo MIB and poll the queue OIDs to get queue depth snapshots.
We would like to be able to get a lot more than that. For example:
* to be able to plot a graph of queue depths over a period of time
* get alerted when queue depths cross a certain limit (trap vs poll)
* work out how long an item spent on the queue before it got processed
So, are we placing too much emphasis on something that is not important to other Tuxedo users or is there a suite of tools one can use to obtain this sort of information that we are not aware of?
How important is request queuing to a typical Tuxedo site.
Regards,
Mike

Hi Mike,
You might want to look at the Oracle Tuxedo System and Application Monitor (TSAM). It is an add-on product from Oracle that provides system and application monitoring for Tuxedo applications. Although TSAM doesn't currently give you the kind of graph you are looking for, it does collect that information and place it in the TSAM monitoring database. TSAM provides the schema of the monitoring database, so creating whatever graphs you want should be pretty easy.
Specifically what I would look at though is TSAM's alert generating mechanism. Alert information can either be checked at the monitoring console, or it can be checked at the monitored nodes plug-in. The later offers the option of simply checking for an alert without having to report the data back to the console unless an alert is triggered. This tends to have much less impact on the monitored system and help keep the monitoring console from being flooded with data. In the Call Path and Service monitoring categories, you can define alerts that check if the number of queued messages exceed a certain amount. This is quite efficient and would have minimal impact on system performance, yet warn you when queues are starting to back up.
These two methods would give you historical data to look for trends as well as real time alerting to be notified that backups are occurring.
Regards,
Todd Little
Oracle Tuxedo Chief Architect

Adapter engine queue monitoring

Hi All,
I have one doubt about adapter engine queue.
We can see adapter engine queue in RWB->Message Monitoring-> Adapter engine-> Display .
Here in queue if one message goes in to system error status, remaining all messages from that queue goes on holding status.
So unless someone manually clears this system error message, remaining messages from same queue will not be processed.
Is there anything to automate this process? Because currently someone has to manually monitor this queue and clear the message if it is in system error.
Thanks in advance.
Warm Regards,
Gouri

Hi Bhavesh,
I am getting a PO file from source system which contains data and control record. But target system expects two different files for data and control. So in mapping program I have done this.
When interface split happens for one scenario and the multiple messages are going to the same receiver, an internal queue name is generated from the message ID of the original message, to ensure that the correct processing sequence is maintained. As a result, the quality of service switches from EO to EOIO. Here is the reference link:
http://help.sap.com/saphelp_nw04/helpdata/en/28/68073c8e56f658e10000000a114084/frameset.htm
Also can you please elaborate on CCMS?
Thanks in advance.
Warm Regards,
Gouri

Queue Monitoring Tool ?

Hi,
I am looking for some monitoring tool or administrative commands for Tibco EMS which can tell me what's happening inside the Queue/topic.
If you know something about it . Please let me know...
Thanks in advance

YES.
the queue manager will monitor any job in the queue even if it was submited from a web client.

Message sent from XI but queue in waiting

Hi Guys,
I am facing a strange problem in XI.
First of all cleared all the inbound and outbound queues in XI.
Then I ran an async service from XI. The flow is as follows.
XI --> SCM system(PROXY)
(PROXY)SCM>XI>HTTP
So as per the flow the response came back to XI and it posted the data to HTTP servlet and the servlet processed the data on its side.
Hence I should see a message status in MONI as "Message successfully processed" with queue in empty status.However the message status is in "Scheduled for Outbound Processing" and the queue is in waiting status(yellow Triangle symbol). Earlier the same scenario worked fine. And now I am facing this issue for all the services.
Remember I have cleared all the queues before I started this process. Hence there is no chance for my message to get stacked on queue bcoz of previous messages stacked on the same queue.
Even I restarted XI box, but the problem still persists.
Could somebody tell the reason behind this issue?
Thanks,
Gujjeti.

Hello Everybody,
Finally I have to close this thread as this issue is solved.
There is nothing wrong on XI side.
The problem is with HTTP servlets hosted on SAP Web AS JAVA. ( different WAS instance other than XI, which is hosting these servlets.)
Restarting java application deployment specific to the servlets on Web AS Java using Visual Administrator resolved the issue.
Still I don't know the exact root cause for this behavior. May be the application environment has got some problems as these servlets are handling huge amounts of data.
Thanks everybody for your inputs. Your answers might be correct w.r.t other kind of issues in XI.
-Gujjeti.

Queue monitoring, best practice

Hi,
          I have had a go at reading the Programming guides supplied on the website, however I still am unsure as to the best approach...
          Situation:
          Server1, Weblogic Server 8.1 with a JMS Queue.
          Server2, Tomcat 6.0.
          Server3, IIS with a Web Server.
          Server2 has a simple daemon process that is intended to monitor a JMS Queue from Server1 and forward (consume) any messages it recieves to Server3.
          The daemon is basically constructed as follows:
                    INIT:
           Initialise JNDI context
           Lookup TopicConnectionFactory
           Create TopicConnection
           Set connection client ID
           Create TopicSession
           Lookup Topic
           Create TopicSubscriber (DurableSubscriber)
           Start connection
          MAIN:
           Loop:
            recieve TextMessage from TopicSubscriber
            Forward consumed message to webservice
            goto Loop: // This is an endless loop
                              As you can see, I initalise all connection details once at the start and then I hope to use it forever.
          Should I be closing the session (or connection) after each consumed message?
          Will this be able to consume messages that are already in the Queue or will it only consume message that are published while it is connected?
          This all seems to work for a while, but I occasionally get the following exception (which is the reason why I'm asking the above questions):
          weblogic.jms.common.InvalidClientIDException: Client id, my_cid, is in use
               at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
               at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:137)
               at weblogic.jms.dispatcher.DispatcherImpl_813_WLStub.dispatchSyncFuture(Unknown Source)
               at weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSync(DispatcherWrapperState.java:345)
               at weblogic.jms.client.JMSConnection.setClientID(JMSConnection.java:513)
          which (i think) courses the following exception:
          weblogic.jms.common.JMSException: Connection clientID is null
               at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:1635)
               at weblogic.jms.client.JMSSession.createDurableSubscriber(JMSSession.java:1461)
               at weblogic.jms.client.JMSSession.createDurableSubscriber(JMSSession.java:1434)
          Thanks in advance for any and all responses to my questions.

-- Should I be closing the session (or connection) after each consumed message?
          No. Connection/session creation has a relatively high overhead.
          -- Will this be able to consume messages that are already in the Queue or will it only consume message that are published while it is connected?
          I assume your refering to topics (pub/sub), not queues. If you want to receive messages were sent while the subscriber was disconnected, then you need to use "durable subscriptions" - a basic standard concept in JMS. Furthermore, if you want the messages to survive even in the event of a server crash, the publisher must specify "PERSISENT" as the delivery mode.
          -- This all seems to work for a while, but I occasionally get the following exception (which is the reason why I'm asking the above questions):
          As part of standard JMS for "durable subscribers", clients must specify a unique client-id when creating a connection. They must also specify a subscriber-id when creating the subscriber. The "connection-id, subscriber-id" tuple uniquely identifies a durable topic subscription. If a connection using the specified connection-id already exists when creating a new connection, the new connection create will fail (must fail) with a duplicate client-id exception.
          I don't know what is causing the null-pointer-exception.
          Hope this helped,
          Tom

Queue Monitor Wait

Similar Messages

Maybe you are looking for