Re: How to tell if ClassServer is running

Start a second instance of the ClassServer with the "-stop" argument on 
the same host as the first. It will send the initial ClassServer the 
shutdown message and terminate. The initial ClassServer should then 
terminate if it was run with "-stoppable".

Fred

Rawlings, Bill A wrote:
> It's the ClassServer that comes with the River release and it is started
> with the start.jar utility.  I figured out how to see if one is up, but
> the shutdown is still problematic.  It is apparently not
> Administratable.  The documentation speaks vaguely of a -stop parameter,
> but the source code documentation says...
> 
> * If the <code>-stoppable</code> option is given, the HTTP server can be
> * shut down with a custom HTTP <code>SHUTDOWN</code> request originating
> * from the local host. The command line options for stopping an existing
> * HTTP server are:
> * <pre>
> * [-port <var>port</var>] -stop
> * </pre>
> 
> So, I'm not sure exactly how you shut it down if it was started with the
> start.jar utility.  What is the correct parameter (-stop or -stoppable)
> and what is a "custom HTTP SHUTDOWN request?
> 
> BAR
> 
> -----Original Message-----
> From: Gregg Wonderly [mailto:[email protected]] 
> Sent: Tuesday, October 21, 2008 9:33 AM
> To: Rawlings, Bill A
> Cc: [email protected]
> Subject: Re: How to tell if ClassServer is running
> 
> Rawlings, Bill A wrote:
>> Hi guys:
>>
>> I need to be able to figure out if a ClassServer is up and running.
>> (This is for a startup/shutdown application).   I see in the
>> documentation the class 
>> com.sun.jini.start.HTTPDStatus, which looks like it "might" do the
>> trick, however the documentation on this class is fairly useless. 
>>
>> What is the "right" way to tell if a ClassServer is up and running,
> 
> Since it's an HTTP server, I'd guess anything that you'd devise that
> uses the 
> protocol and requests a file would work.  You might imagine a local
> process that 
> has access to the file store which the server serves from, making
> requests for 
> files and checking what it receives against what it sees in the
> directory perhaps.
> 
>> and
>> what is the "right" way to shut one down?
> 
> Depends on how you start it.  If it's Administrable, then you could wire
> that up 
> to work, or use what is already in place if DestroyAdmin is implemented
> by the 
> object Administrable.getAdmin() returns.
> 
> Gregg Wonderly
> 
> --------------------------------------------------------------------------
> Getting Started:     http://www.jini.org/wiki/Category:Getting_Started
> Community Web Site:  http://jini.org
> jini-users Archive:  http://archives.java.sun.com/archives/jini-users.html
> Unsubscribing:       email "signoff JINI-USERS"  to [email protected]

--------------------------------------------------------------------------
Getting Started:     http://www.jini.org/wiki/Category:Getting_Started
Community Web Site:  http://jini.org
jini-users Archive:  http://archives.java.sun.com/archives/jini-users.html
Unsubscribing:       email "signoff JINI-USERS"  to [email protected]