RE: [enhydra] two questions about enhydra multiserver wrapper

["Michael Warne" <mwarne@xxxxxxxxxxxxxxxxxx>]

Hi Petr,

Regarding Log4j..  Another project Barracuda,  uses a thread that
dynamically watches the Log4j config file for changes, and reloads the
configuration. 

Apparently there is a Log4J DomConfigurator class that can reconfigure
Log4j dynamically.  I haven't got around to researching it yet, but I
was planning to create an Admin Presentation Object for my apps that
would allow me to click a button that would reload the config, and
reconfigure Log4j.

The Barracuda code, has a Log4j watcher thread I believe that uses
DomConfigurator to do the same.

Mike.

-----Original Message-----
From: Petr Stehlik [mailto:pstehlik@xxxxxxxxxx] 
Sent: Thursday, May 27, 2004 12:56 AM
To: enhydra@xxxxxxxxxxx
Subject: [enhydra] two questions about enhydra multiserver wrapper


Hi,

first, my application sometime hangs and I have to restart the whole
multiserver. But /etc/init.d/multiserverStart stop (pretty weird command
if you read it, I'd suggest to use plain /etc/init.d/multiserver) does
not kill all java threads. Recently I had 97 java threads and the when I
stop the multiserver there remained 85 java threads. I would be happy if
the "multiserverStart stop" killed ALL java processes and threads it
invoked.

Second: if the multiserver is running and I decide to change the
log4j.xml (change the level of details from INFO to WARNING, for
example), how to let the application know that the configuration of
log4j has changed? I don't want to restart whole multiserver.

Thanks

Petr