Menu
▾
▴
#280 wrapped application not detected by JRE installer.
We have been using Java Service Wrapper for a long time to manage our server application and it has worked great. Now we have problems with JRE updates.though. Since the JRE started to patch its updates to the same location (...Java/jre6) we have problems when updating. The JRE installation detects our other applications (a client and a server manager) that run on the JRE and ask the user to save their work and then the installer kills the apps which is fine. The problem is that it does not detect our server that is run by Java Service Wrapper (maybe because the wrapper is the parent process?) and continues with the installation that then crashes leaving us with a broken JRE. The service run by Java Service Wrapper is still running after this until it is stopped but then it fails to start again because of a missing file in the broken JRE:
DEBUG | wrapper | 2010/05/25 18:33:03 | JVM started (PID=1840)
INFO | jvm 1 | 2010/05/25 18:33:03 | Error: could not open `C:\Program\Java\jre6\lib\i386\jvm.cfg'
DEBUG | wrapper | 2010/05/25 18:33:03 | JVM process exited with a code of 1, setting the wrapper exit code to 1.
I realise we run on an old version but since no one is around since the time we started using Java Service Wrapper I do not want to upgrade unless we are certain that it would resolve this issue.
Any ideas?
Thanks,
Tomas
Tomas,
I was looking into this today for quite a while and understood your problem.
However I couldn't find out how the JRE Updater is distinguishing the running instances of the JRE to be updated.
I will keep digging into this more and keep you up to date.
As work-around you might include a jre into your software, which the wrapper uses as JVM.
Best regards,
christian
Thanks for looking into this!
We have been including the JRE all along but since our last release was the first to include the "new" patching JRE that installs into the jre6-folder by default unfortunately noone really saw this problem until now when we are about to ship our next release. In our installer we stop the service before installing Java but then later updates run into problems if the service is runnng.
For now I changed so that we install the JRE with STATIC=1 which installs it in the old way which I prefer anyway so that we can control the environment we are running on and then this is no issue.
Still an interesting problem though :)