Don't complain if we didn't init our PeerManager; we don't do that if
we're not running in a peered environment. Technically it might be better to add the PeerManager to the lifecycle in init, but I don't want to screw with the shutdown order, and this is the lowest-impact solution. git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@6021 542714f4-19e9-0310-aa3c-eee0fc999fb1
This commit is contained in:
@@ -767,9 +767,8 @@ public abstract class PeerManager
|
||||
// from interface Lifecycle.ShutdownComponent
|
||||
public void shutdown ()
|
||||
{
|
||||
if (_nodeName == null) { // sanity check
|
||||
throw new IllegalStateException(
|
||||
"Shutting down PeerManager that was never initialized.");
|
||||
if (_nodeName == null) { // never initialized
|
||||
return;
|
||||
}
|
||||
|
||||
// clear out our invocation service
|
||||
|
||||
Reference in New Issue
Block a user