Did a quick test myself and it looks like this JVM bug is only in JDK 5 -- I've been able to reproduce the JVM crash on Linux with Java 5, but things seem to work fine with Java 6 on both Linux and Mac. I'll try raising a Sun bug report for this, but I don't know how soon we can expect an answer on that.
Using Java 6 when debugging would be a temporary workaround until the JVM bug gets resolved.
The last version of FUSE 18.104.22.168 doesn't work in debug mode.
I set up SERVICEMIX_DEBUG=TRUE env var. Then launch the fuse and have the error like the one described here http://fusesource.com/issues/browse/ESB-759 , but insted of failing on exit the fuse fails on launch.
This error is stable (every time I try to set up SERVICEMIX_DEBUG=TRUE it fails). I tryied on several PCs and UNIX - the same behaviour. That is very sad - we can not run fuse to debug our programs with debugger.
Can somebody update the bug to include that the fuse 22.214.171.124 fails on start with SERVICEMIX_DEBUG=TRUE? Can somebody comment this, because actually it sometimes block our dev process.
Thanks, that works with java6.
We are using FUSEESB 7 and Java 7.
Can you share the steps or url mentioning the steps to start the application in debug mode.
in the shell which you start FUSE ESB.
Thank you able to start Fuse in Debug mode.