On 26 April 2011 14:25, Danushka Menikkumbura <
[email protected]> wrote:
> > Presumably that's due to this code in ServerConfiguration.java:
> >
> >
> > try
> > {
> > Signal sig = new sun.misc.Signal("HUP");
> > sun.misc.Signal.handle(sig, this);
> > }
> > catch (Exception e)
> > {
> > _logger.error("Signal HUP not supported for OS: " +
> > System.getProperty("os.name"));
> > // We're on something that doesn't handle SIGHUP, how sad,
> > Windows.
> > }
> >
>
> Correct.
>
>
> > This code really shouldn't rely on the presence of the sun.misc classes,
> > let
> > alone on the presence of the HUP signal... i.e. the whole thing should be
> > done with Class.forName , and the "error" should at worst be a warning,
> > probably info.
>
>
> So that mean we can safely make it a warning?.
Yes - in fact I would probably make it INFO - really all it's saying is
"functionality not available on this platform is not available on this
platform".
> But still how do we get the
> expected behaviour on Windows amidst there is no SIGHUP on it?.
>
>
>
I think you can also reload the security configuration using the JMX
management interface. I think the JMX method should be considered the
"primary" way of doing this, and SIGHUP an alternate way on platforms/JVMs
which support it.
> > The existence of this dependency on sun.misc.Signal etc. is
> > also the cause of a warning in the build
> >
>
> Exactly. Also it makes the code Sun-JDK-specific.
>
>
Quite.
-- Rob
> Thanks,
> Danushka
>
