|
From: Hubert F. <hub...@ab...> - 2007-01-31 13:07:25
|
Leif, < Not currently Yes, I supposed so. Just a tought: Could one use the anchor files for that? The names of the anchor files would have to follow some rules, to be able to find them from a service name. On startup, wrapper could figure out the dependencies and the belonging anchor files. If one or more of them is deleted or changes date (restart), that would mean either a shutdown or a restart of a dependent service. Wrapper could inform the service about this issue an let the service decide to either shutdown too or request a restart. Or maybe just define a list of anchor files the wrapper should watch for changes? just my two cents. Regards Hubert >>> Leif Mortenson <le...@ta...> 30.01.2007 19:45 >>> Hubert, Not currently. This is something that I need to find a way to get implemented. From within Java, you can control the services if you know what they are. Look at the WrapperManager.getJVMId() method. If it returns a value > 1 then you know the JVM has been restarted since the Wrapper was launched. In that event, you can use the WrapperManger.sendServiceControlCode method to STOP and then START the dependent services. This will only work if you know what they are. Cheers, Leif Hubert Felber wrote: > Hello, > > If the wrapper has to restart a service, is there a way to inform the > dependent services about this? Services that depend on others might have > connections or resources which become invalid after restart or shutdown > of a "parent" service. > > hub > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |