Query slows down after second run for Index Organised Tables

We are trying to optimise our application which supports MSSQL to run with Oracle 9i for one of our customers.
We have created one database with normal tables and PK constraints/indexes and turned caching on for the tables, this seems to work well but no way as fast as MSSQL on similar hardware. The first run of query was slower but as the caching became more effective the query times came down.
So we investigated turning the tables into Index Organised Tables. We ran analyze on the new indexed tables and the response time of one of our more complex queries became akin to MSSQL. We ran the same query 5 seconds later and it took about 3 times longer to return the same data. Subsequent runs produced the same result.
We have run the same query on both styles of tables and also run showplans on the two queries, the regular table returns a cost of 190 and the IOT 340. This would point to the fact that we should use the regular tables for our queries but why did the IOT set return much faster for the first run after the analyze then slow down as if the stats were missing, but the execution plan remain the same.
Any help would be appreiciated.
Darren Fitzgibbon

could be a lot of reasons:
1. Is Oracle the only process that runs on this server? Could it be any other process (i.e. MSSQL) that took the the resources during the secodn run?
2. Is this the only query that was running during your tests? Could there be another query that put the load on the database when you were running the second test?
3. The autotrace statistics and explain plan would be useful for first and second run
(how to use autotrace:
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96533/autotrac.htm#1018
4. If you run the same process again several times - how does the response time change?
Mike

Similar Messages

  • Query slows down after upgrade

    Hi,
    After upgrade from oracle 10 to oracle 11 a simple query is slowing down alot.
    Same amount of records, same table only the execution cost time is increased
    Can someone give me some feedback over this problem?
    Can I check some things to look into the problem?
    Thx in advance.
    Greetings
    query:
    Select nvl(sum(a.BM_OPENSTAAND_DEBET- a.BM_OPENSTAAND_CREDIT),0)
    from bh.bh123gh a
    where
    a.F123_AR_NR>='4400000000' and
    a.F123_AR_NR<='4404000000' and
    a.F123_KL_LEV_AR_NR='0631001000' and
    a.SRT_REK=2 and
    a.F123_BKJR>=0000 and
    a.F123_BKJR<=2011 and
    a.F123_FIRMA=2
    explain plans
    oracle 11
    cost 1,792
    Bytes: 38
    Cardinality: 1
    oracle 10
    cost 1,594
    Bytes: 38
    Cardinality: 1

    >
    After upgrade from oracle 10 to oracle 11 a simple query is slowing down alot.
    Same amount of records, same table only the execution cost time is increased
    Can someone give me some feedback over this problem?
    Can I check some things to look into the problem?
    Thx in advance.
    >
    Is it just one query or all queries are behaving strangely? If it's just one query, do a trace and see where it's slowing down.
    In the meanwhile, you can also modify the optimizer_features_enable parameter at session level and check the explain plan.
    Alter session set optimizer_features_enable='10.2.0.5';
    Now test the query.
    By the way, if you are just worried about the COST factor, you can just ignore it. COST by itself has no real meaning. You will only have to look at the response time.
    Regards

  • 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 :-)

  • Since the update to Yosemite the MacBook has slowed down appreciably. Safari for example takes upwards of 30 seconds to load. How can I speed things up?

    Since the update to Yosemite the MacBook has slowed down appreciably. Safari for example takes upwards of 30 seconds to load. How can I speed things up?

    Hi ..
    Not enough free storage space can slow your Mac down.
    Click your Apple menu icon top left in your screen. From the drop down menu click About This Mac > More Info > Storage. Make sure there's at least 15% free disk space.
    Freeing space on your Mac OS X startup disk
    OS X Tips Where did my Disk Space go?
    Check to see if the startup disk needs repairing.
    Launch Disk Utility located in HD > Applications > Utillities
    Select the startup disk on the left then select the First Aid tab.
    Click:  Verify Disk (not Verify Disk Permissions)
    If Disk Utility reports errors, restart your Mac while holding down the Command + R keys. From there you should be able to access the built in utilities in OS X Recovery to repair the startup disk.
    Make sure to back up all important data first before using OS X Recovery.
    Anti virus software, as well as third party Mac cleaning utilities such as MacKeeper  and CleanMyMac can also slow your Mac down.
    For Safari.
    Open a Finder window. From the Finder menu bar click Go > Go to Folder
    Type or copy paste the following
    ~/Library/Caches/com.apple.Safari/Cache.db
    Click Go then move the Cache.db file to the Trash.
    Relaunch Safari to test. if that doesn't help, troubleshoot Safari extensions.
    From the Safari menu bar click Safari > Preferences then select the Extensions tab. Turn that OFF, quit and relaunch Safari to test.
    If that helped, turn one extension on then quit and relaunch Safari to test until you find the incompatible extension then click uninstall.

  • Query slow down when added a where clause

    I have a procedure that has performance issue, so I copy some of the query and run in the sql plus and try to spot which join cause the problem, but I get a result which I can figuer out why. I have a query which like below:
    Select Count(a.ID) From TableA a
    -- INNER JOIN other tables
    WHERE a.TypeID = 2;
    TableA has 140000 records, when the where clause is not added, the count return quite quick, but if I add the where clause, then the query slow down and seems never return so I have to kill my SQL Plus session. TableA has index on TypeID and TypeID is a number type. When TablA has 3000 records, the procedure return very quick, but it slow down and hang there when the TableA contains 140000 records. Any idea why this will slow down the query?
    Also, the TypeID is a foreign key to another table (TableAType), so the query above can written as :
    Select Count(a.ID) From TableA a
    -- INNER JOIN other tables
    INNER JOIN TableAType atype ON a.TypeID = atype.ID
    WHERE atype.Name = 'typename';
    TableAType table is a small table only contains less than 100 records, in this case, would the second query be more efficient to the first query?
    Any suggestions are welcome, thanks in advance...
    Message was edited by:
    user500168

    TableA now has 230000 records and 28000 of them has the TypeID 2.
    I haven't use the hint yet but thank you for your reply which let me to to run a query to check how many records in TableA has TypeID 2. When I doing this, it seems pretty fast. So I begin with the select count for TableA only and gradually add table to join and seems the query is pretty fast as long as TableA is the fist table to select from.
    Before in my query TableA is the second table to join from, there is another table (which is large as well but not as large as TableA) before TableA. So I think this is why it runs slow before. I am not at work yesterday so the query given in my post is based on my roughly memory and I forget to mention another table is joined before TableA, really sorry about that.
    I think I learn a lesson here, the largest table need to be in the begining of the select statement...
    Thank you very much everyone.

  • 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...

  • 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

  • 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.

  • 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.

  • 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.

  • 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

  • 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.

  • Why does my data logging program slow down after a while?

    A data logging program created with Labview 5.1. Slows down after a few weeks and creates files in the Temp. directory.Computer is Siemens Scenic pro 124 MB ram and AT-MIO-16XE50 Data acquisition board. Also using Solartron Dig. probes and Fieldpoint units.

    Any chance that you are using Win 95/88/ME? Those OS's have well documented
    memory leaks which will consume all your available memory if an application
    is run long enough. Also there are some issues of memory management within
    LabView in the allocation of memory.
    The solution to the first is to switch to WinNT/2K. The second will be much
    more difficult.
    On Thu, 22 Feb 2001 03:19:12 -0800 (PST), Freek wrote:
    >A data logging program created with Labview 5.1. Slows down after a
    >few weeks and creates files in the Temp. directory.Computer is Siemens
    >Scenic pro 124 MB ram and AT-MIO-16XE50 Data acquisition board. Also
    >using Solartron Dig. probes and Fieldpoint units.
    ===========================================================================
    SolidW
    orks Research Partner National Instruments Alliance Member
    Christopher Dubea Phone: (504) 847-2280
    Vice President of Engineering Fax: (504) 847-2282
    Moving Parts L.L.C. email: [email protected]
    P. O. Box 6117 URL: http://www.movingpart.com
    Slidell, LA 70469-6117

  • 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!

Maybe you are looking for