BEQ connections utilizing high CPU.

Hi,
Oracle version :11.2.02
At a higher load ,i found the following process consuming high CPU.Oracle Server and client are in same unix box
During this time other processes were in waiting state.
oracleTESTDB (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq))).
Kindly suggest me why is it consuming high CPU.
Thanks.

user10698496 wrote:
Hi,
Oracle version :11.2.02
At a higher load ,i found the following process consuming high CPU.Oracle Server and client are in same unix box
During this time other processes were in waiting state.
oracleTESTDB (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq))).
Kindly suggest me why is it consuming high CPU.
Thanks.you need to know which OS process ID is consuming most CPU(might you have already identified), now you want want to tune the SQL which is excuting in this session:
select s.sid,s.sql_id from v$session s,v$process p,v$sql sl where s.sql_id=sl.sql_id and s.PADDR=p.ADDR and p.SPID=(os process);
Once the SQL is identified, check its explain plan and if possible trace it down to know where cpu is consumed.. Also ensure that statistics on table(which are reffered in sql) are upto date.

Similar Messages

Airport Process utilizing high CPU utilization

I currently have a 13 inch MacBook Pro i7 (2012 version). Recently I upgraded to Mavericks. After using the computer for a day after the upgrade, I began to notice it becoming very hot and the fans running very high. Looking at the running processes i noticed that a process called "airport" was running and utilizing high CPU times causing the heating up and fans running. Once I stopped this process, the laptop went back to operating at normal levels.
Unfortunately this issue began to come back several times....the "airport" process starting at any time and utilizing high CPU utilization....again only by killing this process fixed this issue.
After seeing this behavior over several days, I decised to wipe the drive and install a clean copy of Mavericks in the computer. Thought here was that possibly something did not carry over correctly from the upgrade from Mountain Lion to Mavericks. Unfortunely this did not correct the issue with the "airport" process as it still is continiung to launch at any time and spike the processor until I manually kill the process.
I do not recall this issue occuring while running Mountain Lion so it seems to be specific to Mavericks at this point.
I was hoping to hear if any other have experienced this type of issues while running Mavericks.

You should be able to find the information you are looking for from the default Total CPU Utilization Percentage monitor. This monitor has a built in diagnostic task that will kick off when an alert is triggered to list the top cpu consuming processes.
To find which processes were causing CPU to spike, simply review the State Change Events history in health explorer for the machine that was affected, for the Total CPU Utilization Percentage monitor. I have modified my second screen shot
to remove machine names, but you should get the idea. If a cpu monitor went from green to red, it will run the diagnostic task and list the process information and cpu usage at the time of the alert under state change events.

High CPU load kills ethernet connection

