JMS Queue slows down after time

          Hi,
          Our system makes use of queues extensively. We, pumps trhough tens of thousands
          of messages every day . Every few days, our Weblogic 7 SP5 JMS queue slows down
          with very little activity. After restarting the instance, everything goes back
          to normal. We have about 14 queues in our system with a very high rate of throughput.
          Any ideas as to what slows down the queue requiring a restart.
          The JMS file store is excluded from anti-virus and backup software.
          Kevin
          

          Hi Tom, The memory usage is fine. 1Gb is available to the JVM and the memory usage
          is usually about 1/4th of that when we experience the issues below
          Tom Barnes <[email protected].bea.com>
          wrote:
          >Another thing to look at is server CPU usage before and
          >during the slowdown.
          >
          >Also memory usage. There may be a memory leak
          >somewhere that expands JVM memory to the point
          >where the operating system begins to page...
          >
          >Kevin Sharfman wrote:
          >
          >> Hi Tom, We are able to measure a slowdown by the time it takes to post
          >messages
          >> to a queueas well as the time for a message to be delievered off the
          >queue. Our
          >> throughput just drops dramatically. During this time, the number of
          >messages in
          >> the queues are quite low, due to the slow duration of posting a message.
          >I will
          >> try and obtain thread drumps. However, the are no error messages nor
          >logs that
          >> point to any problem. Restarting the instance, immediatly solves the
          >performance
          >> problem. This problem occurs intermittedly - sometimes once a week
          >or once every
          >> 2 weeks or even twice a week.
          >>
          >>
          >> Tom Barnes <pleasereplyinnewsgroup.weblogic.developer.interest.jms@newsgrou
          >>
          >> ps.bea.com> wrote:
          >>
          >>>Hi Kevin,
          >>>
          >>>Is the number of messages in the destination higher at
          >>>these times?
          >>>
          >>>If there is "very little activity" how can you
          >>>measure a slowdown?
          >>>
          >>>Can you force server side thread-dumps the next
          >>>time this occurs?
          >>>
          >>>Tom
          >>>
          >>>Kevin Sharfman wrote:
          >>>
          >>>
          >>>>Hi,
          >>>>
          >>>>Our system makes use of queues extensively. We, pumps trhough tens
          >>>
          >>>of thousands
          >>>
          >>>>of messages every day . Every few days, our Weblogic 7 SP5 JMS queue
          >>>
          >>>slows down
          >>>
          >>>>with very little activity. After restarting the instance, everything
          >>>
          >>>goes back
          >>>
          >>>>to normal. We have about 14 queues in our system with a very high
          >rate
          >>>
          >>>of throughput.
          >>>
          >>>>Any ideas as to what slows down the queue requiring a restart.
          >>>>
          >>>>The JMS file store is excluded from anti-virus and backup software.
          >>>>
          >>>>Kevin
          >>>
          >>
          >
          

