Microsoft Windows Server DNS Monitoring v7.1.10100.0 High CPU Usage on Windows Server 2012 R2

Hello!
I've a big problem with this MP. When the zone monitoring is enabled (by default) the MonitoringHost.exe takes up all the CPU. I've put the zones in Maintenance mode.
I've got this problem only with a new Windows 2012 R2 server. Other Windows Servers (2003 R2, 2008 & 2008 R2) with DNS Server Role they don't have this problem.
Any ideas?
Thank you!
The configuration is:
SCOM 2012 R2
Microsoft Windows Server DNS Monitoring v7.1.10100.0 Management Pack
DNS Management Pack Action Account has been configured
"Act as proxy..." is enabled
The monitored server config:
Windows Server 2012 R2 (standalone)
DNS Server Role installed
DNS Management Pack Action Account is a member of the "Administrators" group
The only events I've are the following but I'm not sure if they're related (because of the ...DNSSEC...):
Log Name:      Operations Manager
Source:        Health Service Modules
Date:          8/11/2013 11:16:21
Event ID:      11903
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      NS2...
Description:
The Microsoft Operations Manager Expression Filter Module could not convert the received value to the requested type.
Property Expression: Property[@Name='QueriesResponded']
Property Value: Property[@Name='QueriesResponded']
Conversion Type: DataItemElementTypeInteger(5)
Original Error: 0x80FF005A
One or more workflows were affected by this. 
Workflow name: Microsoft.Windows.Server.DNS.2012R2.Monitor.DNSSEC.NameResolutionQueries
Instance name: <zone-name> on NS2...
Instance ID: {4BCB4738-1287-2E6F-E0AA-1FF8D66DDB0B}
Management group: <grp-name>
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Health Service Modules" />
    <EventID Qualifiers="49152">11903</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-11-08T09:16:21.000000000Z" />
    <EventRecordID>9602</EventRecordID>
    <Channel>Operations Manager</Channel>
    <Computer>NS2...</Computer>
    <Security />
  </System>
  <EventData>
    <Data><grp-name></Data>
    <Data>Microsoft.Windows.Server.DNS.2012R2.Monitor.DNSSEC.NameResolutionQueries</Data>
    <Data><zone name> on NS2...</Data>
    <Data>{4BCB4738-1287-2E6F-E0AA-1FF8D66DDB0B}</Data>
    <Data>Property[@Name='QueriesResponded']</Data>
    <Data>Property[@Name='QueriesResponded']</Data>
    <Data>DataItemElementTypeInteger(5)</Data>
    <Data>0x80FF005A</Data>
  </EventData>
</Event>

Glad to see you found the solution and thanks for your sharing.
Niki Han
TechNet Community Support

