There are problems with the shutdown script. I'll try to fix it. For
now, just kill the process.
> -----Original Message-----
> From: Nentwig, Timo [mailto:timo.nentwig@xxxxxxxxx]
> Sent: Thursday, September 22, 2005 7:29 AM
> To: turbine-jcs-dev@xxxxxxxxxxxxxxxxxx
> Subject: JCS remote server can't be shutdown (?)
>
> Hi!
>
> This applies to JCS 1.2.6.5:
>
> While RemoteCacheServerFactory -stats 1102 /remote.cache.ccf
> works perfectly the same for -shutdown does not (-> connection
refused).
>
> Looking at RemoteCacheServerFactory.main() you'll find that the code
for
> -stats and -shutdown does quite the same but looks slightly different
> (-shutdown appears to be older).
>
> 1) You can't specify the RMI port, but in order to lookup the Registry
> Registry.REGISTRY_PORT==1099 is used anyway.
>
> 2) admin.shutdown() will use Registry.REGISTRY_PORT as well and for
> shutdown(host, port) we don't have the host, i.e. there's code missing
> to either take the host from CLI or from Properties. But this isn't
> done.
>
>
> So, I wonder how it is supposed to work at all?
>
> Applying the above mentioned changes the server is shut down but I get
> an UnmarshalException anyway:
>
> 22.09.2005 12:37:30
> org.apache.jcs.auxiliary.remote.server.RemoteCacheServerFactory main
> SCHWERWIEGEND: java.rmi.UnmarshalException: Error unmarshaling return
> header; nested exception is:
> java.net.SocketException: Connection reset
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jcs-dev-unsubscribe@xxxxxxxxxxxxxxxxxx
> For additional commands, e-mail: jcs-dev-help@xxxxxxxxxxxxxxxxxx
|
