Swing dies if a thread does

Hello all. I’ve noticed that if, in a swing (jruby) app, a thread ever
“raises a backtrace” (say…you hit a button, it hits an exception)
after that point, everything in the app appears broken.

Any pointers/thoughts?
Thanks!
-r

example:

Exception in thread “AWT-EventQueue-0” org.racob.com.ComFailException:
Invoke of: ConnectServer
Source: SWbemLocator
Description:

    at org.racob.com.Dispatch.invokev(Native Method)
    at org.racob.com.Dispatch.invokev(Dispatch.java:803)
    at org.racob.com.Dispatch.callN(Dispatch.java:382)
    at

org.jruby.ext.win32ole.RubyWIN32OLE.invokeMethodOrGet(RubyWIN32OLE.java:203)
at
org.jruby.ext.win32ole.RubyWIN32OLE.method_missing(RubyWIN32OLE.java:113)
at
org.jruby.ext.win32ole.RubyWIN32OLE$i_method_0_0$RUBYINVOKER$method_missing.call(org/jruby/ext/win32ole/RubyWIN32OLE$i_method_0_0$RUBYINVOKER$method_missing.gen:65535)
at
org.jruby.internal.runtime.methods.JavaMethod$JavaMethodN.call(JavaMethod.java:642)