Child process admin thread is shutting down.

Hi,
Operating on a web server with the following error message, Child Process is a phenomenon that restart.
I would like to know what the cause.
Version - Sun Java System Web Server 6.1
errors
[09/Nov/2011:12:31:00] catastrophe ( 7647): Server crash detected (signal SIGBUS)
[09/Nov/2011:12:31:00] info ( 7647): Crash occurred in NSAPI SAF flex-log
[09/Nov/2011:12:31:00] info ( 7647): Crash occurred in function flex_init from module /netscape/servers/bin/https/lib/libns-httpd40.so
[09/Nov/2011:12:31:00] failure (16223): Child process admin thread is shutting down
[09/Nov/2011:13:42:06] catastrophe (16514): Server crash detected (signal SIGSEGV)
[09/Nov/2011:13:42:06] info (16514): Crash occurred in NSAPI SAF flex-log
[09/Nov/2011:13:42:06] info (16514): Crash occurred in function flex_init from module /netscape/servers/bin/https/lib/libns-httpd40.so
[09/Nov/2011:13:42:06] failure (16223): Child process admin thread is shutting down
Edited by: 896618 on 2011. 11. 10 오후 9:21

thanks for the response chris. in answer to your questions - no there are no NSAPI plugins installed and we are getting zero helpful output from the log files.
/server-root/logs/errors is the only log file that has relevant output at the time of the crashes. our own application logs and the sytem's syslogs have nothing relevant at those times.
the o/p from the errors log is basically :
[19/Dec/2002:02:05:39] config ( 5815): [GC
[19/Dec/2002:02:05:39] config ( 5815): 154915K->129640K(249216K)
[19/Dec/2002:02:05:39] config ( 5815): , 0.0299277 secs]
[19/Dec/2002:02:05:39] config ( 5815):
[19/Dec/2002:02:05:59] failure ( 5814): Child process admin thread is shutting down
at which point it resets itself. we have a load balanced system and the resets aren't noticed at the front end but i'm beginning to tear my hair out.
We have the exact same s/w configuration on 2 x Netra T1s and they've been running fine for over a year. We have 2 brand spanking new Fire V100s & the only significant h/w difference between the machines being L2 cache (512k v 2Mb). i would've thought that a bottleneck would throw up errors all over the place and result in a noticeably slower system which isn't the case.
our next step is to throw in an extra 512Mb RAM and see does that increase the time between resets - currently 24-36hrs. i have a niggling suspicion it may be memory related.
any other ideas?