Short spikes in CPU load (MenuMeters installed) are constantly killing my internet connection.
I use an ethernet connection with a cable modem (Motorola SB 4200 E) and have a MB 2 CD, 2 GB of RAM and OS X 10.4.9.
After the ethernet connection is killed, only a complete re-start can fix the problem (and today alone I had to do something like 15 of them already).
These sudden spikes in CPU load can be caused by all different kinds of activity, e.g.
1.) playing back video files which my machine has problems dealing with (like .mkv files),
2.) playing back 'regular' .avi files,
3.) browsing the net (Camino, Safari, Opera, Firefox) and displaying flash content (just watching something on youtube creates a CPU load which kills the connection regularly),
4.) any kind of activity which asks a high CPU load in general.
It seems that the problem is caused by the CPU load in general, not by any particular application which causes the high workload.
What I have tried:
1.) PRAM reset
2.) Apple Hardware Test (extended, loop)
3.) de-installed Flash player
4.) created a new user (admin)
5.) made a clean 10.4.11 install on an external USB drive and booted from there
6.) used Airport instead of the ethernet/cable modem
7.) checked system temperatures (which are ok)
8.) changed/exchanged/checked the RAM
9.) made enough free disk space on my HD (15 GB)
10.) repaired disk permissions
but to no avail.
Any help would be very much appreciated (since I'm ready to get a MS machine and wave my Mac good bye).
Kind regards
FC

Hi Fred, and a warm welcome to the forums!
What Firmware cersion is it?
http://www.dslreports.com/forum/remark,5221851
Mac Modem problems with Broadcom Chipset...
All Linksys Cable Modems
All Motorola Cable Modems except for the SB5120
All Scientific Atlanta Cable Modems
http://discussions.apple.com/thread.jspa?messageID=2985422&#2985422
t seems that the problem is caused by the CPU load in general, not by any particular application which causes the high workload.
Do you have Activity Monitor set to Show All Processes?

NTP/GSP high CPU util

Hi,
We have 2 ASR9k (v4.2.0) routers doing "light" xconnect work, no problems so far.
Lately, we have noticed ntpd/gsp utilizing an abnormally high amount of CPU, is this normal behavoir on the ASR9k?
RP/0/RSP0/CPU0:asr-1#show processes cpu | utility head -n 2
Fri Aug 10 10:52:52.285 CET
CPU utilization for one minute: 57%; five minutes: 57%; fifteen minutes: 57%
RP/0/RSP0/CPU0:asr-1#show processes cpu | utility egrep -e ntpd -e gsp
Fri Aug 10 10:52:59.346 CET
233559 23%     23%      23% gsp
266447 27%     27%      27% ntpd
RP/0/RSP0/CPU0:asr-2#show processes cpu | utility head -n 2
Fri Aug 10 10:53:39.162 CET
CPU utilization for one minute: 56%; five minutes: 56%; fifteen minutes: 56%
RP/0/RSP0/CPU0:asr-2#show processes cpu | utility egrep -e ntpd -e gsp
Fri Aug 10 10:54:11.032 CET
233559 22%     22%      22% gsp
266447 28%     28%      28% ntpd
/Bjorn

CSCtw87827 is a known issue in 4.2.0 causing high CPU in ntpd/gsp.
Workaround is to enable IPv6 on the source interface used by NTP, but I'd recommend considering moving to 4.2.1 which is much more stable (unless extended validation testing was made for 4.2.0 of course)
Here is the full release note:
Issue:
======
The NTPD process takes around 27% cpu usage after upgrade to 4.2.0 30I. We did not see this issue before and we don not see this issue on another ASR9K running on 20L also.
Root cause:
ens_read_nb is getting called irrespective of producer available for requested interface exists or not. So this retry is happening infinitely if the requested interface is not configured with ipv6.
Fix:
====
When ENS_CMD_NB_STATUS is received we need to check the 'status' flag which is part of 'grp_ens_nb_status_msg_st' which is passed as part of 'value' parameter to the consumer callback. If this comes as 'ETIME' then it represents producer is available, but timeout happened due to some other reasons. If status is 'ESRCH' then it represents that producer doesn't exist for the requested interface. These are the two values for 'status' as of now.
Workaround:
===========
Configure either 'ipv6 enable' or an ipv6 address under requested interface. This will avoid infinite retrying from consumer library.
Condition which causes to hit this issue:
===============================
If any one of the LAS client register for link local address without enabling ipv6 on that interface, which may be due to configure/unconfigure/rollback and all.

Help!!! High CPU usage on Connect 8 servers.

Hello everyone,
Recently, we upgraded our Connect servers from 8.1.1 to 8.2.2.3. Since that time almost every evening as the number of concurrent users and meetings increases so does the CPU usage on Connect servers. After all CPUs are maxed out, people are started to be disconnected from meetings in droves. Sometimes, all users in a meeting are disconnected, other times half of the users stays in while another is disconnected.
I can see that during the high CPU usage one of FMSCore processes consumes almost 80%-90% of CPU resources.
I was wondering if somebody else had the same issue and how you solved it.
Any help is appreciated,
Milena

Hi MilenaITS,
It will be great if you could provide some additional informaion and that will help me in finding the cause here.
can you confirm the value for one of the tag in application.xml here are the steps you need to follow in order to check that :
1. got to connect installation folder (on cps servers where appserv/comserv presents)
2, Open comserv\win32\conf\originhost\_defaultVHost_\Application.xml
3. can you check what is the value for following tag in that xml : <SS_DYNAMIC_CODEC>
Also it might worth atry to change the value for this tag to "false" if it is "true" currently. This will remove the disconnects you are getting and may affect on FMS CPU as well . also you need to follow this on each node .
Can you give it a try and let me know if it solves the purpose for you.
Hope this will help!!
regards
Nikhil

High cpu usage when handling multiple rtmfp direct connections?

I'm writing a realtime multiplayer game with adobe AIR and RTMFP. The game uses a server client architecture in which all players are directly connected to a single computer ( host has one output netstream and one input netstream for each player). The problem is that the cpu usage will increase dramatically with the number of connections. 20 players is enough to bring my cpu down to it's knees.
I've made an experiment replacing RTMFP with TCP sockets ( Using AIR ServerSocket for the host ), with this the game handled 20 connections while using only 2% cpu. Unfortunately TCP sockets create a lot of extra lag because of nagle's algorithm so I can't use them as a replacement of RTMFP, but this experiment almost definitely proves that the bottleneck is in the usage of RTMFP NetStreams.
Is such high cpu requirements expeceted? If so, what makes it so cpu intensive? Is there anything I can do to lower the cpu usage?
Some extra data about my game:
I'm not using NetGroups.
The host will send about 15 small messages per second to all clients, all messages target the same method called "msg" and use ByteArray as argument. ( myNetStream.send( "msg", msgByteArrayData ); )
A single game with 20 players is too much for my pc, but 3 game instances with 10 players would still run fine ( although still somewhat high cpu usage )
Thanks in advance for any help you could provide.

I just did a couple of net stream connection tests. It appears that the CPU load increase quadratically with the number of connections.
I also attached the summary for all the results in .png format as attaching the pdf format is not supported.

High CPU Usage On client application when upgrade remote SQL database

Hi,
Is anyone here encountered very high CPU usage after upgraded the database from SQL 2005 to SQL 2012? Following describes my issue.
I have my client application running on Windows 7 that access to central database (SQL 2005) on Windows server 2003 using ODBC connection, this client application basically query data and perform data insert and update. There are a number of this similar
clients connected to the database.
Due to slowness of the database server, company decided to upgrade the database server to SQL 2012 and also new hardware runing Windows Server 2012. There is no change on the client application and client hardware and the client application still using the
same ODBC connection to query, insert or update the new database server.
The problem I am now experiencing now is that my client PC where my client application running the CPU usage is very high almost hitting 100% when accessing to the central database. I am also noticed this program lsass.exe that utilized almost 40-50% of
the CPU time when client application accessing the central database.
Is anyone here know, why client PC CPU usage 100% when access to upgraded SQL 2012 database? What is lsass.exe program doing, it only appear when accessing to database server. How to reduce the CPU usage on client?
Thanks.
Chee Wee.

Hello,
After upgrading, please rebuild indexes and update statistics on the databases.
http://www.mssqltips.com/sqlservertip/1367/sql-server-script-to-rebuild-all-indexes-for-all-tables-and-all-databases/
http://www.mssqltips.com/sqlservertip/1606/execute-update-statistics-for-all-sql-server-databases/
Configure maxdop on the instance.
http://blogs.msdn.com/b/sqlsakthi/archive/2012/05/24/wow-we-have-maxdop-calculator-for-sql-server-it-makes-my-job-easier.aspx
If the above does not solve the issue, let us know.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

High CPU due to dispatch unit in cisco ASA 5540

Hi Any suggestion help
High CPU due to dispatch unit in cisco ASA 5540
ciscoasa# sh processes cpu-usage
PC Thread 5Sec 1Min 5Min Process
0805520c ad5afdf8 0.0% 0.0% 0.0% block_diag
081a8d34 ad5afa08 82.6% 82.1% 82.3% Dispatch Unit
083b6c05 ad5af618 0.0% 0.0% 0.0% CF OIR
08a60aa0 ad5af420 0.0% 0.0% 0.0% lina_int
08069f06 ad5aee38 0.0% 0.0% 0.0% Reload Control Thread
08072196 ad5aec40 0.0% 0.0% 0.0% aaa
08c76f3d ad5aea48 0.0% 0.0% 0.0% UserFromCert Thread
080a6f36 ad5ae658 0.0% 0.0% 0.0% CMGR Server Process
080a7445 ad5ae460 0.0% 0.0% 0.0% CMGR Timer Process
081a815c ad5ada88 0.0% 0.0% 0.0% dbgtrace
0844d75c ad5ad2a8 0.0% 0.0% 0.0% 557mcfix
0844d57e ad5ad0b0 0.0% 0.0% 0.0% 557statspoll
08c76f3d ad5abef8 0.0% 0.0% 0.0% netfs_thread_init
09319755 ad5ab520 0.0% 0.0% 0.0% Chunk Manager
088e3f0e ad5ab328 0.0% 0.0% 0.0% PIX Garbage Collector
088d72d4 ad5ab130 0.0% 0.0% 0.0% IP Address Assign
08ab1cd6 ad5aaf38 0.0% 0.0% 0.0% QoS Support Module
08953cbf ad5aad40 0.0% 0.0% 0.0% Client Update Task
093698fa ad5aab48 0.0% 0.0% 0.0% Checkheaps
08ab6205 ad5aa560 0.0% 0.0% 0.0% Quack process
08b0dd52 ad5aa368 0.0% 0.0% 0.0% Session Manager
08c227d5 ad5a9f78 0.0% 0.0% 0.0% uauth
08bbf615 ad5a9d80 0.0% 0.0% 0.0% Uauth_Proxy
08bf5cbe ad5a9798 0.0% 0.0% 0.0% SSL
08c20766 ad5a95a0 0.0% 0.0% 0.0% SMTP
081c0b4a ad5a93a8 0.0% 0.0% 0.0% Logger
08c19908 ad5a91b0 0.0% 0.0% 0.0% Syslog Retry Thread
08c1346e ad5a8fb8 0.0% 0.0% 0.0% Thread Logger
08e47c82 ad5a81f0 0.0% 0.0% 0.0% vpnlb_thread
08f0f055 ad5a7a10 0.0% 0.0% 0.0% pci_nt_bridge
0827a43d ad5a7620 0.0% 0.0% 0.0% TLS Proxy Inspector
08b279f3 ad5a7428 0.0% 0.0% 0.0% emweb/cifs_timer
086a0217 ad5a7230 0.0% 0.0% 0.0% netfs_mount_handler
08535408 ad5a7038 0.0% 0.0% 0.0% arp_timer
0853d18c ad5a6e40 0.0% 0.0% 0.0% arp_forward_thread
085ad295 ad5a6c48 0.0% 0.0% 0.0% Lic TMR
08c257b1 ad5a6a50 0.0% 0.0% 0.0% tcp_fast
08c28910 ad5a6858 0.0% 0.0% 0.0% tcp_slow
08c53f79 ad5a6660 0.0% 0.0% 0.0% udp_timer
080fe008 ad5a6468 0.0% 0.0% 0.0% CTCP Timer process
08df6853 ad5a6270 0.0% 0.0% 0.0% L2TP data daemon
08df7623 ad5a6078 0.0% 0.0% 0.0% L2TP mgmt daemon
08de39b8 ad5a5e80 0.0% 0.0% 0.0% ppp_timer_thread
08e48157 ad5a5c88 0.0% 0.0% 0.0% vpnlb_timer_thread
081153ff ad5a5a90 0.0% 0.0% 0.0% IPsec message handler
081296cc ad5a5898 0.0% 0.0% 0.0% CTM message handler
089b2bd9 ad5a56a0 0.0% 0.0% 0.0% NAT security-level reconfiguration
08ae1ba8 ad5a54a8 0.0% 0.0% 0.0% ICMP event handler
I want exact troubleshooting.
(1) Steps to follow.
(2) Required configuration
(3) Any good suggestions
(4) Any Tool to troubleshoot.
Suggestions are welcome

Hello,
NMS is probably not the right community to t/s this. You probably want to move this to Security group (Security > Firewalling).
In the meanwhile, i have some details to share for you to check, though i am not a security/ASA expert.
The Dispatch Unit is a process that continually runs on single-core ASAs (models 5505, 5510, 5520, 5540, 5550). The Dispatch Unit takes packets off of the interface driver and passes them to the ASA SoftNP for further processing; it also performs the reverse process.
To determine if the Dispatch Unit process is utilizing the majority of the CPU time, use the command show cpu usage and show process cpu-usage sorted non-zero
show cpu usage (and show cpu usage detail) will show the usage of the ASA CPU cores:
ASA# show cpu usage
CPU utilization for 5 seconds = 0%; 1 minute: 1%; 5 minutes: 0%
show process cpu-usage sorted non-zero will display a sorted list of processes that are using the CPU usage.
In the example below, the Dispatch Unit process has used 50 percent of the CPU for the last 5 seconds:
ASA# show process cpu-usage sorted non-zero
0x0827e731 0xc85c5bf4 50.5% 50.4% 50.3% Dispatch Unit
0x0888d0dc 0xc85b76b4 2.3% 5.3% 5.5% esw_stats
0x090b0155 0xc859ae40 1.5% 0.4% 0.1% ssh
0x0878d2de 0xc85b22c8 0.1% 0.1% 0.1% ARP Thread
0x088c8ad5 0xc85b1268 0.1% 0.1% 0.1% MFIB
0x08cdd5cc 0xc85b4fd0 0.1% 0.1% 0.1% update_cpu_usage
If Dispatch Unit is listed as a top consumer of CPU usage, then use this document to narrow down what might be causing the Dispatch Unit process to be so active.
Most cases of high CPU utilization occur because the Dispatch Unit process is high. Common causes of high utilization include:
Oversubscription
Routing loops
Host with a high number of connections
Excessive system logs
Unequal traffic distribution
More t/s details can be shared by the ASA members from the community.
HTH
-Thanks
Vinod

Very high cpu utilization with mq broker

Hi all,
I see a very high cpu utilization (400% on 8 cpu server) when I connect consumers to OpenQ. It increase close to 100% for every consumer I add. Slowly, the consumer comes to a halt, as the producers are sending messages at a good rate too.
Environment Setup
Glassfish version 2.1
com.sun.messaging.jmq Version Information Product Compatibility Version: 4.3 Protocol Version: 4.3 Target JMS API Version: 1.1
Cluster set up using persistent storage. snippet from broker log.
Java Runtime: 1.6.0_14 Sun Microsystems Inc. /home/user/foundation/jdk-1.6/jre [06/Apr/2011:12:48:44 EDT] IMQ_HOME=/home/user/foundation/sges/imq [06/Apr/2011:12:48:44 EDT] IMQ_VARHOME=/home/user/foundation/installation/node-agent-server1/server1/imq [06/Apr/2011:12:48:44 EDT] Linux 2.6.18-164.10.1.el5xen i386 server1 (8 cpu) user [06/Apr/2011:12:48:44 EDT] Java Heap Size: max=394432k, current=193920k [06/Apr/2011:12:48:44 EDT] Arguments: -javahome /home/user/foundation/jdk-1.6 -Dimq.autocreate.queue=false -Dimq.autocreate.topic=false -Dimq.cluster.masterbroker=mq://server1:37676/ -Dimq.cluster.brokerlist=mq://server1:37676/,mq://server2:37676/ -Dimq.cluster.nowaitForMasterBroker=true -varhome /home/user/foundation/installation/node-agent-server1/server1/imq -startRmiRegistry -rmiRegistryPort 37776 -Dimq.imqcmd.user=admin -passfile /tmp/asmq5711749746025968663.tmp -save -name clusterservercom -port 37676 -bgnd -silent [06/Apr/2011:12:48:44 EDT] [B1004]: Starting the portmapper service using tcp [ 37676, 50, * ] with min threads 1 and max threads of 1 [06/Apr/2011:12:48:45 EDT] [B1060]: Loading persistent data...
I followed step in http://middlewaremagic.com/weblogic/?p=4884 to narrow it down to Threads that was causing high cpu. Both were around 94%.
Following is the stack for those threads.
"Thread-jms[224]" prio=10 tid=0xd635f400 nid=0x5665 runnable [0xd18fe000] java.lang.Thread.State: RUNNABLE at com.sun.messaging.jmq.jmsserver.data.TransactionList.isConsumedInTransaction(TransactionList.java:697) at com.sun.messaging.jmq.jmsserver.core.Session.detatchConsumer(Session.java:918) - locked <0xf3d35730> (a java.util.Collections$SynchronizedMap) at com.sun.messaging.jmq.jmsserver.core.Session.detatchConsumer(Session.java:810) at com.sun.messaging.jmq.jmsserver.data.handlers.ConsumerHandler.destroyConsumer(ConsumerHandler.java:577) at com.sun.messaging.jmq.jmsserver.data.handlers.ConsumerHandler.handle(ConsumerHandler.java:422) at com.sun.messaging.jmq.jmsserver.data.PacketRouter.handleMessage(PacketRouter.java:181) at com.sun.messaging.jmq.jmsserver.service.imq.IMQIPConnection.readData(IMQIPConnection.java:1489) at com.sun.messaging.jmq.jmsserver.service.imq.IMQIPConnection.process(IMQIPConnection.java:644) at com.sun.messaging.jmq.jmsserver.service.imq.OperationRunnable.process(OperationRunnable.java:170) at com.sun.messaging.jmq.jmsserver.util.pool.BasicRunnable.run(BasicRunnable.java:493) at java.lang.Thread.run(Thread.java:619) Locked ownable synchronizers: - None
"Thread-jms[214]" prio=10 tid=0xd56c8000 nid=0x566c waiting for monitor entry [0xd2838000] java.lang.Thread.State: BLOCKED (on object monitor) at com.sun.messaging.jmq.jmsserver.data.TransactionInformation.isConsumedMessage(TransactionList.java:2544) - locked <0xdbeeb538> (a com.sun.messaging.jmq.jmsserver.data.TransactionInformation) at com.sun.messaging.jmq.jmsserver.data.TransactionList.isConsumedInTransaction(TransactionList.java:697) at com.sun.messaging.jmq.jmsserver.core.Session.detatchConsumer(Session.java:918) - locked <0xe4c9abf0> (a java.util.Collections$SynchronizedMap) at com.sun.messaging.jmq.jmsserver.core.Session.detatchConsumer(Session.java:810) at com.sun.messaging.jmq.jmsserver.data.handlers.ConsumerHandler.destroyConsumer(ConsumerHandler.java:577) at com.sun.messaging.jmq.jmsserver.data.handlers.ConsumerHandler.handle(ConsumerHandler.java:422) at com.sun.messaging.jmq.jmsserver.data.PacketRouter.handleMessage(PacketRouter.java:181) at com.sun.messaging.jmq.jmsserver.service.imq.IMQIPConnection.readData(IMQIPConnection.java:1489) at com.sun.messaging.jmq.jmsserver.service.imq.IMQIPConnection.process(IMQIPConnection.java:644) at com.sun.messaging.jmq.jmsserver.service.imq.OperationRunnable.process(OperationRunnable.java:170) at com.sun.messaging.jmq.jmsserver.util.pool.BasicRunnable.run(BasicRunnable.java:493) at java.lang.Thread.run(Thread.java:619) Locked ownable synchronizers: - None
"Thread-jms[213]" prio=10 tid=0xd65be800 nid=0x5670 runnable [0xd1a28000] java.lang.Thread.State: RUNNABLE at com.sun.messaging.jmq.jmsserver.data.TransactionList.isConsumedInTransaction(TransactionList.java:697) at com.sun.messaging.jmq.jmsserver.core.Session.detatchConsumer(Session.java:918) - locked <0xe4c4bad8> (a java.util.Collections$SynchronizedMap) at com.sun.messaging.jmq.jmsserver.core.Session.detatchConsumer(Session.java:810) at com.sun.messaging.jmq.jmsserver.data.handlers.ConsumerHandler.destroyConsumer(ConsumerHandler.java:577) at com.sun.messaging.jmq.jmsserver.data.handlers.ConsumerHandler.handle(ConsumerHandler.java:422) at com.sun.messaging.jmq.jmsserver.data.PacketRouter.handleMessage(PacketRouter.java:181) at com.sun.messaging.jmq.jmsserver.service.imq.IMQIPConnection.readData(IMQIPConnection.java:1489) at com.sun.messaging.jmq.jmsserver.service.imq.IMQIPConnection.process(IMQIPConnection.java:644) at com.sun.messaging.jmq.jmsserver.service.imq.OperationRunnable.process(OperationRunnable.java:170) at com.sun.messaging.jmq.jmsserver.util.pool.BasicRunnable.run(BasicRunnable.java:493) at java.lang.Thread.run(Thread.java:619) Locked ownable synchronizers: - None
Any ideas will be appreciated.
--

Thanks ak, for the response.
Yes, the messages are consumed in transactions. I set imq.txn.reapLimit=200 in Start Arguments in jvm configuration.
I verified that it is being set in the log.txt file for the broker:
-Dimq.autocreate.queue=false -Dimq.autocreate.topic=false -Dimq.txn.reapLimit=250
It did not make any difference. Do I need to set this property somewhere else ?
As far as upgrading MQ is concerned, I am using glassfish 2.1. And I think MQ 4.3 is packaged with it. Can you suggest a safe way to upgrade to OpenMQ 4.5 in a running environment. I can bring down the cluster temporarily. Can I just change the jar file somwhere to use MQ4.5 ?
Here is the snippet of the consumer code :
I create Connection in @postConstruct and close it in @preDestroy, so that I don't have to do it everytime.
private ResultMessage[] doRetrieve(String username, String password, String jndiDestination, String filter, int maxMessages, long timeout, RetrieveType type)
throws InvalidCredentialsException, InvalidFilterException, ConsumerException {
// Resources
Session session = null;
try {
if (log.isTraceEnabled()) log.trace("Creating transacted session with JMS broker.");
session = connection.createSession(true, Session.SESSION_TRANSACTED);
// Locate bound destination and create consumer
if (log.isTraceEnabled()) log.trace("Searching for named destination: " + jndiDestination);
Destination destination = (Destination) ic.lookup(jndiDestination);
if (log.isTraceEnabled()) log.trace("Creating consumer for named destination " + jndiDestination);
MessageConsumer consumer = (filter == null || filter.trim().length() == 0) ? session.createConsumer(destination) : session.createConsumer(destination, filter);
if (log.isTraceEnabled()) log.trace("Starting JMS connection.");
connection.start();
// Consume messages
if (log.isDebugEnabled()) log.trace("Creating retrieval containers.");
List<ResultMessage> processedMessages = new ArrayList<ResultMessage>(maxMessages);
BytesMessage jmsMessage = null;
for (int i = 0 ; i < maxMessages ; i++) {
// Attempt message retrieve
if (log.isTraceEnabled()) log.trace("Attempting retrieval: " + i);
switch (type) {
case BLOCKING :
jmsMessage = (BytesMessage) consumer.receive();
break;
case IMMEDIATE :
jmsMessage = (BytesMessage) consumer.receiveNoWait();
break;
case TIMED :
jmsMessage = (BytesMessage) consumer.receive(timeout);
break;
// Process retrieved message
if (jmsMessage != null) {
if (log.isTraceEnabled()) log.trace("Message retrieved\n" + jmsMessage);
// Extract message
if (log.isTraceEnabled()) log.trace("Extracting result message container from JMS message.");
byte[] extracted = new byte[(int) jmsMessage.getBodyLength()];
jmsMessage.readBytes(extracted);
// Decompress message
if (jmsMessage.propertyExists(COMPRESSED_HEADER) && jmsMessage.getBooleanProperty(COMPRESSED_HEADER)) {
if (log.isTraceEnabled()) log.trace("Decompressing message.");
extracted = decompress(extracted);
// Done processing message
if (log.isTraceEnabled()) log.trace("Message added to retrieval container.");
String signature = jmsMessage.getStringProperty(DIGITAL_SIGNATURE);
processedMessages.add(new ResultMessage(extracted, signature));
} else
if (log.isTraceEnabled()) log.trace("No message was available.");
// Package return container
if (log.isTraceEnabled()) log.trace("Packing retrieved messages to return.");
ResultMessage[] collectorMessages = new ResultMessage[processedMessages.size()];
for (int i = 0 ; i < collectorMessages.length ; i++)
collectorMessages[i] = processedMessages.get(i);
if (log.isTraceEnabled()) log.trace("Returning " + collectorMessages.length + " messages.");
return collectorMessages;
} catch (NamingException ex) {
sessionContext.setRollbackOnly();
log.error("Unable to locate named queue: " + jndiDestination, ex);
throw new ConsumerException("Unable to locate named queue: " + jndiDestination, ex);
} catch (InvalidSelectorException ex) {
sessionContext.setRollbackOnly();
log.error("Invalid filter: " + filter, ex);
throw new InvalidFilterException("Invalid filter: " + filter, ex);
} catch (IOException ex) {
sessionContext.setRollbackOnly();
log.error("Message decompression failed.", ex);
throw new ConsumerException("Message decompression failed.", ex);
} catch (GeneralSecurityException ex) {
sessionContext.setRollbackOnly();
log.error("Message decryption failed.", ex);
throw new ConsumerException("Message decryption failed.", ex);
} catch (JMSException ex) {
sessionContext.setRollbackOnly();
log.error("Unable to consumer messages.", ex);
throw new ConsumerException("Unable to consume messages.", ex);
} catch (Throwable ex) {
sessionContext.setRollbackOnly();
log.error("Unexpected error.", ex);
throw new ConsumerException("Unexpected error.", ex);
} finally {
try {
if (session != null) session.close();
} catch (JMSException ex) {
log.error("Unexpected error.", ex);
Thanks for your help.
Edited by: vineet on Apr 7, 2011 10:06 AM

GETVPN - Rekey High CPU

Hi everybody.
I got GETVPN infrastructure, with two keyservers and 32 group members.
Every time the rekey process takes place, all the groupmembers present high cpu usage and the Crypto ACL consumes all of my resources.
I am very lost, because is a pretty straight forward configuration.
ROUTER# show process cpu history
ROUTER 10:49:38 AM Tuesday Sep 30 2014 UTC
9999999999999999444441111111111 11111 11111111111111
999999999999999988888222223333399999333339999922222666662222
100 ****************
90 ****************
80 ****************
70 ****************
60 ****************
50 *********************
40 *********************
30 *********************
20 ********************* *****
10 ************************************************************
0....5....1....1....2....2....3....3....4....4....5....5....6
0 5 0 5 0 5 0 5 0 5 0
CPU% per second (last 60 seconds)
121111121112111112121212221112111111122211121111111111112212
817295705770864893417188157650667447520279707886569543861074
100
90
80
70
60
50
40
30 * *
20 *** ********** **# #***#*#***#*** ****#*#********** ***#*#
10 ############################################################
0....5....1....1....2....2....3....3....4....4....5....5....6
0 5 0 5 0 5 0 5 0 5 0
CPU% per minute (last 60 minutes)
* = maximum CPU% # = average CPU%
929 9 9 9 99 9 929299192939199 9 9 99 9 9 9 99 9 9 9 99 919 9 99 919 9 9
939994959599798929199496919099595949949595949959496949949495949989099999
100 * * * * * ** * * * ** * * * ** * * ** * * * ** * * * ** * * * ** * * * *
90 * * * * * ** * * * ** * * * ** * * ** * * * ** * * * ** * * * ** * * * *
80 * * * * * ** * * * ** * * * ** * * ** * * * ** * * * ** * * * ** * * * *
70 * * * * * ** * * * ** * * * ** * * ** * * * ** * * * ** * * * ** * * * *
60 * * * * * ** * * * ** * * * ** * * ** * * * ** * * * ** * * * ** * * * *
50 * * * * * ** * * * ** * * * ** * * ** * * * ** * * * ** * * * ** * * * *
40 * * * * * ** * * * ** * * * ** * * ** * * * ** * * * ** * * * ** * * * *
30 * * * * * ** * * * ** ***** ** * * ** * * * ** * * * ** * * * ** * * * *
20 #** * * * ** * ****** ***#* ** * * ** * * * ** * * * ** * * * ** * * * *
10 ##*** **********###########******* ** ***** **** *** ** ***** **********
0....5....1....1....2....2....3....3....4....4....5....5....6....6....7..
0 5 0 5 0 5 0 5 0 5 0 5 0
CPU% per hour (last 72 hours)
* = maximum CPU% # = average CPU%
ROUTER#show process cpu sorted | e 0.00%
CPU utilization for five seconds: 99%/23%; one minute: 39%; five minutes: 19%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
251 1298116 6286 206509 74.91% 22.56% 5.21% 0 Crypto ACL
325 33652 32198 1045 0.23% 0.37% 0.43% 514 Virtual Exec
2 4428 84728 52 0.15% 0.06% 0.07% 0 Load Meter
119 356324 613777 580 0.15% 0.25% 0.27% 0 IP Input
41 10124 423671 23 0.07% 0.08% 0.07% 0 Per-Second Jobs
151 18788 601822 31 0.07% 0.18% 0.22% 0 CEF: IPv4 proces
ROUTER#
Keyserver conf:
crypto isakmp policy 100
encr aes
hash md5
authentication pre-share
group 2
crypto isakmp key cisco address 0.0.0.0
crypto ipsec transform-set CRYPTO_AES esp-aes esp-sha-hmac
crypto ipsec profile PHASE-II
set security-association lifetime seconds 7200
set transform-set CRYPTO_AES
crypto gdoi group GETVPN_CLIENT
identity number 7
server local
rekey lifetime seconds 43200
rekey retransmit 10 number 2
rekey authentication mypubkey rsa REKEY_CLIENT
rekey transport unicast
sa ipsec 1
profile PHASE-II
match address ipv4 ACL
no replay
address ipv4 10.1.1.176
redundancy
local priority 10
peer address ipv4 10.1.1.176
Thanks for your advice

Hello,
NMS is probably not the right community to t/s this. You probably want to move this to Security group (Security > Firewalling).
In the meanwhile, i have some details to share for you to check, though i am not a security/ASA expert.
The Dispatch Unit is a process that continually runs on single-core ASAs (models 5505, 5510, 5520, 5540, 5550). The Dispatch Unit takes packets off of the interface driver and passes them to the ASA SoftNP for further processing; it also performs the reverse process.
To determine if the Dispatch Unit process is utilizing the majority of the CPU time, use the command show cpu usage and show process cpu-usage sorted non-zero
show cpu usage (and show cpu usage detail) will show the usage of the ASA CPU cores:
ASA# show cpu usage
CPU utilization for 5 seconds = 0%; 1 minute: 1%; 5 minutes: 0%
show process cpu-usage sorted non-zero will display a sorted list of processes that are using the CPU usage.
In the example below, the Dispatch Unit process has used 50 percent of the CPU for the last 5 seconds:
ASA# show process cpu-usage sorted non-zero
0x0827e731 0xc85c5bf4 50.5% 50.4% 50.3% Dispatch Unit
0x0888d0dc 0xc85b76b4 2.3% 5.3% 5.5% esw_stats
0x090b0155 0xc859ae40 1.5% 0.4% 0.1% ssh
0x0878d2de 0xc85b22c8 0.1% 0.1% 0.1% ARP Thread
0x088c8ad5 0xc85b1268 0.1% 0.1% 0.1% MFIB
0x08cdd5cc 0xc85b4fd0 0.1% 0.1% 0.1% update_cpu_usage
If Dispatch Unit is listed as a top consumer of CPU usage, then use this document to narrow down what might be causing the Dispatch Unit process to be so active.
Most cases of high CPU utilization occur because the Dispatch Unit process is high. Common causes of high utilization include:
Oversubscription
Routing loops
Host with a high number of connections
Excessive system logs
Unequal traffic distribution
More t/s details can be shared by the ASA members from the community.
HTH
-Thanks
Vinod

High CPU utilization in voice gateways

High CPU utilization during non-peak hours in all the gateways.
Process-http core is utilizing more CPU and it reaches to 99% and after sometime it automatically resolved and sometimes reload solves the issue.
We are using contact centre and back office calls.
Any reason why this is happening?
IOS version- 15.0(1)M9

Hi Tagir,
We don't have ip http server and ip http secure-server command in our gateways.
No connections for the sh ip http client connections.
Please advice what could be the cause of the issue and also note that this is happening only in the late night when there is less call volume/no calls to the gateway.
Thanks...

Attn: ALL APPLE PORTABLE OWNERS -Macbook Pro, MacBook Air Apple portable slowdown / kernel high CPU solution

Attn: ALL APPLE PORTABLE OWNERS -MacBook Pro, MacBook Air, Mac mini slowdown kernel / high CPU use problem and solution.
YOU COULD FRY YOUR COMPUTER IF YOU DO NOT FIX THIS PROBLEM SO PLEASE READ THIS ENTIRE MESSAGE!
YOUR MAC WILL THANK YOU
Hey all.
Like many of you I've got a newer Apple portable which slows down to an unusable level for an unknown reason. In my case a 13" mid 2009 Intel MacBook Pro Core 2 duo laptop. After many failed attempts to figure out what this nutty problem is I have discovered the problem, the solution and I have solved this for my own MacBook Pro. Since this fix it has been working immediately and consistently -without issue
I am sharing this with you in hopes that you to can fix your Apple portable yourself or so you know what to tell the Apple techs so they can quickly fix your Mac from this wacky and unfortunate kernel CPU hogging problem.
User Software Symptoms :
Your Apple portable computer periodically for an unknown reason slows down making everything frustratingly slow. This happens even when running previous apps that were never a problem; things that your Mac should be able to handle easily but for some reason now it can't.
Slowdown most often happens during high CPU use such as gaming, video playback/editing, etc. or when running multiple apps (even non CPU intensive apps) at the same time.
Possible Hardware Symptoms:
Your computer is making more noise than it did previously.
Your computer occasionally makes more noise but then gets quieter.
Your computer is always extremely quiet (too quiet) even during high CPU apps -worst case scenario.
It feels hotter than it normally does. Test: After several minutes of the slowness/high kernel CPU touch the computer to feel if it's hotter than normal.
Looking at Activity Monitor (in the Utilities folder) shows the kernel_task is going bonkers eating up CPU but you have no idea why.
After trying many different things to solve this problem such as :
PR ram reset, SMC reset, fresh OS install of 10.5 and 10.6 on external hard-drives, calling and speaking to various Apple tech people who had no ideas/solutions, etc. I had no luck.
Btw, if you're having the symptoms I've decscribed above I would not run the Apple Hardware check (read below as to why). You could fry your Mac!
After much testing I found the problem :
It is my belief that "recent" Apple portable computers are using low quality internal fans which soon stop working!
Fail time period seems to be about 1.0 years to 2.5 years of use but this fail rate could vary depending on use.
First noticeable symptoms (depending on what you notice) could be computer slowdown or your fan is making more noise than it normally does. This is your fan's lubrication slowly eroding making your fan spin slower and less smooth resulting in the louder noise and slower rpm spin speed. The slower fan spin speed means less cooling is happening for your computer. The effect on your computer is that the CPU and other chips are heating up! Overheating to be more specific. When your computer's chips overheat they get wonky and screw things up. Most often this seems to have the effect of making the kernel hog CPU resulting in a frustratingly slow user experience! Heat kills computer chips and it is extremely bad for them. Extreme overheat or repeated overheating has been said to shorten the life of computer chips or in extreme cases even fry them completely!
The longer this goes on without being fixed your fan loses more lubrication and spins slower and slower cooling lesser and lesser resulting in your CPU heating up more and more possibly shortening the life of your Mac! Eventually your fan will stop completely and you could fry your chips! My fan stopped completely and my MBP was running very quietly, too quietly. Luckily I did not fry my chips because I was avoiding using high CPU apps because I knew something was wrong due to the massive slow down and wonkiness when I'd run them.
Side Note:I'm a bit concerned about all those Mac mini servers which may be using the same defective low quality fans which cannot be easily serviced by their owners as they are co-located in some server facility. One positive thing is those facilities are usually well airconditioned keeping temps low.
I suggest you do not run the Apple hardware test if you suspect your computer is overheating because the hardware test can seriously heat up your Mac! I tried running this test and my Mac got so hot I had to shut it down forcefully and I was concerned I damaged the chips. If you want to run the Apple hardware check make sure your CPU temperature is ok and that your fan works well before you run the test.
IF YOU DON'T FIX THIS PROBLEM YOU COULD FRY YOUR COMPUTER DUE TO HEAT DAMAGE!
DO NOT IGNORE THIS PROBLEM YOUR MACS LIFE MAY DEPEND ON IT!
First you need to properly diagnose this problem and see if your CPU is getting to hot and you need to see if your fans are spinning at high rpms giving proper cooling, or if they are spinning at low rpms when running high intensive apps as your CPU temp increases.
TEST IF YOUR FAN(s) IS WORKING CORRECTLY :
Unfortunately Apple does not include CPU temperature reading software nor fan rpm speed software that I am aware of.
However, There are two free ways that I know of to check your CPU tempurature and your fan speed :
One app shows fan speed, and CPU heat, etc.
One app shows fan speed, CPU heat and allows you to adjust your fan speed settings.
One app is a dashboard widget, the other is a system preference.
I suggest you download both of these to check your computer statistics.
http://www.eidac.de/?p=134
http://www.islayer.com/apps/istatpro/
http://fan-control.en.softonic.com/mac
I am not exactly sure what proper CPU temperatures are for the different Apple computers and this will change given different CPU loads.
My MBP doesn't seem to function properly with anything around 90 degrees or higher (celcius).
It seems when the fan is operating normally the CPU temp should not stay above 78 degrees even under heavy load, at least with the apps I'm running in the room temperature I'm in.
I can post back later with more specific temps under longer load, etc. but I wanted to get this post up for people to read as soon as possible so they don't fry their Macs.
If a bad fan is your problem :
THERE ARE ONLY TWO SOLUTIONS FOR THIS PROBLEM :
Fix or replace your fan so it cools the CPU and other chips properly.
I fixed my fan myself and I didn't need to buy a new one. Total cost was about $8.00 because I had to buy a #00 sized screwdriver and had it shipped to me. Price includes shipping.
On my mid 2009 model MacBook Pro fixing the fan was incredibly easy :
Before I started doing this I wasn't 100% this was the problem so I decided to try to fix my fan instead of ordering a new one and replacing it. As it turns out I didn't need a new fan, I only needed to clean the existing fan and relube it's axl so it could spin easier like when it was new. It also didn't make sense to buy a brand new fan from an Apple authorized parts reseller selling me the same low quality fan for $49.00 which would probably fail in 2 years again. Prices for new comparable fans from different manufactures range from about $15.00 USD + shipping to around $49.00 USD + shipping depending on where you order them from and what brand you get.
How to fix / replace your internal fan on a mid 2009 MacBook Pro :
Please note : I am not a hardware technician, nor expert. If you decide to fix your Mac yourself you do so at your own risk through no fault of my own. Prior to opening up your Mac you should google around and learn how to do it correctly and safely so you won't damage your Mac. For example, it is possible for you to damage your Mac by static electricity from your body. To avoid this I believe proper procedure is that you wear a 'ground strap' (around your wrist) which you clip to your Mac's metal body so your body will not excude a charge into your Mac. I believe the idea here is to keep your body's charge level and your Mac's similar. Since I do not have a ground strap and fixing/replacing the fan doesn't require touching any chips I did not wear a ground strap during my fan fix. What I did was periodically repeatedly touch the metal case of my MBP hoping that would be enough and it was. Avoid unecessary actions that can build up a static charge in you. Once I started the repair I did not walk around the room building up an electrical charge in my body. Walking on carpet can often build up a large charge in us so it is better to be avoided while working on your Mac. Certain clothing can build up static charges. Combing hair, etc. If you need to get up from your repair when you come back make sure you first touch the Mac's metal case and not anything inside.
Now that we're done with the scary paranoia, below you will find some instructions on how I fixed my MBP's internal fan
Before you begin:
Check out someone's video (not mine) on how to remove / replace the fan (but not take it apart and repair it):
http://www.youtube.com/watch?v=AghE9newvbs
Check out someone's web page (not mine) on how to replace the fan in a mid 2009 MacBook Pro:
http://www.ifixit.com/Guide/Installing-MacBook-Pro-13-Inch-Unibody-Mid-2009-Fan/ 1338/1
How to repair your mid 2009 MacBook Pro fan:
Make sure you are in a 'secure' environment. No pets, no kids running around, no drinks near the Mac, etc.
Make sure your computer is unplugged from it's power supply and turned off. NOT slept. Totally off / powered down.
1. Get a size #00 phillips screwdriver (Hobby store, Radioshack, Amazon).
2. Open up your MBP by unscrewing the bottom (yes flip it over so it's resting upsidedown). Note where each screw goes because some are different lengths. I placed each one around my MBP where they go, insuring I know their order (don't jumble them up). Note which direction your MBP is facing when it's upside down so if you spin it around while working on it you still know where the screws go.
2b. Some recommend removing the MBP's battery but I didn't do this step. You probably should, just to be safe. Follow the online instructions from the web page I listed about disconnecting the battery.
3. Unscrew the fan's 3 holding screws.
4. Unplug the fan's electrical connection (lift it straight up off the board). If you need to you can try to pry it up while you lift with a non metal/non electrical conductive object like a spudger if you have one or -perhaps a pen cap. Before you remove it, look closely at how it's attached so when you put it back on you won't wonder if you're doing it correctly. There's only one way it can go because it cannot fit 'the wrong way' but looking at it closely will make you feel more confident popping it back on when the time comes.
5. Remove the fan - it easily lifts out.
6. Take the fan apart by unscrewing it's one screw then unlatching the plastic clips which hold it together.
7. Seperate the fan blades from the housing. Lift the fan blades off of the fan housing by pulling it straight out away from the housing.
8. Clean off the dust that's gathered. A can of compressed air helps here (I didn't have one). I used a little brush from my electric shaver kit which worked well. Once you've removed all the dust from the fan and surrounding areas proceed to the next step.
9. Reapply new lubrication. You need less than 1 drop. Be sure it covers the entire fan blade axl as this is what needs to be well lubricated. Make sure there isn't excess oil that will fly around when the axl/fan spins at high rpms. I used the only oil I had which was olive oil (for cooking!) but I do not suggest this. At the time I was doing this I didn't know my fan was the problem so I wasn't even sure I was going to relube it. You should probably use something more appropriate perhaps like 3 in 1 oil. A good idea would be to call the manufatures of these little fans and ask them. Maybe a hobby store knows of good lubricants for these purposes?
DO NOT use things like WD 40 as it's not a long term lubricant or so I've read.
10. Once your fan is now clean and oiled (make sure there isn't too much oil) reassmble the fan.
Push the fan blades/axl back into the housing shaft. Give it a few spins with your finger.
Screw together the fan housing then reclip the clips.
11. Place the now reassembled fan back into your Mac and screw it in place (3 screws).
12. Reattach the fan's electrical wiring by gently pushing it into place. Make sure you've got the right end facing down before you push it in place.
13. Once your Mac's internals are clean and reassembled, place the rear cover back on your Mac and screw it in place.
14. Double check you didn't forget anything like screws, tools, etc.
15. Boot up your Mac and monitor the temperature and fan speed using those programs.
Compare the previous temps/fan speed to the current temp/fan speed.
Run a high CPU intensive app where your computer has been slowing down.
You should now have a happy Mac
If you have this problem and this solution fixed it for you please post in this thread letting me and everyone else know!
Hope that helps.

Thanks for your lengthy reminder dude, I have a similar Mac with yours. I suspect its a software fault because it happens after I upgraded to Lion, 10.7.2.

CUCM 8.6(2) - High CPU utilization - CCM process

Hello,
Process name ccm is peacking 91% of CPU utilization in one of Subscribers.
On cluster there are 1 Pub, 2 Subs, and 2 TFTP.
CCM service was already restart, and Subs reload, but problem remain.
We have checked and removed association with phones not registered, but problem remain.
Proc,PID,CPU,Status,SharedMem,Nice(Level)VmRSS,VMSize,VMData,ThreadCount,DataStackSize,PageFault
ccm,32687,90,SLEEPING,87380,0,426792,605276,468544,47,418345,744
VMware Installation:
        1 vCPU: Intel(R) Xeon(R) CPU E5-2643 0 @ 3.30GHz
        Disk 1: 80GB
        4096 Mbytes RAM
admin:show process name ccm
PID PPID   TID %CPU S COMMAND
32687     1 32687 0.0 S ccm
32687     1 19549 0.0 S ccm
32687     1 19570 0.0 S ccm
32687     1 19639 0.0 S ccm
32687     1 20057 0.0 S ccm
32687     1 20331 0.0 S ccm
32687     1 20332 0.0 S ccm
32687     1 20333 0.0 S ccm
32687     1 20354 0.0 S ccm
32687     1 20360 0.0 S ccm
32687     1 20361 0.0 S ccm
32687     1 23336 0.0 S ccm
32687     1 23337 0.0 S ccm
32687     1 23338 0.0 S ccm
32687     1 23339 1.0 S ccm
32687     1 23340 0.1 S ccm
32687     1 23341 0.2 S ccm
32687     1 23342 0.0 S ccm
32687     1 23349 0.0 S ccm
32687     1 23988 0.0 S ccm
32687     1 23989 21.6 S ccm
32687     1 23990 0.7 S ccm
32687     1 24013 0.0 S ccm
32687     1 24043 0.0 R ccm
32687     1 24044 0.0 S ccm
32687     1 24045 0.0 S ccm
32687     1 24046 0.0 S ccm
32687     1 24047 0.0 S ccm
32687     1 24048 0.7 R ccm
32687     1 24049 0.2 S ccm
32687     1 24050 0.1 R ccm
32687     1 24051 0.0 S ccm
32687     1 24052 0.0 S ccm
32687     1 24053 0.0 S ccm
32687     1 24054 0.0 S ccm
32687     1 24091 0.0 S ccm
32687     1 24092 0.0 S ccm
32687     1 24093 0.0 S ccm
32687     1 24181 0.0 S ccm
32687     1 24182 0.0 S ccm
32687     1 24192 0.0 S ccm
32687     1 24277 0.1 S ccm
32687     1 24278 0.0 S ccm
32687     1 24279 0.0 S ccm
32687     1 24280 0.0 S ccm
32687     1 24281 0.0 S ccm
32687     1 24282 0.0 S ccm
admin:
Are there any specific tests, or logs prior to isolate this issue?

Hi,
A few points:
> Use one of the recommended OVA templates
> Check if the spike is random or occurs at a specific time. If it occurs at a specific time it could be coinciding with something like DRS backup, CDR load, busy hours etc.
> Minimum set of logs needed for one such high CPU spike instance are:
Detailed ccm traces from all nodes
RisDC Perfmon logs
Proglogs
Also, capture the output of the following:
utils diagnose test
utils core active list
show process load
HTH
Manish

SBS 2011 - High CPU usage - Help me Microsoft forums! You're my only hope!

My company supports a client that has a SBS 2011 server. For about the past year, we've been fighting a recurring issue with performance on this server. There are about ten local users and four remote users. The server's CPU idles at
about 60%-80% but is usally running when under *any* load from 80%-100%. If you do anything on the console, it will stay pretty much at 100%. These are not power users by any means. The server is utilized for file/printer sharing, Exchange
2010, and one flat file database application (non-SQL). SharePoint is not utilized.
Needless to say, our client is frustrated. When opening files, using their database application, or doing anything Exchange-related, there is a large amount of lag on the client side. First, here are the server's specs:
Make:Dell PowerEdge T420
OS: SBS 2011 Standard SP1
CPU: 2 - Intel Xeon E5-2407
Memory: 32GB
RAID: RAID 1 - Operating System (C:)/Data Volume (E:) | RAID 5 - Data Volume (D:)
Here is what we have tried to resolve this to finality:
* Doubled resources - Initially the server had a single physical processor and 16GB of memory. While these specs alone should have been fine, and were fine when the server was installed, we had periods of time where the server would just sit all day at
100% usage. We doubled the resources and while this seemed like it would fix the issue, we are still seeing abnormally high processor usage.
* Removed all monitoring tools, antivirus, and backup software - As part of our testing, we removed our monitoring agent (LabTech) and antivirus (GFI Vipre). Mozy is utilized for an off-site backup so that was disabled. No dice.
* Verified updates - We made absolutely sure the server was 100% patched.
* Malware/Virus/Rootkit checks - We have ran scans checking for any potential issues with security.
* Ran MBSA and MBCA to fix any issues with the server's configuration.
There is no single process which is using all of the CPU, or we would simply be able to narrow it down. Our calls to Microsoft support have yielded no answers. The last call ended with Microsoft stating that a SBS server should always be running
at high CPU usage. Meanwhile, we have many other clients with less-beefy servers, with more users, who have no issues like these.
So, I'm turning to you all. I will gladly provide logs, configuration settings, even remote assistance sessions if you all can help shed some light on what might be causing my issues.
Thank you!

Some comments/ideas:
How long was the server running after this screenshot? I ask because store.exe is only got a 1GB of RAM which is really low - it should grab most of the RAM within a few hours.
The server was up for about 12 hours. I believe an adjustment was made before to limit the Exchange memory usage.
Strange that SearchIndexer (wsearch service) is so high although that may be a startup condition.
The LT* processes seem to be a 3rd party monitoring tool - no idea why it would ever need that much CPU though (I thought you disabled this?).
We had, but we cannot go forever without monitoring our client's server. It has been pulled off in the past and results on performance are pretty much the same.
The taskmgr process run by amnet_admin has used a lot of total CPU Time. What is it? (can't see the command line).
That's the user I was logged in as when I took the screenshot. Even the task manager seems to eat up the CPU.
The sqlserver process right above it is also busy - may want to look at the command line and figure out which SQL database that is (SBS has 3 - WSUS, Sharepoint, and SBS monitoring)
I believe that's the SharePoint database. They don't currently use their site. Would you recommend a removal and reinstallation? I would not completely remove as I know SBS doesn't like you removing parts of the complete package.
Strange that vds.exe is 10% - that is the interface to the disk management interface IIRC. Perhaps your monitoring service has gone awry here - definitely lose it.
I'll see about pulling it off and I'll see if there are any improvements.
-- Al

High cpu usage during JSF lifecycle phase execution

In our performance test we encountered a high cpu usage (100%) and the thread dumps indicated that most of the times the threads are either executing restore view or render response phase of the JSF lifecycle or they are blocked while accessing the jar files which containing the xhtml pages.
One of the thread dump of a runnable thread is
java.lang.Thread.State: RUNNABLE
at java.util.HashMap.get(HashMap.java:317)
at javax.faces.component.ComponentStateHelper.get(ComponentStateHelper.java:174)
at javax.faces.component.ComponentStateHelper.add(ComponentStateHelper.java:216)
at javax.faces.component.UIComponent.setValueExpression(UIComponent.java:436)
at com.sun.faces.facelets.tag.jsf.CompositeComponentTagHandler$CompositeComponentRule$CompositeExpressionMetadata.applyMetadata(CompositeComponentTagHandler.java:631)
at com.sun.faces.facelets.tag.MetadataImpl.applyMetadata(MetadataImpl.java:81)
at javax.faces.view.facelets.MetaTagHandler.setAttributes(MetaTagHandler.java:129)
at javax.faces.view.facelets.DelegatingMetaTagHandler.setAttributes(DelegatingMetaTagHandler.java:102)
at com.sun.faces.facelets.tag.jsf.CompositeComponentTagHandler.setAttributes(CompositeComponentTagHandler.java:246)
at com.sun.faces.facelets.tag.jsf.CompositeComponentTagHandler.applyNextHandler(CompositeComponentTagHandler.java:184)
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:184)
at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98)
at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93)
at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98)
at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:86)
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:308)
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:367)
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:346)
at com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:199)
at com.sun.faces.facelets.tag.ui.IncludeHandler.apply(IncludeHandler.java:120)
at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:184)
at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
at com.sun.faces.facelets.tag.ui.DefineHandler.applyDefinition(DefineHandler.java:107)
at com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:178)
at com.sun.faces.facelets.impl.DefaultFaceletContext$TemplateManager.apply(DefaultFaceletContext.java:395)
at com.sun.faces.facelets.impl.DefaultFaceletContext.includeDefinition(DefaultFaceletContext.java:366)
at com.sun.faces.facelets.tag.ui.InsertHandler.apply(InsertHandler.java:112)
at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98)
at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:184)
at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98)
at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93)
at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:86)
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:308)
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:367)
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:346)
at com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:199)
at com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:155)
at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93)
at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:86)
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:308)
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:367)
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:346)
at com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:199)
at com.sun.faces.facelets.tag.ui.IncludeHandler.apply(IncludeHandler.java:120)
at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98)
at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93)
at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98)
at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:86)
at com.sun.faces.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:152)
at com.sun.faces.application.view.FaceletViewHandlingStrategy.buildView(FaceletViewHandlingStrategy.java:774)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:100)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1550)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:343)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217)while a thread trace for a blocked thread is
java.lang.Thread.State: BLOCKED (on object monitor)
at java.util.zip.ZipFile.getEntry(ZipFile.java:302)
- waiting to lock <0x00000000c0f678f8> (a java.util.jar.JarFile)
at java.util.jar.JarFile.getEntry(JarFile.java:225)
at java.util.jar.JarFile.getJarEntry(JarFile.java:208)
at sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:817)
at sun.misc.URLClassPath$JarLoader.findResource(URLClassPath.java:795)
at sun.misc.URLClassPath.findResource(URLClassPath.java:172)
at java.net.URLClassLoader$2.run(URLClassLoader.java:551)
at java.net.URLClassLoader$2.run(URLClassLoader.java:549)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findResource(URLClassLoader.java:548)
at java.lang.ClassLoader.getResource(ClassLoader.java:1138)
at java.lang.ClassLoader.getResource(ClassLoader.java:1133)
at org.glassfish.web.loader.WebappClassLoader.getResource(WebappClassLoader.java:1156)
at org.glassfish.web.loader.WebappClassLoader.getResourceFromJars(WebappClassLoader.java:1111)
at org.apache.catalina.core.StandardContext.getMetaInfResource(StandardContext.java:7586)
at org.apache.catalina.core.StandardContext.getResource(StandardContext.java:6979)
at org.apache.catalina.core.ApplicationContext.getResource(ApplicationContext.java:382)
at org.apache.catalina.core.ApplicationContextFacade.getResource(ApplicationContextFacade.java:260)
at com.sun.faces.context.ExternalContextImpl.getResource(ExternalContextImpl.java:502)
at com.sun.faces.application.resource.WebappResourceHelper.getURL(WebappResourceHelper.java:119)
at com.sun.faces.application.resource.ResourceImpl.getURL(ResourceImpl.java:190)
at com.sun.faces.facelets.tag.jsf.CompositeComponentTagHandler.applyCompositeComponent(CompositeComponentTagHandler.java:366)
at com.sun.faces.facelets.tag.jsf.CompositeComponentTagHandler.applyNextHandler(CompositeComponentTagHandler.java:191)
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:184)
at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98)
at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93)
at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98)
at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:86)
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:308)
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:367)
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:346)
at com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:199)
at com.sun.faces.facelets.tag.ui.IncludeHandler.apply(IncludeHandler.java:120)
at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:184)
at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
at com.sun.faces.facelets.tag.ui.DefineHandler.applyDefinition(DefineHandler.java:107)
at com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:178)
at com.sun.faces.facelets.impl.DefaultFaceletContext$TemplateManager.apply(DefaultFaceletContext.java:395)
at com.sun.faces.facelets.impl.DefaultFaceletContext.includeDefinition(DefaultFaceletContext.java:366)
at com.sun.faces.facelets.tag.ui.InsertHandler.apply(InsertHandler.java:112)
at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98)
at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:184)
at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98)
at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93)
at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:86)
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:308)
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:367)
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:346)
at com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:199)
at com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:155)
at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93)
at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:86)
at com.sun.faces.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:152)
at com.sun.faces.application.view.FaceletViewHandlingStrategy.buildView(FaceletViewHandlingStrategy.java:774)
at com.sun.faces.application.view.StateManagementStrategyImpl.restoreView(StateManagementStrategyImpl.java:223)
at com.sun.faces.application.StateManagerImpl.restoreView(StateManagerImpl.java:188)
at com.sun.faces.application.view.ViewHandlingStrategy.restoreView(ViewHandlingStrategy.java:123)
at com.sun.faces.application.view.FaceletViewHandlingStrategy.restoreView(FaceletViewHandlingStrategy.java:453)
at com.sun.faces.application.view.MultiViewHandler.restoreView(MultiViewHandler.java:148)
at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:192)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:116)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593)
at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1550)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:343)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217)We use glassfish 3.1.1 as our application and the project_stage property is set to System_test. I would like to get suggestions on how should I investigate this further. Is this a normal behavior? Does glassfish provide an alternative for resolving blocked threads like some caching mechanism for resources etc?
Thanks in advance

Nik wrote:
Even if it is legal, have you tried moving them out of there (just to pinpoint a possible bug since the stacktrace indicates a wait on a jar file)?Indeed. If that clears up the issue it is good information to put in a JSF bug report (which may even cascade to the Glassfish level).
Putting resources in a jar file is only really useful when you want to share those resources among different web applications, which should be a rare case. Even when it happens I would probably still choose to simply copy the resources so they are individually managed and you don't get unnecessary dependencies between applications. Just because something is technically possible doesn't make it a good idea.

BEQ connections utilizing high CPU.

Similar Messages

Maybe you are looking for