[Wrapper-user] What is the best way to handle JRE updates on end user computers

[Stephen S. <s.s...@ca...>]

(Re-submitted after subscribing to the mailing list)

 

What is the best way to handle JRE updates on end user computers once a
service is up and running using the wrapper?

 

When a new JRE update comes out, on running the installer, it notes that
"java.exe" is running and asks to stop this so that it can update java.  If
I tell it to do this, the wrapper log shows "JVM exited unexpectedly" and
that it then automatically restarts it.  The JRE update install then seems
to complete OK but has actually failed with browser plugins not added.
Restarting the computer does not fix this, and it is necessary to uninstall
the JRE and install it again to fix it.  Until this is done Java client
applets run on the same computer are broken.

 

If I manually stop the service while doing the JRE update then everything
goes fine, but if the software is installed on a customer's computer it
would be highly preferable for automatic Java updates to go through without
them having to worry about stopping a service.

 

We have considered including a separate version of JRE used only by our
service when our software is installed, so that the main JRE installation
used by browsers could be updated without the wrapper service interfering,
but our management considers this not acceptable because it would not get
updated with the latest JRE security fixes.  We also considered using the
wrapper.restart.delay setting to delay restarts by 15 minutes to give the
JRE updater time to finish, but our management also declared this
unacceptable.

 

What is the best way to deal with this?

 

(We're running version 3.2.3 by the way.)