Similar Messages

  • CSA 4.5.1(657) high cpu usage on windows 2003 sp1

    Hi,
    We have experiancing high cpu usage on windows 2003 sp1, when somebody logs in remotely. The server has 1gb of ram and the cpu is 2ghz. The Cisco Trust Agent (1.0.55) is installed also.
    When somebody logs in remotely the process okclient goes to 100% cpu and eats all the available RAM and the machine starts to swap, the pagefile has grown to 1gb. This is not all the time though, only in some cases like this one.
    Could this be due to some specigic policies associated with this machine be the cause of such behaviour?

    Hi Rossen,
    It could be due to some @remote rule but first some questions:
    What is the server function?
    What groups is it in?
    Does it have 2 enabled NICS?
    Is it sharing anything other than admin shares?
    Is it a member of AD\Domain or standalone?
    Why is the CTA installed?
    Why is your page file dynamic and not static and why is it only 1GB (should be 1.5x physical RAM)? Growing a page file is a slow and painful process.
    You can try some things right away:
    Either remove if from the groups that have @remote rules or put the server in a group with no rules\policies at all. That will tell you if it's the agent or the rules causing the problem.
    Good luck!
    Tom

  • Adobe Reader High CPU Usage on terminal server

    Hello,
    I have a question?
    Yesterday one of our customers ran into a problem where the Adobe Reader process (Acrord32.exe) was using the maximum available CPU resources constantly on a terminal server. Even when Adobe reader program was closed, therefore the process remains running in the background continuing to use all of the available CPU resources. Customer is using Windows server 2012 R2 with Adobe Reader please help?

    Hi Michaeld71937612,
    Try terminating the 'process Tree' using Task Manager then restart Adobe Reader, and check the CPU Usage again.
    Please make sure that there are no other instances of Acrobat running on your system once you end Task.
    I would also recommend you to check for malicious activity on your system using a reputed Antivirus/Security software.
    Regards,
    Rahul

  • High Cpu Usage on Windows 8.1

    I'm running Bootcamp with Windows 8.1 on my late 2013 retina macbook pro, and the "System" and "System Interrupts" processes are using about half of my cpu at all times. Is this an issue with the drivers? I also recently updated to Yosemite, if that helps.

    rRe: System and System Interrupts- high cpu utilization

  • High CPU Usage on Windows 2000

    Is it normal for my CPU usage to spike to 100% everytime a page loads? I'm doing some minor load testing on the example StockPortal with 30 users, and my CPU usage keeps maxing out. Even when I'm the only one on it, the CPU usage spikes to 100%.
    The machine I'm using is a 1.4 ghz Pentium with 1 gig of RAM. I also changed the cloudscape database to SQL Server 2000.
    Am I suppose to do anything else? Please email me any answers.
    Thanks,
    Edward
    [email protected]

    Chris,
    I asked around here yesterday. A couple of our performance test guys said
    they had seen similar symptoms on some machines when:
    (1) Pages may be getting compiled on every hit. As a result,
    you will see CPU getting pegged.
    They have to make sure the ServletReloadCheckSecs is not set to 0 (in
    config.xml).
    (2) They also have to set "pagecheckseconds" in weblogic.xml to non zero.
    setting them to 300 secs may be appropriate....
    Sincerely,
    Daniel Selman
    "Chris" <[email protected]> wrote in message
    news:[email protected]...
    >
    Thanks for your replies.
    This is WLS 6.1 sp1, WLP 4.0 sp1. we are testing against theout-of-the-box stockPortal
    (Avitek). only change is that we are using a MSSQL database.
    we are going to be running JProbe this morning to attempt to findbottlenecks
    in the code.
    "Daniel Selman" <[email protected]> wrote:
    Chris,
    Did you make any customizations or is this a plain download of WLP 7.0?
    Any
    help in reproducing this would be helpful.
    Thanks,
    Daniel Selman
    "Chris" <[email protected]> wrote in message
    news:[email protected]...
    Unfortunately, we are seeing the same phenomenon on a DELL 6450,
    2x700Mhz
    PIIIX,
    4G Ram.
    The webserver CPUs peg at 92-98%, login response times are 17sec andpage
    response
    times are 10sec and this is a test with a blank portal page, ie norendered portlets
    at all.
    On the other hand, the DB servers (same config) are struggling to reach5%
    CPU
    utilization.
    we've tweaked threads, socket readers, heap size, logging, cxn pools,and
    everything
    else we can think of.
    anyone have any ideas?
    "Daniel Selman" <[email protected]> wrote:
    Edward,
    A slightly facecious question: would you rather that the CPU was at
    50%
    utilization and the operation took twice as long?
    100% CPU utilization is not necessarily a bad thing, it depends onhow
    competing OS tasks are being scheduled by the OS and the overallperformance
    of the system.
    Sincerely,
    Daniel Selman
    "Edward" <[email protected]> wrote in message
    news:[email protected]...
    Is it normal for my CPU usage to spike to 100% everytime a page
    loads?
    I'm
    doing some minor load testing on the example StockPortal with 30
    users,
    and
    my CPU usage keeps maxing out. Even when I'm the only one on it, the
    CPU
    usage spikes to 100%.
    The machine I'm using is a 1.4 ghz Pentium with 1 gig of RAM. I
    also
    changed the cloudscape database to SQL Server 2000.
    Am I suppose to do anything else? Please email me any answers.
    Thanks,
    Edward
    [email protected]

  • High CPU usage on idle server.

    Hi
    I have a problem with a weblogic server 5.1 SP#6 running with JDK1.2.2 on a Solaris Sparc server.
    The server starts using about 80-90 % of the cpu after about 2 hours (even if it is idle). After two
    days the server hungs completely and needs to be restarted.
    During this time the server gets longer and longer response time.
    At the bottom of this post, i added a thread dump when the server had about 85% CPU usage and low
    usage.
    Gratefull for any help.
    Regards Ståle
    A SIGQUIT has been received. Do you want to:
    [ 0 ] continue program
    [ 1 ] check & print one deadlock
    [ 2 ] check & print all deadlocks
    [ 3 ] dump thread stacks
    [ 4 ] dump lock registry
    [ 5 ] heap inspection
    [ 6 ] terminate program
    Type number corresponding to selected action: Found 0 deadlock
    Full thread dump:
    "Keep-Alive-Timer:lille.hvor.no" (TID:0x2c792f8, sys_thread_t:0x2c79230, state:CW, thread_t: t@1180,
    threadID:0xe7731dc8, stack_bottom:0xe7732000, stack_size:0x20000) prio=8
    [1] java.lang.Thread.sleep(Native Method)
    [2] sun.net.www.http.ClientVector.run(KeepAliveCache.java:220)
    [3] java.lang.Thread.run(Thread.java:478)
    "Keep-Alive-Timer:www.movieseer.com" (TID:0x27b5140, sys_thread_t:0x27b5078, state:CW, thread_t:
    t@1109, threadID:0xe7791dc8, stack_bottom:0xe7792000, stack_size:0x20000) prio=8
    [1] java.lang.Thread.sleep(Native Method)
    [2] sun.net.www.http.ClientVector.run(KeepAliveCache.java:220)
    [3] java.lang.Thread.run(Thread.java:478)
    "Keep-Alive-Timer:wap.politiet.net" (TID:0x331f790, sys_thread_t:0x331f6c8, state:CW, thread_t:
    t@1100, threadID:0xe78f1dc8, stack_bottom:0xe78f2000, stack_size:0x20000) prio=8
    [1] java.lang.Thread.sleep(Native Method)
    [2] sun.net.www.http.ClientVector.run(KeepAliveCache.java:220)
    [3] java.lang.Thread.run(Thread.java:478)
    "Keep-Alive-Timer:stars927.com" (TID:0x2e6d530, sys_thread_t:0x2e6d468, state:CW, thread_t: t@919,
    threadID:0xe78c1dc8, stack_bottom:0xe78c2000, stack_size:0x20000) prio=8
    [1] java.lang.Thread.sleep(Native Method)
    [2] sun.net.www.http.ClientVector.run(KeepAliveCache.java:220)
    [3] java.lang.Thread.run(Thread.java:478)
    "Keep-Alive-Timer:wap.eurosport.com" (TID:0x32a8d88, sys_thread_t:0x32a8cc0, state:CW, thread_t:
    t@802, threadID:0xe7ac1dc8, stack_bottom:0xe7ac2000, stack_size:0x20000) prio=8
    [1] java.lang.Thread.sleep(Native Method)
    [2] sun.net.www.http.ClientVector.run(KeepAliveCache.java:220)
    [3] java.lang.Thread.run(Thread.java:478)
    "Keep-Alive-Timer:wap.caplex.net" (TID:0x320bed8, sys_thread_t:0x320be10, state:CW, thread_t: t@622,
    threadID:0xe7af1dc8, stack_bottom:0xe7af2000, stack_size:0x20000) prio=8
    [1] java.lang.Thread.sleep(Native Method)
    [2] sun.net.www.http.ClientVector.run(KeepAliveCache.java:220)
    [3] java.lang.Thread.run(Thread.java:478)
    "Thread-138" (TID:0x2540a10, sys_thread_t:0x2540948, state:CW, thread_t: t@303, threadID:0xe7da1dc8,
    stack_bottom:0xe7da2000, stack_size:0x20000) prio=1
    [1] java.lang.Thread.sleep(Native Method)
    [2] com.telenor.wamp.framework.cache.CacheHolder.run(CacheHolder.java:243)
    [3] java.lang.Thread.run(Thread.java:478)
    "HighPriority TimeEventGenerator" (TID:0x1a34788, sys_thread_t:0x1a346c0, state:CW, thread_t: t@104,
    threadID:0xe7f11dc8, stack_bottom:0xe7f12000, stack_size:0x20000) prio=9
    [1] weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:256)
    [2] weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:131)
    [3] java.lang.Thread.run(Thread.java:479)
    "ListenThread" (TID:0x1969ea0, sys_thread_t:0x1969dd8, state:R, thread_t: t@103,
    threadID:0xe7f91dc8, stack_bottom:0xe7f92000, stack_size:0x20000) prio=5
    [1] java.net.PlainSocketImpl.socketAccept(Native Method)
    [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
    [3] java.net.ServerSocket.implAccept(ServerSocket.java:238)
    [4] java.net.ServerSocket.accept(ServerSocket.java:223)
    [5] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
    "Thread-1" (TID:0x19681d0, sys_thread_t:0x1968108, state:CW, thread_t: t@102, threadID:0xe7fc1dc8,
    stack_bottom:0xe7fc2000, stack_size:0x20000) prio=1
    [1] java.lang.Thread.sleep(Native Method)
    [2] no.infohwy.djuice.common.CacheHolder.run(CacheHolder.java:215)
    [3] java.lang.Thread.run(Thread.java:479)
    "SessionMessageProcessor $SESSION$ " (TID:0x1957158, sys_thread_t:0x1957090, state:CW, thread_t:
    t@101, threadID:0xe8021dc8, stack_bottom:0xe8022000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
    [3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
    [4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
    "SessionMessageProcessor $SESSION$ " (TID:0x195adc0, sys_thread_t:0x195acf8, state:CW, thread_t:
    t@100, threadID:0xe8051dc8, stack_bottom:0xe8052000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
    [3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
    [4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
    "JMS Session Delivery Thread" (TID:0x195fe58, sys_thread_t:0x195fd90, state:CW, thread_t: t@99,
    threadID:0xe8081dc8, stack_bottom:0xe8082000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] progress.message.jclient.Session.Rv_(Session.java:1398)
    [3] progress.message.jclient.QueueSession.run(QueueSession.java:579)
    [4] progress.message.jclient.uj.run(Session$SessionThread.java:1206)
    "SessionMessageProcessor $QR$ " (TID:0x195ec50, sys_thread_t:0x195eb88, state:CW, thread_t: t@98,
    threadID:0xe80e1dc8, stack_bottom:0xe80e2000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
    [3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
    [4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
    "SessionMessageProcessor $QR$ " (TID:0x195ea30, sys_thread_t:0x195e968, state:CW, thread_t: t@97,
    threadID:0xe8111dc8, stack_bottom:0xe8112000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
    [3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
    [4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
    "SessionMessageProcessor $SESSION$ " (TID:0x194c4e0, sys_thread_t:0x194c418, state:CW, thread_t:
    t@96, threadID:0xe8141dc8, stack_bottom:0xe8142000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
    [3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
    [4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
    "SessionMessageProcessor $SESSION$ " (TID:0x1939ad0, sys_thread_t:0x1939a08, state:CW, thread_t:
    t@95, threadID:0xe8171dc8, stack_bottom:0xe8172000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
    [3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
    [4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
    "ClientListener MIP Djuice2" (TID:0x18c3db0, sys_thread_t:0x18c3ce8, state:R, thread_t: t@94,
    threadID:0xe81c1dc8, stack_bottom:0xe81c2000, stack_size:0x20000) prio=5
    [1] java.net.SocketInputStream.socketRead(Native Method)
    [2] java.net.SocketInputStream.read(SocketInputStream.java:85)
    [3] java.io.BufferedInputStream.fill(BufferedInputStream.java:171)
    [4] java.io.BufferedInputStream.read1(BufferedInputStream.java:221)
    [5] java.io.BufferedInputStream.read(BufferedInputStream.java:278)
    [6] progress.message.zclient.MgramBuffer.read(MgramBuffer.java:91)
    [7] progress.message.zclient.Mgram.<init>(Mgram.java:551)
    [8] progress.message.zclient.ClientListener.qI_(ClientListener.java:482)
    [9] progress.message.zclient.ClientListener.threadMain(ClientListener.java:267)
    [10] progress.message.zclient.DebugThread.run(DebugThread.java:54)
    "ClientSender MIP Djuice2" (TID:0x18c7a98, sys_thread_t:0x18c79d0, state:CW, thread_t: t@93,
    threadID:0xe8201dc8, stack_bottom:0xe8202000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] progress.message.zclient.ClientSender.threadMain(ClientSender.java:460)
    [3] progress.message.zclient.DebugThread.run(DebugThread.java:54)
    "SessionMessageProcessor MIP " (TID:0x1849970, sys_thread_t:0x18498a8, state:CW, thread_t: t@92,
    threadID:0xe8241dc8, stack_bottom:0xe8242000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
    [3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
    [4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
    "SessionMessageProcessor MIP " (TID:0x183c008, sys_thread_t:0x183bf40, state:CW, thread_t: t@91,
    threadID:0xe8271dc8, stack_bottom:0xe8272000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
    [3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
    [4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
    "NBExecuteThread-1" (TID:0x5b4cf8, sys_thread_t:0x5b4c30, state:CW, thread_t: t@87,
    threadID:0xe8ca1dc8, stack_bottom:0xe8ca2000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "NBExecuteThread-0" (TID:0x5afcf8, sys_thread_t:0x5afc30, state:CW, thread_t: t@86,
    threadID:0xe8cf1dc8, stack_bottom:0xe8cf2000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-74" (TID:0x5b50f8, sys_thread_t:0x5b5030, state:R, thread_t: t@85,
    threadID:0xe8d21dc8, stack_bottom:0xe8d22000, stack_size:0x20000) prio=5
    [1] java.net.PlainDatagramSocketImpl.peek(Native Method)
    [2] java.net.DatagramSocket.receive(DatagramSocket.java:348)
    [3] weblogic.cluster.TDMSocketIPM.receive(TDMSocketIPM.java:80)
    [4] weblogic.cluster.TMSocket.execute(TMSocket.java:233)
    [5] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-73" (TID:0x5b54f8, sys_thread_t:0x5b5430, state:R, thread_t: t@84,
    threadID:0xe8d71dc8, stack_bottom:0xe8d72000, stack_size:0x20000) prio=5
    [1] weblogic.socket.PosixSocketMuxer.poll(Native Method)
    [2] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
    [3] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    [4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-72" (TID:0x5c50f8, sys_thread_t:0x5c5030, state:MW, thread_t: t@83,
    threadID:0xe8da1dc8, stack_bottom:0xe8da2000, stack_size:0x20000) prio=5
    [1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
    [2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-71" (TID:0x5c60f8, sys_thread_t:0x5c6030, state:MW, thread_t: t@82,
    threadID:0xe8df1dc8, stack_bottom:0xe8df2000, stack_size:0x20000) prio=5
    [1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
    [2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-70" (TID:0x5c64f8, sys_thread_t:0x5c6430, state:R, thread_t: t@81,
    threadID:0xe8e21dc8, stack_bottom:0xe8e22000, stack_size:0x20000) prio=5
    [1] java.net.SocketOutputStream.socketWrite(Native Method)
    [2] java.net.SocketOutputStream.write(SocketOutputStream.java:87)
    [3] weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:84)
    [4] weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:99)
    [5] weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:94)
    [6] weblogic.servlet.internal.ServletOutputStreamImpl.print(ServletOutputStreamImpl.java:195)
    [7] weblogic.servlet.jsp.JspWriterImpl.print(JspWriterImpl.java:134)
    [8] jsp_servlet._projects._djuice._prod._mcommerce._mainProducts._jspService(_mainProducts.java:87)
    [9] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    [10] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
    [11] weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:96)
    [12] no.infohwy.djuice.command.CCommandServlet.doGet(CCommandServlet.java:156)
    [13] javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
    [14] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
    [15] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
    [16] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:723)
    [17] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:707)
    [18] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:76)
    [19] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:344)
    [20] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:244)
    [21] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-69" (TID:0x7c7950, sys_thread_t:0x7c7888, state:CW, thread_t: t@80,
    threadID:0xe8e71dc8, stack_bottom:0xe8e72000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-68" (TID:0x601cf8, sys_thread_t:0x601c30, state:R, thread_t: t@79,
    threadID:0xe8ea1dc8, stack_bottom:0xe8ea2000, stack_size:0x20000) prio=5
    [1] java.net.SocketInputStream.socketRead(Native Method)
    [2] java.net.SocketInputStream.read(SocketInputStream.java:85)
    [3] weblogic.socket.ResettableSocket.getPrefix(ResettableSocket.java:53)
    [4] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:109)
    [5] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:99)
    [6] weblogic.socket.JVMSocketManager.accept(JVMSocketManager.java:377)
    [7] weblogic.t3.srvr.ListenThread$RJVMListenRequest.execute(ListenThread.java:505)
    [8] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-67" (TID:0x60b0f8, sys_thread_t:0x60b030, state:R, thread_t: t@78,
    threadID:0xe8ef1dc8, stack_bottom:0xe8ef2000, stack_size:0x20000) prio=5
    [1] java.net.SocketOutputStream.socketWrite(Native Method)
    [2] java.net.SocketOutputStream.write(SocketOutputStream.java:87)
    [3] weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:84)
    [4] weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:99)
    [5] weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:94)
    [6] weblogic.servlet.internal.ServletOutputStreamImpl.print(ServletOutputStreamImpl.java:195)
    [7] weblogic.servlet.jsp.JspWriterImpl.print(JspWriterImpl.java:134)
    [8] jsp_servlet._projects._djuice._prod._mcommerce._mainProducts._jspService(_mainProducts.java:87)
    [9] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    [10] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
    [11] weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:96)
    [12] no.infohwy.djuice.command.CCommandServlet.doGet(CCommandServlet.java:156)
    [13] javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
    [14] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
    [15] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
    [16] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:723)
    [17] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:707)
    [18] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:76)
    [19] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:344)
    [20] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:244)
    [21] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-66" (TID:0x6034f8, sys_thread_t:0x603430, state:CW, thread_t: t@77,
    threadID:0xe8f21dc8, stack_bottom:0xe8f22000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-65" (TID:0x5c70f8, sys_thread_t:0x5c7030, state:CW, thread_t: t@76,
    threadID:0xe8f71dc8, stack_bottom:0xe8f72000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-64" (TID:0x616cf8, sys_thread_t:0x616c30, state:CW, thread_t: t@75,
    threadID:0xe8fa1dc8, stack_bottom:0xe8fa2000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-63" (TID:0x6384f8, sys_thread_t:0x638430, state:CW, thread_t: t@74,
    threadID:0xe8ff1dc8, stack_bottom:0xe8ff2000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-62" (TID:0x6374f8, sys_thread_t:0x637430, state:CW, thread_t: t@73,
    threadID:0xe9021dc8, stack_bottom:0xe9022000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-61" (TID:0x644cf8, sys_thread_t:0x644c30, state:CW, thread_t: t@72,
    threadID:0xe9071dc8, stack_bottom:0xe9072000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-60" (TID:0x648cf8, sys_thread_t:0x648c30, state:CW, thread_t: t@71,
    threadID:0xe90a1dc8, stack_bottom:0xe90a2000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-59" (TID:0x64dcf8, sys_thread_t:0x64dc30, state:CW, thread_t: t@70,
    threadID:0xe90f1dc8, stack_bottom:0xe90f2000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-58" (TID:0x64d0f8, sys_thread_t:0x64d030, state:CW, thread_t: t@69,
    threadID:0xe9121dc8, stack_bottom:0xe9122000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-57" (TID:0x6528f8, sys_thread_t:0x652830, state:R, thread_t: t@68,
    threadID:0xe9171dc8, stack_bottom:0xe9172000, stack_size:0x20000) prio=5
    [1] java.net.SocketInputStream.socketRead(Native Method)
    [2] java.net.SocketInputStream.read(SocketInputStream.java:85)
    [3] weblogic.socket.ResettableSocket.getPrefix(ResettableSocket.java:53)
    [4] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:109)
    [5] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:99)
    [6] weblogic.socket.JVMSocketManager.accept(JVMSocketManager.java:377)
    [7] weblogic.t3.srvr.ListenThread$RJVMListenRequest.execute(ListenThread.java:505)
    [8] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-56" (TID:0x6834f8, sys_thread_t:0x683430, state:CW, thread_t: t@67,
    threadID:0xe91a1dc8, stack_bottom:0xe91a2000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-55" (TID:0x525cf8, sys_thread_t:0x525c30, state:CW, thread_t: t@66,
    threadID:0xe91f1dc8, stack_bottom:0xe91f2000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-54" (TID:0x5260f8, sys_thread_t:0x526030, state:CW, thread_t: t@65,
    threadID:0xe9221dc8, stack_bottom:0xe9222000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-53" (TID:0x6aacf8, sys_thread_t:0x6aac30, state:CW, thread_t: t@64,
    threadID:0xe9271dc8, stack_bottom:0xe9272000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-52" (TID:0x6ab0f8, sys_thread_t:0x6ab030, state:R, thread_t: t@63,
    threadID:0xe92a1dc8, stack_bottom:0xe92a2000, stack_size:0x20000) prio=5
    [1] java.net.SocketOutputStream.socketWrite(Native Method)
    [2] java.net.SocketOutputStream.write(SocketOutputStream.java:87)
    [3] weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:84)
    [4] weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:99)
    [5] weblogic.servlet.internal.ServletOutputStreamImpl.writeStream(ServletOutputStreamImpl.java:439)
    [6] weblogic.servlet.internal.ServletOutputStreamImpl.writeStream(ServletOutputStreamImpl.java:463)
    [7] weblogic.servlet.FileServlet.sendFile(FileServlet.java:220)
    [8] weblogic.servlet.FileServlet.service(FileServlet.java:48)
    [9] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
    [10] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
    [11] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:723)
    [12] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:707)
    [13] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:76)
    [14] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:344)
    [15] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:244)
    [16] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-51" (TID:0x70e4f8, sys_thread_t:0x70e430, state:CW, thread_t: t@62,
    threadID:0xe92f1dc8, stack_bottom:0xe92f2000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-50" (TID:0x7174f8, sys_thread_t:0x717430, state:CW, thread_t: t@61,
    threadID:0xe9321dc8, stack_bottom:0xe9322000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-49" (TID:0x71d0f8, sys_thread_t:0x71d030, state:CW, thread_t: t@60,
    threadID:0xe9371dc8, stack_bottom:0xe9372000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-48" (TID:0x733a60, sys_thread_t:0x733998, state:R, thread_t: t@59,
    threadID:0xe93a1dc8, stack_bottom:0xe93a2000, stack_size:0x20000) prio=5
    [1] java.io.BufferedInputStream.read(BufferedInputStream.java:207)
    [2] jsp_servlet._projects._djuice._prod._wapalizer._index._jspService(_index.java:79)
    [3] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    [4] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
    [5] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:723)
    [6] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:707)
    [7] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:76)
    [8] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:344)
    [9] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:244)
    [10] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-47" (TID:0x73acf8, sys_thread_t:0x73ac30, state:CW, thread_t: t@58,
    threadID:0xe93f1dc8, stack_bottom:0xe93f2000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-46" (TID:0x77a0f8, sys_thread_t:0x77a030, state:CW, thread_t: t@57,
    threadID:0xe9421dc8, stack_bottom:0xe9422000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-45" (TID:0x785530, sys_thread_t:0x785468, state:CW, thread_t: t@56,
    threadID:0xe9471dc8, stack_bottom:0xe9472000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-44" (TID:0x7834f8, sys_thread_t:0x783430, state:CW, thread_t: t@55,
    threadID:0xe94a1dc8, stack_bottom:0xe94a2000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-43" (TID:0x78b0f8, sys_thread_t:0x78b030, state:CW, thread_t: t@54,
    threadID:0xe94f1dc8, stack_bottom:0xe94f2000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-42" (TID:0x78ecf8, sys_thread_t:0x78ec30, state:CW, thread_t: t@53,
    threadID:0xe9521dc8, stack_bottom:0xe9522000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-41" (TID:0x79b4f8, sys_thread_t:0x79b430, state:CW, thread_t: t@52,
    threadID:0xe9571dc8, stack_bottom:0xe9572000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-40" (TID:0x7a18f8, sys_thread_t:0x7a1830, state:CW, thread_t: t@51,
    threadID:0xe95a1dc8, stack_bottom:0xe95a2000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-39" (TID:0x7c9cf8, sys_thread_t:0x7c9c30, state:CW, thread_t: t@50,
    threadID:0xe95f1dc8, stack_bottom:0xe95f2000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-38" (TID:0x7ca0f8, sys_thread_t:0x7ca030, state:R, thread_t: t@49,
    threadID:0xe9621dc8, stack_bottom:0xe9622000, stack_size:0x20000) prio=5
    [1] java.net.SocketInputStream.socketRead(Native Method)
    [2] java.net.SocketInputStream.read(SocketInputStream.java:85)
    [3] weblogic.socket.ResettableSocket.getPrefix(ResettableSocket.java:53)
    [4] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:109)
    [5] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:99)
    [6] weblogic.socket.JVMSocketManager.accept(JVMSocketManager.java:377)
    [7] weblogic.t3.srvr.ListenThread$RJVMListenRequest.execute(ListenThread.java:505)
    [8] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-37" (TID:0x7dfcf8, sys_thread_t:0x7dfc30, state:CW, thread_t: t@48,
    threadID:0xe9671dc8, stack_bottom:0xe9672000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-36" (TID:0x7fa0f8, sys_thread_t:0x7fa030, stat

    Another Thread dump when the server have more load.
    Still running with about 90 % of the CPU
    -regards Ståle
    SIGQUIT
    A SIGQUIT has been received. Do you want to:
    [ 0 ] continue program
    [ 1 ] check & print one deadlock
    [ 2 ] check & print all deadlocks
    [ 3 ] dump thread stacks
    [ 4 ] dump lock registry
    [ 5 ] heap inspection
    [ 6 ] terminate program
    Type number corresponding to selected action: Found 0 deadlock
    Full thread dump:
    "Keep-Alive-Timer:wap.mobitel.si" (TID:0x3062ee0, sys_thread_t:0x3062e18, state:CW, thread_t:
    t@4879, threadID:0xe7a41dc8, stack_bot
    tom:0xe7a42000, stack_size:0x20000) prio=8
    [1] java.lang.Thread.sleep(Native Method)
    [2] sun.net.www.http.ClientVector.run(KeepAliveCache.java:220)
    [3] java.lang.Thread.run(Thread.java:478)
    "Keep-Alive-Timer:wap.thai2hand.com" (TID:0x2734098, sys_thread_t:0x2733fd0, state:CW, thread_t:
    t@4812, threadID:0xe7bd1dc8, stack_
    bottom:0xe7bd2000, stack_size:0x20000) prio=8
    [1] java.lang.Thread.sleep(Native Method)
    [2] sun.net.www.http.ClientVector.run(KeepAliveCache.java:220)
    [3] java.lang.Thread.run(Thread.java:478)
    "Keep-Alive-Timer:lille.hvor.no" (TID:0x2738ba0, sys_thread_t:0x2738ad8, state:CW, thread_t: t@4756,
    threadID:0xe7a71dc8, stack_bott
    om:0xe7a72000, stack_size:0x20000) prio=8
    [1] java.lang.Thread.sleep(Native Method)
    [2] sun.net.www.http.ClientVector.run(KeepAliveCache.java:220)
    [3] java.lang.Thread.run(Thread.java:478)
    "Keep-Alive-Timer:stars927.com" (TID:0x3c7fbd8, sys_thread_t:0x3c7fb10, state:CW, thread_t: t@4415,
    threadID:0xe7cd1dc8, stack_botto
    m:0xe7cd2000, stack_size:0x20000) prio=8
    [1] java.lang.Thread.sleep(Native Method)
    [2] sun.net.www.http.ClientVector.run(KeepAliveCache.java:220)
    [3] java.lang.Thread.run(Thread.java:478)
    "Thread-113" (TID:0x2089788, sys_thread_t:0x20896c0, state:CW, thread_t: t@266, threadID:0xe7e11dc8,
    stack_bottom:0xe7e12000, stack_
    size:0x20000) prio=1
    [1] java.lang.Thread.sleep(Native Method)
    [2] com.telenor.wamp.framework.cache.CacheHolder.run(CacheHolder.java:243)
    [3] java.lang.Thread.run(Thread.java:478)
    "HighPriority TimeEventGenerator" (TID:0x1bd29f0, sys_thread_t:0x1bd2928, state:CW, thread_t: t@107,
    threadID:0xe7e41dc8, stack_bott
    om:0xe7e42000, stack_size:0x20000) prio=9
    [1] weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:256)
    [2] weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:131)
    [3] java.lang.Thread.run(Thread.java:479)
    "ListenThread" (TID:0x17825c8, sys_thread_t:0x1782500, state:R, thread_t: t@103,
    threadID:0xe7f91dc8, stack_bottom:0xe7f92000, stack
    _size:0x20000) prio=5
    [1] java.net.PlainSocketImpl.socketAccept(Native Method)
    [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
    [3] java.net.ServerSocket.implAccept(ServerSocket.java:238)
    [4] java.net.ServerSocket.accept(ServerSocket.java:223)
    [5] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
    "Thread-1" (TID:0x195e9d0, sys_thread_t:0x195e908, state:CW, thread_t: t@102, threadID:0xe7fc1dc8,
    stack_bottom:0xe7fc2000, stack_si
    ze:0x20000) prio=1
    [1] java.lang.Thread.sleep(Native Method)
    [2] no.infohwy.djuice.common.CacheHolder.run(CacheHolder.java:215)
    [3] java.lang.Thread.run(Thread.java:479)
    "SessionMessageProcessor $SESSION$ " (TID:0x19505b0, sys_thread_t:0x19504e8, state:CW, thread_t:
    t@101, threadID:0xe8021dc8, stack_b
    ottom:0xe8022000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
    [3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
    [4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
    "SessionMessageProcessor $SESSION$ " (TID:0x18bf198, sys_thread_t:0x18bf0d0, state:CW, thread_t:
    t@100, threadID:0xe8051dc8, stack_b
    ottom:0xe8052000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
    [3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
    [4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
    "JMS Session Delivery Thread" (TID:0x1958158, sys_thread_t:0x1958090, state:CW, thread_t: t@99,
    threadID:0xe8081dc8, stack_bottom:0x
    e8082000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] progress.message.jclient.Session.Rv_(Session.java:1398)
    [3] progress.message.jclient.QueueSession.run(QueueSession.java:579)
    [4] progress.message.jclient.uj.run(Session$SessionThread.java:1206)
    "SessionMessageProcessor $QR$ " (TID:0x194b820, sys_thread_t:0x194b758, state:CW, thread_t: t@98,
    threadID:0xe80e1dc8, stack_bottom:
    0xe80e2000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
    [3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
    [4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
    "SessionMessageProcessor $QR$ " (TID:0x194b600, sys_thread_t:0x194b538, state:CW, thread_t: t@97,
    threadID:0xe8111dc8, stack_bottom:
    0xe8112000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
    [3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
    [4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
    "SessionMessageProcessor $SESSION$ " (TID:0x19428e0, sys_thread_t:0x1942818, state:CW, thread_t:
    t@96, threadID:0xe8141dc8, stack_bo
    ttom:0xe8142000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
    [3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
    [4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
    "SessionMessageProcessor $SESSION$ " (TID:0x192de58, sys_thread_t:0x192dd90, state:CW, thread_t:
    t@95, threadID:0xe8171dc8, stack_bo
    ttom:0xe8172000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
    [3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
    [4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
    "ClientListener MIP Djuice2" (TID:0x18c4338, sys_thread_t:0x18c4270, state:R, thread_t: t@94,
    threadID:0xe81c1dc8, stack_bottom:0xe8
    1c2000, stack_size:0x20000) prio=5
    [1] java.net.SocketInputStream.socketRead(Native Method)
    [2] java.net.SocketInputStream.read(SocketInputStream.java:85)
    [3] java.io.BufferedInputStream.fill(BufferedInputStream.java:171)
    [4] java.io.BufferedInputStream.read1(BufferedInputStream.java:221)
    [5] java.io.BufferedInputStream.read(BufferedInputStream.java:278)
    [6] progress.message.zclient.MgramBuffer.read(MgramBuffer.java:91)
    [7] progress.message.zclient.Mgram.<init>(Mgram.java:551)
    [8] progress.message.zclient.ClientListener.qI_(ClientListener.java:482)
    [9] progress.message.zclient.ClientListener.threadMain(ClientListener.java:267)
    [10] progress.message.zclient.DebugThread.run(DebugThread.java:54)
    "ClientSender MIP Djuice2" (TID:0x18b9688, sys_thread_t:0x18b95c0, state:CW, thread_t: t@93,
    threadID:0xe8201dc8, stack_bottom:0xe82
    02000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] progress.message.zclient.ClientSender.threadMain(ClientSender.java:460)
    [3] progress.message.zclient.DebugThread.run(DebugThread.java:54)
    "SessionMessageProcessor MIP " (TID:0x18ba280, sys_thread_t:0x18ba1b8, state:CW, thread_t: t@92,
    threadID:0xe8241dc8, stack_bottom:0
    xe8242000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
    [3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
    [4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
    "SessiOnMessageProcessor MIP " (TID:0x184ee78, sys_thread_t:0x184edb0, state:CW, thread_t: t@91,
    threadID:0xe8271dc8, stack_bottom:0
    xe8272000, stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
    [3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
    [4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
    "NBExecuteThread-1" (TID:0x7678f0, sys_thread_t:0x767828, state:CW, thread_t: t@87,
    threadID:0xe8ca1dc8, stack_bottom:0xe8ca2000, st
    ack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "NBExecuteThread-0" (TID:0x812d28, sys_thread_t:0x812c60, state:CW, thread_t: t@86,
    threadID:0xe8cf1dc8, stack_bottom:0xe8cf2000, st
    ack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-74" (TID:0x4fccf8, sys_thread_t:0x4fcc30, state:R, thread_t: t@85,
    threadID:0xe8d21dc8, stack_bottom:0xe8d22000, stac
    k_size:0x20000) prio=5
    [1] java.net.PlainDatagramSocketImpl.peek(Native Method)
    [2] java.net.DatagramSocket.receive(DatagramSocket.java:348)
    [3] weblogic.cluster.TDMSocketIPM.receive(TDMSocketIPM.java:80)
    [4] weblogic.cluster.TMSocket.execute(TMSocket.java:233)
    [5] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-73" (TID:0x5500f8, sys_thread_t:0x550030, state:MW, thread_t: t@84,
    threadID:0xe8d71dc8, stack_bottom:0xe8d72000, sta
    ck_size:0x20000) prio=5
    [1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
    [2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-72" (TID:0x5628f8, sys_thread_t:0x562830, state:MW, thread_t: t@83,
    threadID:0xe8da1dc8, stack_bottom:0xe8da2000, sta
    ck_size:0x20000) prio=5
    [1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
    [2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-71" (TID:0x5db0f8, sys_thread_t:0x5db030, state:R, thread_t: t@82,
    threadID:0xe8df1dc8, stack_bottom:0xe8df2000, stac
    k_size:0x20000) prio=5
    [1] weblogic.socket.PosixSocketMuxer.poll(Native Method)
    [2] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
    [3] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    [4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-70" (TID:0x5db4f8, sys_thread_t:0x5db430, state:R, thread_t: t@81,
    threadID:0xe8e21dc8, stack_bottom:0xe8e22000, stac
    k_size:0x20000) prio=5
    [1] java.net.SocketInputStream.socketRead(Native Method)
    [2] java.net.SocketInputStream.read(SocketInputStream.java:85)
    [3] com.sybase.timedio.RawDbio.reallyRead(RawDbio.java)
    [4] com.sybase.timedio.Dbio.doRead(Dbio.java)
    [5] com.sybase.timedio.InStreamMgr.readIfOwner(InStreamMgr.java)
    [6] com.sybase.timedio.InStreamMgr.doRead(InStreamMgr.java)
    [7] com.sybase.tds.TdsProtocolContext.getChunk(TdsProtocolContext.java)
    [8] com.sybase.tds.PduInputFormatter.readPacket(PduInputFormatter.java)
    [9] com.sybase.tds.PduInputFormatter.read(PduInputFormatter.java)
    [10] com.sybase.tds.TdsInputStream.read(TdsInputStream.java)
    [11] com.sybase.tds.TdsInputStream.readUnsignedByte(TdsInputStream.java)
    [12] com.sybase.tds.Tds.nextResult(Tds.java)
    [13] com.sybase.jdbc.ResultGetter.nextResult(ResultGetter.java)
    [14] com.sybase.jdbc.SybStatement.nextResult(SybStatement.java)
    [15] com.sybase.jdbc.SybStatement.updateLoop(SybStatement.java)
    [16] com.sybase.jdbc.SybStatement.executeUpdate(SybStatement.java)
    [17] com.sybase.jdbc.SybPreparedStatement.executeUpdate(SybPreparedStatement.java)
    [18] weblogic.jdbc.pool.PreparedStatement.executeUpdate(PreparedStatement.java:63)
    [19]
    com.djuice.ci.ejb.ProfileDeviceEntityPSWebLogic_CMP_RDBMS.update(ProfileDeviceEntityPSWebLogic_CMP_R
    DBMS.java:302)
    [20]
    com.djuice.ci.ejb.ProfileDeviceEntityPSWebLogic_CMP_RDBMS.store(ProfileDeviceEntityPSWebLogic_CMP_RD
    BMS.java:287)
    [21] weblogic.ejb.internal.EntityEJBContext.store(EntityEJBContext.java:170)
    [22] weblogic.ejb.internal.EntityEJBContext.beforeCompletion(EntityEJBContext.java:224)
    [23] weblogic.ejb.internal.StatefulEJBObject.postInvokeNoTx(StatefulEJBObject.java:295)
    [24] weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:697)
    [25]
    com.djuice.ci.ejb.ProfileDeviceEntityBeanEOImpl.setDateLastLogon(ProfileDeviceEntityBeanEOImpl.java:
    188)
    [26] com.djuice.ci.ejb.ProfileManagerBean.chooseProfile(ProfileManagerBean.java:1221)
    [27] com.djuice.ci.ejb.ProfileManagerBean.getProfile(ProfileManagerBean.java:221)
    [28] com.djuice.ci.ejb.ProfileManagerBeanEOImpl.getProfile(ProfileManagerBeanEOImpl.java:769)
    [29] no.infohwy.djuice.ejb.CFacadeBean.getProfile(CFacadeBean.java:170)
    [30] no.infohwy.djuice.ejb.CFacadeBeanEOImpl.getProfile(CFacadeBeanEOImpl.java:2146)
    [31]
    no.infohwy.djuice.ejb.CFacadeBeanEOImpl_ServiceStub.getProfile(CFacadeBeanEOImpl_ServiceStub.java:71
    8)
    .... remainder of stack truncated ...
    "ExecuteThread-69" (TID:0x7a21c0, sys_thread_t:0x7a20f8, state:R, thread_t: t@80,
    threadID:0xe8e71dc8, stack_bottom:0xe8e72000, stac
    k_size:0x20000) prio=5
    [1] java.net.SocketInputStream.socketRead(Native Method)
    [2] java.net.SocketInputStream.read(SocketInputStream.java:85)
    [3] com.sybase.timedio.RawDbio.reallyRead(RawDbio.java)
    [4] com.sybase.timedio.Dbio.doRead(Dbio.java)
    [5] com.sybase.timedio.InStreamMgr.readIfOwner(InStreamMgr.java)
    [6] com.sybase.timedio.InStreamMgr.doRead(InStreamMgr.java)
    [7] com.sybase.tds.TdsProtocolContext.getChunk(TdsProtocolContext.java)
    [8] com.sybase.tds.PduInputFormatter.readPacket(PduInputFormatter.java)
    [9] com.sybase.tds.PduInputFormatter.read(PduInputFormatter.java)
    [10] com.sybase.tds.TdsInputStream.read(TdsInputStream.java)
    [11] com.sybase.tds.TdsInputStream.readUnsignedByte(TdsInputStream.java)
    [12] com.sybase.tds.Tds.nextResult(Tds.java)
    [13] com.sybase.jdbc.ResultGetter.nextResult(ResultGetter.java)
    [14] com.sybase.jdbc.SybStatement.nextResult(SybStatement.java)
    [15] com.sybase.jdbc.SybStatement.updateLoop(SybStatement.java)
    [16] com.sybase.jdbc.SybStatement.executeUpdate(SybStatement.java)
    [17] com.sybase.jdbc.SybPreparedStatement.executeUpdate(SybPreparedStatement.java)
    [18] weblogic.jdbc.pool.PreparedStatement.executeUpdate(PreparedStatement.java:63)
    [19]
    com.djuice.ci.ejb.ProfileDeviceEntityPSWebLogic_CMP_RDBMS.update(ProfileDeviceEntityPSWebLogic_CMP_R
    DBMS.java:302)
    [20]
    com.djuice.ci.ejb.ProfileDeviceEntityPSWebLogic_CMP_RDBMS.store(ProfileDeviceEntityPSWebLogic_CMP_RD
    BMS.java:287)
    [21] weblogic.ejb.internal.EntityEJBContext.store(EntityEJBContext.java:170)
    [22] weblogic.ejb.internal.EntityEJBContext.beforeCompletion(EntityEJBContext.java:224)
    [23] weblogic.ejb.internal.StatefulEJBObject.postInvokeNoTx(StatefulEJBObject.java:295)
    [24] weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:697)
    [25]
    com.djuice.ci.ejb.ProfileDeviceEntityBeanEOImpl.setDateLastLogon(ProfileDeviceEntityBeanEOImpl.java:
    188)
    [26] com.djuice.ci.ejb.ProfileManagerBean.chooseProfile(ProfileManagerBean.java:1221)
    [27] com.djuice.ci.ejb.ProfileManagerBean.getCurrentProfile(ProfileManagerBean.java:3136)
    [28] com.djuice.ci.ejb.ProfileManagerBean.login(ProfileManagerBean.java:146)
    [29] com.djuice.ci.ejb.ProfileManagerBeanEOImpl.login(ProfileManagerBeanEOImpl.java:80)
    [30] no.infohwy.djuice.ejb.CFacadeBean.login(CFacadeBean.java:122)
    [31] no.infohwy.djuice.ejb.CFacadeBeanEOImpl.login(CFacadeBeanEOImpl.java:1200)
    .... remainder of stack truncated ...
    "ExecuteThread-68" (TID:0x5af0f8, sys_thread_t:0x5af030, state:R, thread_t: t@79,
    threadID:0xe8ea1dc8, stack_bottom:0xe8ea2000, stac
    k_size:0x20000) prio=5
    [1] java.net.SocketInputStream.socketRead(Native Method)
    [2] java.net.SocketInputStream.read(SocketInputStream.java:85)
    [3] weblogic.socket.ResettableSocket.getPrefix(ResettableSocket.java:53)
    [4] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:109)
    [5] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:99)
    [6] weblogic.socket.JVMSocketManager.accept(JVMSocketManager.java:377)
    [7] weblogic.t3.srvr.ListenThread$RJVMListenRequest.execute(ListenThread.java:505)
    [8] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-67" (TID:0x5dbcf8, sys_thread_t:0x5dbc30, state:R, thread_t: t@78,
    threadID:0xe8ef1dc8, stack_bottom:0xe8ef2000, stac
    k_size:0x20000) prio=5
    [1] java.net.SocketInputStream.socketRead(Native Method)
    [2] java.net.SocketInputStream.read(SocketInputStream.java:85)
    [3] weblogic.socket.ResettableSocket.getPrefix(ResettableSocket.java:53)
    [4] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:109)
    [5] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:99)
    [6] weblogic.socket.JVMSocketManager.accept(JVMSocketManager.java:377)
    [7] weblogic.t3.srvr.ListenThread$RJVMListenRequest.execute(ListenThread.java:505)
    [8] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-66" (TID:0x5b30f8, sys_thread_t:0x5b3030, state:R, thread_t: t@77,
    threadID:0xe8f21dc8, stack_bottom:0xe8f22000, stac
    k_size:0x20000) prio=5
    [1] java.io.BufferedInputStream.fill(BufferedInputStream.java:171)
    [2] java.io.BufferedInputStream.read(BufferedInputStream.java:207)
    [3] jsp_servlet._projects._djuice._prod._wapalizer._index._jspService(_index.java:79)
    [4] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    [5] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
    [6] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:723)
    [7] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:707)
    [8] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:76)
    [9] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:344)
    [10] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:244)
    [11] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-65" (TID:0x5c28f8, sys_thread_t:0x5c2830, state:R, thread_t: t@76,
    threadID:0xe8f71dc8, stack_bottom:0xe8f72000, stac
    k_size:0x20000) prio=5
    [1] java.net.SocketInputStream.socketRead(Native Method)
    [2] java.net.SocketInputStream.read(SocketInputStream.java:85)
    [3] weblogic.socket.ResettableSocket.getPrefix(ResettableSocket.java:53)
    [4] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:109)
    [5] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:99)
    [6] weblogic.socket.JVMSocketManager.accept(JVMSocketManager.java:377)
    [7] weblogic.t3.srvr.ListenThread$RJVMListenRequest.execute(ListenThread.java:505)
    [8] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-64" (TID:0x5c5cf8, sys_thread_t:0x5c5c30, state:R, thread_t: t@75,
    threadID:0xe8fa1dc8, stack_bottom:0xe8fa2000, stac
    k_size:0x20000) prio=5
    [1] java.net.SocketInputStream.socketRead(Native Method)
    [2] java.net.SocketInputStream.read(SocketInputStream.java:85)
    [3] com.sybase.timedio.RawDbio.reallyRead(RawDbio.java)
    [4] com.sybase.timedio.Dbio.doRead(Dbio.java)
    [5] com.sybase.timedio.InStreamMgr.readIfOwner(InStreamMgr.java)
    [6] com.sybase.timedio.InStreamMgr.doRead(InStreamMgr.java)
    [7] com.sybase.tds.TdsProtocolContext.getChunk(TdsProtocolContext.java)
    [8] com.sybase.tds.PduInputFormatter.readPacket(PduInputFormatter.java)
    [9] com.sybase.tds.PduInputFormatter.read(PduInputFormatter.java)
    [10] com.sybase.tds.TdsInputStream.read(TdsInputStream.java)
    [11] com.sybase.tds.TdsInputStream.readUnsignedByte(TdsInputStream.java)
    [12] com.sybase.tds.Tds.nextResult(Tds.java)
    [13] com.sybase.jdbc.ResultGetter.nextResult(ResultGetter.java)
    [14] com.sybase.jdbc.SybStatement.nextResult(SybStatement.java)
    [15] com.sybase.jdbc.SybStatement.updateLoop(SybStatement.java)
    [16] com.sybase.jdbc.SybStatement.executeUpdate(SybStatement.java)
    [17] com.sybase.jdbc.SybPreparedStatement.executeUpdate(SybPreparedStatement.java)
    [18] weblogic.jdbc.pool.PreparedStatement.executeUpdate(PreparedStatement.java:63)
    [19]
    com.djuice.ci.ejb.ProfileDeviceEntityPSWebLogic_CMP_RDBMS.update(ProfileDeviceEntityPSWebLogic_CMP_R
    DBMS.java:302)
    [20]
    com.djuice.ci.ejb.ProfileDeviceEntityPSWebLogic_CMP_RDBMS.store(ProfileDeviceEntityPSWebLogic_CMP_RD
    BMS.java:287)
    [21] weblogic.ejb.internal.EntityEJBContext.store(EntityEJBContext.java:170)
    [22] weblogic.ejb.internal.EntityEJBContext.beforeCompletion(EntityEJBContext.java:224)
    [23] weblogic.ejb.internal.StatefulEJBObject.postInvokeNoTx(StatefulEJBObject.java:295)
    [24] weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:697)
    [25]
    com.djuice.ci.ejb.ProfileDeviceEntityBeanEOImpl.getDeviceType(ProfileDeviceEntityBeanEOImpl.java:442
    [26] com.djuice.ci.ejb.ProfileManagerBean.createProfileBean(ProfileManagerBean.java:2598)
    [27] com.djuice.ci.ejb.ProfileManagerBean.getProfileBean(ProfileManagerBean.java:318)
    [28] com.djuice.ci.ejb.ProfileManagerBean.getProfilesForDevice(ProfileManagerBean.java:411)
    [29] com.djuice.ci.ejb.ProfileManagerBean.getCurrentProfile(ProfileManagerBean.java:3136)
    [30] com.djuice.ci.ejb.ProfileManagerBean.login(ProfileManagerBean.java:146)
    [31] com.djuice.ci.ejb.ProfileManagerBeanEOImpl.login(ProfileManagerBeanEOImpl.java:80)
    .... remainder of stack truncated ...
    "ExecuteThread-63" (TID:0x5e18f8, sys_thread_t:0x5e1830, state:R, thread_t: t@74,
    threadID:0xe8ff1dc8, stack_bottom:0xe8ff2000, stac
    k_size:0x20000) prio=5
    [1] java.net.SocketInputStream.socketRead(Native Method)
    [2] java.net.SocketInputStream.read(SocketInputStream.java:85)
    [3] weblogic.socket.ResettableSocket.getPrefix(ResettableSocket.java:53)
    [4] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:109)
    [5] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:99)
    [6] weblogic.socket.JVMSocketManager.accept(JVMSocketManager.java:377)
    [7] weblogic.t3.srvr.ListenThread$RJVMListenRequest.execute(ListenThread.java:505)
    [8] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-62" (TID:0x60b4f8, sys_thread_t:0x60b430, state:R, thread_t: t@73,
    threadID:0xe9021dc8, stack_bottom:0xe9022000, stac
    k_size:0x20000) prio=5
    [1] java.net.SocketInputStream.socketRead(Native Method)
    [2] java.net.SocketInputStream.read(SocketInputStream.java:85)
    [3] com.sybase.timedio.RawDbio.reallyRead(RawDbio.java)
    [4] com.sybase.timedio.Dbio.doRead(Dbio.java)
    [5] com.sybase.timedio.InStreamMgr.readIfOwner(InStreamMgr.java)
    [6] com.sybase.timedio.InStreamMgr.doRead(InStreamMgr.java)
    [7] com.sybase.tds.TdsProtocolContext.getChunk(TdsProtocolContext.java)
    [8] com.sybase.tds.PduInputFormatter.readPacket(PduInputFormatter.java)
    [9] com.sybase.tds.PduInputFormatter.read(PduInputFormatter.java)
    [10] com.sybase.tds.TdsInputStream.read(TdsInputStream.java)
    [11] com.sybase.tds.TdsInputStream.readUnsignedByte(TdsInputStream.java)
    [12] com.sybase.tds.Tds.nextResult(Tds.java)
    [13] com.sybase.jdbc.ResultGetter.nextResult(ResultGetter.java)
    [14] com.sybase.jdbc.SybStatement.nextResult(SybStatement.java)
    [15] com.sybase.jdbc.SybStatement.updateLoop(SybStatement.java)
    [16] com.sybase.jdbc.SybStatement.executeUpdate(SybStatement.java)
    [17] com.sybase.jdbc.SybPreparedStatement.executeUpdate(SybPreparedStatement.java)
    [18] weblogic.jdbc.pool.PreparedStatement.executeUpdate(PreparedStatement.java:63)
    [19]
    com.djuice.ci.ejb.ProfileDeviceEntityPSWebLogic_CMP_RDBMS.update(ProfileDeviceEntityPSWebLogic_CMP_R
    DBMS.java:302)
    [20]
    com.djuice.ci.ejb.ProfileDeviceEntityPSWebLogic_CMP_RDBMS.store(ProfileDeviceEntityPSWebLogic_CMP_RD
    BMS.java:287)
    [21] weblogic.ejb.internal.EntityEJBContext.store(EntityEJBContext.java:170)
    [22] weblogic.ejb.internal.EntityEJBContext.beforeCompletion(EntityEJBContext.java:224)
    [23] weblogic.ejb.internal.StatefulEJBObject.postInvokeNoTx(StatefulEJBObject.java:295)
    [24] weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:697)
    [25]
    com.djuice.ci.ejb.ProfileDeviceEntityBeanEOImpl.getDeviceType(ProfileDeviceEntityBeanEOImpl.java:442
    [26] com.djuice.ci.ejb.ProfileManagerBean.createProfileBean(ProfileManagerBean.java:2598)
    [27] com.djuice.ci.ejb.ProfileManagerBean.getProfileBean(ProfileManagerBean.java:318)
    [28] com.djuice.ci.ejb.ProfileManagerBean.getProfilesForDevice(ProfileManagerBean.java:411)
    [29] com.djuice.ci.ejb.ProfileManagerBean.getCurrentProfile(ProfileManagerBean.java:3136)
    [30] com.djuice.ci.ejb.ProfileManagerBean.login(ProfileManagerBean.java:146)
    [31] com.djuice.ci.ejb.ProfileManagerBeanEOImpl.login(ProfileManagerBeanEOImpl.java:80)
    .... remainder of stack truncated ...
    "ExecuteThread-61" (TID:0x607cf8, sys_thread_t:0x607c30, state:CW, thread_t: t@72,
    threadID:0xe9071dc8, stack_bottom:0xe9072000, sta
    ck_size:0x20000) prio=5
    [1] weblogic.ejb.internal.LockManagerImpl$LockEntry.waitWithtimeout(LockManagerImpl.java:262)
    [2] weblogic.ejb.internal.LockManagerImpl.waitForLock(LockManagerImpl.java:35)
    [3] weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:98)
    [4] weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:81)
    [5] weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:427)
    [6] weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObject.java:92)
    [7] weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:454)
    [8]
    com.djuice.ci.ejb.ProfileDeviceEntityBeanEOImpl.setDateLastLogon(ProfileDeviceEntityBeanEOImpl.java:
    188)
    [9] com.djuice.ci.ejb.ProfileManagerBean.chooseProfile(ProfileManagerBean.java:1221)
    [10] com.djuice.ci.ejb.ProfileManagerBean.getCurrentProfile(ProfileManagerBean.java:3136)
    [11] com.djuice.ci.ejb.ProfileManagerBean.login(ProfileManagerBean.java:146)
    [12] com.djuice.ci.ejb.ProfileManagerBeanEOImpl.login(ProfileManagerBeanEOImpl.java:80)
    [13] no.infohwy.djuice.ejb.CFacadeBean.login(CFacadeBean.java:122)
    [14] no.infohwy.djuice.ejb.CFacadeBeanEOImpl.login(CFacadeBeanEOImpl.java:1200)
    [15]
    no.infohwy.djuice.ejb.CFacadeBeanEOImpl_ServiceStub.login(CFacadeBeanEOImpl_ServiceStub.java:760)
    [16] no.infohwy.djuice.command.wap.CWapLogIn.execute(CWapLogIn.java:118)
    [17] no.infohwy.djuice.command.CCommandServletWapPda.doGet(CCommandServletWapPda.java:123)
    [18] javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
    [19] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
    [20] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
    [21] weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:96)
    [22] no.infohwy.djuice.common.LogonWapPda.doGet(LogonWapPda.java:65)
    [23] javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
    [24] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
    [25] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
    [26] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:723)
    [27] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:707)
    [28] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:76)
    [29] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:344)
    [30] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:244)
    [31] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    .... remainder of stack truncated ...
    "ExecuteThread-60" (TID:0x6124f8, sys_thread_t:0x612430, state:R, thread_t: t@71,
    threadID:0xe90a1dc8, stack_bottom:0xe90a2000, stac
    k_size:0x20000) prio=5
    [1] java.net.SocketInputStream.socketRead(Native Method)
    [2] java.net.SocketInputStream.read(SocketInputStream.java:85)
    [3] java.io.BufferedInputStream.fill(BufferedInputStream.java:171)
    [4] java.io.BufferedInputStream.read1(BufferedInputStream.java:221)
    [5] java.io.BufferedInputStream.read(BufferedInputStream.java:278)
    [6] java.io.FilterInputStream.read(FilterInputStream.java:118)
    [7] java.io.PushbackInputStream.read(PushbackInputStream.java:147)
    [8] sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:504)
    [9] sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:440)
    [10] java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:141)
    [11] jsp_servlet._projects._djuice._prod._wapalizer._index._jspService(_index.java:79)
    [12] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    [13] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
    [14] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:723)
    [15] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:707)
    [16] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:76)
    [17] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:344)
    [18] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:244)
    [19] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
    "ExecuteThread-59" (TID:0x6378f8, sys_thread_t:0x637830, state:R, thread_t: t@70,
    threadID:0xe90f1dc8, stack_bottom:0xe90f2000, stac
    k_size:0x20000) prio=5
    [1] java.net.SocketInputStream.socketRead(Native Method)
    [2] java.net.SocketInputStream.read(SocketInputStream.java:85)
    [3] weblogic.socket.ResettableSocket.getPrefix(ResettableSocket.java:53)
    [4] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:109)
    [5] weblogic.socket.JVMSocketT3.claimSocket(

  • System (ntoskrnl.exe) high cpu usage in Windows 8.1

    Sir/Mam,
    I'm having this issue since last week, when i checked it is the "system" (ntoskrnl.exe) file which is using upto 18-24% of my CPU and causing all other applications to stutter for a second (incluuding Media player, mouse pointer, everything).
    By using a Process Explorer software i found out that it's related to these values running under that file:
    " ntoskrnl.exe!RtlSidHashLookup+0x1ffc  "
    It slows down my PC for a second and it happens after every 5-6 seconds (approx.).
    Using Microsoft Windows 8.1
    Lenovo Z50-70
    Need help.

    Hi,
    The WPA shows that it is WmiPrvSE.exe (WMI Provider Host)that occupies up to 20% CPU, and three threads are the causes, 8328\7988\8828. but hard to find deeper information from this, so please use process Explorer or process monitor to find more information
    about WmiPrvSE.exe and the 3 threads, you can refer to this link
    http://social.technet.microsoft.com/Forums/en-US/77f8bc7d-663c-4c33-b732-f362c5585300/service-host-local-system-is-intermittently-using-30-of-my-cpu-windows-81?forum=w8itproperf
    Regarding to the wireless or LAN driver, I suggest you update the driver to latest version if it doesn't work fine.
    Yolanda Zhu
    TechNet Community Support

  • High cpu usage by Admin Server

    We've running iPlanet 6.0 SP5 (Sun One Web Server) on Sun Solaris 8.
    The https-admserv process used to manage the server uses significant CPU resources (usually greater that 60% of the system). This behavior is reproducible and is triggered by accessing any number of different links from within the management GUI.
    I have to resort to doing kill -9 to kill off the process.
    I've seen comparable threads in the forums. Is Sun listening?

    Hi Gerald ,
    Are you seeing this behavior with the JRE shipped by default with the server? Or are you pointing the webserver to use an external JDK like 1.4.1 or newer versions?
    Thanks,
    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

  • SQL Server 2012 - RESOURCE MONITOR / PREEMPTIVE_XE_CALLBACKEXECUTE high CPU usage

    Hello, 
      We are currently in the process of migrating an existing clustered SQL Server 2008 R2 instance over to a clustered SQL Server 2012 instance as we phase out the Windows Server 2008 with SQL Server 2008 R2.
      The setup is identical for the SQL Server 2012 instance as it is on the SQL Server 2008 R2 instance.  (meaning the RAM and CPU are both the same or better on the SQL Server 2012 instance)
      The process in which we are migrating is that we're moving a few databases over to the new SQL Server 2012 instance each night.  What we've noticed is that the CPU usage is much higher on the SQL Server 2012 instance than on the previous
    SQL Server 2008 R2 instance even though the there is only 1/2 of the databases migrated to the 2012 instance. 
      Running the following script:
    ;with cte ([totalCPU]) as (select sum(cpu) from master.dbo.sysprocesses)
    select
    tblSysprocess.spid
    , tblSysprocess.cpu
    , CONVERT(BIGINT,(tblSysprocess.cpu * CONVERT(BIGINT,100))) / CONVERT(BIGINT, cte.totalCPU) as [percentileCPU]
    , tblSysprocess.physical_io
    , tblSysprocess.memusage
    , tblSysprocess.cmd
    , tblSysProcess.lastwaittype
    from master.dbo.sysprocesses tblSysprocess
    cross apply cte
    order by tblSysprocess.cpu desc
    Produces the following results:
    In a clustered environment, is this normal and if not, does anyone know what this means or how to reduce the CPU usage?
    Thanks.

    Hello,
    The following query may help us identify extended events or audit configurations running on that SQL Server server that are producing that high CPU usage scenario.
    SELECT
    s.name
    AS 'Sessions'
    FROM
    sys.server_event_sessions
    AS s
    WHERE
    s.name
    <> 'system_health'
    and s.name
    <> 'AlwaysOn_health';
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • DNS server process, high CPU usage

    Hello,
    I am having a problem with high CPU usage on DNS process. We have 1921 setup in network of about 100 workstations that use it as DNS server. It also performs split view functionality for couple of domains in order to avoid hairpin NAT. I know that a router is not fit for heavy server duty but such setup was unfortunately necessary.
    In peak work hours we oftenly have CPU hitting 100%  with DNS server process being the root cause,and on several occasions we had DNS process stuck in such state for prolonged periods of time during which other router functions were affected (t's a default gateway, IPsec concentrator etc.). Sometimes shutting the process and restarting it would solve the problem, but once it required a full reload in order to restore functionality (such was the description that engineer on duty reported to me).
    Forwarder queue statistics:
    Current size = 0
    Maximum size = 86
    Drops        = 0
    IOS upgrade did not help, we are currently running 15.2(2)T.
    The question is ... is such behaviour (CPU load) to be expected on LAN with 100 workstations due to slow CPU on router or we have bugged IOS DNS server (requiring a TAC case)?
    The previous solution seem to do this functionality quite nicely (even though it was also a router), so I am not inclined to think that we are dealing with someone DoS-ing the DNS (WAN access to DNS is of course forbidden)
    P.S.
    Since we moved servers off the routers DNS, we do not receive complaints, but we had a couple of unresolved messages a day while mail server was using router for DNS. I am suspecting that an old bug where IOS DNS servers occasionaly sends clients back empty DNS replies (properly formatted message but without A record) could be still around?

    hi,
    i have the same problem on UC540 and 2911 on IOS 15.0.1. CPU high, router crashed. Reboot helps but until CPU usage spikes again. the only fix is to remove "ip dns server" from config and use a different DNS server
                        111                       1111    1111111111
              999999999900077777777799999777778888000099990000000000
        322222111119999900077776666622222111119999000088880000000000
    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)
    after removed IP dns server
                                           111                      
                                 99999999990007777777779999977777888
                  33333333332222211111999990007777666662222211111999
    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)

  • Mixer window can cause high CPU usage, crashes

    This is probably one of the weirdest bugs I've seen for a while. Here are the steps that I reproduce it for me, maybe someone will want to try this out and see if they get the same.
    1) Open an Empty Project template.
    2) Create 16 instrument tracks when it gives you the dialog. (even 1 will be enough, but the effect is clearer the more tracks you create)
    3) Open the mixer. Either in a window or in the pane.
    4) Now create a "multi-timbral" instrument track with the plus button (use the checkbox there).
    5) Select the 16th track, and now select one of the arrange tracks of the multi-timbral instrument.
    6) Open up Activity Monitor from your Utilities folder in Finder and see how much Logic is taking up CPU. It should be significantly higher than the idle state. On my MBP it'll be around 80%.
    This is not a problem in itself, because when reproducing it like this the high CPU usage goes away when you select another track and won't return if you select the multi-timbral instrument again.
    However, I have sessions where this will continue happening with a multi-timbral instrument all the time. Not only that, I've had Logic crash when this starts happening. And this whole thing will slow down the UI considerably when it's active.
    The workaround that seems to work for me is simply not keeping the mixer window/pane open.

    This is one of the issue which has already been raised to Microsoft and hopefully a public build will be available soon  in next cumulative update pack .
    There are variety of reason for this starting for password mismatch or password not given , SFTP adapter unable to connect and so on .
    There is good post here in below link for this issue
    http://thoughtsofmarcus.blogspot.co.uk/2013/06/leaving-password-blank-in-biztalk-2013.html
    Another greate artcicle is by Nino which states these issues .SFTP adapter is  protocol  sensitive and some configuration by server side, can cause a lot of crazy situations
    http://ninocrudele.me/2014/01/29/checkstat-and-sftp-adapter-issues/
    Thanks
    Abhishek

  • Microsoft Office 2004 -- extremely high cpu usage and virtual ram

    hi,
    when i use office it causes a very high cpu usage even when its in idle mode.
    i am unable to work with it, because its extremely slow.
    does anyone have same experiences?
    thanks for your help!
    mbp 2.0 1,5gb ram 80gb hdd   Mac OS X (10.4.7)  

    I am able to work OK with office, I'm using the 'old version' Microsoft Office v.X, not much details in the About Box, just listed as MSoft Word/Excel/etc for Mac service release 1.
    I get the occasional crash, and I have seen Word in particular use 90% of a single core and amazingly large virtual memory usage, gigabytes sometimes, but eventually the document gets printed.
    It shows how useful the dual core (or quad) cpu approach is!
    One cpu for Word to print, and one cpu to run the rest of my applications/life!
    I still use this old office rather than re-booting into Window§ for whatever is the latest version of office.
    Doing some playing with a similar one page document in Office v.X and Pages 2.01, I get Word using about 25% of a core , Pages using 5%, - whilst editing; Intel native Pages has 20% of a core and 80MB ram 480 virtual whilst printing, Word has about 100% of a core and 65MB ram 650 virtual whilst printing, but it is a powerPC code so Rosetta is in there somewhere.
    check Activity Monitor or other apps/widgets for some parasitic processes? have fun!
    many Macs 512k -> MacBool Pro 2GHz 1GB ram   Mac OS X (10.4.7)   Yes, I have Key Lime

  • SQL query against ConfigMgr DB causing 100% cpu usage on SQL server throughout day

    Hi, I am hoping someone here may have an idea of what I can do to resolve this as I am not much of a SQL guy. Here is what I know. Throughout the day, monday-friday, my ConfigMgr SQL server sits at 98-100% processor usage.
    Using the following query I have narrowed down the culprit of the high cpu usage throughout the day:
    SELECT p.spid, p.status, p.hostname, p.loginame, p.cpu, r.start_time, r.command,
    p.program_name, text
    FROM sys.dm_exec_requests AS r,
    master.dbo.sysprocesses AS p
    CROSS APPLY sys.dm_exec_sql_text(p.sql_handle)
    WHERE p.status NOT IN ('sleeping', 'background')
    AND r.session_id = p.spid
    Even though my knowledge of SQL is light, I believe the following output clearly defines the thread responsible for the high cpu usage. This "program_name" is present throughout the day and as long as its there, cpu usage remains at or near 100%:
    The text output of the above culprit is as follows (sorry this is long):
    -- Name : spDrsSummarizeSendHistory
    -- Definition : SqlObjs
    -- Scope : CAS_OR_PRIMARY_OR_SECONDARY
    -- Object : P
    -- Dependencies : <Detect>
    -- Description : Summarize DrsSendHistory information into DrsSendHistorySummary
    CREATE PROCEDURE spDrsSummarizeSendHistory
    AS
    BEGIN
    SET NOCOUNT ON;
    DECLARE @CurrentTime DateTime;
    DECLARE @SiteCode nvarchar(3);
    DECLARE @LastSummarizationTime DateTime;
    DECLARE @NextSummarizationTime DateTime;
    DECLARE @Interval INT; -- summarize interval in minutes
    DECLARE @ReplicationID INT
    DECLARE @iMaxID INT
    DECLARE @iCurrentID INT
    DECLARE @iBatchSize INT = 50
    DECLARE @ReplicationPattern NVARCHAR(255)
    DECLARE @TargetSite NVARCHAR(3);
    DECLARE @TimeTable TABLE (TargetSite NVARCHAR(3), StartTime DATETIME, EndTime DATETIME, PRIMARY KEY (TargetSite, StartTime, EndTime))
    DECLARE @TargetSites TABLE (SiteCode NVARCHAR(3) PRIMARY KEY)
    DECLARE @ChildTargetSites TABLE (TargetSite NVARCHAR(3), LastSummarizationTime DATETIME, [Interval] INT, PRIMARY KEY (TargetSite))
    DECLARE @ReplicationGroup TABLE (ID INT, ReplicationPattern NVARCHAR(255))
    IF OBJECT_ID(N'TempDB..#DrsSendHistorySummary') IS NOT NULL
    DROP TABLE #DrsSendHistorySummary
    CREATE TABLE #DrsSendHistorySummary (ID BIGINT IDENTITY(1, 1) NOT NULL, SourceSite NVARCHAR(3), TargetSite NVARCHAR(3), ReplicationGroupID INT, SyncDataSize BIGINT, CompressedSize BIGINT, UnCompressedSize BIGINT, MessageCount INT, ChangeCount INT, SummarizationTime DATETIME, PRIMARY KEY (ID))
    SET @CurrentTime = GETUTCDATE();
    SET @SiteCode = dbo.fnGetSiteCode();
    INSERT INTO @ReplicationGroup (ID, ReplicationPattern)
    SELECT RD.ID, RD.ReplicationPattern
    FROM ReplicationData RD
    WHILE EXISTS (SELECT * FROM @ReplicationGroup)
    BEGIN
    SELECT TOP (1) @ReplicationID = ID, @ReplicationPattern = ReplicationPattern FROM @ReplicationGroup
    TRUNCATE TABLE #DrsSendHistorySummary
    IF (((@ReplicationPattern = N'global' OR @ReplicationPattern=N'site') AND dbo.fnIsPrimary() = 1)
    OR (@ReplicationPattern = N'global_proxy' AND dbo.fnIsSecondary() = 1))
    BEGIN -- when current site is child
    SET @LastSummarizationTime = ISNULL(( SELECT MAX(SummarizationTime) FROM DrsSendHistorySummary WHERE SourceSite = @SiteCode AND ReplicationGroupID = @ReplicationID),
    (SELECT MIN(EndTime) FROM DrsSendHistory WHERE ReplicationGroupID = @ReplicationID) );
    SET @Interval = ISNULL((SELECT VALUE FROM RCMSQLCONTROLPROPERTY SCP, RCMSQLCONTROL SC
    WHERE SCP.ControlID = SC.ID AND SCP.Name = N'Send History Summarize Interval' AND SC.TypeID = 3 and SC.SiteNumber = dbo.fnGetSiteNumber()), 15); -- default 15 minutes
    DELETE @TargetSites
    INSERT INTO @TargetSites (SiteCode)
    SELECT DISTINCT SiteCode FROM DRS_MessageActivity_Send WHERE ReplicationID = @ReplicationID
    IF @LastSummarizationTime IS NOT NULL AND EXISTS (SELECT * FROM @TargetSites)
    BEGIN
    SET @NextSummarizationTime = DATEADD( minute, DATEDIFF(minute, 0, @LastSummarizationTime)/@Interval *@Interval + @Interval, 0);
    -- Summarized according to interval
    DELETE @TimeTable
    WHILE (@CurrentTime >= @NextSummarizationTime )
    BEGIN
    INSERT INTO @TimeTable (TargetSite, StartTime, EndTime)
    SELECT SiteCode, @LastSummarizationTime, @NextSummarizationTime FROM @TargetSites
    SET @LastSummarizationTime = @NextSummarizationTime;
    SET @NextSummarizationTime = DATEADD(mi, @Interval, @NextSummarizationTime );
    END
    INSERT INTO #DrsSendHistorySummary (SourceSite, TargetSite, ReplicationGroupID, SyncDataSize, CompressedSize, UnCompressedSize, MessageCount, ChangeCount, SummarizationTime)
    SELECT @SiteCode, T.TargetSite, @ReplicationID, SUM(ISNULL(D.SyncDataSize, 0)), SUM(ISNULL(D.CompressedSize, 0)), SUM(ISNULL(D.UnCompressedSize, 0)), SUM(ISNULL(D.MessageCount, 0)), SUM(ISNULL(ChangeCount, 0)), T.EndTime
    FROM DrsSendHistory D RIGHT JOIN @TimeTable T ON D.EndTime >= T.StartTime AND D.EndTime < T.EndTime AND ReplicationGroupID = @ReplicationID AND T.TargetSite = D.TargetSite
    GROUP BY T.TargetSite, T.StartTime, T.EndTime;
    END
    END
    ELSE IF ((@ReplicationPattern = N'global' AND dbo.fnIsCAS() = 1)
    OR (@ReplicationPattern = N'global_proxy' AND dbo.fnIsPrimary() = 1))
    BEGIN -- when current site is parent
    DELETE @ChildTargetSites
    INSERT INTO @ChildTargetSites(TargetSite, LastSummarizationTime, [Interval])
    SELECT DISTINCT(DSH.SiteCode),
    ISNULL(( SELECT MAX(SummarizationTime) FROM DrsSendHistorySummary WHERE SourceSite = @SiteCode AND ReplicationGroupID = @ReplicationID AND TargetSite=DSH.SiteCode),
    (SELECT MIN(EndTime) FROM DrsSendHistory WHERE ReplicationGroupID = @ReplicationID) ) AS LastSummarizeTime,
    ISNULL((SELECT VALUE FROM RCMSQLCONTROLPROPERTY SCP, RCMSQLCONTROL SC WHERE SCP.ControlID = SC.ID AND SCP.Name = N'Send History Summarize Interval' AND SC.TypeID = 3 and SC.SiteNumber = dbo.fnGetSiteNumberBySiteCode(DSH.SiteCode)), 15) AS Interval
    FROM DRS_MessageActivity_Send DSH WHERE DSH.ReplicationID = @ReplicationID
    GROUP BY DSH.SiteCode;
    DELETE @TimeTable
    WHILE EXISTS (SELECT * FROM @ChildTargetSites)
    BEGIN
    SELECT TOP (1) @TargetSite = TargetSite, @LastSummarizationTime = LastSummarizationTime, @Interval = Interval FROM @ChildTargetSites
    SET @NextSummarizationTime = DATEADD( minute, DATEDIFF(minute, 0, @LastSummarizationTime)/@Interval *@Interval + @Interval, 0);
    -- Summarized according to interval
    WHILE (@CurrentTime >= @NextSummarizationTime )
    BEGIN
    INSERT INTO @TimeTable (TargetSite, StartTime, EndTime)
    SELECT @TargetSite, @LastSummarizationTime, @NextSummarizationTime
    SET @LastSummarizationTime = @NextSummarizationTime;
    SET @NextSummarizationTime = DATEADD(mi, @Interval, @NextSummarizationTime );
    END
    DELETE @ChildTargetSites WHERE TargetSite = @TargetSite
    END;
    INSERT INTO #DrsSendHistorySummary (SourceSite, TargetSite, ReplicationGroupID, SyncDataSize, CompressedSize, UnCompressedSize, MessageCount, ChangeCount, SummarizationTime)
    SELECT @SiteCode, T.TargetSite, @ReplicationID, SUM(ISNULL(D.SyncDataSize, 0)), SUM(ISNULL(D.CompressedSize, 0)), SUM(ISNULL(D.UnCompressedSize, 0)), SUM(ISNULL(D.MessageCount, 0)), SUM(ISNULL(D.ChangeCount, 0)), @NextSummarizationTime
    FROM DrsSendHistory D RIGHT JOIN @TimeTable T ON D.EndTime >= T.StartTime AND D.EndTime < T.EndTime AND ReplicationGroupID = @ReplicationID AND T.TargetSite = D.TargetSite
    GROUP BY T.TargetSite, T.StartTime, T.EndTime;
    END;
    SELECT @iMaxID = MAX(ID), @iCurrentID = 0 FROM #DrsSendHistorySummary
    -- BATCH INSERT TO REAL TABLE
    WHILE (@iCurrentID < @iMaxID)
    BEGIN
    INSERT INTO DrsSendHistorySummary (SourceSite, TargetSite, ReplicationGroupID, SyncDataSize, MessageCount, ChangeCount, SummarizationTime)
    SELECT SourceSite, TargetSite, ReplicationGroupID, SyncDataSize, MessageCount, ChangeCount, SummarizationTime
    FROM #DrsSendHistorySummary WHERE ID > @iCurrentID AND ID <= (@iCurrentID + @iBatchSize)
    SET @iCurrentID = @iCurrentID + @iBatchSize
    END
    TRUNCATE TABLE #DrsSendHistorySummary
    DELETE @ReplicationGroup WHERE ID = @ReplicationID
    END
    END
    If anyone has any experience with this issue or anything similar and might be able to point me in the right direction, any responses would be greatly appreciated. Thanks for reading!

    Normally, this summary job every few mins which only summarize last few mins sending history. If the job was not running for long time, the first time, this sproc will summarize a lot more data than normal. So it could fail which will make things worse and
    worse over time.
    If sending summary data is not a big concern here, you can manually insert a dummy row with most recent time as Summarizationtime, so that, when summary job kicks in next time, it will only summary short interval data.
    DrsSendHistory is that the table records every sending on every group. This table is one of the key of replication logic. For your environment, on primary site, it could have up to 24(hrs) * 60 (mins) / 2 (sync interval) * 36(secondary sites) records per
    day for Secondary_Site_Replication_Configuration group and 24 * 60 / 5 * 22 records for Secondary Site Data.
    Umair Khan | http://blogs.technet.com/umairkhan
    Hi Umair,
    Thank you for the reply. My plan was to go ahead with your suggestions but what I tried first was to get my VM guy to give the SQL server access to more CPU resources. We had already configured it with what would have seemed to be plenty, as per Microsoft's
    sizing requirements, but I figured it couldn't hurt to rule out - he gave the SQL server access to a huge portion of the host processing power and since then CPU usage on the server has NOT been an issue.
    It would appear that the large amounts of secondary sites we have just simply put a lot of stress on the SQL server with out of the box replication settings. Since the entire VM host is for System Center only, and our other System Center servers are using
    very little resources, this solution has ended up being valid.
    Thanks again for everyone's help with this.

  • High cpu usage when moving application windows

    Hello all,
    I have two machines with arch installed:
    - an eeepc 701 surf/intel gpu(xorg driver) with xfce
    - an amd 3800+ X2/nvidia 8860 gt(proprietary driver) with kdemod3(also checked with xfce4)/arch amd64 installed.
    I noticed that when i move a window of an application(for example konsole, etc..) too fast i get high cpu usage(30-40 %), when checking with htop.
    Is it normal that the X server uses the cpu so much when moving a window??
    EDIT: up to now i tested it in a friends windows machine, and it happens exactly the same, so i guess is normal. It seems i need to be informed better about how X works :-)
    Last edited by mechmg93 (2008-10-15 08:04:10)

    today i switced back my desktop system to debian unstable and tried to see what the difference is concerning this problem.
    I found out that in kde3 the solution to the "problem" is debians kde default configuration about window behaviour.
    Especially the one mentioned below :
    In debian this is not ticked and this has as a result zero cpu usage when windows are moved.
    Last edited by mechmg93 (2008-10-23 18:36:58)

Maybe you are looking for