ExceptionHelper problem

In my JUnit tests, I use a number of System.out.println() calls in my JUnit model package tests. And I have also adapted the testInsertingRowIntoAccountsView() JUnit test from the ToyStore Demo.
But once the ExceptionHelper.showExceptionIncludingDetail() call is made and its output has been displayed, no further output is produced by subsequent System.out.println() calls. If I comment out the ExceptionHelper call, then all of the output from all println() calls is visible.
Is there something unusual about how ExceptionHelper outputs its text such that it interferes with println()? Can this be easily fixed?
Thanks very much.
Dennis

Hi, Beverley.
Thank you for visiting Apple Support Communities.
I understand that you are unable to trim clips using iMovie. I would need a little more information on how you were attempting to trim a clip to provide a better answer. However, make sure you have the movie project open and are selecting the clip that you wish to trim as this will activate the clip trimmer.
Trim clips
-Jason H.

Similar Messages

Would like to redirect java error ExceptionHelper.java

Hi All,
I think this might be the right forum... anyway, I'd like to redirect this java exception handler to a different URL. Pretty simple.
I've tried this line of code, but I can't compile... might just be in the wrong place, line 348 :
response.sendRedirect(response.encodeRedirectURL('http://dev.sheridan.edu/uportal/errors/') );This is the whole exception file. Thank youf or your help.. I'm a newbie...
* Copyright � 2001 The JA-SIG Collaborative. All rights reserved.
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
*    notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
*    notice, this list of conditions and the following disclaimer in
*    the documentation and/or other materials provided with the
*    distribution.
* 3. Redistributions of any form whatsoever must retain the following
*    acknowledgment:
*    "This product includes software developed by the JA-SIG Collaborative
*    (http://www.jasig.org/)."
* THIS SOFTWARE IS PROVIDED BY THE JA-SIG COLLABORATIVE "AS IS" AND ANY
* EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE JA-SIG COLLABORATIVE OR
* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
* OF THE POSSIBILITY OF SUCH DAMAGE.
package org.jasig.portal;
import java.io.PrintWriter;
import java.util.ArrayList;
import java.util.Iterator;
import java.util.List;
import javax.servlet.http.HttpServletResponse;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
public class ExceptionHelper {
    private static final Log log = LogFactory.getLog(ExceptionHelper.class);
    // List of strings to match in traceback for various containers
     // This array must be expanded as additional Application Server
     // containers become better known
    public static final String boundaries[] =
              "at javax.servlet.http.HttpServlet."
     * Generate traceback only to the Servlet-container interface.
     * @param ex any throwable exception
     * @return stack trace string without container layers
    public static String shortStackTrace(Throwable ex) {
         if (ex == null)
              return "";
        java.io.StringWriter sw = new java.io.StringWriter();
        ex.printStackTrace(new java.io.PrintWriter(sw));
        sw.flush();
        String stktr = sw.toString();
        return trimStackTrace(stktr);
     * Trims a String representation of a Stack Trace to remove
     * the portion of the trace that is in the servlet container layer.
     * @param stackTrace - String result of printStackTrace
     * @return the stack trace with portions of the trace that dive into the container
     * layer removed.
    static String trimStackTrace(String stackTrace) {
        StringBuffer trimmedTrace = new StringBuffer();
        // a List of Strings to be trimmed and appended to the buffer
        // these represent elements in the causal chain
        List fragments = new ArrayList();
        int causeCut = (stackTrace.indexOf("Caused by"));
        if (causeCut > 0) {
            // there are one or more Caused by fragments to consider
            // we traverse stackTrace, parsing out fragments for later processing
            // and updating stackTrace to contain the remaining unparsed portion
            // as we go
            while (stackTrace.length() > 0) {
                if (stackTrace.startsWith("Caused by")){
                    // don't count the "Caused by" leading the stackTrace
                    causeCut = stackTrace.substring(9).indexOf("Caused by");
                    if (causeCut > 0)
                        causeCut += 9;
                } else {
                    causeCut = stackTrace.indexOf("Caused by");
                if (causeCut > -1) {
                    // stackTrace currently includes multiple fragments
                    // parse out the first and leave the rest for next iteration
                    fragments.add(stackTrace.substring(0, causeCut));
                    stackTrace = stackTrace.substring(causeCut);
                } else {
                    // stackTrace currently is a bare fragment
                    // grab it
                    fragments.add(stackTrace);
                    stackTrace = "";
        } else {
            // there's ony a single Throwable in the chain
            fragments.add(stackTrace);
        // now that we have fragments to consider
        for (Iterator iter = fragments.iterator(); iter.hasNext();){
            String consideredFragment = (String) iter.next();
            // flag to indicate that a trimmed form of this fragment has been appended
            // to the trimmed stack trace buffer
            boolean appended = false;
            for (int i=0; i < boundaries.length; i++) {
                int cut = consideredFragment.indexOf(boundaries);
if (cut > 0) {
// stack trace includes a trace through our container
// in which we are not interested: trim it.
// grab the desired portion up to the boundary
trimmedTrace.append(consideredFragment.substring(0, cut).trim());
trimmedTrace.append("\n");
appended = true;
break;
if (! appended) {
// a trimmed version of this fragment was not appended
// because it doesn't need to be trimmed -- append the whole thing.
trimmedTrace.append(consideredFragment.trim());
trimmedTrace.append("\n");
return trimmedTrace.toString();
* Generic Exception Handler called from catch clause
* @param eid the ErrorID (as seen from catch)
* @param parm
* @param ex the Exception caught
* @throws PortalException
public static void genericHandler(ErrorID eid, String parm, Throwable ex)
throws PortalException {
// *** Handle PortalExceptions ***
     // Log it if logging was deferred in .signal() call
     // Rethrow it
if (ex instanceof PortalException) {
     if (((PortalException)ex).isLogPending())
          traceToLog(eid,parm,ex);
               throw (PortalException) ex;
// *** Handle all other Exceptions ***
// Log the message and traceback
traceToLog(eid, parm, ex);
// Create a derived PortalException chained to this
PortalException nex;
if (ex instanceof Exception) {
nex = new PortalException(eid, (Exception) ex);
} else {
     // Sorry, at this point PortalExceptions don't chain to
     // non-Exception subclasses of Throwable
nex = new PortalException(eid);
nex.setLogPending(false);
ProblemsTable.store(nex);
throw nex;
     public static void genericHandler(ErrorID eid, Throwable ex)
          throws PortalException {
               genericHandler(eid,null,ex);
     * Create PortalException from ErrorID and throw it. Maybe trace it.
     * @param eid ErrorId
     * @param parm Additional error information
     * @param tracenow Trace now or defer till first catch.
     * @throws PortalException
public static void signal(ErrorID eid, String parm, boolean tracenow)
throws PortalException {
PortalException nex = new PortalException(eid);
          nex.setParameter(parm);
signal(nex,tracenow);
* Create PortalException from Errorid, trace, and throw it.
* @param eid ErrorID to use to generate PortalException
* @param parm Additional error information
* @throws PortalException
public static void signal(ErrorID eid, String parm) throws PortalException {
     signal(eid,parm,true);
* Throw PortalException provided by caller, maybe trace it.
* @param nex Exception provided by caller
* @param tracenow Trace now, or later after first catch.
* @throws PortalException
private static void signal(PortalException nex, boolean tracenow)
throws PortalException {
if (tracenow) {
     traceToLog(nex.getErrorID(), nex.getParameter(), nex);
     ProblemsTable.store(nex);
throw nex;
* Generate, trace, and throw Portal Exception given ErrorID.
* @param eid ErrorID
* @throws PortalException
public static void signal(ErrorID eid)
     throws PortalException {
     signal(eid,null,true);
* Common logic for generating log entry of errors
* @param eid ErrorID with initial message
* @param parm Parameter string to append to eid msg
* @param ex Old exception
private static void traceToLog(ErrorID eid, String parm, Throwable ex) {
     if (ex !=null &&
          ex instanceof PortalException) {
               if (!((PortalException)ex).isLogPending())
                    return; // This PortalException was already logged.
               else
                    ((PortalException)ex).setLogPending(false);
String logmsg = errorInfo(eid, parm, ex);
log.error( logmsg);
* Generate error string for logging or /problems online display
* @param eid Error ID
* @param parm Parameter string
* @param ex Exception
* @return Multiline text with message and traceback
public static String errorInfo(ErrorID eid, String parm, Throwable ex) {
          StringBuffer errorinfobuffer = new StringBuffer(1000);
          if (eid!=Errors.legacy)
     errorinfobuffer.append(eid.getMessage()); // Error ID message
else
     errorinfobuffer.append(ex.getMessage());
          if (parm != null) { // Parameter data
               errorinfobuffer.append("\n [specific data: ");
               errorinfobuffer.append(parm);
               errorinfobuffer.append("] ");
          errorinfobuffer.append("\n");
          if (ex!=null)
               errorinfobuffer.append(shortStackTrace(ex)); // Stack trace
          return errorinfobuffer.toString();
* Generic Top-Level Exception Handler caled from catch clause
* (doesn't rethrow exception)
* @param eid Error ID
* @param parm Parameter string
* @param ex Exception caught
public static void genericTopHandler(ErrorID eid, String parm, Throwable ex) {
// If this is an already logged Portal Exception, we are done
if (ex instanceof PortalException &&
     !((PortalException)ex).isLogPending()) {
     return;
traceToLog(eid, parm, ex);
if (ex instanceof PortalException) // already in the table
     return;
          // Create a derived PortalException (just for Problems Table)
          PortalException nex=null;
          if (ex instanceof Exception)
               nex = new PortalException(eid, (Exception) ex);
          else
               nex = new PortalException(eid);
          ProblemsTable.store(nex);
     public static void genericTopHandler(ErrorID eid, Throwable ex) {
          genericTopHandler(eid, null, ex);
* Generate HTML page to send to end user after fatal error
* @param resp Servlet response object
* @param e PortalException received at Servlet code.
     public static void generateErrorPage(HttpServletResponse resp, Exception e) {
          resp.setContentType("text/html");
          try {
               response.sendRedirect(response.encodeRedirectURL('http://dev.sheridan.edu/uportal/errors/') );
               PrintWriter out = resp.getWriter();
               out.println("<h1>Cannot start uPortal</h1>");
               out.println("<p>Sorry, but a problem is preventing the Portal from starting. "+
                    "The error must be corrected by system administrators. Try again later.</p>");
               //out.println("<p><a href='http://www.yale.edu/portal'>Click here to display the static Yaleinfo page.</a></p>");
               out.println("");
               out.flush();
          } catch (Exception ex) {

I've tried this line of code, but I can't compile...
might just be in the wrong place, line 348 :
response.sendRedirect(response.encodeRedirectURL ('http://dev.sheridan.edu/uportal/errors/') );
Use double quotes instead of single quotes!
Single quotes are for char literals, not string literals.
And next time please copy and paste the complete error message, instead of just saying "it doesn't compile".

Problem when installing Teaming 2.0 on an new SLES11 system

hello,
I've just installed SLES11 on a new computer and after that, I've done a basic installation for Teaming 2.0 .
Evrything seems to be fine during installation process but it's impossible to connect with an HTTP 404 error message and The requested resource () is not available.
I've stopped teaming, cleaned the catalina.out file and even before attempting any connection here is the significant content :
INFO: JK: ajp13 listening on /0.0.0.0:8009
Sep 30, 2009 4:16:00 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/14 config=null
Sep 30, 2009 4:16:00 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 10338 ms
Exception in thread "Quartz Scheduler [Sitescape]" Sep 30, 2009 4:16:56 PM org.apache.catalina.loader.WebappClassLoader loadClass
INFO: Illegal access: this web application instance has been stopped already. Could not load org.quartz.utils.ExceptionHelper. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
java.lang.IllegalStateException
at org.apache.catalina.loader.WebappClassLoader.loadC lass(WebappClassLoader.java:1273)
at org.apache.catalina.loader.WebappClassLoader.loadC lass(WebappClassLoader.java:1233)
at java.lang.ClassLoader.loadClassInternal(ClassLoade r.java:320)
at org.quartz.SchedulerException.getUnderlyingExcepti on(SchedulerException.java:169)
at org.quartz.SchedulerException.toString(SchedulerEx ception.java:265)
at java.lang.String.valueOf(String.java:2826)
at java.lang.StringBuffer.append(StringBuffer.java:21 9)
at org.springframework.core.NestedExceptionUtils.buil dMessage(NestedExceptionUtils.java:47)
at org.springframework.core.NestedRuntimeException.ge tMessage(NestedRuntimeException.java:67)
at java.lang.Throwable.getLocalizedMessage(Throwable. java:267)
at java.lang.Throwable.toString(Throwable.java:343)
at java.lang.String.valueOf(String.java:2826)
at java.io.PrintStream.println(PrintStream.java:771)
at org.apache.tomcat.util.log.SystemLogHandler.printl n(SystemLogHandler.java:242)
at java.lang.Throwable.printStackTrace(Throwable.java :461)
at java.lang.ThreadGroup.uncaughtException(ThreadGrou p.java:974)
at java.lang.ThreadGroup.uncaughtException(ThreadGrou p.java:965)
at java.lang.Thread.dispatchUncaughtException(Thread. java:1831)
Some idea on this Quark Scheduler exception ?
Regards
Daniel

Sorry but the first problem while launching is not the one described before.
Here is the first one in catalina.out :
FROM_HEADER=
LANG=POSIX}
2009-10-01 06:43:40,753 WARN [main] [org.hibernate.impl.SessionFactoryObjectFactory] - InitialContext did not implement EventContext
2009-10-01 06:43:41,963 INFO [main] [org.kablink.teaming.license.LicenseManager] - Loading license
2009-10-01 06:43:42,916 INFO [main] [com.novell.teaming.docconverter.impl.TextStellentC onverter] - DOCCONVERTER: Loading config/docconverter.cfg
2009-10-01 06:43:43,897 ERROR [main] [org.springframework.web.context.ContextLoader] - Context initialization failed
org.springframework.beans.factory.BeanCreationExce ption: Error creating bean with name 'defaultEmailFormatter' defined in ServletContext resource [/WEB-INF/context/applicationContext.xml]: Cannot resolve reference to bean 'smtpService' whil
e setting bean property 'smtpService'; nested exception is org.springframework.beans.factory.BeanCreationExce ption: Erro
r creating bean with name 'smtpService' defined in ServletContext resource [/WEB-INF/context/applicationContext.xml]: In
vocation of init method failed; nested exception is java.lang.RuntimeException: java.net.SocketException: Permission denied
It's perhaps easier to resolve.
Daniel

A problem with threads

I am trying to implement some kind of a server listening for requests. The listener part of the app, is a daemon thread that listens for connections and instantiates a handling daemon thread once it gets some. However, my problem is that i must be able to kill the listening thread at the user's will (say via a sto button). I have done this via the Sun's proposed way, by testing a boolean flag in the loop, which is set to false when i wish to kill the thread. The problem with this thing is the following...
Once the thread starts excecuting, it will test the flag, find it true and enter the loop. At some point it will LOCK on the server socket waiting for connection. Unless some client actually connects, it will keep on listening indefinatelly whithought ever bothering to check for the flag again (no matter how many times you set the damn thing to false).
My question is this: Is there any real, non-theoretical, applied way to stop thread in java safely?
Thank you in advance,
Lefty

This was one solution from the socket programming forum, have you tried this??
public Thread MyThread extends Thread{
     boolean active = true;
     public void run(){
          ss.setSoTimeout(90);
          while (active){
               try{
                    serverSocket = ss.accept();
               catch (SocketTimeoutException ste){
               // do nothing
     // interrupt thread
     public void deactivate(){
          active = false;
          // you gotta sleep for a time longer than the
          // accept() timeout to make sure that timeout is finished.
          try{
               sleep(91);
          }catch (InterruptedException ie){
          interrupt();
}

A problem with Threads and MMapi

I am tring to execute a class based on Game canvas.
The problem begin when I try to Play both a MIDI tone and to run an infinit Thread loop.
The MIDI tone "Stammers".
How to over come the problem?
Thanks in advance
Kobi
See Code example below:
import java.io.IOException;
import java.io.InputStream;
import javax.microedition.lcdui.Graphics;
import javax.microedition.lcdui.Image;
import javax.microedition.lcdui.game.GameCanvas;
import javax.microedition.media.Manager;
import javax.microedition.media.MediaException;
import javax.microedition.media.Player;
public class MainScreenCanvas extends GameCanvas implements Runnable {
     private MainMIDlet parent;
     private boolean mTrucking = false;
     Image imgBackgound = null;
     int imgBackgoundX = 0, imgBackgoundY = 0;
     Player player;
     public MainScreenCanvas(MainMIDlet parent)
          super(true);
          this.parent = parent;
          try
               imgBackgound = Image.createImage("/images/area03_bkg0.png");
               imgBackgoundX = this.getWidth() - imgBackgound.getWidth();
               imgBackgoundY = this.getHeight() - imgBackgound.getHeight();
          catch(Exception e)
               System.out.println(e.getMessage());
      * starts thread
     public void start()
          mTrucking = true;
          Thread t = new Thread(this);
          t.start();
      * stops thread
     public void stop()
          mTrucking = false;
     public void play()
          try
               InputStream is = getClass().getResourceAsStream("/sounds/scale.mid");
               player = Manager.createPlayer(is, "audio/midi");
               player.setLoopCount(-1);
               player.prefetch();
               player.start();
          catch(Exception e)
               System.out.println(e.getMessage());
     public void run()
          Graphics g = getGraphics();
          play();
          while (true)
               tick();
               input();
               render(g);
      * responsible for object movements
     private void tick()
      * response to key input
     private void input()
          int keyStates = getKeyStates();
          if ((keyStates & LEFT_PRESSED) != 0)
               imgBackgoundX++;
               if (imgBackgoundX > 0)
                    imgBackgoundX = 0;
          if ((keyStates & RIGHT_PRESSED) != 0)
               imgBackgoundX--;
               if (imgBackgoundX < this.getWidth() - imgBackgound.getWidth())
                    imgBackgoundX = this.getWidth() - imgBackgound.getWidth();
      * Responsible for the drawing
      * @param g
     private void render(Graphics g)
          g.drawImage(imgBackgound, imgBackgoundX, imgBackgoundY, Graphics.TOP | Graphics.LEFT);
          this.flushGraphics();
}

You can also try to provide a greater Priority to your player thread so that it gains the CPU time when ever it needs it and don't harm the playback.
However a loop in a Thread and that to an infinite loop is one kind of very bad programming, 'cuz the loop eats up most of your CPU time which in turn adds up more delays of the execution of other tasks (just as in your case it is the playback). By witting codes bit efficiently and planning out the architectural execution flow of the app before start writing the code helps solve these kind of issues.
You can go through [this simple tutorial|http://oreilly.com/catalog/expjava/excerpt/index.html] about Basics of Java and Threads to know more about threads.
Regds,
SD
N.B. And yes there are more articles and tutorials available but much of them targets the Java SE / EE, but if you want to read them here is [another great one straight from SUN|http://java.sun.com/docs/books/tutorial/essential/concurrency/index.html] .
Edited by: find_suvro@SDN on 7 Nov, 2008 12:00 PM

J2ME problem with threads

Hi all,
I would like to ask you for a help. I need to write a small program at my university. I started to write a midlet which function would be to countdown time for sports activities. I woul like to start a new thread - the one that counts down - and at the same time make the main thread sleep. After the "countdown" thread finishes, the main thread wakes up and waits for user input. The problem is that when the "countdown" thread finishes his work, I've got Uncaught exception java/lang/NullPointerException. error and the midlet halts.
Below you can find the code
import java.lang.*;
import java.util.*;
import javax.microedition.lcdui.*;
import javax.microedition.midlet.*;
public class intervals extends MIDlet implements CommandListener
public Display ekran;
private SweepCanvas sweeper;
private Form rundy;
private TextField round0, round1, round2, round3, round4, round5, round6, round7, round8;
private long czas,x;
private Command exitCommand;
private Command addRound;
private Command delRound;
private Command start;
private TextField repeat;
private Form odliczanie;
private Alert ostrz;
Licznik thread;
String test;
StringItem test1;
int parz,i,j,k;
static int l;
int ilrund;
int ilpowt;
Item sec;
long sec1;
public intervals()
    rundy = new Form("Interwały sportowe");
    exitCommand = new Command("Wyjście", Command.EXIT, 2);
    addRound = new Command("Dodaj","Dodaj rundę", Command.ITEM,1);
    delRound = new Command("Usuń","Usuń ostatnią rundę", Command.ITEM,1);
    start = new Command("Start", Command.ITEM,1);
    odliczanie = new Form("Odliczanie");
    TextField dodaj(TextField kolej)
        kolej=new TextField("Podaj czas (s) rundy "+parz,null, 4, TextField.NUMERIC);//stworzenie nowej instancji do wybierania czasu trwania rundy
        if(rundy.size()==0)
            rundy.insert(rundy.size(),kolej);
            else
                rundy.insert(rundy.size()-1, kolej);
        return kolej;
    void odliczanie(TextField round)
        monitor m=new monitor();
        k=Integer.parseInt(round.getString());
        ekran.setCurrent(odliczanie);
        thread=new Licznik(k,odliczanie);
        thread.start();
        ekran.setCurrent(rundy);
public void startApp()// throws MIDletStateChangeException
    rundy.deleteAll();
    repeat = new TextField("Podaj ilość powtórzeń",null,1,TextField.NUMERIC);
    rundy.addCommand(addRound);
    rundy.addCommand(exitCommand);
    rundy.setCommandListener(this);
    Canvas obrazek = new MyCanvas();
    ekran = Display.getDisplay(this);
    ekran.setCurrent(obrazek);
    czas=System.currentTimeMillis();
    while (System.currentTimeMillis()<czas+1000)
        continue;
    ekran.setCurrent(rundy);
public void pauseApp()
public void destroyApp(boolean unconditional)
    notifyDestroyed();
public void commandAction(Command c, Displayable s)
    if (c == exitCommand)
        destroyApp(false);
        notifyDestroyed();
    else if(c==addRound)
        if(rundy.size()==0)//Sprawdzenie ilości elementów w celu poprawnego wyświetlania liczby rund w formie
            parz=1;
            else
            parz=rundy.size();
        switch(parz)
            case 1:
                round0=dodaj(round0);break;
            case 2:
                round1=dodaj(round1);break;
            case 3:
               round2= dodaj(round2);break;
            case 4:
                round3=dodaj(round3);break;
            case 5:
                round4=dodaj(round4);break;
            default:
                ostrz=new Alert("Uwaga","Maksymalna liczba rund wynosi 9", null, AlertType.INFO);
                ostrz.setTimeout(3000);
                ekran.setCurrent(ostrz);
        if(rundy.size()==1)
            rundy.append(repeat);
            rundy.addCommand(start);
        rundy.addCommand(delRound);
    else if(c==delRound)
        if(rundy.size()!=0)
            rundy.delete(rundy.size()-2);
            if (rundy.size()==1)
                rundy.deleteAll();
            if(rundy.size()==0)
                rundy.removeCommand(delRound);
                rundy.removeCommand(start);
    else if(c==start)
        ilrund=rundy.size()-1;
        if(this.repeat.size()>0)
            ilpowt=Integer.parseInt(this.repeat.getString());
        ekran = Display.getDisplay(this);
        for (i=1; i<=ilpowt;i++)
            odliczanie= new Form("Odliczanie");
             for (j=0;j<ilrund;j++)
                switch(j)
                     case 0:
                         odliczanie(round0);
                         break;
                     case 1:
                         odliczanie(round1);
                         break;
                     case 2:
                         odliczanie(round2);
                         break;
                     case 3:
                         odliczanie(round3);
                         break;
                     case 4:
                         odliczanie(round4);
                         break;
                     case 5:
                         odliczanie(round5);
                         break;
                     case 6:
                         odliczanie(round6);
                         break;
                     case 7:
                         odliczanie(round7);
                         break;
                     case 8:
                         odliczanie(round8);
                         break;
class Licznik extends Thread
    int czas1,k;
    Form forma;
    monitor m;
    public Licznik(int k,Form formap)
        czas1=k;
        forma=formap;
    public synchronized void run()
        while(czas1>0)
            forma.deleteAll();
            forma.append("Czas pozostały (s): "+czas1);
            try{Thread.sleep(1000);} catch(InterruptedException e){e.printStackTrace();}
            czas1--;
        if(czas1<=0)
            m.put();
    }and monitor class
public class monitor
boolean busy=false;
synchronized void get()
    if(!busy)
        try
            wait();
        }catch(InterruptedException e){e.printStackTrace();}
    notify();
synchronized void put()
    if(busy)
        try
        wait();
        }catch(InterruptedException e){e.printStackTrace();}
    busy=true;
    notify();
}Can anybody help me with this?

Groovemaker,
Your Licznik class has a member m of type monitor, which has not been instantiated (in other words is null) hence, when calling m.put() you get NullPointerException. Please also mind, that using Thread.sleep(1000) is not an accurate way of measuring time.
If I may, please use recommended for Java class naming conventions - some of your names use lower case, while other don't which is confusing to the reader.
Daniel

Problem with threads within applet

Hello,
I got an applet, inside this applet I have a singleton, inside this singleton I have a thread.
this thread is running in endless loop.
he is doing something and go to sleep on and on.
the problem is,
when I refresh my IE6 browser I see more than 1 thread.
for debug matter, I did the following things:
inside the thread, sysout every time he goes to sleep.
sysout in the singleton constructor.
sysout in the singleton destructor.
the output goes like this:
when refresh the page, the singleton constructor loading but not every refresh, sometimes I see the constructor output and sometimes I dont.
The thread inside the singleton is giving me the same output, sometime I see more than one thread at a time and sometimes I dont.
The destructor never works (no output there).
I don't understand what is going on.
someone can please shed some light?
thanks.
btw. I am working with JRE 1.1
this is very old and big applet and I can't convert it to something new.

Ooops. sorry!
I did.
     public void start() {
     public void stop() {
     public void destroy() {
          try {
               resetAll();
               Configuration.closeConnection();
               QuoteItem.closeConnection();
          } finally {
               try {
                    super.finalize();
               } catch (Throwable e) {
                    e.printStackTrace();
     }

Problem with Threads and a static variable

I have a problem with the code below. I am yet to make sure that I understand the problem. Correct me if I am wrong please.
Code functionality:
A timer calls SetState every second. It sets the state and sets boolean variable "changed" to true. Then notifies a main process thread to check if the state changed to send a message.
The problem as far I understand is:
Assume the timer Thread calls SetState twice before the main process Thread runs. As a result, "changed" is set to true twice. However, since the main process is blocked twice during the two calls to SetState, when it runs it would have the two SetState timer threads blocked on its synchronized body. It will pass the first one, send the message and set "changed" to false since it was true. Now, it will pass the second thread, but here is the problem, "changed" is already set to false. As a result, it won't send the message even though it is supposed to.
Would you please let me know if my understanding is correct? If so, what would you propose to resolve the problem? Should I call wait some other or should I notify in a different way?
Thanks,
B.D.
Code:
private static volatile boolean bChanged = false;
private static Thread objMainProcess;
   protected static void Init(){
        objMainProcess = new Thread() {
            public void run() {
                while( objMainProcess == Thread.currentThread() ) {
                   GetState();
        objMainProcess.setDaemon( true );
        objMainProcess.start();
    public static void initStatusTimer(){
        if(objTimer == null)
             objTimer = new javax.swing.Timer( 1000, new java.awt.event.ActionListener(){
                public void actionPerformed( java.awt.event.ActionEvent evt){
                          SetState();
    private static void SetState(){
        if( objMainProcess == null ) return;
        synchronized( objMainProcess ) {
            bChanged = true;
            try{
                objMainProcess.notify();
            }catch( IllegalMonitorStateException e ) {}
    private static boolean GetState() {
        if( objMainProcess == null ) return false;
        synchronized( objMainProcess ) {
            if( bChanged) {
                SendMessage();
                bChanged = false;
                return true;
            try {
                objMainProcess.wait();
            }catch( InterruptedException e ) {}
            return false;
    }

Thanks DrClap for your reply. Everything you said is right. It is not easy to make them alternate since SetState() could be called from different places where the state could be anything else but a status message. Like a GREETING message for example. It is a handshaking message but not a status message.
Again as you said, There is a reason I can't call sendMessage() inside setState().
The only way I was able to do it is by having a counter of the number of notifies that have been called. Every time notify() is called a counter is incremented. Now instead of just checking if "changed" flag is true, I also check if notify counter is greater than zero. If both true, I send the message. If "changed" flag is false, I check again if the notify counter is greater than zero, I send the message. This way it works, but it is kind of a patch than a good design fix. I am yet to find a good solution.
Thanks,
B.D.

Problem with threads running javaw

Hi,
Having a problem with multi thread programming using client server sockets. The program works find when starting the the application in a console using java muti.java , but when using javaw multi.java the program doesnt die and have to kill it in the task manager. The program doesnt display any of my gui error messages either when the server disconnect the client. all works find in a console. any advice on this as I havent been able to understand why this is happening? any comment would be appreciated.
troy.

troy,
Try and post a minimum code sample of your app which
does not work.
When using javaw, make sure you redirect the standard
error and standard output streams to file.
Graeme.Hi Graeme,
I dont understand what you mean by redirection to file? some of my code below.
The code works fine under a console, code is supposed to exit when the client (the other server )disconnects. the problem is that but the clientworker side of the code still works. which under console it doesnt.
public class Server{
ServerSocket aServerSocket;
Socket dianosticsSocket;
Socket nPortExpress;
ClientListener aClientListener;
LinkedList queue = new LinkedList();
int port = 0;
int clientPort = 0;
String clientName = null;
boolean serverAlive = true;
* Server constructor generates a server
* Socket and then starts a client threads.
* @param aPort      socket port of local machine.
public Server(int aPort, String aClientName, int aClientPort){
port = aPort;
clientName = aClientName;
clientPort = aClientPort;
try{
// create a new thread
aServerSocket = new ServerSocket(port) ;
// connect to the nPortExpress
aClientListener = new ClientListener(InetAddress.getByName(clientName), clientPort, queue,this);
// aClientListener.setDaemon(true);
aClientListener.start();
// start a dianostic port
DiagnosticsServer aDiagnosticsServer = new DiagnosticsServer(port,queue,aClientListener);
// System.out.println("Server is running on port " + port + "...");
// System.out.println("Connect to nPort");
catch(Exception e)
// System.out.println("ERROR: Server port " + port + " not available");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Server port " + port + " not available", JOptionPane.ERROR_MESSAGE);
serverAlive = false;
System.exit(1);
while(serverAlive&&aClientListener.hostSocket.isConnected()){
try{
// connect the client
Socket aClient = aServerSocket.accept();
//System.out.println("open client connection");
//System.out.println("client local: "+ aClient.getLocalAddress().toString());
// System.out.println("client localport: "+ aClient.getLocalPort());
// System.out.println("client : "+ aClient.getInetAddress().toString());
// System.out.println("client port: "+ aClient.getLocalPort());
// make a new client thread
ClientWorker clientThread = new ClientWorker(aClient, queue, aClientListener, false);
// start thread
clientThread.start();
catch(Exception e)
//System.out.println("ERROR: Client connection failure");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Client connection failure", JOptionPane.ERROR_MESSAGE);
}// end while
} // end constructor Server
void serverExit(){
     JOptionPane.showMessageDialog(null, "Server ","ERROR: nPort Failure", JOptionPane.ERROR_MESSAGE);
     System.exit(1);
}// end class Server
*** connect to another server
public class ClientListener extends Thread{
InetAddress hostName;
int hostPort;
Socket hostSocket;
BufferedReader in;
PrintWriter out;
boolean loggedIn;
LinkedList queue;      // reference to Server queue
Server serverRef; // reference to main server
* ClientListener connects to the host server.
* @param aHostName is the name of the host eg server name or IP address.
* @param aHostPort is a port number of the host.
* @param aLoginName is the users login name.
public ClientListener(InetAddress aHostName, int aHostPort,LinkedList aQueue,Server aServer)      // reference to Server queue)
hostName = aHostName;
hostPort = aHostPort;
queue = aQueue;
serverRef = aServer;
// connect to the server
try{
hostSocket = new Socket(hostName, hostPort);
catch(IOException e){
//System.out.println("ERROR: Connection Host Failed");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Connection to nPort Failed", JOptionPane.ERROR_MESSAGE);
System.exit(0);
} // end constructor ClientListener
** multi client connection server
ClientWorker(Socket aSocket,LinkedList aQueue, ClientListener aClientListener, boolean diagnostics){
queue = aQueue;
addToQueue(this);
client = aSocket;
clientRef = aClientListener;
aDiagnostic = diagnostics;
} // end constructor ClientWorker
* run method is the main loop of the server program
* in change of handle new client connection as well
* as handle all messages and errors.
public void run(){
boolean alive = true;
String aSubString = "";
in = null;
out = null;
loginName = "";
loggedIn = false;
while (alive && client.isConnected()&& clientRef.hostSocket.isConnected()){
try{
in = new BufferedReader(new InputStreamReader(client.getInputStream()));
out = new PrintWriter(new OutputStreamWriter(client.getOutputStream()));
if(aDiagnostic){
out.println("WELCOME to diagnostics");
broadCastDia("Connect : diagnostics "+client.getInetAddress().toString());
out.flush();
else {
out.println("WELCOME to Troy's Server");
broadCastDia("Connect : client "+client.getInetAddress().toString());
     out.flush();
String line;
while(((line = in.readLine())!= null)){
StringTokenizer aStringToken = new StringTokenizer(line, " ");
if(!aDiagnostic){
broadCastDia(line);
clientRef.sendMessage(line); // send mesage out to netExpress
out.println(line);
out.flush();
else{
if(line.equals("GETIPS"))
getIPs();
else{
clientRef.sendMessage(line); // send mesage out to netExpress
out.println(line);
out.flush();
} // end while
catch(Exception e){
// System.out.println("ERROR:Client Connection reset");
                         JOptionPane.showMessageDialog(null, (e.toString()),"ERROR:Client Connection reset", JOptionPane.ERROR_MESSAGE);
try{
if(aDiagnostic){
broadCastDia("Disconnect : diagnostics "+client.getInetAddress().toString());
out.flush();
else {
broadCastDia("Disconnect : client "+client.getInetAddress().toString());
     out.flush();
// close the buffers and connection;
in.close();
out.close();
client.close();
// System.out.println("out");
// remove from list
removeThreadQueue(this);
alive = false;
catch(Exception e){
// System.out.println("ERROR: Client Connection reset failure");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Client Connection reset failure", JOptionPane.ERROR_MESSAGE);
}// end while
} // end method run
* method run - Generates io stream for communicating with the server and
* starts the client gui. Run also parses the input commands from the server.
public void run(){
boolean alive = true;
try{
// begin to life the gui
// aGuiClient = new ClientGui(hostName.getHostName(), hostPort, loginName, this);
// aGuiClient.show();
in = new BufferedReader(new InputStreamReader(hostSocket.getInputStream()));
out = new PrintWriter(new OutputStreamWriter(hostSocket.getOutputStream()));
while (alive && hostSocket.isConnected()){
String line;
while(((line = in.readLine())!= null)){
System.out.println(line);
broadCast(line);
} // end while
} // end while
catch(Exception e){
//     System.out.println("ERRORa Connection to host reset");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Connection to nPort reset", JOptionPane.ERROR_MESSAGE);
try{
hostSocket.close();
     }catch(Exception a){
     JOptionPane.showMessageDialog(null, (a.toString()),"ERROR: Exception", JOptionPane.ERROR_MESSAGE);
alive = false;
System.exit(1);
} // end method run

Problem with Threads and "plase wait..."-Window

Hi everyone,
I have a problem that I'm not able to solve in any way... I have a time-consuming task (a file decryption) which I execute in a separate thread; I've used the SwingWorker class, like suggested by sun-tutorial, and it works right. The problem is that I have to wait that the decryption have finished before continuing with program-execution. Therefore I would like to display a "please wait"-window while the task runs. I've tryed all the possible ways I know but the problem is always the same: the waitWindow is displayed empty, the bounds are painted but the contents no; it's only painted when the decrypt-task has finished. Please help me, I have no more resources....
decrypt-file code:
public class DecryptFile {
private String cryptedFileNameAndPath;
private ByteArrayInputStream resultStream = null;
// need for progress
private int lengthOfTask;
private int current = -1;
private String statMessage;
public DecryptFile(String encZipFileNameAndPath) {
    cryptedFileNameAndPath = encZipFileNameAndPath;
    //Compute length of task...
    // 0 for indeterminate
    lengthOfTask = 0;
public ByteArrayInputStream getDecryptedInputStream() {
    return this.resultStream;
   * Called from ProgressBarDemo to start the task.
public void go() {
    current = -1;
    final SwingWorker worker = new SwingWorker() {
      public Object construct() {
        return new ActualTask();
    worker.start();
   * Called from ProgressBarDemo to find out how much work needs
   * to be done.
public int getLengthOfTask() {
    return lengthOfTask;
   * Called from ProgressBarDemo to find out how much has been done.
public int getCurrent() {
    return current;
public void stop() {
    current = lengthOfTask;
   * Called from ProgressBarDemo to find out if the task has completed.
public boolean done() {
    if (current >= lengthOfTask)
      return true;
    else
      return false;
public String getMessage() {
    return statMessage;
   * The actual long running task. This runs in a SwingWorker thread.
class ActualTask {
    ActualTask () {
      current = -1;
      statMessage = "";
      resultStream = AIUtil.getInputStreamFromEncZip(cryptedFileNameAndPath); //here the decryption happens
      current = 0;
      statMessage = "";
}The code that calls decryption and displays waitWindow
      final WaitSplash wS = new WaitSplash("Please wait...");
      final DecryptFile cryptedTemplate = new DecryptFile (this.templateFile);
      cryptedTemplate.go();
      while (! cryptedTemplate.done()) {
        try {
          wait();
        } catch (Exception e) { }
      this.templateInputStream = cryptedTemplate.getDecryptedInputStream();
      wS.close();Thanks, thanks, thanks in advance!
Edoardo

Maybe you can try setting the priority of the long-running thread to be lower? so that the UI will be more responsive...

Problem with threads in j2me

im using jdk 1.6 with java wtk 2.1
ya i know..
2.1 is a jdk1.4 source
but im using souce as 1.4 during compiliation so thats not the prob
this is my code
package org.learn;
import javax.microedition.midlet.MIDlet;
import javax.microedition.lcdui.Alert;
import javax.microedition.lcdui.Display;
public class thtest extends MIDlet
Thread t;
public void startApp()
Alert a=new Alert("hello");
a.setString("hello");
Alert b=new Alert("world");
b.setString("world");
Display d = Display.getDisplay(this );
d.setCurrent(a);
t=Thread.currentThread();
try{
t.sleep(10000);
catch (Exception e){}
d.setCurrent(b);
public void pauseApp()
public void destroyApp(boolean unconditional)
its just supposed to pause between the alerts using threads
however when i run it using the wtk, the emulator run properly but when i launch the app, it stops executing giving me this:
"Error verifying method org/learn/thtest startApp()V
Approximate bytecode offset 49: Inconsistent or missing stackmap at target
%the stack info%
Execution completed.
437782 bytecodes executed
9 thread switches
486 classes in the system (including system classes)
2506 dynamic objects allocated (73832 bytes)
2 garbage collections (60652 bytes collected)
Execution completed.
437782 bytecodes executed
9 thread switches
486 classes in the system (including system classes)
ALERT: java/lang/VerifyError: org/learn/thtest.
2506 dynamic objects allocated (73832 bytes)
2 garbage collections (60652 bytes collected)
please can someone help me out with this, is it an error on my part or do i have to set some option.

Hi gandalf123,
First, Thread.sleep is a static method, so you don't need to create a Thread object to use it.
I think the problem is due to the fact you don't preverify your midlet.
More over, you don't need to double post your question.

Problem with threads and camera.

Hi everybody!
I've a problem with taking snapshot.
I would like to display a loading screen after it take snapshot ( sometimes i
have to wait few seconds after i took snapshot. Propably photo is being taken in time where i have to wait).
I was trying to use threads but i didn't succeed.
I made this code:
display.setCurrent(perform);
        new Thread(new Runnable(){
            public void run() {
                while((!performing.isShown()) && (backgroundCamera.isShown())){
                    Thread.yield();
                notifyAll();
        }).start();
        new Thread(new Runnable(){
            public void run() {
                try {
                    this.wait();
                } catch(Exception e) {
                    exceptionHandler(e);
                photo = camera.snapshot();
                display.setCurrent(displayPhoto);
        }).start();This code is sometimes showing performing screen but sometimes no.
I don't know why. In my opinion performing.isShown() method isn't working correctly.
Does anyone have some idea how to use threads here?

Hi,
I've finally managed to work this fine.
The code:
       Object o = new Object();
       display.setCurrent(perform);
        new Thread(new Runnable(){
            public void run() {
                while(!performing.isShown()){
                    Thread.yield();
               synchronized(o) {
                  o.notify();
        }).start();
        new Thread(new Runnable(){
            public void run() {
                try {
                    synchronized(o) {
                       o.wait(1);
                } catch(Exception e) {
                    exceptionHandler(e);
                photo = camera.snapshot();
                display.setCurrent(displayPhoto);
        }).start();

Problem with threads and graphics

I have a thread that chooses paths for a Travelling salesman problem, it then calls a TSPdraw class and passes it the path, which the class then draws. the problem is when i have two threads it creates two windows but only draws a path in one of them. any ideas where i`m going wrong

Are you using swing components? Swing isn't threadsafe. If you have multiple threads that want to update your UI you need to use the SwingUtilities.invokeLater(...)or invokeAndWait(...). There is a page in the swing tutorial about this at: http://java.sun.com/docs/books/tutorial/uiswing/misc/threads.html

Problem with threads hanging

We have a problem where our application stops responding after a few days of usage. Things will for fine for a day or two, and then pretty quickly threads will start getting hung up, usually in places where they are allocating memory
We are running WebLogic 8.1 SP2 on Sun JDK 1.4.2_04 on Solaris 8 using the alternate threading model and the -server hotspot vm. We are running pretty much the same code that we had no problems with under WebLogic 6.1 SP4 and Sun JDK 1.3.1.
A thread dump usually shows that some or all of our execute threads are in the state "waiting for monitor entry" even though they are not currently waiting on any java locks. Here is a sample thread from the thread dump (we have ~120 threads so I don't want to post the full dump).
=============================================================================================
"ExecuteThread: '8' for queue: 'itgCrmWarExecutionQueue'" daemon prio=5 tid=0x005941d0 nid=0x2c waiting for monitor entry [c807f000..c807fc28]
at java.lang.String.substring(String.java:1446)
at java.lang.String.substring(String.java:1411)
at weblogic.servlet.internal.ServletRequestImpl.getRelativeUri(ServletRequestImpl.java:1872)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3492)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
=============================================================================================
String.java line 1446 for this jdk allocates a new String object, and all the other threads in this state also are creating new objects or arrays, etc.
We've done a pstack on this process when it's in this state, and the threads that are in the "waiting for monitor entry" that look like they're allocating memory are all waiting on the same lwp_mutex_lock with some allocation method that's calling into the native TwoGenerationCollectorPolicy.mem_allocate_work (see pstack output below for the same thread as in the thread dump above)
=============================================================================================
----------------- lwp# 44 / thread# 44 --------------------
ff31f364 lwp_mutex_lock (e3d70)
fee92384 __1cNObjectMonitorGenter26MpnGThread__v_ (5000, 525c, 5000, 50dc, 4800, 4af0) + 2d8
fee324d4 __1cSObjectSynchronizerKfast_enter6FnGHandle_pnJBasicLock_pnGThread__v_ (c807f65c, c807f7d4, 5941d0, 0, 35d654, fee328ec) + 68
fee32954 __1cQinstanceRefKlassZacquire_pending_list_lock6FpnJBasicLock__v_ (c807f7d4, ff170000, d4680000, 4491d4, fee1bc2c,
0) + 78
fee3167c __1cPVM_GC_OperationNdoit_prologue6M_i_ (c807f7bc, 4400, ff170000, 2d2b8, 4a6268, c807fa18) + 38
fee2e0b0 __1cIVMThreadHexecute6FpnMVM_Operation__v_ (c807f7bc, 963a8, 0, 0, 1, 0) + 90
fed2c2a4 __1cbCTwoGenerationCollectorPolicyRmem_allocate_work6MIii_pnIHeapWord__ (962c0, ff1c29ec, ff1c297c, ff131a26, 4800, 4998) + 160
fed22940 __1cNinstanceKlassRallocate_instance6MpnGThread__pnPinstanceOopDesc__ (ee009020, 5941d0, 15ca581, 3647f0, 4a6268, c807f8c8) + 180
fed34928 __1cLOptoRuntimeFnew_C6FpnMklassOopDesc_pnKJavaThread__v_ (ee009018, 5941d0, 0, 0, 0, 0) + 28
fa435a58 ???????? (ee009018, e86de, 15ca4de, 50dc, 5941d0, c807f9c8)
fb36f9a4 ???????? (0, d412ccd8, ee046c28, ff170000, 0, 0)
fad8b278 ???????? (ee046c28, d6000c90, ee046530, 8, db8e8450, c807f9e8)
fad62abc ???????? (d412ccd8, ee046530, d6000c90, ee3bfa38, 8, c807fa18)
fa4b3c38 ???????? (c807fb9c, 0, f2134700, fa415e50, 8, c807faa8)
fa40010c ???????? (c807fc28, c807fe90, a, ee9e1e20, 4, c807fb40)
fed5d48c __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (c807fe88, c807fcf0, c807fda8, 5941d0, 5941d0, c807fd00) + 27c
fee4b784 __1cJJavaCallsMcall_virtual6FpnJJavaValue_nLKlassHandle_nMsymbolHandle_4pnRJavaCallArguments_pnGThread__v_ (ff170000, 594778, c807fd9c, c807fd98, c807fda8, 5941d0) + 164
fee5e8dc __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_nMsymbolHandle_5pnGThread__v_ (c807fe88, c807fe84, c807fe7c, c807fe74, c807fe6c, 5941d0) + 6c
fee6fc74 __1cMthread_entry6FpnKJavaThread_pnGThread__v_ (5941d0, 5941d0, 838588, 594778, 306d10, fee69254) + 128
fee6927c __1cKJavaThreadDrun6M_v_ (5941d0, 2c, 40, 0, 40, 0) + 284
fee6575c _start   (5941d0, fa1a1600, 0, 0, 0, 0) + 134
ff3758c0 lwpstart (0, 0, 0, 0, 0, 0)
=============================================================================================
Also when it's having this problem, the "VM Thread" is always using a lot of processor time. We did a couple of pstacks today while it was having this problem, and this thread was stuck in the ONMethodSweeper.sweep for over 15 minutes when we finally killed the server.
From the thread dump:
"VM Thread" prio=5 tid=0x000e2d20 nid=0x2 runnable
From the first pstack:
=============================================================================================
----------------- lwp# 2 / thread# 2 --------------------
fed40c04 __1cXvirtual_call_RelocationIparse_ic6FrpnICodeBlob_rpC5rppnHoopDesc_pi_nNRelocIterator__ (42a2f4, fa5fa46d, ffffffff, fc4ffcb8, 42a2f4, 42a324) + 124
fed46318 __1cKCompiledIC2t5B6MpnKRelocation__v_ (42a2f0, fc4ffd24, fc4ffd4c, e802, 0, 6) + 38
fed90c38 __1cHnmethodVcleanup_inline_caches6M_v_ (fa5f7f88, fa608940, 1, 0, fa400000, 6) + 1ac
fede18b4 __1cONMethodSweeperFsweep6F_v_ (2cf38, 0, ffffffff, ff1cf1fc, ff1c66e8, fede1d44) + 1b0
fede1e6c __1cUSafepointSynchronizeFbegin6F_v_ (2cf38, ff1ba138, 5000, 50dc, 5000, 525c) + 248
feef1fd4 __1cIVMThreadEloop6M_v_ (4400, 4000, 4324, 4000, 42b0, 3800) + 3d4
feef1ae4 __1cIVMThreadDrun6M_v_ (e2d20, 2, 40, 0, 40, 0) + 8c
fee6575c _start   (e2d20, ff270200, 0, 0, 0, 0) + 134
ff3758c0 lwpstart (0, 0, 0, 0, 0, 0)
=============================================================================================
Second pstack
=============================================================================================
----------------- lwp# 2 / thread# 2 --------------------
fed41180 __1cXvirtual_call_RelocationIparse_ic6FrpnICodeBlob_rpC5rppnHoopDesc_pi_nNRelocIterator__ (0, ff1b9664, ffffffff, fc4ffcb8, a6f2cc, fc4ffbd0) + 6a0
fed46318 __1cKCompiledIC2t5B6MpnKRelocation__v_ (a6f2c8, fc4ffd24, fc4ffd4c, e802, 0, 6) + 38
fed90c38 __1cHnmethodVcleanup_inline_caches6M_v_ (faded4c8, fadf2c80, 1, 0, fa400000, 6) + 1ac
fede18b4 __1cONMethodSweeperFsweep6F_v_ (2cf38, 0, ffffffff, ff1cf1fc, ff1c66e8, fede1d44) + 1b0
fede1e6c __1cUSafepointSynchronizeFbegin6F_v_ (2cf38, ff1ba138, 5000, 50dc, 5000, 525c) + 248
feef1fd4 __1cIVMThreadEloop6M_v_ (4400, 4000, 4324, 4000, 42b0, 3800) + 3d4
feef1ae4 __1cIVMThreadDrun6M_v_ (e2d20, 2, 40, 0, 40, 0) + 8c
fee6575c _start   (e2d20, ff270200, 0, 0, 0, 0) + 134
ff3758c0 lwpstart (0, 0, 0, 0, 0, 0)
=============================================================================================
Has anyone ever seen anything like this? I'm trying to figure out if this is caused by something we're doing, or something relating to our environment and jvm options. Any ideas?

Thanks for the reply - I'm testing our app with the +UseConcMarkSweepGC now in our test environment to make sure it doesn't cause any problems there. Unfortunately the only place we've had this problem is on the production server, so it's extra difficult debugging this.
We're using the following memory options:
-ms512m -mx512m -XX:NewSize=128m -XX:PermSize=192m -XX:MaxNewSize=128m -XX:MaxPermSize=192m -XX:SurvivorRatio=8and the following debugging options, as we've also been seeing OutOfMemoryErrors ( see http://forum.java.sun.com/thread.jsp?forum=37&thread=522354&tstart=45&trange=15 )
-verbosegc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintHeapAtGCBTW, which c++filt version and options are you using? Our Solaris boxes only seem to have the GNU version installed. I was trying to run that on some of the other stack traces and wasn't getting anywhere, and didn't know if because it was GNU version wouldn't work on something compiled with the Sun compiler.
Thanks!
--Andy

Problem with threads and ProgressMonitor

Dear Friends:
I have a little problem with a thread and a ProgressMonitor. I have a long time process that runs in a thread (the thread is in an separate class). The thread has a ProgressMonitor that works fine and shows the tasks progress.
But I need deactivate the main class(the main class is the user interface) until the thread ends.
I use something like this:
LongTask myTask=new LongTask();
myTask.start();
myTask.join();
Now, the main class waits for the task to end, but the progress monitor don`t works fine: it shows only the dialog but not the progress bar.
What's wrong?

Is the dialog a modal dialog? This can block other UI updates.
In general, you should make sure that it isn't modal, and that your workThread has a fairly low priority so that the UI can do its updating

ExceptionHelper problem

Similar Messages

Maybe you are looking for