We've integrated v1.0.1 of DJNativeSwing in our project. On some client
machines we're having an "Failed to connect to spawned VM!" exception. It is
not really clear why this error is generated on certain machines and not on
others.
-Would it be possible to get more information about the real cause of this exception ?
-How can we generate detailed logging for the DJNativeSwing component ?
-Does DJNativeSwing depends on certain OS settings to be able to work correctly ?
_java.lang.IllegalStateException: Failed to connect to spawned VM!
at chrriis.dj.nativeswing.swtimpl.core.SWTNativeInterface$OutProcess.createOut
ProcessMessagingInterface(SWTNativeInterface.java:990)
at chrriis.dj.nativeswing.swtimpl.core.SWTNativeInterface$OutProcess.createOut
ProcessCommunicationChannel(SWTNativeInterface.java:735)
at chrriis.dj.nativeswing.swtimpl.core.SWTNativeInterface.open_(SWTNativeInter
face.java:320)
at
chrriis.dj.nativeswing.swtimpl.NativeInterface.open(NativeInterface.java:100)
at be.irisnet.nova.client.com.BootClass.main(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.sun.javaws.Launcher.executeApplication(Unknown Source)
at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
1.0.2 only contains bug fixes. I don't have any particular features to add.
I have no plans to release 1.0.2 because it does not contain any features, and
does not contain any critical bug fixes... Of course, if after a very long
time there is no particular addition to 1.0.2, then I might release it.
In other words, yes, as of now it should be stable, more stable than 1.0.2
because of potential bug fixes.
hope this helps,
-Christopher
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We've integrated v1.0.1 of DJNativeSwing in our project. On some client
machines we're having an "Failed to connect to spawned VM!" exception. It is
not really clear why this error is generated on certain machines and not on
others.
-Would it be possible to get more information about the real cause of this exception ?
-How can we generate detailed logging for the DJNativeSwing component ?
-Does DJNativeSwing depends on certain OS settings to be able to work correctly ?
_java.lang.IllegalStateException: Failed to connect to spawned VM!
at chrriis.dj.nativeswing.swtimpl.core.SWTNativeInterface$OutProcess.createOut
ProcessMessagingInterface(SWTNativeInterface.java:990)
at chrriis.dj.nativeswing.swtimpl.core.SWTNativeInterface$OutProcess.createOut
ProcessCommunicationChannel(SWTNativeInterface.java:735)
at chrriis.dj.nativeswing.swtimpl.core.SWTNativeInterface.open_(SWTNativeInter
face.java:320)
at
chrriis.dj.nativeswing.swtimpl.NativeInterface.open(NativeInterface.java:100)
at be.irisnet.nova.client.com.BootClass.main(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.sun.javaws.Launcher.executeApplication(Unknown Source)
at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
at com.sun.javaws.Launcher.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at chrriis.dj.nativeswing.swtimpl.core.SWTNativeInterface$OutProcess.createOut
ProcessMessagingInterface(SWTNativeInterface.java:972)_
Hi,
Use the 1.0.2 preview version. I improved this troubleshooting a while ago.
The is no particular logging interface. Lots of system properties can be
activated but they generally dump the information to the console.
For certain browser runtimes to work there may be tweaks to paths on certain
platforms, but generally the default case should just work.
Hope this helps,
-Christopher
-Is the 1.0.2 preview version "stable" enough to be used in a production environment ?
-When do you plan to release an official 1.0.2 version ?
1.0.2 only contains bug fixes. I don't have any particular features to add.
I have no plans to release 1.0.2 because it does not contain any features, and
does not contain any critical bug fixes... Of course, if after a very long
time there is no particular addition to 1.0.2, then I might release it.
In other words, yes, as of now it should be stable, more stable than 1.0.2
because of potential bug fixes.
hope this helps,
-Christopher