Enabling NIC teaming on Server slows down RDP connection

You shouldn't run teaming if the adapters are on different subnets; it's used for two adapters in the same subnet

I have psychical host with two NICs running server 2012 R2. Each NIC has it's own separate subnet. Reason why i wanted to enable teaming so i'm able to ping all the IP addresses in both range. After i enabled teaming i was no longer able to RDP in to machine, sometimes it will work but i will be painfully slow and will disconnect shortly after. This machines also hosts 4 VMs and i can RDP in to those VMs without any problem but the psychical host seems to have issues. i also tried to login to that host using logmein but logmein just keeps waiting on screen to load but never does where as VMs on that host work perfectly fine.
When i ping host using another computer on subnet ping response time all seems to be

Similar Messages

  • Is enabling NIC teaming service affecting?

    Hi,
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:"";
    mso-padding-alt:0in 5.4pt 0in 5.4pt;
    mso-para-margin:0in;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"Calibri","sans-serif";
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:"Times New Roman";
    mso-fareast-theme-font:minor-fareast;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:"Times New Roman";
    mso-bidi-theme-font:minor-bidi;}
    I want to enable NIC teaming on a CUCM 7.1 with the "set network failover enable" command.  Is this a service affecting command (e.g. does it require a server reboot or cause phones to unregister)?
    Thanks!
    Mike

    Hi Mike,
    Configuring NIC Teaming via cli does not require a server
    restart and will not cause the phones to re-register
    Cheers!
    Rob

  • Can others on a shared wi-fi slow down my connection or block my connection with software or special hardware?

    Hi, Can others on a shared wi-fi slow down my connection or block my connection with software or special hardware?  My connection has been very spotty and many times cuts off.  The router is in our upstairs living room only 70 feet from my room, but it just seems like recent connections have been horrible.  Also, I noticed the following image when trying to access the apple webpage.  Anyone know what that might be?  It's not the usual apple icon next to the address.
    thanks
    Dave

    Welcome,
    Indeed, by definition other users would "share" the bandwith and hence slow you down - but not cut you off.
    More likely is that there are other devices (e.g. cordless phones) are causing interference. You don't specify which AP you have but if it an 802.11n one you should get better reception as the 5GHz range does get so much interference.
    Try utilities like NetSpot or iStumbler to see what's in range.
    The icon on the web page is probably something else not related to WiFi
    Regards,
    Shawn

  • HT1677 why when i connect safari to internet the other windows computers slow down the connection?

    why when i connect safari to internet the other windows computers slow down the connection?

    Your question has nothing to do with using iPhones in the Enterprise...which is the focus of this forum.  Suggest you post it in the OS X forums

  • Can the wireless card in my mac wear out and slow down internet connection??

    can the wireless card in my mac wear out and slow down internet connection??

    Yes the WiFi card can wear out but not what you would really call wearing out like a pair of pants do. It can start to fail causing the connection between your computer and your Wifi router to slow down, IE transmit and receive less data in a given time period. And then it will fail completely.
    But as to your internet connection being affected by a failing WiFi card no that can't happen.
    If you turn the WiFi off and connect the computer to your router with an Ethernet cable does your internet browsing and downloading speed increase? If it does then there may be something wrong with the WiFi card in your computer or the WiFi section of your router. Hard to say which.
    If after connecting the computer to your router with an Ethernet cable and your speeds do not increase then it is a problem with the router or on your ISPs end.

  • Internet speed slows down when connected via airport express

    Internet speed slows down when connecting via airport express. When connecting directly via the timecapsulethe internet speed is ok, when connecting via the airport express the speed slows down.What can I do to change that? Any suggestions?

    Turn off the AirPort Express completely as a test, and move your computer very close to the location of the Express.
    As I said before, the Express can only extend the bandwidth (speed) that it receives from the Time Capsule, so the speed that you see there with the Express powered off will be the fastest speed of which the Express is capable.
    The Express will make the signal go further when it extends....but it will not make the signal go faster.
    A good location for a device that extends wirelessly is a point that is about half the distance from the Time Capsule and the general area that needs more wireless coverage.
    If you locate the AirPort Express too far from the Time Capsule or there are more than a couple of walls in the signal path, the signal will be very slow by the time that it reaches the Express....and the Express simply extends a signal that has already slowed down significantly.
    If you already have the Express located about half the distance between the Time Capsule and general area that needs more wireless coverage, how many walls, ceilings or other obstructions are there in the signal path between the Time Capsule, the AirPort Express and the area that needs more coverage?
    Often, due to obstructions, it is just not possible to achieve good performance when you try to extend a network wirelessly. The solution is connect the AirPort Express to the Time Capsule using a wired Ethernet connection.
    There is virtually no signal loss with this type of connection, so the Express can be located exactly where it is needed and it will produce a much faster wireless signal in this type of setup.

  • Switch-independent load-balancing NIC teaming on server-side and MAC/ARP flapping on L2/L3 switches

    Since active deployment of Windows Server 2012, our servers support team began to utilize new feature - switch-independent load-balancing NIC teaming. At first look it seems great - no additional network configuration is required and load balancing is performed by server itself by sending frames in round-robin or some hash algorithm out from different NICs (say two for simplicity) but with same MAC address. Theoretical bandwith is now grown up to 2Gbps (if we have two 1G NICs per server) against failover NIC teaming configuration, when one of two adapters is always down.
    But how does this affect (if does) switching and routing performance of network equipment? From point of view of L2 switch - it has to rewrite its CAM table each time a server sends frame from different NIC. Isn't it expensive operation? Won't it affect switching in a bad way? We see in our logs that same server make switches to change mac-to-port associations several times per second.
    Well, and how does it affect routing, if the switch to which server is connected is L3 switch an performs routing for the subnet server connected to? Will CEF operate well if ARP entry chages several times per second?
    Thank you.

    Since nobody answered here, we created service request and got the following answer (in short):
    L2 MAC flapping between ports is very bad and you must avoid such configurations as much as possible. There is one possible variant that can be considered in your situation - use port-channel (either L2 or L3), in this configuration port-channel will be treted as single port and there won't be flapping.
    Conversation example is here: https://ramazancan.wordpress.com/tag/best-practice/

  • 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

  • Blackberry Desktop Software slows down Network Connectivity on Win 7 start up

    Hi,
    I am new so be gently..lol
    I am running windows 7 64bit Home Premium. I recently noticed that on start up my PC was taking between 10 and 20 seconds to set up it's network connectivity, which previously was almost instant. There were no erros within the event logs to suggest why this was occuring. The last thing installed was the blackberry desktop manager. I uninstalled this, and found that my network connectivity was now occuring almost instantly again.
    Is this a know issue with this software? I have searched the forum but cannot find anything simliar, only people saying it was slowing down start up as a whole which is not what is happening to me.
    Thanks for any help or advice in advance.
    TLE

    Hi and Welcome to the Forums!
    Typically, if you have installed the RIM DTM software to auto-start every time you boot your PC, the boot time will increase. Personally, I've found no reason to allow DTM to auto-start...I only launch it when I need it.
    To perform a full clean uninstall, see this KB:
    KB02206 How to perform a clean uninstall of BlackBerry Desktop Software
    Good luck and let us know!
    Occam's Razor nearly always applies when troubleshooting technology issues!
    If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
    Join our BBM Channels
    BSCF General Channel
    PIN: C0001B7B4   Display/Scan Bar Code
    Knowledge Base Updates
    PIN: C0005A9AA   Display/Scan Bar Code

  • High processor load slows down wireless connection

    My wireless connection slows to a crawl when the CPU is being utilized more than 80% (average for both CPU cores).
    For example, if I have Safari and Quicktime open, web pages load very fast and the CPU load is less than 5%. When encoding a video in Quicktime, the processor load is around 85%, but web pages load very slowly in Safari (or any other browser). Ping times also increase considerably (from 25ms under low CPU load to 200-2000ms under heavy CPU load). As soon as the video is done encoding and the CPU load drops back down, web pages load fast again.
    This problems only seems to apply to AirPort connections. High CPU load does not appear to affect speeds when connected via Ethernet.
    Has anyone else experienced this?
    MacBook Pro 15" 2.33GHz/2GB/160GB/256MB   Mac OS X (10.4.9)  

    Has no one else experienced this? I can reproduce this problem consistently. Anything that utilizes the processor at least 40% slows down my wireless internet connection.

  • Connecting to remote server slows down computer

    We've been connecting to a remote server for years, and only recently have this problem:
    When connected to a remote server, the entire system runs sluggish. This only happens with one remote server -- other connections don't cause this problem. The system is slow even if we are not reading or writing -- just the connection seems to cause the slowdown.
    What could be causing this?

    You need to enable WinRM on your system. Open powershell on the system you want to connect to remotely and enable it by typing:
    C:>enable-psremoting -force
    WinRM already is set up to receive requests on this machine.
    WinRM has been updated for remote management.
    Created a WinRM listener on HTTP://* to accept WS-Man requests to any IP on this machine.
    This will configure WinRM for you. Check out this technet powershell training session.
    http://technet.microsoft.com/en-au/events/ee676904.aspx
    ref: http://social.technet.microsoft.com/Forums/en/ITCG/thread/54417b48-68ae-40ac-a303-74aed4e7e81a
    Satyam MCITP, MCPD

  • Problem with InDesign server - Server slows down fast

    My javascript code iterates the pages of the InDesign Document and searches for the text frames with some special character style.
    I found some samples from Jongware :
    sourcelist = app.activeDocument.findText()
    and
    sourcelist = app.activeDocument.pages[p].textFrames[f].findText();
    if I use the first variant the memory goes to ca. 1.2GB (the server has 4GB), the search is completed in ca. 2 minutes but InDesign Server works incredibly slow.
    The problem is I have to find a page for each text found.
    If I use second variant the memory goes high slowly and so each iteration needs more time.
    After 300th page InDesign Server needs up to 30-40 seconds to process the page.
    (First pages are processed 3-4 per second)
    I tried several possible implementations, like
    for each page
         var actualPage = pages[i]
         for each frame
              var actualFrame = frames[i]
              var sourceList = searchText(actualFrame)
                   parseText(sourceList)
    or
    var actualPage=null,  actualFrame = null, sourceList = null;
    for each page
         actualPage = pages[i]
         for each frame
              actualFrame = frames[i]
              sourceList = searchText(actualFrame)
                   parseText(sourceList)
    I've tried functions with local variables. Nothing changes.
    Processing of the first 50 pages is really fast, but the test document has 630 pages.
    And I have no ideas how to make InDesign continue to work fast.
    Have someone had similar problem? Any ideas?

    To clarify my comment on pages:
    JavaScript objects referencing a native InDesign object have an internal representation for their "address" in the DOM, a textual form (similar to an XPath) is available via toSpecifier(). The specifier starts at the document and then follows collections (e.g. pages) and collection accessors (e.g. itemByID()) to finally reach the same object.
    You can see that the specifier of the document before and after the close/open roundtrip changes in CS5 or later (different document ID), where CS4 used a different specifier form (itemByName() for the document) . The renumbered document ID renders previous references to the same page invalid - see the isValid property. If you want to revive such a stale object reference across close/open, you can remember the page ID and use your reopened document's myDoc.pages.itemByID() method to get to the same object.
    Regarding your other performance problem: print the output of the ExtendScript helper function "$.summary()" before and after the code sequence in question, or compute the differences. You may want to precede that with two explicit calls for the garbage collection "$.gc()" - yes, double invokation seems to be more thorough. Sometimes you find memory leaks that way, for example caused by the javascript "closure" design pattern (all those "Workspace" objects).
    Dirk

  • Server slow down with client and server slowdown

    The problem started a couple of weeks ago and it has been hard to nail down. When people are working there are times when the computers will pause for a few seconds(1 to 5) and then continue. It doesn't seem to be any one program or type of computer (G4 or G5). Everybody that is experiencing the problem is logged in via the OS X server with their Home directory on the server. If we create a local user the problem doesn't appear. It seems to point to the OS X server but all indicators show the server is hardly doing anything thing at all. Very low CPU utilization, disk usage, network traffic, throughput, and the system memory never maxs out.
    We switched to a different X Server, same problem.Everything is running 10.3.9 client and the server version is 10.3.9

    The problem started a couple of weeks ago and it has been hard to nail down. When people are working there are times when the computers will pause for a few seconds(1 to 5) and then continue. It doesn't seem to be any one program or type of computer (G4 or G5). Everybody that is experiencing the problem is logged in via the OS X server with their Home directory on the server. If we create a local user the problem doesn't appear. It seems to point to the OS X server but all indicators show the server is hardly doing anything thing at all. Very low CPU utilization, disk usage, network traffic, throughput, and the system memory never maxs out.
    We switched to a different X Server, same problem.Everything is running 10.3.9 client and the server version is 10.3.9

  • Opening an Indesign file from server slows down [very urgent please]

    Hi All,
    I have a book that is already paginated. (Every indesign file has hyperlinks targeted to the another indesign file (paragraph Anchor destinations)).
    After few days the server was crashed due to some network problems.
    Now a new server has been created with different name and path.
    If I try to open the indesign file it takes much much longer time than usual, For the same file if I disconnect the network connection it is working as usual.
    What is the cause of this? Is there any way to overcome this issue or any work around? At the same time I need to retain the hyperlinks also. Because it is very very difficult to re-create the links (more than 100 or 200 number of links will be there in every chapter).
    Note: I have tried something like trashing indesign preferences. It is also not working.
    Thanks,
    Green4ever

    I restored all my indesign file in the same folder structure except the root folder. I already tried the way you suggested. It is not helping me.
    "I thought that may be Indesign is searching for the missing links" So I try editing the preferences so that indesign will not search for the missing links(I think it is only aplicable for graphic links is it?). After that also I am facing the same problem.
    Is there anyway to open the indesign file without checking for missing hyperlinks. So that it may open faster.    
    Thanks,
    Green4ever

  • App Server Slow Down

    Hi All,
    I had posted my query earlier, no one seem 2 hv replied. hopefully someone will this time.
    Oracle 9iAS admin console takes a long time to load, around 15 mins, and also as much for other tasks as deploying applications etc. Development is just not happening becuz of it. I'm using P4 1Gz, 512 + 256 MB DDR. Any solutions to make it faster.
    Thanks in advance,
    Albert Mendonca.

    Oracle doesn't manage the Apache logs. If a log file fills to the OS limit, the App Server crawls. Look for log files that are 2GB in size.
    Don't know if that helps, but till I can convince our sysadmin to run a cron job, it's a monthly problem for us.

Maybe you are looking for

  • I,m using macbook pro retina, I have changed the language to Arabic but still I find that password and downloading are coming in arabia

    I,m using macbook pro retina, I have changed the language from arabic to Endlish through system preference, but still I find that password and downloading are coming in arabia, when I start my computer it show password request in Arabic.

  • Update payment info in account

    How do I add a new credit card to my account/ID/Whatever . I know it's got to be somewhere in my "manage accounts". Sorry I'm PC only by protest and am half ******** here with this simplest things. Audrey.krostich

  • Looking for a manual for gpib232ct converter

    I am trying to test a gpib232ct converter but I don't have a manual. At least I want to know which one of the 2 switches in the board control the baud rate and if I need a null modem adapter for this converter. Thanks, David

  • Form getting hit by spam

    Hello the form on this page : http://accounting.smartpros.com/standard/forms/adpcpe3.asp?category=adp is getting hit by porn spam and we need it to stop. So I was hoping to jsut change the form name at least.. may be that would help? Any ideas? Thank

  • Monitoring a Clustered Resource

    Can you let me know if it's possible to monitor a service like SMTP on the clustered resource. I'd like idealy to know if SMTP had failed, even if the server is still up and running, but this resource could be on one of two servers, even though it's