|
From: Leif M. <lei...@ta...> - 2010-09-21 17:02:42
|
Dave, Currently, the Wrapper itself does not publish itself as a JMX bean. You are talking about delaying the launch of a JVM so any JMX access there would not be available as the JVM would be down. In addition to the fixed delay, we added a new "Paused" state to the JVM starting in version 3.5.0. You will need to first enable pausing: http://wrapper.tanukisoftware.com/doc/english/prop-pausable.html You can use the Wrapper's command file to send PAUSE or RESUME commands to the Wrapper as it is running: http://wrapper.tanukisoftware.com/doc/english/prop-commandfile.html You can use the on exit properties to tell the Wrapper to pause when a JVM exits http://wrapper.tanukisoftware.com/doc/english/prop-on-exit-n.html There is not currently a way to tell the Wrapper to start paused. Please let me know how this works for you. Cheers, Leif On Tue, Sep 21, 2010 at 1:43 AM, Dave Muirhead <mui...@ya...> wrote: > The wrapper.restart.delay "...controls the number of seconds to pause > between a JVM exiting for any reason, and a new JVM being launched." > But I wonder, is there any way to use criteria other than time to decide > when to relaunch? For example, is there a way to configure JSW to monitor > the value of a JMX MBean attribute and wait to restart the JVM until that > MBean attribute takes on a specific value? > > Thanks, > > Dave |