jakarta-jcs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nentwig, Timo" <timo.nent...@jamba.net>
Subject JCS remote server can't be shutdown (?)
Date Thu, 22 Sep 2005 11:28:30 GMT

This applies to JCS

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

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@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org

View raw message