Similar Messages

  • Thread problems - shutting down.

    Okay, I've got my multi-threaded server program working just fine and all is well...until I shut down the server.
    By some quirky twist of fate, java chat servers seem to be a popular education assignment in the last two weeks, which will probably put some people off answering this simply because of all the clueless posts on the subject recently. :)
    Anyway, a little background on how I'm doing things first.
    At the top there is the Server object, which is implementing Runnable. This instances the ClientManager, creates the ServerSocket and then kicks off its own thread and loops in the run() method waiting for connections while a boolean is true. If it gets a connection it calls the ClientManager addConnection() method and passes it the received client socket.
    The ClientManager holds a List of ClientConnections and provides methods to add and remove ClientConnections. The ClientManager also runs in its own thread by implementing the Runnable interface and uses its run() method to loop through checking for incoming messages from each client.
    A ClientConnection object also runs in its own thread via the Runnable interface. This checks for incoming messages from the client and stores the String ready to be received by the ClientManager and broadcast to all ClientConnections.
    So, you've got the Server running in its own thread, the ClientManager running in its own thread and the ClientManager maintaining a List of ClientConnections, each running in its own thread.
    I'm starting my threads like this:-
    // Constructor.
    Public SomeObject() {
        start();
    // Runnable method.
    Public void start() {
        // threadObject is private class variable.
        bThreadActive = true;
        this.threadObject = new Thread(this);
        threadObject.setDaemon(true);
        threadObject.start();
    }I'm running my threadded object like this: -
    Public void run() {
        do {
            // Do work here.
        } while(bThreadActive);
        // Activates the shutdown method for this object.
        shutdownObject();
    }I'm shutting down my threads like this: -
    Public void shutdown() {
        this.bThreadActive = false;
    // The main shutdown code.
    Public void shutdownObject() {
        // Kill thread object.
        this.threadObject = null;
        // Do other stuff.
    }Which I think should work fine. Anything wrong with the above?
    I'm getting problems with NullPointerExceptions with the Server object at the point where it tries to shutdown the ClientManager. This works by shutting down all ClientConnections in the List first and then emptying the List before killing its own thread. Also, the Server object seems to shutdown before the ClientManager. And other such weirdness.
    I know you're all going to ask for specific code and a stacktrace, which I'll provide....I just want to check that my method for using threads as above is correct first, so I can rule that out - mostly because I suspect I'm missing some vital piece of knowledge on using threads....things are not working as I expect.
    Anyway, a quick answer on the above and then I'll start posting more specific info.
    Thanks all :)

    Ooops....my mistake. I was calling shutdown() twice. Once from the GUI code and automatically from after the loop in the run() method. Funny how the stacktrace doesn't drill down any further than the method that makes this call.
    Okay, its almost all working perfectly, except for this part....
        //  Start accepting client connections from the server service.
        public void run() {
             while(bThreadActive) {
                 if (sockServer != null) {
                     if (!sockServer.isClosed()) {
                         try {
                             sockClient = sockServer.accept();
                             if (sockClient != null) {
                                 this.clientManager.addClientConnection(sockClient);
                                 this.pOutput.printOutput("Connection accepted from: " + sockClient.getInetAddress().getHostAddress());
                         } catch (IOException ioe) {
                             if (bThreadActive) {
                                 this.pOutput.printOutput("ERROR: Could not accept incoming client connection");
                         } catch (NullPointerException npe) {
                             // Leave this for now.
             shutdown();
        // Shutdown the server service and disconnect all client connections.
        public void shutdown() {
            try {
                clientManager.stopThread();
                sockServer.close();
                threadServer = null;
            } catch (NullPointerException npe) {
                npe.printStackTrace();
            } catch (IOException ioe) {
                pOutput.printOutput("ERROR: Could not cleanly shutdown the server socket");
            pOutput.printOutput("Server service shut down successfully");
        // Stop the server thread (automatically shuts down).
        public synchronized void stopThread() {
            bThreadActive = false;
        }When I call the above like this from the GUI object...
        // Stop the server.
        private void stopServer() {
             try {
                  server.stopThread();
                  setGUIMode(MODE_DISCONNECTED);
             } catch (NullPointerException npe) {
                  npe.printStackTrace();
        }...the string "Server service shut down successfully" from the completion of the shutdown() method never appears, so it looks as though its not executing.
    But if I do this instead in the stopServer() method and remove the shutdown() call in the run() method, it works......but I get two (sometimes three) outputs of "Server service shut down successfully" which makes me think its being run twice somehow.....once before the ClientManager has been shutdown and once after or twice after.
    Server service shut down successfully
    Shutting down Client Manager...
    All client connections disconnected
    Client Manager successfully shutdown
    Server service shut down successfully
    Server service shut down successfully
    Any ideas?

  • IPlanet 6.1-SP6 auto re-starting with Child admin thread shutting down

    We are running the same application everywhere without any issues. Just migrated to new machine/environment and whenever the client (browser) tries to acess a JSP, the web-server automatically re-starts itself with message Child admin thread is shutting down.
    We are using Solaris OS 9, with Sun Cluster 3.1, JDK both 1.3.1_04 and 1.4.2_06.
    Any help will be highly appreciated.

    Issue is resolved, there was an issue with classpath settings in jvm12.conf

  • Weblogic Server Shutting down execute threads

    Weblogic 5.1 SP9 on Solaris.
    After upgrading to SP9 from SP8 we are observing a new message in our log during
    the START UP PROCESS. It seems that after performing a GC and during the creation
    of the connection pools we are receiving a message "Shutting down execute threads".
    Though Weblogic starts up ok after this and performs ok we are still concerned
    on what execute threads are shutting down?
    Any help in an explanation would be appreciated.
    <I> <GC> GC: After free/total=505281560/531955712 (94%)
    GC: After free/total=505281560/531955712 (94%)Wed Aug 08 18:08:33 EDT 2001:<I> <WebLogicServer> Shutting down execute threads
    Wed Aug 08 18:08:33 EDT 2001:<I> <WebLogicServer> Shutdown completed
    Wed Aug 08 18:08:33 EDT 2001:<I> <WebLogicServer> Shutdown completed

    could you post complete the log file
    right from the server startup to until WLS
    listens on http & SSL ports?
    Kumar
    Andy wrote:
    Weblogic 5.1 SP9 on Solaris.
    After upgrading to SP9 from SP8 we are observing a new message in our log during
    the START UP PROCESS. It seems that after performing a GC and during the creation
    of the connection pools we are receiving a message "Shutting down execute threads".
    Though Weblogic starts up ok after this and performs ok we are still concerned
    on what execute threads are shutting down?
    Any help in an explanation would be appreciated.
    <I> <GC> GC: After free/total=505281560/531955712 (94%)
    GC: After free/total=505281560/531955712 (94%)Wed Aug 08 18:08:33 EDT 2001:<I> <WebLogicServer> Shutting down execute threads
    Wed Aug 08 18:08:33 EDT 2001:<I> <WebLogicServer> Shutdown completed
    Wed Aug 08 18:08:33 EDT 2001:<I> <WebLogicServer> Shutdown completed

  • Unable to start weblogic - force shutting down

    Weblogic admin server force shutting down, with the below dump... it is on windows 7...
    ===== FULL THREAD DUMP ===============
    Thu Mar 21 12:41:47 2013
    BEA JRockit(R) R27.6.5-32_o-121899-1.6.0_14-20091001-2107-windows-ia32
    "Main Thread" id=1 idx=0x4 tid=4728 prio=5 alive, in native, blocked
    -- Blocked trying to get lock: java/lang/Class@0x15AB9AE0[thin lock]
    at jrockit/vm/Threads.sleep(I)V(Native Method)
    at jrockit/vm/Locks.waitForThinRelease(Locks.java:1209)
    at jrockit/vm/Locks.monitorEnterSecondStageHard(Locks.java:1342)
    at jrockit/vm/Locks.monitorEnterSecondStage(Locks.java:1259)
    at jrockit/vm/Locks.monitorEnter(Locks.java:2466)
    at java/lang/Shutdown.exit(Shutdown.java:164)
    at java/lang/Runtime.exit(Runtime.java:90)
    at java/lang/System.exit(System.java:904)
    at weblogic/Server.main(Server.java:87)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "(Signal Handler)" id=2 idx=0x8 tid=2200 prio=5 alive, in native, daemon
    "(GC Main Thread)" id=3 idx=0xc tid=4500 prio=5 alive, in native, native_waiting, daemon
    "(GC Worker Thread 1)" id=? idx=0x10 tid=400 prio=5 alive, in native, daemon
    "(GC Worker Thread 2)" id=? idx=0x14 tid=5004 prio=5 alive, in native, daemon
    "(Code Generation Thread 1)" id=4 idx=0x18 tid=5568 prio=5 alive, in native, native_waiting, daemon
    "(Code Optimization Thread 1)" id=5 idx=0x1c tid=4048 prio=5 alive, in native, native_waiting, daemon
    "(VM Periodic Task)" id=6 idx=0x20 tid=4224 prio=10 alive, in native, daemon
    "(Attach Listener)" id=7 idx=0x24 tid=1628 prio=5 alive, in native, daemon
    "Finalizer" id=8 idx=0x28 tid=4416 prio=8 alive, in native, native_waiting, daemon
    at jrockit/memory/Finalizer.waitForFinalizees([Ljava/lang/Object;)I(Native Method)
        at jrockit/memory/Finalizer.access$500(Finalizer.java:12)
        at jrockit/memory/Finalizer$4.run(Finalizer.java:159)
        at java/lang/Thread.run(Thread.java:619)
        at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
        -- end of trace
    "Reference Handler" id=9 idx=0x2c tid=5864 prio=10 alive, in native, native_waiting, daemon
        at java/lang/ref/Reference.waitForActivatedQueue()Ljava/lang/ref/Reference;(Native Method)
        at java/lang/ref/Reference.access$100(Reference.java:11)
        at java/lang/ref/Reference$ReferenceHandler.run(Reference.java:79)
        at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
        -- end of trace
    "(Sensor Event Thread)" id=10 idx=0x30 tid=3640 prio=5 alive, in native, daemon
    "JDWP Transport Listener: dt_socket" id=11 idx=0x34 tid=4120 prio=10 alive, in native, daemon
    "JDWP Event Helper Thread" id=12 idx=0x38 tid=3428 prio=10 alive, in native, native_waiting, daemon
    "Timer-0" id=15 idx=0x3c tid=3808 prio=5 alive, in native, waiting, daemon
        -- Waiting for notification on: java/util/TaskQueue@0x120011C0[fat lock]
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
    at java/lang/Object.wait(J)V(Native Method)
    at java/lang/Object.wait(Object.java:485)
    at java/util/TimerThread.mainLoop(Timer.java:483)
    ^-- Lock released while waiting: java/util/TaskQueue@0x120011C0[fat lock]
    at java/util/TimerThread.run(Timer.java:462)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "Timer-1" id=16 idx=0x40 tid=4724 prio=5 alive, in native, waiting, daemon
    -- Waiting for notification on: java/util/TaskQueue@0x12001578[fat lock]
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
    at java/lang/Object.wait(J)V(Native Method)
    at java/util/TimerThread.mainLoop(Timer.java:509)
    ^-- Lock released while waiting: java/util/TaskQueue@0x12001578[fat lock]
    at java/util/TimerThread.run(Timer.java:462)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" id=17 idx=0x44 tid=5008 prio=5 alive, in native, waiting, daemon
    -- Waiting for notification on: weblogic/t3/srvr/T3Srvr$2@0x15AC6550[fat lock]
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
    at java/lang/Object.wait(J)V(Native Method)
    at java/lang/Thread.join(Thread.java:1143)
    ^-- Lock released while waiting: weblogic/t3/srvr/T3Srvr$2@0x15AC6550[fat lock]
    at java/lang/Thread.join(Thread.java:1196)
    at java/lang/ApplicationShutdownHooks.runHooks(ApplicationShutdownHooks.java:79)
    at java/lang/ApplicationShutdownHooks$1.run(ApplicationShutdownHooks.java:24)
    at java/lang/Shutdown.runHooks(Shutdown.java:79)
    at java/lang/Shutdown.sequence(Shutdown.java:123)
    at java/lang/Shutdown.exit(Shutdown.java:168)
    ^-- Holding lock: java/lang/Class@0x15AB9AE0[thin lock]
    at java/lang/Runtime.exit(Runtime.java:90)
    at java/lang/System.exit(System.java:904)
    at com/fedex/k2/webapp/servlet/IK2StartupServletContextListener.contextInitialized(IK2StartupServletContextListener.java:61)
    at weblogic/servlet/internal/EventsManager$FireContextListenerAction.run(EventsManager.java:481)
    at weblogic/security/acl/internal/AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic/security/service/SecurityManager.runAs(SecurityManager.java:121)
    at weblogic/servlet/internal/EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
    at weblogic/servlet/internal/WebAppServletContext.preloadResources(WebAppServletContext.java:1801)
    ^-- Holding lock: weblogic/servlet/internal/WebAppServletContext@0x1449CBA8[thin lock]
    at weblogic/servlet/internal/WebAppServletContext.start(WebAppServletContext.java:3045)
    at weblogic/servlet/internal/WebAppModule.startContexts(WebAppModule.java:1397)
    at weblogic/servlet/internal/WebAppModule.start(WebAppModule.java:460)
    at weblogic/application/internal/flow/ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic/application/utils/StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic/application/internal/flow/ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic/application/internal/flow/ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic/application/internal/flow/ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic/application/internal/flow/ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic/application/utils/StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic/application/internal/flow/ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic/application/internal/flow/StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic/application/internal/BaseDeployment$2.next(BaseDeployment.java:1267)
    at weblogic/application/utils/StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic/application/internal/BaseDeployment.activate(BaseDeployment.java:409)
    at weblogic/application/internal/SingleModuleDeployment.activate(SingleModuleDeployment.java:39)
    at weblogic/application/internal/DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic/deploy/internal/targetserver/AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic/deploy/internal/targetserver/BasicDeployment.activate(BasicDeployment.java:184)
    at weblogic/deploy/internal/targetserver/BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
    at weblogic/management/deploy/internal/DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
    at weblogic/management/deploy/internal/DeploymentAdapter.activate(DeploymentAdapter.java:196)
    at weblogic/management/deploy/internal/AppTransition$2.transitionApp(AppTransition.java:30)
    at weblogic/management/deploy/internal/ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
    at weblogic/management/deploy/internal/ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
    at weblogic/management/deploy/internal/ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
    at weblogic/management/deploy/internal/DeploymentServerService.resume(DeploymentServerService.java:173)
    at weblogic/management/deploy/internal/DeploymentServerService.start(DeploymentServerService.java:89)
    at weblogic/t3/srvr/SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic/work/ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic/work/ExecuteThread.run(ExecuteThread.java:173)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "weblogic.time.TimeEventGenerator" id=18 idx=0x48 tid=1180 prio=9 alive, in native, waiting, daemon
    -- Waiting for notification on: weblogic/time/common/internal/TimeTable@0x12001E70[fat lock]
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
    at java/lang/Object.wait(J)V(Native Method)
    at weblogic/time/common/internal/TimeTable.snooze(TimeTable.java:286)
    ^-- Lock released while waiting: weblogic/time/common/internal/TimeTable@0x12001E70[fat lock]
    at weblogic/time/common/internal/TimeEventGenerator.run(TimeEventGenerator.java:117)
    at java/lang/Thread.run(Thread.java:619)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "JMAPI event thread" id=19 idx=0x4c tid=4752 prio=5 alive, in native, native_waiting, daemon
    "weblogic.timers.TimerThread" id=20 idx=0x50 tid=3764 prio=9 alive, in native, waiting, daemon
    -- Waiting for notification on: weblogic/timers/internal/TimerThread@0x144839C0[fat lock]
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
    at java/lang/Object.wait(J)V(Native Method)
    at weblogic/timers/internal/TimerThread$Thread.run(TimerThread.java:267)
    ^-- Lock released while waiting: weblogic/timers/internal/TimerThread@0x144839C0[fat lock]
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" id=21 idx=0x54 tid=1840 prio=5 alive, in native, waiting, daemon
    -- Waiting for notification on: weblogic/work/ExecuteThread@0x1447C848[fat lock]
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
    at java/lang/Object.wait(J)V(Native Method)
    at java/lang/Object.wait(Object.java:485)
    at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:157)
    ^-- Lock released while waiting: weblogic/work/ExecuteThread@0x1447C848[fat lock]
    at weblogic/work/ExecuteThread.run(ExecuteThread.java:178)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "Thread-7" id=24 idx=0x58 tid=5156 prio=5 alive, in native, parked, daemon
    -- Parking to wait for: java/util/concurrent/locks/AbstractQueuedSynchronizer$ConditionObject@0x12F80AC0
    at jrockit/vm/Locks.park0(J)V(Native Method)
    at jrockit/vm/Locks.park(Locks.java:2517)
    at sun/misc/Unsafe.park(ZJ)V(Native Method)
    at java/util/concurrent/locks/LockSupport.park(LockSupport.java:158)
    at java/util/concurrent/locks/AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1925)
    at java/util/concurrent/LinkedBlockingQueue.take(LinkedBlockingQueue.java:358)
    at weblogic/utils/concurrent/JDK15ConcurrentBlockingQueue.take(JDK15ConcurrentBlockingQueue.java:89)
    at weblogic/store/internal/PersistentStoreImpl.getOutstandingWork(PersistentStoreImpl.java:567)
    at weblogic/store/internal/PersistentStoreImpl.run(PersistentStoreImpl.java:615)
    at weblogic/store/internal/PersistentStoreImpl$2.run(PersistentStoreImpl.java:383)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'" id=25 idx=0x5c tid=1880 prio=5 alive, in native, daemon
    at weblogic/socket/NTSocketMuxer.getIoCompletionResult(Lweblogic/socket/NTSocketMuxer$IoCompletionData;)Z(Native Method)
    at weblogic/socket/NTSocketMuxer.processSockets(NTSocketMuxer.java:81)
    at weblogic/socket/SocketReaderRequest.run(SocketReaderRequest.java:29)
    at weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:42)
    at weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:145)
    at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:117)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "ExecuteThread: '1' for queue: 'weblogic.socket.Muxer'" id=26 idx=0x60 tid=4688 prio=5 alive, in native, daemon
    at weblogic/socket/NTSocketMuxer.getIoCompletionResult(Lweblogic/socket/NTSocketMuxer$IoCompletionData;)Z(Native Method)
    at weblogic/socket/NTSocketMuxer.processSockets(NTSocketMuxer.java:81)
    at weblogic/socket/SocketReaderRequest.run(SocketReaderRequest.java:29)
    at weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:42)
    at weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:145)
    at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:117)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'" id=27 idx=0x64 tid=5300 prio=5 alive, in native, daemon
    at weblogic/socket/NTSocketMuxer.getIoCompletionResult(Lweblogic/socket/NTSocketMuxer$IoCompletionData;)Z(Native Method)
    at weblogic/socket/NTSocketMuxer.processSockets(NTSocketMuxer.java:81)
    at weblogic/socket/SocketReaderRequest.run(SocketReaderRequest.java:29)
    at weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:42)
    at weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:145)
    at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:117)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "VDE Transaction Processor Thread" id=30 idx=0x68 tid=4260 prio=2 alive, in native, waiting, daemon
    -- Waiting for notification on: com/octetstring/vde/backend/standard/TransactionProcessor@0x12F80720[fat lock]
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
    at java/lang/Object.wait(J)V(Native Method)
    at java/lang/Object.wait(Object.java:485)
    at com/octetstring/vde/backend/standard/TransactionProcessor.waitChange(TransactionProcessor.java:367)
    ^-- Lock released while waiting: com/octetstring/vde/backend/standard/TransactionProcessor@0x12F80720[fat lock]
    at com/octetstring/vde/backend/standard/TransactionProcessor.run(TransactionProcessor.java:212)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "DoSManager" id=32 idx=0x70 tid=3492 prio=6 alive, in native, sleeping, native_waiting, daemon
    at java/lang/Thread.sleep(J)V(Native Method)
    at com/octetstring/vde/DoSManager.run(DoSManager.java:433)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "Thread-11" id=33 idx=0x74 tid=5936 prio=5 alive, in native, parked, daemon
    -- Parking to wait for: java/util/concurrent/locks/AbstractQueuedSynchronizer$ConditionObject@0x12F80FA0
    at jrockit/vm/Locks.park0(J)V(Native Method)
    at jrockit/vm/Locks.park(Locks.java:2517)
    at sun/misc/Unsafe.park(ZJ)V(Native Method)
    at java/util/concurrent/locks/LockSupport.park(LockSupport.java:158)
    at java/util/concurrent/locks/AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1925)
    at java/util/concurrent/LinkedBlockingQueue.take(LinkedBlockingQueue.java:358)
    at weblogic/utils/concurrent/JDK15ConcurrentBlockingQueue.take(JDK15ConcurrentBlockingQueue.java:89)
    at weblogic/store/internal/PersistentStoreImpl.getOutstandingWork(PersistentStoreImpl.java:567)
    at weblogic/store/internal/PersistentStoreImpl.run(PersistentStoreImpl.java:615)
    at weblogic/store/internal/PersistentStoreImpl$2.run(PersistentStoreImpl.java:383)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'" id=34 idx=0x78 tid=3976 prio=5 alive, in native, waiting, daemon
    -- Waiting for notification on: weblogic/work/ExecuteThread@0x1447C920[fat lock]
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
    at java/lang/Object.wait(J)V(Native Method)
    at java/lang/Object.wait(Object.java:485)
    at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:157)
    ^-- Lock released while waiting: weblogic/work/ExecuteThread@0x1447C920[fat lock]
    at weblogic/work/ExecuteThread.run(ExecuteThread.java:178)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "Timer-2" id=35 idx=0x7c tid=4992 prio=5 alive, in native, waiting, daemon
    -- Waiting for notification on: java/util/TaskQueue@0x12F81018[fat lock]
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
    at java/lang/Object.wait(J)V(Native Method)
    at java/util/TimerThread.mainLoop(Timer.java:509)
    ^-- Lock released while waiting: java/util/TaskQueue@0x12F81018[fat lock]
    at java/util/TimerThread.run(Timer.java:462)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=36 idx=0x80 tid=4668 prio=5 alive, in native, waiting, daemon
    -- Waiting for notification on: weblogic/work/ExecuteThread@0x1447C9F8[fat lock]
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
    at java/lang/Object.wait(J)V(Native Method)
    at java/lang/Object.wait(Object.java:485)
    at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:157)
    ^-- Lock released while waiting: weblogic/work/ExecuteThread@0x1447C9F8[fat lock]
    at weblogic/work/ExecuteThread.run(ExecuteThread.java:178)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "Session Monitor" id=37 idx=0x84 tid=4308 prio=5 alive, in native, sleeping, native_waiting, daemon
    at java/lang/Thread.sleep(J)V(Native Method)
    at com/icesoft/faces/webapp/http/servlet/SessionDispatcher$Listener$1.run(SessionDispatcher.java:315)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "Thread-1" id=14 idx=0xb0 tid=1404 prio=5 alive, in native, blocked
    -- Blocked trying to get lock: weblogic/servlet/internal/WebAppServletContext@0x1449CBA8[thin lock]
    at jrockit/vm/Threads.sleep(I)V(Native Method)
    at jrockit/vm/Locks.waitForThinRelease(Locks.java:1209)
    at jrockit/vm/Locks.monitorEnterSecondStageHard(Locks.java:1342)
    at jrockit/vm/Locks.monitorEnterSecondStage(Locks.java:1259)
    at jrockit/vm/Locks.monitorEnter(Locks.java:2466)
    at weblogic/servlet/internal/WebAppServletContext.destroy(WebAppServletContext.java:3094)
    at weblogic/servlet/internal/ServletContextManager.destroyContext(ServletContextManager.java:240)
    at weblogic/servlet/internal/HttpServer.unloadWebApp(HttpServer.java:457)
    ^-- Holding lock: weblogic/servlet/internal/HttpServer@0x14508638[thin lock]
    at weblogic/servlet/internal/WebAppModule.destroyContexts(WebAppModule.java:1424)
    at weblogic/servlet/internal/WebAppModule.unprepare(WebAppModule.java:501)
    at weblogic/application/internal/flow/ModuleStateDriver$1.previous(ModuleStateDriver.java:339)
    at weblogic/application/utils/StateMachineDriver.previousState(StateMachineDriver.java:329)
    at weblogic/application/utils/StateMachineDriver.previousState(StateMachineDriver.java:309)
    at weblogic/application/internal/flow/ModuleStateDriver.unprepare(ModuleStateDriver.java:167)
    at weblogic/application/internal/flow/ScopedModuleDriver.unprepare(ScopedModuleDriver.java:212)
    at weblogic/application/internal/flow/ModuleListenerInvoker.unprepare(ModuleListenerInvoker.java:285)
    at weblogic/application/internal/flow/DeploymentCallbackFlow$1.previous(DeploymentCallbackFlow.java:397)
    at weblogic/application/utils/StateMachineDriver.previousState(StateMachineDriver.java:329)
    at weblogic/application/utils/StateMachineDriver.previousState(StateMachineDriver.java:309)
    at weblogic/application/internal/flow/DeploymentCallbackFlow.unprepare(DeploymentCallbackFlow.java:111)
    at weblogic/application/internal/flow/DeploymentCallbackFlow.unprepare(DeploymentCallbackFlow.java:102)
    at weblogic/application/internal/BaseDeployment$1.previous(BaseDeployment.java:1233)
    at weblogic/application/utils/StateMachineDriver.previousState(StateMachineDriver.java:329)
    at weblogic/application/utils/StateMachineDriver.previousState(StateMachineDriver.java:309)
    at weblogic/application/internal/BaseDeployment.unprepare(BaseDeployment.java:495)
    at weblogic/application/internal/SingleModuleDeployment.unprepare(SingleModuleDeployment.java:39)
    at weblogic/application/internal/DeploymentStateChecker.unprepare(DeploymentStateChecker.java:205)
    at weblogic/deploy/internal/targetserver/AppContainerInvoker.unprepare(AppContainerInvoker.java:117)
    at weblogic/deploy/internal/targetserver/BasicDeployment.unprepare(BasicDeployment.java:287)
    at weblogic/management/deploy/internal/DeploymentAdapter$1.doUnprepare(DeploymentAdapter.java:81)
    at weblogic/management/deploy/internal/DeploymentAdapter.unprepare(DeploymentAdapter.java:220)
    at weblogic/management/deploy/internal/AppTransition$7.transitionApp(AppTransition.java:75)
    at weblogic/management/deploy/internal/ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
    at weblogic/management/deploy/internal/ConfiguredDeployments.unprepare(ConfiguredDeployments.java:204)
    at weblogic/management/deploy/internal/ConfiguredDeployments.undeploy(ConfiguredDeployments.java:192)
    at weblogic/management/deploy/internal/DeploymentServerService.shutdownApps(DeploymentServerService.java:188)
    at weblogic/management/deploy/internal/DeploymentServerService.shutdownHelper(DeploymentServerService.java:120)
    at weblogic/application/ApplicationShutdownService.halt(ApplicationShutdownService.java:142)
    at weblogic/t3/srvr/ServerServicesManager.haltInternal(ServerServicesManager.java:504)
    at weblogic/t3/srvr/ServerServicesManager.halt(ServerServicesManager.java:336)
    at weblogic/t3/srvr/T3Srvr.shutdown(T3Srvr.java:986)
    at weblogic/t3/srvr/T3Srvr.forceShutdown(T3Srvr.java:892)
    at weblogic/t3/srvr/T3Srvr$2.run(T3Srvr.java:905)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "Thread-14" id=49 idx=0xc4 tid=5752 prio=5 alive, in native, daemon
    at bea/jmapi/DiagnosticCommandImpl.execute(Ljava/lang/String;Ljava/io/FileDescriptor;)V(Native Method)
    at bea/jmapi/DiagnosticCommandImpl.execute(DiagnosticCommandImpl.java:50)
    at com/bea/jvm/DiagnosticCommand.execute(DiagnosticCommand.java:242)
    at com/bea/jvm/DiagnosticCommand$Command.execute(DiagnosticCommand.java:394)
    at bea/jmapi/ThreadSystemImpl.getThreadStackDump(ThreadSystemImpl.java:98)
    at weblogic/platform/JRockitVM.threadDump(JRockitVM.java:61)
    at weblogic/t3/srvr/T3Srvr.logThreadDump(T3Srvr.java:280)
    at weblogic/t3/srvr/ServerLifeCycleTimerThread.run(ServerLifeCycleTimerThread.java:77)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'" id=50 idx=0xc8 tid=5500 prio=5 alive, in native, waiting, daemon
    -- Waiting for notification on: weblogic/work/ExecuteThread@0x01C1A998[fat lock]
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
    at java/lang/Object.wait(J)V(Native Method)
    at java/lang/Object.wait(Object.java:485)
    at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:157)
    ^-- Lock released while waiting: weblogic/work/ExecuteThread@0x01C1A998[fat lock]
    at weblogic/work/ExecuteThread.run(ExecuteThread.java:178)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    Blocked lock chains
    ===================
    Chain 2:
    "Thread-1" id=14 idx=0xb0 tid=1404 waiting for weblogic/servlet/internal/WebAppServletContext@0x1449CBA8 held by:
    "[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" id=17 idx=0x44 tid=5008 in chain 1
    Open lock chains
    ================
    Chain 1:
    "Main Thread" id=1 idx=0x4 tid=4728 waiting for java/lang/Class@0x15AB9AE0 held by:
    "[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" id=17 idx=0x44 tid=5008 (waiting on notification)
    ===== END OF THREAD DUMP ===============

    Hi,
    This is a one off issue which occurred when there are thread dumps originating from WLS trying to determine if there are stuck threads in the system.
    The upgrade to R28 is pertinent because these code level changes will not be feasible to be backported and that the code level fixes are included in R28.1.1.
    Please upgrade the Jrockit version to R28.1.1.
    Mark If this helps you.
    Regards,
    Kishore

  • IMac 27" Not Shutting Down

    Hi,
    recently my iMac has begun not shutting down properly. For the past week or so, I have had numerous attempts at shutting down my iMac. When I begin the shutdown process, i.e. clicking 'shut down', the iMac gets to a white screen with a rotating symbol, like the start up screen but without the Apple Logo, and goes no further. I leave it for an hour, even more and it still does not shut down. What is the problem?
    Thanks

    I notice you're on 10.6.7. You might try upgrading to 10.6.8 and see if that helps. I'd recommend updating using the Combo updater instead of using Software Update.
    You might also try starting your computer while holding Command and V. Then use it for a while, and try to shut down. Additional lines of text should be displayed, and the last few lines may give us some clues as to what's holding things up.

  • Printer will not shut down

    Tried to shut down my Photosmart C7280 printer to clear a paper jamb. Printer prepared itself for shut down, but never completed the process. Screen says "shutting down"  Has been that way for 5 hours. Pressing on/off button does nothing. It no longer communicates with the computer. Manual says that unplugging printer without shutting it down first can damage the printed. The Help pages make no mention of this type of problem. Where do I go from here to get the printer to shut down or to stop trying to shut down?

    having the same problem, did you ever get a resolution?

  • QT32 Server needs to be shut down prior to updating

    Does anyone in the world know how to fix the annoying qt32 server fiasco on my mac Snow Leopard current release? I need to supposibly shut down the qt32 server mac before I finish the updates for CS5 production Premiere which is not possible. I know 2 other editors that have the same issue and they gave up and went back to Final Cut.

    I cannot address how things are done on the Mac-side of the street, but there are often programs and processes, that must be shut down for some program updates, as they will need to be rewritten too, and this cannot happen, if they are running, or resident.
    On a PC, if one encounters such an issue, the offending program is usually being called at bootup, and one would use a utility, like the built-in MSCONFIG, to just not load that program, or process, until the update is done.
    I can only guess that similar exists for the Mac, but could be horribly wrong.
    Maybe Todd, Jeremy, or another valued Adobe employee, who also knows Mac's, can weigh in and help.
    Good luck,
    Hunt

  • Laptop suddenly shuts down with battery at +60%

    Hey guys,
    So i had my laptop for a 6 month now, it is an MSI GT683DX Windows 8.1/Updated from  Win 7 HP,  but recently i did a battery calibration using the offical MSI software (it just charges and decharges the laptop)
    But now, my laptop would just die randomly whenever it is off the charger.
    The symptoms are:
    When not plugged in, it would just die randomly. It won't do a proper shutdown/sleep/hibernate, it just goes black, as if you pull the power on a desktop.
    About a month ago, the windows battery indicator would be a little off, sometimes it would show 15% left, where i would get a message indicating that it is at 15%. However, if i dont plug it in, it would suddenly show a message saying it has 2% left, and then just shut off immediatly. I have fixed this by setting the low and critical battery warnings higher, and didn't have a problem since.
    So i think something is wrong with the windows battery meter, for example, the battery is actually empty and windows thinks it is at 80%. So can't finish properly calibration process it will just shut down and thinks that have 0% but I know that is fully charged and forced shut down at 60% or 70% ??
    Is there a way to reset the windows battery stats? Or should i let the laptop totally run itself dead, by letting it shut off, powering on, and repeating this until it would not boot?
    Any help appreciated

    Quote from: runningman on 24-March-15, 12:16:05
    Hi, may I know your OS is MSI OEM WIN7 HP or it is a retail version?
    Have you updated the drivers, BIOS, EC after upgrade to WIN8.1?
    Also you can remove MSI SCM and check if the problem still exists.
    A better way to judge it is battery hardware problem or OS problem is to recover the OS to MSI factory default and check again.  I guess you haven't build any MSI OS recovery DVD before, so this way can't work.  Then maybe you need the help of repair center.
    Hi, thanks for help
    So when I buy laptop it was WIN 7 Home Premium OEM and later I see some discount for Win 8 to upgrade machine..
    Now using Win 8.1 and I don't think is OS problem, force shut down start to happening after I run MSI Battery Calibrate software.
    Bios is not upgraded since win 7
    Drivers and scm  running fine all from Msi site as well
    EC updated whit last version
    So laptop running fine but it seems that I make mistake when I decided to run calibrate software due to max 5-10% error on battery counter..Now its 60% :-) I am afraid that my battery is dead...

  • HT3964 Imac shuts down after start up

    New hard drive in Imac when I power it on goes throught the process and then it shuts down, I have new memory as well.

    Your capacitors are leaking, this is a known issue with Rev A G5 iMacs, and they should be replaced, along with the logic board. Take it in and if t stays up long enough, try to clone it to an external drive to save your data. I use SuperDuper! to do this.
    Let us know how you make out,

  • IMac (3.4gHz Intel Core i7) shuts down when sleeps, then won't restart

    Just bought a brand new 27" iMac (3.4gHz Intel Core i7) which shuts down when sleeps, then won't restart (ie completely dead).
    In order to restart, I have to unplug the power cord from the computer, hold power key down for 10secs, replug in and it then starts up. I returned to the store and they spent a couple days letting it go to sleep etc and overnight and for them it was fine. Woke up no problems. They returned it to me yesterday.
    So I set it all up again, left it overnight and this morning it was dead again. So now it leaves me to wonder if it's something I have plugged into it.
    I have a new Seagate 3TB external hard drive hooked up using USB3.0. This is plugged directly into the back of the computer.
    I also have a powered USB hub plugged into the computer which has regular USB stuff such as printer, graphics tablet and another external hard drive (this one is older LaCie 500gb, and have put it into a new USB 3.0 case as well for the arrival of the new iMac (this had an old firewire hard drive case). However this hard drive is switched off at the case and is not being used.
    I believe it could possibly be the Seagate 3TB disk causing this problem, but it works fine during the day while I am using the computer, it's just when I either leave it at lunch time to go to a meeting or walk etc or overnight that I come back and it has shut down....leaving me to believe that it's due to the computer going to sleep.
    Has anyone else had a similar problem with a Seagate drive? Today I'm conducting an experiment and heading off for lunch with both hard drives unhooked. If I come back and the computer wakes up from a click of the mouse or keyboard as it should, I will plug in one hard drive at a time and re-test. I will leave the Seagate for last, as I don't think it is the old LaCie disk (which is off).
    For reference sake, I also have a NAS running off my network through Airport Extreme etc and have my old iMac hooked up to the network too, but don't believe this is the problem.
    Initially I did put in some after market RAM (another 8GB) and though that might be the problem, but I removed and it still reacted the same way (plus store I bought it from again booted up fine and woke up fine at their shop after I had taken RAM out too).
    Will keep this post updated with my next test (letting computer sleep without either hard drive in), but keen to hear if anyone has had any similar experiences with Seagate disks/cases and the new iMacs.
    Cheers,
    Kristin

    Hey kristinandmike,
    I had a similar problem shortly after I bought my 27" iMac. Here is an excerpt from my discussion:
    "As BDAqua suggested, I started the process of elimination by shutting down the externals and just leaving up one of the USB drives and using the computer until time to shut it off. After eliminating 2 of the 3 drives I figured it had to be the last one. That drive is a Seagate GoFlex Desk version that allows different bases with differing connectivity. I had previously used FW800 to connect but had switched to USB3 on the new computer. I went ahead and got a Thunderbolt to FW adaptor cable and switched this drive back to Firewire rather than USB3. So far so good."
    For some reason the Seagate I was using didn't agree with the USB3 on the Mac.

  • Premiere won't shut down

    Whenever I close Premiere Pro CS6 on my Win7 box, it saves my project and shuts down.  However, attempts to run it again fail.
    I learned the reason why... it had never really shut down to begin with.  Opening up Windows Task Manager shows it still running in the Process tab.  If I right-click and choose "End Process" it will then shut down so I can open up a new instance of the program.
    Anybody know what the problem could be?  My other Creative Cloud apps do shut down correctly.
    Thanks,
    Rick

    Possibly damaged prefs.  Launch with the Alt key held down to refresh them.

  • Shut-down problems in 10.5.8

    Hi there,
    I wonder if anyone can throw a little light on my problem!
    I have just set up a new 24" iMac, and after updating to 10.5.8 when I am logged into my admin account and have 'fast user switching' enabled between my 'other user' account, I cannot seem to shut down the iMac.
    My 'other user' account is a 'standard' account and does not have administrator privileges.
    When I go to shut down in my admin account the usual window appears with the following info: 'There are currently logged in users who may lose unsaved changes if you shut down this computer' and an invitation to give the administrator's name and password. I do so, but another widow appears advising me that '.... the user name or password is incorrect, please try again' and I cannot shut down. The iMac does not seem to recognise the admin (system) password nor my name - although it accepts my name and password elsewhere on the system ..
    When I go to the top right hand corner of the screen and click on my admin name (fast user) both user accounts are checked.
    I thought that the administrator's name and password was 'final' and used to over-ride any problems. I now have to logout of one account before I can shutdown - I have never had to do this before.
    Why does the iMac not recognise my admin password when shutting down?
    I don't have this problem with my G5 MacBook Pro, nor my G4 PowerBook.
    The iMac shipped with 10.5.6 and after the update is now running 10.5.8.
    Sorry to appear a little 'long winded', but any advice would as usual be fully appreciated. My apologies if this post is in the wrong area.
    Thanks
    John
    Message was edited by: John Rawnsley1
    Message was edited by: John Rawnsley1

    Hi CMCSK,
    Thanks for your reply; yes I tried Apple Care - but sadly the particular techie I talked to couldn't help me - I don't think he really understood the problem.
    Why does my iMac fail to recognise the Administrator's name and password when shutting down whilst two accounts are logged in?
    On the other hand, I will try again today and hopefully I will speak to a techie nearer England!
    Thanks for your help,
    best
    John

  • It'll restart and sleep but NOT shut down

    I've a system that won't shut down! When I select "shut down" from drop down, it'll go through the process but instead of shutting down it restarts. The only way to shut down the system is to hold down the power button.
    The problem originated on a PowerBook G4 550 running 10.3.8 so I upgraded it to 10.4.8 but the problem still exists. I've tried disk warrior, permissions repair, and disk repair w/o luck. Any tips?

    The problem exists even when there isn't anything connected to the Powerbook.
    I've zapped the PRAM w/o success.

  • Race detection in child processes

    Hi,
    the program given below creates a child process with two threads accessing a shared variable. Unfortunately, Thread Analyzer does not detect the race (neither version 12.0 nor 12.3). The race is only detected if it occurs in the parent process. Option "-F on/all" to instrument child processes does not work in conjunction with option "-r all" (the collect tool emits the error message "
    Race-detection data cannot be collected with any of -F -j -J -x"). Is this an inherent limitation of Thread Analyzer or is there a way to detect races and deadlocks in child processes?
    Thank you very much in advance for your help.
    Regards
    #include <unistd.h>
    #include <stdlib.h>
    #include <assert.h>
    #include <pthread.h>
    int x;
    void* fun(void*)
        x++;
        return NULL;
    int main ()
        x = 0;
        int pid = fork();
        assert(pid >= 0);
        if (pid == 0)
            /* Child process */
            pthread_t thread;
            assert(pthread_create(&thread, NULL, fun, NULL) == 0);
            x++;
            assert(pthread_join(thread, NULL) == 0);
            _exit(0);
        else
            /* Parent process */
            sleep (1);
        return 0;

    Just an update in case someone has seen this issue. The problem I am seeing is that some reports will spawn these child processes (that's how the appear in toad). At the DB level it is just another database process which shows up from v$session. I don't know how the application is calling to use as many processes as possible but this is what I am trying to limit on. If I run the same query in SQLPlus, only one process SID is created.

Maybe you are looking for