🚀 go-pugleaf

Hi.
I work in a NT4 environment, and just upgraded from JB2 to JB3.
I have converted an existing project  that used swing 1.0.3 to use the
new swing package path with the package migration wizard.
That seemed to work allright, and I can work without problems in the
IDE, use the UI designer and compile the project.

A problem does however whenever I execute my compiled java apps.
After closing the swing GUI, when I try to close the DOS console window,

several Java exceptions occur, displaying cryptic messages on stdout.
I would like to know if this is a common problem, if it is specific to
NT, or if it is a local anomaly with my configuration.
Another thing, I suspect that this also happens if I run the application

with the JDK 1.2.2 outside JBuilder.
Please help, and thanks in advance.
    Gabriel

P.S. I have pasted some of the messages below.

        Waiting to be notified:
            "Reference Handler" (0x8efdc0)
    sun.awt.PostEventQueue@19E70B8/1A27960: <unowned>
        Waiting to be notified:
            "SunToolkit.PostEventQueue-0" (0x9ac730)
    javax.swing.TimerQueue@19D4950/1AA2850: <unowned>
        Waiting to be notified:
            "TimerQueue" (0xa0b830)
Registered Monitor Dump:
    Invoker change lock: <unowned>
    utf8 hash table: <unowned>
    JNI pinning lock: <unowned>
    JNI global reference lock: <unowned>
    BinClass lock: <unowned>
    Class linking lock: <unowned>
    System class loader lock: <unowned>
    Code rewrite lock: <unowned>
    Heap lock: <unowned>
    Monitor cache lock: owner "Signal dispatcher" (0x8ef560) 1 entry
    Thread queue lock: owner "Signal dispatcher" (0x8ef560) 1 entry
        Waiting to be notified:
            "Thread-0" (0xa861d0)
    Monitor registry: owner "Signal dispatcher" (0x8ef560) 1 entry