LV Threads, Monitors

Hi,
I am trying to solve something like a producer-consumer problem in Labview
(thinking about Mesa-style monitors) but having a problem. It does not seem
like the Notify VIs can atomically release a lock and go to sleep.
Am I missing something?
-joey

"valiot" wrote in message
news:[email protected]..
> Why is the Notifier not working for you?
> If you want the "wait on notification" vi to sleep then do not wire
> the timeout value. Otherwise the wait function will timeout and
> wake-up at the specified timeout value.
Indeed, that works fine. I guess I should have been more specific. My
understanding of Mesa-Monitors (just school, I am no expert) is that you
must hold a lock before you wait() for a condition variable, and then wait()
should atomically release then wait for the condition variable. That way
whatever you signaled is blocked until after the wait() is complete.
The problem becomes that I can implement locks with semaphores, and I can
implement wait/signal with notify VIs, but I don't see how I can atomically
release a lock and wait().
It is of course possible to signal, unlock, wait. However "worst case" is
that the signalled thread executes, signals, and the first thread was not
waiting at the time so it misses the signal; unlikely but possible. In some
cases it is possible to check the history for missed signals but it seems
programmatically clumsy and does not always fix the problem.
In short... Are monitors actually possible given the resources available? I
was somewhat confused by the lack of atomic unlock/sleep.
-joey

Similar Messages

Servlet Exec Thread Monitor - MII 11.5

We have some reports that get "stuck", and they consume CPU usage, so we have to go into Servlet Exec's Thread Monitor to kill these reports.
Currently, we go into MII to manually check to see if there are any stuck reports. It would be nice if we could have MII load these log files automatically and send us an eMail when a report is stuck, so I thought we could use the HTML loader to do this. The problem is Servlet Exec has security, and it requires an ID and Password. I thought I could use the HTTP Post action block to get around this, but for the life of me, I can't get it to work.
Is it possible to use Logic Editor to open Servlet Exec's Thread Monitor screen, and if so, how?

Hi Lino,
Keep the original code of the applet.
<APPLET NAME="myChart" CODEBASE="/Illuminator/Classes" CODE="iChart" ARCHIVE="illum8.zip" WIDTH="840" HEIGHT="400">
<PARAM NAME="DisplayTemplate" VALUE="Demo_Project/Vale_POC/SampleChart.xml">
<PARAM NAME="QueryTemplate" VALUE="Demo_Project/Vale_POC/QryValePOC.xml">
<PARAM Name="TagName.1" VALUE="CylTemp1">
</APPLET>
In 11.5 existis guest user. add two parameters in you applet.
<PARAM NAME="IllumLoginName" VALUE="Guest">
<PARAM NAME="IllumLoginPassword" VALUE="Guest">
I believe the best solution would be to use the SAP MII portal for developing your application and not the. NET. In SAP MII already have a lot tools ready for development of application.
If you use frame follow the link.
http://help.sap.com/saphelp_xmii115/helpdata/en/Security/Programmatic_Logins.htm
Hope this help.
Danilo Santos

HTTP Acceptor Thread Monitoring

I'm attempting to monitor the HTTP Acceptor Thread pool in a Production environment. JMX Monitoring threshold has been set to HIGH but I still can't seem to find the pool monitor. I see HTTP Listener Threads, but not acceptor thread monitoring.
Is there any way to achieve this?

Hi,
Do you really need a HTTP Sender communication channel. Generally there is no need for a Sender communication channel for HTTP and IDOC adapter. They directly come into Integration engine.
This would be the URL for communicating
http://<hostname:port>/<path>?<query-string>
The <query string> contains the following data:
Sender namespace ?namespace=<namespace>
Sender interface &interface=<interface>
These details define the sender interface.
Sender service &service=<service>
Sender party (optional) &party=<party>
Sender agency (optional) &agency=<agency>
Sender scheme (optional) &scheme=<scheme>
Thanks,
Prakash

Synchronized thread monitors!!! AHHH!!!

Hi,
In my program , I'm trying to start a thread which immediately begins waiting and when a notify is received the Thread executes a method and then right back to waiting. The program I'm having trouble writing is far too bulky and complicated to be easily made sense of here, so I've written this concise version:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
import java.util.*;
class syncTest1 {
     public static void main(String[] args) {
          syncTest2 thread = new syncTest2();
          Monitor monitor = new Monitor();
          try {
               for(int i = 1; i <= 100; i++) {
                    synchronized(monitor) {
                         System.out.println("Notifying...");
                         monitor.notify();
                         Thread.sleep(500);
          } catch(InterruptedException ie) {}
class syncTest2 extends Thread {
     Monitor monitor;
     syncTest2() {}
     public void run() {
          try {
               while (monitor.progress() < 100) {
                    synchronized(monitor) {
                         monitor.wait();
                         monitor.increment(1);
                         System.out.println("Notified! Progress = " + monitor);
          } catch(InterruptedException ie) {}
     public Monitor getMonitor() { return monitor; }
// Used to store a dynamic integer value that can passed around as a synchronized monitor
class Monitor {
     int Int;
     Monitor() { Int = 0; }
     public void increment(int howMuch) { Int += Math.abs(howMuch); }
     public void decrement(int howMuch) { Int -= Math.abs(howMuch) * -1; }
     public int progress() { return Int; }
}<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
When ran, this is the output:
java syncTest1
Notifying...
Notifying...
Notifying...
Notifying...
Notifying...
Notifying...
Notifying...
<and so on>
Notice how the monitor is never notified and syncTest1's monitor is still reacquired and able to be notified. I assume the problem lies somewhere in the trading of the monitor between classes, but for the life of me, I can't figure this one out...
Any help at all would be appreciated.
Thanks,
Jick

There are 2 things wrong.
1) You did not start your your thread.
2) You were not synchronizing on the same object.
I have also made some cosmetic changes but you are free to remove them.
import java.util.*;
public class Test20041229
    public static void main(String[] args)
        syncTest2 thread = new syncTest2();
        Monitor monitor = thread.getMonitor();//new Monitor(); !!!!!!!!!!!!!!!!!!!!!!!!!!
        thread.start(); // !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!1
        for(int i = 1; i <= 100; i++)
            synchronized(monitor)
                System.out.println("Notifying..." + i);
                monitor.notify();
                try
                    monitor.wait(500);
                } catch(InterruptedException ie)
class syncTest2 extends Thread
    Monitor monitor = new Monitor();
    syncTest2()
    public void run()
        while (monitor.progress() < 100)
            synchronized(monitor)
                try
                    monitor.wait();
                } catch(InterruptedException ie)
                monitor.increment(1);
                System.out.println("Notified! Progress = " + monitor);
    public Monitor getMonitor()
    { return monitor; }
// Used to store a dynamic integer value that can passed around as a synchronized monitor
class Monitor
    int Int;
    Monitor()
    { Int = 0; }
    public void increment(int howMuch)
    { Int += Math.abs(howMuch); }
    public void decrement(int howMuch)
    { Int -= Math.abs(howMuch) * -1; }
    public int progress()
    { return Int; }
    public String toString()
        return "Monitor(" + Int + ")";
}

Java threads monitoring

I am using Java threads in my Java program, running on Windows Professional 2000. I am monitoring the threads using Windows Performance Monitor (WPM). However, even running a small Java program which creates only 2 threads, results in many (at least 10) instances of Java threads being reported by the WPM. Problem is, in WPM, there is no way to determine which threads in the WPM are the threads that I programmatically created. Any ideas on how to determine this?
Thanks.
Rhodie

Hi Dmirty ,
To handle large asynchronous message in queues you can use message packaging where multiple message are processed in one package . to make it applicable you have to perform these simple steps
1. go to SXMB_ADM add one RUNTIME parameter PACKAGING and value 1
2 GO TO transaction SXMS_BCONF set delay time 0 message count 100 messages and package size 1000 KB
with these setting your improvement will increase .secondly also put IN SXMB_ADM monitor category parameter QRFC_RESTART_ALLOWED TO 1
this will automatically start your queue . Only thing you have to take care if you enable packaging them don't keep too many parallel queue i.e EO_INBOUND_PARALLEL and EO_OUTBOUND_PARALLEL should be less than 20
Regards,
Saurabh

Thread monitor in portal

Hi.
I want to monitor thread usage in portal.
Where can I do this ?
I already try "System management -> Monitor -> Thread overview" but I don't know this is correct information.
Welcome any comments.
Regards, Arnold.

Hi Arnold,
Yes that is the correct place
Regards
Arun

Thread Monitoring in a clustered BPEL environment

Hi BPEL community,
does anybody know how I can monitor the "Pending Requests" and "Thread Allocation Activity" (BPEL Console - Threads) over all cluster-nodes? Inside the BPEL Console I only see the data of the cluster-node I'm logged in.
I was not able to see an over-all cluster-nodes view of the load on the bpel-engine.
Regards, Harald

I am not familior with anything called Quartz but I think this issue should be handled task scheduler itself.
In the place I work the task scheduler we use (I house developed one) has following approach
Once the task is posted it is in "posted" state and once a batch server (Thats what we call the service that executes it) picks a task up it changes the state to "executing". Once the execution is complete it change the state to "ready". If an exception occures it will abort the operation and set the state to "error".
Batch Server can pick up only the tasks with state "Posted" so two services will not pick up same task.
By the way the tasks with error state can be reset to posted state by the user.
probably you need a solution like this. Either you have to develop one or find one which considers the existance of multiple execution services

How are Apple Support Communities threads monitored?

While most threads seem to be about solving problems, or discussions on using products etc, I recently say two threads disappear, probably because the original posters were ranting, being overtly critical of Apple, and insulting other community members without reason. The threads really had no value at all.
Do Apple employees actively monitor these threads? Or is it only after someone reports an abuse, or as you level up do you get special priveledges to boot people. XD

"Do Apple employees actively monitor these threads? Or is it only after someone reports an abuse, or as you level up do you get special priveledges to boot people."
It's a combination of both. Upper level users can report abuse on any observed topic or poster in a topic. There are also moderators who monitor the forums. They are Apple employees.

DPS 6 worker threads monitor command?

In the deployment guide it states:
Directory Proxy Server allows you to configure how many threads the server maintains to
process requests. You configure this using the server property number-of-worker-threads,
described in number-of-worker-threads(5dpconf). As a rule of thumb, try setting this number
to 50 threads plus 20 threads for each data source used. To gauge whether the number is
sufficient, monitor the status of the Directory Proxy Server work queue on cn=Work
Queue,cn=System Resource,cn=instance-path,cn=Application
System,cn=DPS6.0,cn=Installed Product,cn=monitor.
How do you do an ldapsearch on monitor in a dps? I dont know how to do the command suggested in the manual.

ldapsearch -p port -h host -b cn=monitor -D 'cn=proxy manager' -w password cn=*

Thread monitoring for database query

Hi,
I need to be able to store a database query in a thread. This means that the entire query from executing to return should take place in this thread (as well as connection etc). I would then like to know when it have finished its work so i can carry on some more porcessing.
I tried doing this with two threads, one to do the work and the other to 'watch' and then tell me when is is done. However, i errors 'every now and again' to which i can attribute to my thread structure not working properly. I am using a synchronised class and code post the code if anyone wishes to see it, however, i would appreciate it if someone could give me a basic structure to how i can go about this so that i do not get these 'random' errors.
Thanks Rudy

Okay -
I have an idea. Withut fully implementing your code, mind you.
If looks like you're having problems with concurrent access to your Vector.
A Vector is, of course, a Collection and a List (interfaces) - these are not thread safe. To make them thread safe, you need to "wrap" them.
<lifted from JavaDocs>
public static Collection synchronizedCollection(Collection c)
    Returns a synchronized (thread-safe) collection backed by the specified collection. In order to guarantee
serial access, it is critical that all access to the backing collection is accomplished through the returned
collection.
    It is imperative that the user manually synchronize on the returned collection when iterating over it:
Collection c = Collections.synchronizedCollection(myCollection);
synchronized(c) {
      Iterator i = c.iterator(); // Must be in the synchronized block
      while (i.hasNext())
         foo(i.next());
    Failure to follow this advice may result in non-deterministic behavior.
    The returned collection does not pass the hashCode and equals operations through to the backing
collection, but relies on Object's equals and hashCode methods. This is necessary to preserve the
contracts of these operations in the case that the backing collection is a set or a list.
    The returned collection will be serializable if the specified collection is serializable.
    Parameters:
        c - the collection to be "wrapped" in a synchronized collection.
    Returns:
        a synchronized view of the specified collection.</lifted from JavaDocs>
Give your Vector a wrapper and see if that solves your problem.
+M

Profiler API - Locks, Threading.Monitor.Enter and Exit

I'm using the Profiler API in a project in order to track the locks made using Monitor.Enter, Monitor.Exit, and the lock keyword. I planned to do this by outputting using a pipe, the events from the FunctionEnter3WithInfo and FunctionLeave3WithInfo callbacks.
These callbacks are called when methods are entered and exited, and appear to be functioning fine regarding their implementation - they generate a large output of methods that had been entered and left, but I'm not receiving callbacks for the following:
ENTER: Monitor.Exit
LEAVE: Monitor.Enter and Monitor.Exit
Oddly enough, I do get receive a callback for entering Monitor.Enter. Other than these problematic methods, I appear to be getting calls from the Profiler API for everything else.
Is there a known issue regarding these methods not being reported by the API?
Alternatively, if there's a better way of achieving my goal than the way I'm doing it, feel free to point me in the right direction :)
Thanks,
Olu

Thanks for the reply Brian,
I don't get a JITInlining callback for Monitor.Exit (however I do for some Monitor.Enter calls). For FunctionTailcall3WithInfo, I also don't get a callback for Monitor.Exit (but I do for some Monitor.Enter calls).
I'm not getting anything from ExceptionUnwindFunctionEnter, though when manually tested by throwing an exception within a try-catch, I get a callback.
If it helps, I have the following flags set for events:
COR_PRF_MONITOR_ALL
COR_PRF_ENABLE_FUNCTION_ARGS
COR_PRF_ENABLE_FUNCTION_RETVAL
COR_PRF_ENABLE_FRAME_INFO
Additionally, I've tried the following flags to see if it resolves the issue:
COR_PRF_DISABLE_INLINING
COR_PRF_DISABLE_OPTIMIZATIONS
Edit 1: Using COR_PRF_DISABLE_OPTIMIZATIONS now means I get a callback to FunctionLeave3WithInfo when Monitor.Enter leaves, however there is still no sign of Monitor.Exit
Edit 2: As a test, in the small application that I'm profiling, I've wrapped the Monitor.Exit and Monitor.Enter method calls in another class, so I can call them as so:
CCMonitor.Enter(obj) and CCMonitor.Exit(obj).
The profiler reports both the enter and leave of these functions correctly.
Thanks,
Olu

How do you monitor a background thread and update the GUI

Hello,
I have a thread which makes its output available on PipedInputStreams. I should like to have other threads monitor the input streams and update a JTextArea embedded in a JScrollPane using the append() method.
According to the Swing tutorial, the JTextArea must be updated on the Event Dispatch Thread. When I use SwingUtilities.invokeLater () to run my monitor threads, the component is not redrawn until the thread exits, so you don't see the progression. If I add a paint () method, the output is choppy and the scrollbar doesn't appear until the thread exits.
Ironically, if I create and start new threads instead of using invokeLater(), I get the desired result.
What is the correct architecture to accomplish my goal without violating Swing rules?
Thanks,
Brad
Code follows:
import java.lang.*;
import java.io.*;
import javax.swing.*;
import javax.swing.text.*;
import java.awt.*;
import java.awt.event.*;
public class SystemCommand implements Runnable
     private String[] command;
     private PipedOutputStream pipeout;
     private PipedOutputStream pipeerr;
     public SystemCommand ( String[] cmd )
          command = cmd;
          pipeout = null;
          pipeerr = null;
     public void run ()
          exec ();
     public void exec ()
          // --- Local class to redirect the process input stream to a piped output stream
          class OutputMonitor implements Runnable
               InputStream is;
               PipedOutputStream pout;
               public OutputMonitor ( InputStream i, PipedOutputStream p )
                    is = i;
                    pout = p;
               public void run ()
                    try
                         int inputChar;
                         for ( ;; )
                              inputChar = is.read();
                              if ( inputChar == -1 ) { break; }
                              if ( pout == null )
                                   System.out.write ( inputChar );
                              else
                                   pout.write ( inputChar );
                         if ( pout != null )
                              pout.flush ();
                              pout.close ();
                         else
                              System.out.flush();
                    catch ( Exception e ) { e.printStackTrace (); }
          try
               Runtime r = Runtime.getRuntime ();
               Process p = r.exec ( command );
               OutputMonitor out = new OutputMonitor ( p.getInputStream (), pipeout );
               OutputMonitor err = new OutputMonitor ( p.getErrorStream (), pipeerr );
               Thread t1 = new Thread ( out );
               Thread t2 = new Thread ( err );
               t1.start ();
               t2.start ();
               //p.waitFor ();
          catch ( Exception e ) { e.printStackTrace (); }
     public PipedInputStream getInputStream () throws IOException
          pipeout = new PipedOutputStream ();
          return new PipedInputStream ( pipeout );
     public PipedInputStream getErrorStream () throws IOException
          pipeerr = new PipedOutputStream ();
          return new PipedInputStream ( pipeerr );
     public void execInThread ()
          Thread t = new Thread ( this );
          t.start ();
     public static JPanel getContentPane ( JTextArea ta )
          JPanel p = new JPanel ( new BorderLayout () );
          JPanel bottom = new JPanel ( new FlowLayout () );
          JButton button = new JButton ( "Exit" );
          button.addActionListener ( new ActionListener ( )
                                   public void actionPerformed ( ActionEvent e )
                                        System.exit ( 0 );
          bottom.add ( button );
          p.add ( new JScrollPane ( ta ), BorderLayout.CENTER );
          p.add ( bottom, BorderLayout.SOUTH );
          p.setPreferredSize ( new Dimension ( 640,480 ) );
          return p;
     public static void main ( String[] argv )
          // --- Local class to run on the event dispatch thread to update the Swing GUI
          class GuiUpdate implements Runnable
               private PipedInputStream pin;
               private PipedInputStream perr;
               private JTextArea outputArea;
               GuiUpdate ( JTextArea textArea, PipedInputStream in )
                    pin = in;
                    outputArea = textArea;
               public void run ()
                    try
                         // --- Reads whole file before displaying...takes too long
                         //outputArea.read ( new InputStreamReader ( pin ), null );
                         BufferedReader r = new BufferedReader ( new InputStreamReader ( pin ) );
                         String line;
                         for ( ;; )
                              line = r.readLine ();
                              if ( line == null ) { break; }
                              outputArea.append ( line + "\n" );
                              // outputArea.paint ( outputArea.getGraphics());
                    catch ( Exception e ) { e.printStackTrace (); }
          // --- Create and realize the GUI
          JFrame f = new JFrame ( "Output Capture" );
          f.setDefaultCloseOperation ( JFrame.EXIT_ON_CLOSE );
          JTextArea textOutput = new JTextArea ();
          f.getContentPane().add ( getContentPane ( textOutput ) );
          f.pack();
          f.show ();
          // --- Start the command and capture the output in the scrollable text area
          try
               // --- Create the command and setup the pipes
               SystemCommand s = new SystemCommand ( argv );
               PipedInputStream stdout_pipe = s.getInputStream ();
               PipedInputStream stderr_pipe = s.getErrorStream ();
               // --- Launch
               s.execInThread ( );
               //s.exec ();
               // --- Watch the results
               SwingUtilities.invokeLater ( new GuiUpdate ( textOutput, stdout_pipe ) );
               SwingUtilities.invokeLater ( new GuiUpdate ( textOutput, stderr_pipe ) );
               //Thread t1 = new Thread ( new GuiUpdate ( textOutput, stdout_pipe ) );
               //Thread t2 = new Thread ( new GuiUpdate ( textOutput, stderr_pipe ) );
               //t1.start ();
               //t2.start ();
          catch ( Exception e ) { e.printStackTrace (); }


Thanks for pointing out the SwingWorker class. I didn't use it directly, but the documentation gave me some ideas that helped.
Instead of using invokeLater on the long-running pipe-reader object, I run it on a normal thread and let it consume the output from the background thread that is running the system command. Inside the reader thread I create a tiny Runnable object for each line that is read from the pipe, and queue that object with invokeLater (), then yield() the reader thread.
Seems like a lot of runnable objects, but it works ok.

Monitoring threading

Hello,
I was looking at the little JVMTI documentation I could find. Any pointers to good docs? I had to go mostly with the API style reference..
As to my needs, I would like to monitor thread scheduling in real-time. So I could record which thread is running at which point and for how long. Is this possible with JVM TI or some other API? I see there are event functions for thread start and end. I could possibly hook those and add an event listener to each thread to record when it starts execution. I just dont know what event to use to record execution start after the switch, since none really seem good for the job. Naturally, I am interested in minimal overhead. Ideas?
Also as a second note, I am also interested in monitoring resource usage, such as file access, network activity, etc... much like probes in systemtap (http://sourceware.org/systemtap/) and similar tools. Is there some way to do this effectively in Java? I realize it may be more difficult as the VM is not quite the OS kernel here..?
Any pointers and other help would be great.
thanks!

Why don't you have a common data object which is
passed to all the threads and the thread monitor
class? In such a approach it will be easy for the
threads to communicate and also if you need to
synchronize them you can use wait / notify.Nah, I wouldn't pool the data unless I needed to. That way deadlock madness lies. If the data is specific to a thread, keep it in the thread's class.

Wake up a specific thread

Hello All,
We have a site that has the potential of multiple users hitting our site at the same time. Each user initiates a transaction request, which goes to a controller servlet and then fires off a transaction worker. While these transaction are running, the request enters a synchronized method (a java thread monitor) that puts the request into a pool until the transaction worker completes.
My question is: how do you ensure that you only wake up the specific request that fired off the transaction worker, when the transaction worker is completed?
Any help is appreciated,
Thanks!
James

Have the worker invoke notifyAll() on the request object and the caller (your servlet) invoke wait() on the same object. Since one and only one client thread will exist for each request, that will work fine. Use the pool (queue?) to hold requests that have not yet been taken by a worker. The workers .wait() on the queue (or some other monitor) for work to do.
Consider using Doug Lea's excellent Executor class from his concurrency library (http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/intro.html), it and the associated classes handles these kinds of need beautifully. Oh and they are also the basis of the work in JSR 166 to create a set of standardized concurrency utility classes in a future version of Java...
Chuck

Aplication server thread pool problem

I'm using sun app server 8.
After some time from starting (and using) the server, it stops responding to clients.
When I change the max number of threads on server the number of clients it can serve before hanging folows the change. So I guess that some threads are not recycled.
But, I can't get full thread dump to see what's happening.
Also I can't get any thread pool monitoring information through asadmin.
(I can see that EJB's are all removed successfuly)
Any suggestions.
Thanks in advance.

First of all, thank you for helping me.
The client wasn't making problems, but server did. (I didn't said that I use the app. server on XP.)
For now I solved the problem by installing the new beta 2004Q4. It works fine now, it also has some thread monitoring in web console...
I was getting this, when I tried to monitor the thread-pool (it is set on HIGH):
asadmin> get -m server.thread-pools.thread-pool.thread-pool-1.*
No matches resulted from the wildcard expression.
CLI137 Command get failed.
If it means anything this is what I was getting when I do ctrl-break. (this thread dump stays the same even after server stops responding...)
Full thread dump Java HotSpot(TM) Client VM (1.4.2_04-b04 mixed mode):
"Thread-6" prio=5 tid=0x02edad08 nid=0xb40 runnable [331f000..331fd8c]
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(FileInputStream.java:177)
at org.apache.commons.launcher.StreamConnector.run(StreamConnector.java:
115)
"Thread-5" prio=5 tid=0x02ebbb98 nid=0x8ac runnable [32df000..32dfd8c]
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(FileInputStream.java:194)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:220)
at java.io.BufferedInputStream.read(BufferedInputStream.java:277)
- locked <0x10089900> (a java.io.BufferedInputStream)
at java.io.FilterInputStream.read(FilterInputStream.java:90)
at org.apache.commons.launcher.StreamConnector.run(StreamConnector.java:
115)
"Signal Dispatcher" daemon prio=10 tid=0x0093dc18 nid=0x930 waiting on condition
[0..0]
"Finalizer" daemon prio=9 tid=0x008a5c20 nid=0xbd0 in Object.wait() [2b5f000..2b
5fd8c]
at java.lang.Object.wait(Native Method)
- waiting on <0x10502a00> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111)
- locked <0x10502a00> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
"Reference Handler" daemon prio=10 tid=0x008a47f0 nid=0xb4 in Object.wait() [2b1
f000..2b1fd8c]
at java.lang.Object.wait(Native Method)
- waiting on <0x10502a68> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:429)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:115)
- locked <0x10502a68> (a java.lang.ref.Reference$Lock)
"main" prio=5 tid=0x000362a0 nid=0xc38 runnable [7f000..7fc3c]
at java.lang.Win32Process.waitFor(Native Method)
at org.apache.commons.launcher.LaunchTask.execute(LaunchTask.java:705)
at org.apache.tools.ant.Task.perform(Task.java:341)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
at org.apache.commons.launcher.Launcher.start(Launcher.java:402)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at LauncherBootstrap.main(LauncherBootstrap.java:185)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.admin.servermgmt.pe.PEInstancesManager.startInstan
ce(PEInstancesManager.java:115)
at com.sun.enterprise.admin.servermgmt.pe.PEDomainsManager.startDomain(P
EDomainsManager.java:126)
at com.sun.enterprise.cli.commands.StartDomainCommand.runCommand(StartDo
mainCommand.java:59)
at com.sun.enterprise.cli.framework.CLIMain.invokeCommand(CLIMain.java:1
23)
at com.sun.enterprise.cli.framework.CLIMain.main(CLIMain.java:39)
"VM Thread" prio=5 tid=0x0093c698 nid=0x9b4 runnable
"VM Periodic Task Thread" prio=10 tid=0x00940438 nid=0xbd4 waiting on condition
"Suspend Checker Thread" prio=10 tid=0x0093d2b8 nid=0x2c0 runnable

LV Threads, Monitors

Similar Messages

Maybe you are looking for