Similar Messages

  • Server slows down after a while

    Hi all,
    I've a problem with a linux machine which slows down after running for
    some days. It usually handles about 100 request per second and after a
    while it goes down to about 5 requests per second. I'm running WL6.1Sp1
    on Linux with JDK1.3.1 and "-hotspot -ms512m -mx512m". I'm wondering if
    this is related to some problem in my code or maybe rather is a database
    issue. I took a thread dump, and the server looks idle. Does anyone see
    something unusual in this dump? Does it indicate anything else than a
    nearly totally idle server?
    Thanks for your input!
    Daniel
    Full thread dump:
    "process forker" daemon prio=1 tid=0x82fe460 nid=0x5bf6 waiting on
    monitor [0xb75ff000..0xb75ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.UNIXProcessForker.run(Native Method)
         at java.lang.Thread.run(Thread.java:484)
    "process reaper" daemon prio=1 tid=0x82fdde0 nid=0x5bf5 runnable
    [0xb77ff000..0xb77ff8c0]
         at java.lang.UNIXProcessReaper.run(Native Method)
         at java.lang.Thread.run(Thread.java:484)
    "HighPriority TimeEventGenerator" daemon prio=1 tid=0x8148b98 nid=0x5ad6
    waiting on monitor [0xb79ff000..0xb79ff8c0]
         at java.lang.Object.wait(Native Method)
         at
    weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
         at
    weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.
    java:138)
         at java.lang.Thread.run(Thread.java:484)
    "ListenThread" prio=1 tid=0x679c3c10 nid=0x5ad5 runnable
    [0xb7bff000..0xb7bff8c0]
         at java.net.PlainSocketImpl.socketAccept(Native Method)
         at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:421)
         at java.net.ServerSocket.implAccept(ServerSocket.java:243)
         at java.net.ServerSocket.accept(ServerSocket.java:222)
         at weblogic.t3.srvr.ListenThread.run(ListenThread.java:255)
    "Thread-2" prio=1 tid=0x83a3b68 nid=0x5ad3 waiting on monitor
    [0xb7dff000..0xb7dff8c0]
         at java.lang.Object.wait(Native Method)
         at java.util.TimerThread.mainLoop(Timer.java:432)
         at java.util.TimerThread.run(Timer.java:385)
    "ExecuteThread: '0' for queue: 'JMS.TimerTreePool'" daemon prio=1
    tid=0x67680b10 nid=0x5ad2 waiting on monitor [0xb7fff000..0xb7fff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: 'JMS.TimerClientPool'" daemon prio=1
    tid=0x676809e8 nid=0x5ad1 waiting on monitor [0xb81ff000..0xb81ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'JMS.TimerClientPool'" daemon prio=1
    tid=0x65a8b358 nid=0x5ad0 waiting on monitor [0xb83ff000..0xb83ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'JMS.TimerClientPool'" daemon prio=1
    tid=0x65a873b0 nid=0x5acf waiting on monitor [0xb85ff000..0xb85ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'JMS.TimerClientPool'" daemon prio=1
    tid=0x65af9d88 nid=0x5ace waiting on monitor [0xb87ff000..0xb87ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '14' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x6764bfb8 nid=0x5acc waiting on monitor [0xb89ff000..0xb89ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '13' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x67951208 nid=0x5acb waiting on monitor [0xb8bff000..0xb8bff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '12' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x67667450 nid=0x5aca waiting on monitor [0xb8dff000..0xb8dff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '11' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x679819b0 nid=0x5ac9 waiting on monitor [0xb8fff000..0xb8fff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '10' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x6799ade8 nid=0x5ac8 waiting on monitor [0xb91ff000..0xb91ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '9' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x6765d0b8 nid=0x5ac7 waiting on monitor [0xb93ff000..0xb93ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x67903838 nid=0x5ac6 waiting on monitor [0xb95ff000..0xb95ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x676688a8 nid=0x5ac5 waiting on monitor [0xb97ff000..0xb97ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x676976e8 nid=0x5ac4 waiting on monitor [0xb99ff000..0xb99ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x65ada048 nid=0x5ac3 waiting on monitor [0xb9bff000..0xb9bff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x6766e550 nid=0x5ac2 waiting on monitor [0xb9dff000..0xb9dff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x67630ea8 nid=0x5ac1 waiting on monitor [0xb9fff000..0xb9fff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x65acf508 nid=0x5ac0 waiting on monitor [0xba1ff000..0xba1ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x65ada1e8 nid=0x5abf waiting on monitor [0xba3ff000..0xba3ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x676ed050 nid=0x5abe waiting on monitor [0xba5ff000..0xba5ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'weblogic.transaction.AsyncQueue'" daemon
    prio=1 tid=0x6762af98 nid=0x5abd waiting on monitor
    [0xba7ff000..0xba7ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'weblogic.transaction.AsyncQueue'" daemon
    prio=1 tid=0x676a0838 nid=0x5abc waiting on monitor
    [0xba9ff000..0xba9ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'weblogic.transaction.AsyncQueue'" daemon
    prio=1 tid=0x6765c0d8 nid=0x5abb waiting on monitor
    [0xbabff000..0xbabff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '9' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x65ab6bf8 nid=0x5aba waiting on monitor
    [0xbadff000..0xbadff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x676865f0 nid=0x5ab9 waiting on monitor
    [0xbafff000..0xbafff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x676dfcb0 nid=0x5ab8 waiting on monitor
    [0xbb1ff000..0xbb1ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x676120f0 nid=0x5ab7 waiting on monitor
    [0xbb3ff000..0xbb3ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x67611fb0 nid=0x5ab6 waiting on monitor
    [0xbb5ff000..0xbb5ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x67699720 nid=0x5ab5 waiting on monitor
    [0xbb7ff000..0xbb7ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x67926328 nid=0x5ab4 waiting on monitor
    [0xbb9ff000..0xbb9ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x6767e820 nid=0x5ab3 waiting on monitor
    [0xbbbff000..0xbbbff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x65ab61a0 nid=0x5ab2 waiting on monitor
    [0xbbdff000..0xbbdff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x676cff58 nid=0x5ab1 waiting on monitor
    [0xbbfff000..0xbbfff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'" daemon
    prio=1 tid=0x6765ff60 nid=0x5ab0 waiting on monitor
    [0xbc1ff000..0xbc1ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'" daemon
    prio=1 tid=0x6765f958 nid=0x5aaf waiting on monitor
    [0xbc3ff000..0xbc3ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "TimeEventGenerator" daemon prio=1 tid=0x676f3818 nid=0x5aae waiting on
    monitor [0xbc5ff000..0xbc5ff8c0]
         at java.lang.Object.wait(Native Method)
         at
    weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
         at
    weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.
    java:138)
         at java.lang.Thread.run(Thread.java:484)
    "TimeEventGenerator" daemon prio=1 tid=0x676ffae8 nid=0x5aad waiting on
    monitor [0xbc7ff000..0xbc7ff8c0]
         at java.lang.Object.wait(Native Method)
         at
    weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
         at
    weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.
    java:138)
         at java.lang.Thread.run(Thread.java:484)
    "SpinnerRandomSource" daemon prio=1 tid=0x67646dd8 nid=0x5aac waiting on
    monitor [0xbc9ff000..0xbc9ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.security.SpinnerRandomBitsSource.run(SpinnerRandomBitsSource.ja
    va:57)
         at java.lang.Thread.run(Thread.java:484)
    "ExecuteThread: '14' for queue: 'default'" daemon prio=1 tid=0x6767ff00
    nid=0x5aab runnable [0xbcbff000..0xbcbff8c0]
         at java.net.SocketInputStream.socketRead(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:86)
         at
    weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:273
         at
    weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
         at
    weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '13' for queue: 'default'" daemon prio=1 tid=0x67929c90
    nid=0x5aaa waiting on monitor [0xbcdff000..0xbcdff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '12' for queue: 'default'" daemon prio=1 tid=0x65aa0b58
    nid=0x5aa9 waiting on monitor [0xbcfff000..0xbcfff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '11' for queue: 'default'" daemon prio=1 tid=0x65a9ed80
    nid=0x5aa8 waiting on monitor [0xbd1ff000..0xbd1ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '10' for queue: 'default'" daemon prio=1 tid=0x679036d0
    nid=0x5aa7 runnable [0xbd3ff000..0xbd3ff8c0]
         at java.net.SocketInputStream.socketRead(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:86)
         at
    weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:273
         at
    weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
         at
    weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '9' for queue: 'default'" daemon prio=1 tid=0x6767fdc0
    nid=0x5aa6 waiting on monitor [0xbd5ff000..0xbd5ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: 'default'" daemon prio=1 tid=0x676680f8
    nid=0x5aa5 waiting on monitor [0xbd7ff000..0xbd7ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: 'default'" daemon prio=1 tid=0x676123e0
    nid=0x5aa4 waiting on monitor [0xbd9ff000..0xbd9ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: 'default'" daemon prio=1 tid=0x6766f658
    nid=0x5aa3 waiting on monitor [0xbdbff000..0xbdbff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: 'default'" daemon prio=1 tid=0x67647858
    nid=0x5aa2 waiting on monitor [0xbddff000..0xbddff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: 'default'" daemon prio=1 tid=0x67665970
    nid=0x5aa1 waiting on monitor [0xbdfff000..0xbdfff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: 'default'" daemon prio=1 tid=0x676426d8
    nid=0x5aa0 runnable [0xbe1ff000..0xbe1ff8c0]
         at java.net.SocketInputStream.socketRead(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:86)
         at
    weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:273
         at
    weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
         at
    weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '2' for queue: 'default'" daemon prio=1 tid=0x65afac38
    nid=0x5a9f runnable [0xbe3ff000..0xbe3ff8c0]
         at java.net.SocketInputStream.socketRead(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:86)
         at
    weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:273
         at
    weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
         at
    weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '1' for queue: 'default'" daemon prio=1 tid=0x65aa1088
    nid=0x5a9e waiting on monitor [0xbe5ff000..0xbe5ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'default'" daemon prio=1 tid=0x6765ef78
    nid=0x5a9d waiting on monitor [0xbe7ff000..0xbe7ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "Thread-0" daemon prio=1 tid=0x6764ced0 nid=0x5a9c waiting on monitor
    [0xbe9ff000..0xbe9ff8c0]
         at java.lang.Thread.sleep(Native Method)
         at
    weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionMa
    nagerImpl.java:1546)
         at java.lang.Thread.run(Thread.java:484)
    "Signal Dispatcher" daemon prio=1 tid=0x808d4b0 nid=0x5a9a waiting on
    monitor [0..0]
    "Finalizer" daemon prio=1 tid=0x8086ca0 nid=0x5a97 waiting on monitor
    [0xbf3ff000..0xbf3ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:108)
         at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:123)
         at
    java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:162)
    "Reference Handler" daemon prio=1 tid=0x80851f8 nid=0x5a96 waiting on
    monitor [0xbf5ff000..0xbf5ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    java.lang.ref.Reference$ReferenceHandler.run(Reference.java:110)
    "main" prio=1 tid=0x804e750 nid=0x5a7c waiting on monitor
    [0xbfffd000..0xbfffd220]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:596)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
         at weblogic.Server.main(Server.java:35)
    "VM Thread" prio=1 tid=0x80821a8 nid=0x5a95 runnable
    "VM Periodic Task Thread" prio=1 tid=0x808c220 nid=0x5a98 waiting on
    monitor
    "Suspend Checker Thread" prio=1 tid=0x808cb68 nid=0x5a99 runnable

    There are several threads like the one below. I would think that they are the
    problem. But I don't know what they are doing - doesn't look like any application
    code.
    Mike
    "ExecuteThread: '2' for queue: 'default'" daemon prio=1 tid=0x65afac38 nid=0x5a9f
    runnable [0xbe3ff000..0xbe3ff8c0] at java.net.SocketInputStream.socketRead(Native
    Method) at java.net.SocketInputStream.read(SocketInputStream.java:86) at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:273
    ) at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24) at
    weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    ============================================================
    Daniel Hoppe <[email protected]> wrote:
    Hi all,
    I've a problem with a linux machine which slows down after running for
    some days. It usually handles about 100 request per second and after
    a
    while it goes down to about 5 requests per second. I'm running WL6.1Sp1
    on Linux with JDK1.3.1 and "-hotspot -ms512m -mx512m". I'm wondering
    if
    this is related to some problem in my code or maybe rather is a database
    issue. I took a thread dump, and the server looks idle. Does anyone see
    something unusual in this dump? Does it indicate anything else than a
    nearly totally idle server?
    Thanks for your input!
    Daniel
    Full thread dump:
    "process forker" daemon prio=1 tid=0x82fe460 nid=0x5bf6 waiting on
    monitor [0xb75ff000..0xb75ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.UNIXProcessForker.run(Native Method)
         at java.lang.Thread.run(Thread.java:484)
    "process reaper" daemon prio=1 tid=0x82fdde0 nid=0x5bf5 runnable
    [0xb77ff000..0xb77ff8c0]
         at java.lang.UNIXProcessReaper.run(Native Method)
         at java.lang.Thread.run(Thread.java:484)
    "HighPriority TimeEventGenerator" daemon prio=1 tid=0x8148b98 nid=0x5ad6
    waiting on monitor [0xb79ff000..0xb79ff8c0]
         at java.lang.Object.wait(Native Method)
         at
    weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
         at
    weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.
    java:138)
         at java.lang.Thread.run(Thread.java:484)
    "ListenThread" prio=1 tid=0x679c3c10 nid=0x5ad5 runnable
    [0xb7bff000..0xb7bff8c0]
         at java.net.PlainSocketImpl.socketAccept(Native Method)
         at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:421)
         at java.net.ServerSocket.implAccept(ServerSocket.java:243)
         at java.net.ServerSocket.accept(ServerSocket.java:222)
         at weblogic.t3.srvr.ListenThread.run(ListenThread.java:255)
    "Thread-2" prio=1 tid=0x83a3b68 nid=0x5ad3 waiting on monitor
    [0xb7dff000..0xb7dff8c0]
         at java.lang.Object.wait(Native Method)
         at java.util.TimerThread.mainLoop(Timer.java:432)
         at java.util.TimerThread.run(Timer.java:385)
    "ExecuteThread: '0' for queue: 'JMS.TimerTreePool'" daemon prio=1
    tid=0x67680b10 nid=0x5ad2 waiting on monitor [0xb7fff000..0xb7fff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: 'JMS.TimerClientPool'" daemon prio=1
    tid=0x676809e8 nid=0x5ad1 waiting on monitor [0xb81ff000..0xb81ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'JMS.TimerClientPool'" daemon prio=1
    tid=0x65a8b358 nid=0x5ad0 waiting on monitor [0xb83ff000..0xb83ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'JMS.TimerClientPool'" daemon prio=1
    tid=0x65a873b0 nid=0x5acf waiting on monitor [0xb85ff000..0xb85ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'JMS.TimerClientPool'" daemon prio=1
    tid=0x65af9d88 nid=0x5ace waiting on monitor [0xb87ff000..0xb87ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '14' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x6764bfb8 nid=0x5acc waiting on monitor [0xb89ff000..0xb89ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '13' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x67951208 nid=0x5acb waiting on monitor [0xb8bff000..0xb8bff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '12' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x67667450 nid=0x5aca waiting on monitor [0xb8dff000..0xb8dff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '11' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x679819b0 nid=0x5ac9 waiting on monitor [0xb8fff000..0xb8fff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '10' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x6799ade8 nid=0x5ac8 waiting on monitor [0xb91ff000..0xb91ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '9' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x6765d0b8 nid=0x5ac7 waiting on monitor [0xb93ff000..0xb93ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x67903838 nid=0x5ac6 waiting on monitor [0xb95ff000..0xb95ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x676688a8 nid=0x5ac5 waiting on monitor [0xb97ff000..0xb97ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x676976e8 nid=0x5ac4 waiting on monitor [0xb99ff000..0xb99ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x65ada048 nid=0x5ac3 waiting on monitor [0xb9bff000..0xb9bff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x6766e550 nid=0x5ac2 waiting on monitor [0xb9dff000..0xb9dff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x67630ea8 nid=0x5ac1 waiting on monitor [0xb9fff000..0xb9fff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x65acf508 nid=0x5ac0 waiting on monitor [0xba1ff000..0xba1ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x65ada1e8 nid=0x5abf waiting on monitor [0xba3ff000..0xba3ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'JmsDispatcher'" daemon prio=1
    tid=0x676ed050 nid=0x5abe waiting on monitor [0xba5ff000..0xba5ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'weblogic.transaction.AsyncQueue'" daemon
    prio=1 tid=0x6762af98 nid=0x5abd waiting on monitor
    [0xba7ff000..0xba7ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'weblogic.transaction.AsyncQueue'" daemon
    prio=1 tid=0x676a0838 nid=0x5abc waiting on monitor
    [0xba9ff000..0xba9ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'weblogic.transaction.AsyncQueue'" daemon
    prio=1 tid=0x6765c0d8 nid=0x5abb waiting on monitor
    [0xbabff000..0xbabff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '9' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x65ab6bf8 nid=0x5aba waiting on monitor
    [0xbadff000..0xbadff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x676865f0 nid=0x5ab9 waiting on monitor
    [0xbafff000..0xbafff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x676dfcb0 nid=0x5ab8 waiting on monitor
    [0xbb1ff000..0xbb1ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x676120f0 nid=0x5ab7 waiting on monitor
    [0xbb3ff000..0xbb3ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x67611fb0 nid=0x5ab6 waiting on monitor
    [0xbb5ff000..0xbb5ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x67699720 nid=0x5ab5 waiting on monitor
    [0xbb7ff000..0xbb7ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x67926328 nid=0x5ab4 waiting on monitor
    [0xbb9ff000..0xbb9ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x6767e820 nid=0x5ab3 waiting on monitor
    [0xbbbff000..0xbbbff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x65ab61a0 nid=0x5ab2 waiting on monitor
    [0xbbdff000..0xbbdff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '__weblogic_admin_rmi_queue'" daemon
    prio=1 tid=0x676cff58 nid=0x5ab1 waiting on monitor
    [0xbbfff000..0xbbfff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'" daemon
    prio=1 tid=0x6765ff60 nid=0x5ab0 waiting on monitor
    [0xbc1ff000..0xbc1ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'" daemon
    prio=1 tid=0x6765f958 nid=0x5aaf waiting on monitor
    [0xbc3ff000..0xbc3ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "TimeEventGenerator" daemon prio=1 tid=0x676f3818 nid=0x5aae waiting
    on
    monitor [0xbc5ff000..0xbc5ff8c0]
         at java.lang.Object.wait(Native Method)
         at
    weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
         at
    weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.
    java:138)
         at java.lang.Thread.run(Thread.java:484)
    "TimeEventGenerator" daemon prio=1 tid=0x676ffae8 nid=0x5aad waiting
    on
    monitor [0xbc7ff000..0xbc7ff8c0]
         at java.lang.Object.wait(Native Method)
         at
    weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
         at
    weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.
    java:138)
         at java.lang.Thread.run(Thread.java:484)
    "SpinnerRandomSource" daemon prio=1 tid=0x67646dd8 nid=0x5aac waiting
    on
    monitor [0xbc9ff000..0xbc9ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.security.SpinnerRandomBitsSource.run(SpinnerRandomBitsSource.ja
    va:57)
         at java.lang.Thread.run(Thread.java:484)
    "ExecuteThread: '14' for queue: 'default'" daemon prio=1 tid=0x6767ff00
    nid=0x5aab runnable [0xbcbff000..0xbcbff8c0]
         at java.net.SocketInputStream.socketRead(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:86)
         at
    weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:273
         at
    weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
         at
    weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '13' for queue: 'default'" daemon prio=1 tid=0x67929c90
    nid=0x5aaa waiting on monitor [0xbcdff000..0xbcdff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '12' for queue: 'default'" daemon prio=1 tid=0x65aa0b58
    nid=0x5aa9 waiting on monitor [0xbcfff000..0xbcfff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '11' for queue: 'default'" daemon prio=1 tid=0x65a9ed80
    nid=0x5aa8 waiting on monitor [0xbd1ff000..0xbd1ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '10' for queue: 'default'" daemon prio=1 tid=0x679036d0
    nid=0x5aa7 runnable [0xbd3ff000..0xbd3ff8c0]
         at java.net.SocketInputStream.socketRead(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:86)
         at
    weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:273
         at
    weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
         at
    weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '9' for queue: 'default'" daemon prio=1 tid=0x6767fdc0
    nid=0x5aa6 waiting on monitor [0xbd5ff000..0xbd5ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: 'default'" daemon prio=1 tid=0x676680f8
    nid=0x5aa5 waiting on monitor [0xbd7ff000..0xbd7ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: 'default'" daemon prio=1 tid=0x676123e0
    nid=0x5aa4 waiting on monitor [0xbd9ff000..0xbd9ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: 'default'" daemon prio=1 tid=0x6766f658
    nid=0x5aa3 waiting on monitor [0xbdbff000..0xbdbff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: 'default'" daemon prio=1 tid=0x67647858
    nid=0x5aa2 waiting on monitor [0xbddff000..0xbddff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: 'default'" daemon prio=1 tid=0x67665970
    nid=0x5aa1 waiting on monitor [0xbdfff000..0xbdfff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: 'default'" daemon prio=1 tid=0x676426d8
    nid=0x5aa0 runnable [0xbe1ff000..0xbe1ff8c0]
         at java.net.SocketInputStream.socketRead(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:86)
         at
    weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:273
         at
    weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
         at
    weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '2' for queue: 'default'" daemon prio=1 tid=0x65afac38
    nid=0x5a9f runnable [0xbe3ff000..0xbe3ff8c0]
         at java.net.SocketInputStream.socketRead(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:86)
         at
    weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:273
         at
    weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
         at
    weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '1' for queue: 'default'" daemon prio=1 tid=0x65aa1088
    nid=0x5a9e waiting on monitor [0xbe5ff000..0xbe5ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'default'" daemon prio=1 tid=0x6765ef78
    nid=0x5a9d waiting on monitor [0xbe7ff000..0xbe7ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "Thread-0" daemon prio=1 tid=0x6764ced0 nid=0x5a9c waiting on monitor
    [0xbe9ff000..0xbe9ff8c0]
         at java.lang.Thread.sleep(Native Method)
         at
    weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionMa
    nagerImpl.java:1546)
         at java.lang.Thread.run(Thread.java:484)
    "Signal Dispatcher" daemon prio=1 tid=0x808d4b0 nid=0x5a9a waiting on
    monitor [0..0]
    "Finalizer" daemon prio=1 tid=0x8086ca0 nid=0x5a97 waiting on monitor
    [0xbf3ff000..0xbf3ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:108)
         at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:123)
         at
    java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:162)
    "Reference Handler" daemon prio=1 tid=0x80851f8 nid=0x5a96 waiting on
    monitor [0xbf5ff000..0xbf5ff8c0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at
    java.lang.ref.Reference$ReferenceHandler.run(Reference.java:110)
    "main" prio=1 tid=0x804e750 nid=0x5a7c waiting on monitor
    [0xbfffd000..0xbfffd220]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:596)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
         at weblogic.Server.main(Server.java:35)
    "VM Thread" prio=1 tid=0x80821a8 nid=0x5a95 runnable
    "VM Periodic Task Thread" prio=1 tid=0x808c220 nid=0x5a98 waiting on
    monitor
    "Suspend Checker Thread" prio=1 tid=0x808cb68 nid=0x5a99 runnable

  • AME CS4 Batch - Slow Down After First File

    I've been using AME to batch timelines from various different Premiere Pro projects. Problem is the first one in the batch will take the normal amount of time around 2 hours. Then everyone in the batch after that takes 5 hours.
    If I stop the encode once it gets to the second file and slows. And then restart the program and put that one as first it renders in a fraction of the time....
    Why does AME drastically slow down after the first file in the queue?

    Where do you close the ResultSet?
    Where do you close the Statement?
    Presumably you only create one connection for all users or you close it somewhere.

  • System Slow-Down After Printing

    I recently installed Mountain Lion. Over the last couple of weeks I have noticed a significant operating system (10.8.2) slow down after printing with my Epson R3000 printer. This happens after every printing session. When I say slow-down I mean significant delays and dreading "beachballs" when opening applications, selecting menu items or anything else I should choose to do. I'm left with re-starting the computer to get going normally again.After re-atarting I have gone to "verify permissions" and I get approx "5" pages of permission errors, all associated with the printer library in some fashion or another. I then repair all those permissions and re-start my MacPro. The operating system then works as normal and I can use the computer with no problems (until I start printing again). I mainly use the computer for photo editing with Adobe Photoshop CS6, Adobe Lightroom 4 and Aperture 3.2.
    I did not have this problem before upgrading to Mountain Lion (and then to 10.8.2). I did not get "significant" permission errors before upgrading. Since all printer drivers for this printer are handled now by Apple via the "new" Software Update process I can't even re-download the Epson printer driver and start over. I'm completely at a loss as to what, associated with the printer function, is causing these "significant" permission errors and subsequent operating system slow down. My printer is almost brand new and was working flawlessly before Mountain Lion. Let me be clear though, I can print fine. My problem is the system slow down after using the print function which I am only guessing has something to do with the "5" pages of permission errors after printting photos (with CS6/Lightroom/Aperture).
    Incidently, I am not in any way a computer expert. Verifying and repairing permissions is about all I know how to do that's why I need help. I also just thought I would try the forums first before going to technical support to see what people thought about this.
    Again, I repair the permission errors, re-start my system and all is fine. Any further suggestions would be deeply appreciated.

    When you see a beachball cursor or the slowness is especially bad, note the exact time: hour, minute, second.  
    These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad and start typing the name.
    The title of the Console window should be All Messages. If it isn't, select
              SYSTEM LOG QUERIES ▹ All Messages
    from the log list on the left. If you don't see that list, select
              View ▹ Show Log List
    from the menu bar at the top of the screen.
    Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above.
    Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first.
    Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
    The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
    Please don't indiscriminately dump thousands of lines from the log into this discussion.
    Please don't post screenshots of log messages—post the text.
    Some private information, such as your name, may appear in the log. Anonymize before posting.

  • System slow down after lion update 8/18/11

    Has anyone else had a problem with their system slowing down after downloading the system update for Lion on 8/18?  My system is not nearly as responsive and is only about two weeks old and have not installed any software other than Microsoft Office 2011 when I bought the machine.  Any ideas?

    Ok my system is booting and shutting down faster now.. This method worked for me:
    First, I repaired the permissions:
    1) Open up Disk Utility
    2) Select your hard drive
    3) Now select Repair Disk Permissions.
    Then, I deleted the caches folder:
    1) From the Finder's Go menu, select Go To Folder, and go to this folder: /Library
    2) Delete everything inside the Caches folder (This might require the Admin Username & Password)
    Finally, go to System Preferences and click on Startup Disc then click on your boot drive (In my case I've selected my HD labeled "Macintosh HD Mac OS X, 10.7.1". Now do a restart by clicking on the Restart button. If you don't have a Startup drive selected your mac will waste time at boot searching for a suitable boot drive !
    I Hope this works for you as well.
    Cheers!

  • System slow down after upgrade to 10.10.2

    Still have a slow down after updating to 10.10.2    
    Tried everything I can think of.
    Get spinning color wheel for a long time when opening even small files. Scrolling through folders, cursor hangs for a moment. opening and saving takes much longer.
    Used HD repair and repaired permissions and diagnosed HD.  No problems.
    Looking at Activity Monitor, I don't see anything that stand out-
    -C

    When you see a beachball cursor or the slowness is especially bad, note the exact time: hour, minute, second.  
    These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad and start typing the name.
    The title of the Console window should be All Messages. If it isn't, select
              SYSTEM LOG QUERIES ▹ All Messages
    from the log list on the left. If you don't see that list, select
              View ▹ Show Log List
    from the menu bar at the top of the screen.
    Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above.
    Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first.
    Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
    The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
    Please don't indiscriminately dump thousands of lines from the log into this discussion.
    Please don't post screenshots of log messages—post the text.
    Some private information, such as your name, may appear in the log. Anonymize before posting.

  • Lightroom workflow slows down after modifying an image

    Hi fellow users,
    Lightroom 4.3 runs smoothly if I work on unmodified images.
    However, if I apply modifications on an image, retouching it afterwards becomes much slower, even if I render a preview AFTER I made modifications on the image.
    I tell you an example: I import a raw file to the program and I render it`s preview. Then I retouch the image - it works very fast, no waiting time, no Loading overlay.
    Where the problem starts: I import a raw file, I apply some modifications on it (for example a preset), then I render it`s preview - then I want to do more modifications on the image, which becomes very slow.
    I was monitoring the cpu usage of the computer. In the first case, the cpu usage during modifying the image is normal.
    In the second case, it goes up to 100%.
    It seems that applying modifications on an image makes working on it slow, no matter if you have the most up-to-date preview or not.
    Anyone knows if it is normal or not?
    Is there any solution to this?
    Thanks,
    Tamas
    My configuration:
    Windows 7 64 bit (up to date)
    Lightroom 4.3 64 bit
    Fast PC
    lightroom settings:
    camera raw cache: 20gb
    video cache: 10gb

    First of all, you can forget about the preview rendering, that's irrelevant. Previews are only used by the Library module, not the Develop module. In Develop, it's handled by the ACR cache.
    Now, as for slowing down after initial adjustments, that's a variable I haven't looked out for. But it could well be correct (it would explain some weird results I got across two machines recently).
    In general, Lightroom 4 performs well below expected standards on some systems, while others fly along, and it seems nobody can explain why. Long story, do a search on this forum and you'll come up with several lengthy threads. The problem is that there are so many variables in this that it's almost impossible to even define what "slow" means. And now you've added another (interesting) one...

  • Why do my loops slow down after many iterations

    My Vi seems to freeze up or slow down after several iterations of the loop. This is an Analog Input Capture VI.
    Attachments:
    Final_Main_VI_with_working_amp.vi ‏456 KB

    First of all, thank you for your contribution. You are right to say that I have no need in changing the AI Config every time that the loop runs. But as this is supposed to be a soft-scope, I need to be able to update the parameters associated with AI Start while the loop is running (e.g. trigger level).
    I have tried to move the AI Config subVI out of both loops but the error as a result is: "No transfer in progress for the specified source."
    I also need a sampling rate of exactly 96kHz. I realize that the laptop clock cannot attain this value. Do you know how I could get exactly 96kHz.
    Attachments:
    Final_Main_VI_with_working_amp.vi ‏498 KB

  • Adobe slowed down after running fine on a Mac Book Pro Photoshop settings have been reset

    adobe slowed down after running fine on a Mac Book Pro.   Adobe Settings have been Reset

    Hello Gener7,
         I did try everything on the FAQ page (all steps) I also did them a few more times with "Adobe help" walking me through 2 more times.  I just don't get it, I have been on with Adobe on some days up to 5 hours at a time for over a month now.  I think it must be something with the installation disc but they say no, no, switchboard is just not working on my OS X 10.9.4.  I even took the computer into the apple store here and had them look it over, reinstall everything and they say it's the Adobe software.
         Thank you very much for your help, it's nice to know someone is reading this :-)  I do work around this by saving the files and reopening them in the next program I need but everyone in class is always waiting on me, (it sucks) and I just think it should work.  Hope you have a good day and I will put an update on here if this is ever figured out.
    Thanks one more time :-)

  • RFGuns slowing down several times a day

    Hello,
    RFGuns in our warehouse really slow down several times a day and start taking time. I am wondering if this is a network problem. Any ideas where to look? Thanks

    Irfan sheikh wrote:
    Hello,
    > RFGuns in our warehouse really slow down several times a day and start taking time. I am wondering if this is a network problem. Any ideas where to look? Thanks
    Try to determin when the issue started and whether or not any changes went in when the problem started, updated security measures? new access points, switches and such? any thing related to RF connectivity has changed?
    After checking with network team, they should monitor, look for network issues, check sygnal strength
    1. check with network security team, ask if they run scans durring the times you see slowness
    2. check for batch jobs that might suck system resources (financial batch jobs can slow entire sytems)
    3. check for firmware updates for the devices, some devices have known issues w/newer secure networks
    4. do server analysis to make sure enough resources are devoted to the boxes that handle the transactions
    good luck

  • Slow down after installing Lion OS

    My Macbook pro later than 2009 model slowed down after installing the new OS Lion
    any suggestions to speed it up

    First suggestion ,there have been a number of identical user questions like yours, in the Lion Community. If you want to talk to other MacBook Pro owners, try the forum they have.
    http://www.apple.com/support/macbookpro
    What you do not need is some gizmo to "speed up" or clean caches etc.
    Maybe you need to make more room on your hard drive, or add more RAM.
    For now, hold down Command-R and run Disk Utility to check the health of your system drive (Lion Recovery Mode)
    http://www.apple.com/support/lion

  • Compleat system slow down after current updates

    Has anyone learned why we all seem to have a compleat system slow down after the current set of updates? Everything works, but is VERY slow to respond. Even iTunes 7.1.1 plays video choppy now. Audio track plays fine however. Odd.
    -Apple //GS

    First of all, try repairing your permissions with Applications> Utilities> Disk Utility. Select the hard drive you're running off of and then click the Repair Permissions button.
    If that doesn't work I'd do an archive and install:
    http://docs.info.apple.com/article.html?artnum=107120
    Then run the combo update(s) instead of the consecutive ones. That seems to be working for a lot of people, but it will probably take a while.

  • Has anyone noticed MacBook Air slowing down after installing Maverick

    Has anyone noticed MacBook Air slowing down after installing Maverick?

    Activity Monitor - Mavericks
    Activity Monitor in Mavericks has significant changes
    Performance Guide
    Why is my computer slow
    Why your Mac runs slower than it should
    Slow Mac After Mavericks
    Things you can do to resolve slowdowns  see post by Kappy

  • EA6200 slows down over time and needs reboot

    Anyone with a EA6200 notice it slowing down after about a week of use?  I just replaced my e2000 with a EA6200 and its runs very well for about a week.  After about a week I notice it slows down.  Pages start loading very slow on all of my devices on my 2.4ghz and 5ghz ssids.  It slows down to a point where it takes forever just to get logged into the router to and get to the page where I can reboot it so I know its the router.  Once I reboot it, it runs great for about another week.  Its using newest firmware.  I have 2.4ghz set to 20mhz and 5ghz set to 80mhz, channels set to auto.  Nothing to customized beyond that.

    Try:
    Connectivity => Administration => Cut through Forwarding => Uncheck
    If IPv6 isn't required by your ISP; Connectivity => Internet Settings => IPv6 => Edit => Uncheck Enable
    Media Prioritization => Enable => Check
    Media Prioritization => Settings and apply accurate Downstream and if available Upstream values; Initially keep all devices and Apps normal priority
    If you have throughput issues on Wifi try Disabling WMM support (EA6200\6400); if no difference is notice re-enable WMM
    Please remember to Kudo those that help you.
    Linksys
    Communities Technical Support

  • Windows 8.1 gradually slows down after hours. Speed returns normal if restart "explorer.exe".

    I have Windows 8.1 Pro (x64) installed on Alienware M17x. The slowdown mostly appears as slow response in the situation such as open a folder/window, open/close/switch tabs in IE, drag window, and there's also cursor lag. It gradually
    slows down after system boot, noticeable after 3-4 hours, really slow after 8-9 hours.
    I have thought about many possible processes which can cause this issue, and then I found out that it's caused by "explorer.exe". If I kill "explorer.exe", the speed suddenly becomes normal. Then, I restart explorer.exe
    again, it stays normal, and then it still gradually slows down again after hours.
    I have checked driver or software compatibility. Also, CPU usage and Disk usage is normal.
    Please give some advises, reasoning, or solutions.

    SaccoSVD
    The process that is causing the problem is called sidebar.exe and I am curious why it is running on a win 8 machine as I dont believe it is built in. (It seems to have over 22,000 instances launched so I suspect either malware or a broken app)
    It is usually associated with a Vista machine, or updated win 7 machine.  Did you do do a clean install?  Have you run a malwarebytes scan?
    Please download the free version of Malwarebytes.
    Update it immediately.
    Do a full system scan
    Let us know the results at the end.
    http://www.malwarebytes.org/products
    Wanikiya and Dyami--Team Zigzag

Maybe you are looking for

  • [JS][CS3]Applying Character Style to First Word

    I am a noob as far as Javascript  is concerned, and I was hoping for a little guidance. Here's my scenario: I have a book that has been typeset all in one file; the main content is all in one story. I want to select the first word of every text frame

  • Weblogic Cluster and Perfoemance Reduction

              Hi All,           Is there a performance reduction caused by using Weblogic Clustering?           I am experiencing much slower performance in my clustered           environment compared to my non-clustered environment. They           are b

  • Mac acrobat 9 full using Reader 10.1 Filliable form

    I'm sure this is a Compatibility issue... Fillable form made on MAC 9 full version. Sales staff using PC on Reader 10.1 Text fields are fin. The Check boxes will not work. Any Ideas??

  • How to keep playing when Premiere window not on focus?

    I make home movies in Premiere, which means putting together a lot of spontaneous clips. Because of that, I must censor them on the editing table so that no disgusting, gossipy or insulting comment gets burned to a disc and sent to my relatives. Adob

  • Problem to install office mac

    i'm trying to install office mac but it asks me to close safari. I have no safari window that is open... what do I have to do?, i'm trying to install office mac but it asks me to close safari. I have no safari window that is open... what do I have to