Re: continued threading issues


Bill Hibbard wrote:
I doubt that hacking the ThreadPool to create just one
thread will work. We have had lots of trouble with
offscreen rendering over the years. To track down the
cause of this hang, I'd run in jdb (haven't done so in
years) and when the systems hangs, enter "where all" to
see where all the threads are and why they are all hung
(deadlock or whatever).

I agree that hacking the ThreadPool would be dangerous.
You can get a stack trace without running the jdb by:

- pressing Ctrl-Break (windows)
- sending a kill -3 to the java process (unix)

which will show any deadlocks.

Jeff McWhirter ran into some problems with the screen
capture in the IDV using the wait flag.  We've since
moved to using java.awt.Robot to capture images:

              Dimension dim   = comp.getSize();
              Point     loc   = comp.getLocationOnScreen();
              Robot     robot = new Robot();
              BufferedImage image
                    robot.createScreenCapture(new Rectangle(loc.x,
                               loc.y, dim.width, dim.height));

which allows us to capture the UI portion as well as the
VisAD component.  Jeff's out this week, but could
fill you in on the details when he returns.

Don Murray                               UCAR Unidata Program
dmurray@xxxxxxxxxxxxxxxx                        P.O. Box 3000
(303) 497-8628                              Boulder, CO 80307

To unsubscribe visad, visit:

  • 2006 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the visad archives: