Association with java.exe or javaw.exe causes unexcpected troubles

[melf]

If *.jar -files are associated with java.exe or javaw.exe and a java program is started by double clicking some strange things happen. E.g Frostwire launches well but can't connect to internet. However using java -jar frostwire.jar makes it work. A cmd-file with the same expression works as well.

There are also effects on other programs. Vbox, ecomarket, pmmaps don't launch. Pdf-merge launch an error message. They work again after reboot. PM123 launch an error message,and no new files can be loaded. However last loaded file can be "played", it isn't played but saved as *.wav. Turns out that the DART-plugin has "popped out". It can be reinserted only after a reboot. Those effects do not happen if a java program is run by commandline or a cmd-file.

It should be said that the installed java is a wpi-pack from hobbes, but the content of openjdk is identical with build 22GA, except for an icon (java.ico). There are no additional entries in config.sys except for the SET JAVA_HOME=C:\openjdk6\ statement. The program object parameter is initially set to -jar %F , but the effect is the same for just -jar .

The behaviour has been confirmed by another person, see this thread in os2world.com forum ​http://www.os2world.com/forum/index.php/topic,4460.msg22284.html#msg22284 .

[Batchheizer]

Because I'm the creator of the WPI, I'm interested why this conflicts appear. I can confirm the problems after starting a JAVA-APP. via double-clicking on a JAR: PM123 makes troubles, PMMAP and ECOMARKET (and DVD-Toys) cannot be started. Maybe problems with the new FOC are related to this issue. Maybe it is related to the eco-runtime. Here is the line from the WPI for the WPS_object:

CREATEOBJECT="REPLACE WPProgram|OpenJDK6|<OPENJDK_FOLDER>|EXENAME=$(1)\bin\JAVA.EXE;ASSOCFILTER=*.JAR,*JAR;STARTUPDIR=;ICONFILE=$(1)\bin\JAVA.ico;SET BEGINLIBPATH=$(1)\bin;SET PATH=$(1)\bin^;%PATH%;PARAMETERS=-jar %**F;MINIMIZED=YES;NOAUTOCLOSE=NO;OBJECTID=<OPENJDK_JAVAEXE>;"

CONFIGSYS="SET JAVA_HOME=$(1)\ | UNIQUE"
CONFIGSYS="SET CLASSPATH= | REMOVELINE"
CONFIGSYS="SET SWING_HOME= | REMOVELINE"

What could be wrong?

[Silvan Scherrer]

as a first step, get rid of FOC eco-runtime and all those stuff and see if it's still there. f it's gone you know the problematic one.
as a second try use the rpm version and create a wps obj. and see if this behaves the same.

[melf]

Replying to diver:

as a first step, get rid of FOC eco-runtime and all those stuff and see if it's still there. f it's gone you know the problematic one.
as a second try use the rpm version and create a wps obj. and see if this behaves the same.

Getting rid of FOC doesn't change anything. However, deinstalling the wpi-packag, installing the zip-package from this site and then make my own java object, -jar parameter, (and associate it with jar-files)make things work. No problem with any other program. So, as the openjdk folder is identical with the original the problem has to be in the object created by wpi?

[Silvan Scherrer]

as this seems to be a wpi only problem i changed some ticket properties. i hope Oliver will take care on that.

[Batchheizer]

Replying to diver:

as this seems to be a wpi only problem i changed some ticket properties. i hope Oliver will take care on that.

I removed

SET BEGINLIBPATH=$(1)\bin;SET PATH=$(1)\bin^;%PATH%

from WPS-Object (via DragText). Now FOC and PM-MAps runs fine after closing a JAVA-App. JAVA-Apps also start fine without these settings. Can some people reproduce this? Are all problems gone after removing these settings (Environment) from the WPS-Objects?

[abwillis]

beginlibpath cannot be set from the environment tab... I don't think trying to should cause the issue you see but there is no reason to have it there (beginlibpath is not truly an environment variable in the typical sense as I understand the reason it doesn't do anything there).

[Silvan Scherrer]

either fixed or on one is interested anymore in that ticket. and as it doesn't belong to our distribution i close it.