Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

How can I "gracefully" shutdown a node on WebSphere Network Deployment 6.1? My worry is do not end active sessions when a shutdown is necessary. My intention is to prevent a node of accepting new sessions and then, when there are no more active sessions, I can safely shutdown that node. I believe that this can be done preventing the node for accepting new sessions (but keeping the existing sessions until their end) AND and preventing the IBM HTTP Server to send requests to that node. There is some way to do this? There is other way more appropriate? Meanwhile I'm considering to enable session sharing among the nodes, but that is not achievable right now.

share|improve this question
up vote 2 down vote accepted

Well, you don't really shut down a "node"; you shut down servers within a node. You may be confusing with a "Node Agent"; but a Node Agent doesn't process requests - it simply keeps the "link" between the Deployment Manager and the server instances on the actual node (you can shut down the Node Agent and server instances would still continue handling requests).

So, the answer to your question is simply - stop all servers in that node. A "regular" stop (i.e. not an immediate stop) does what you described as desirable - it first stops receiving new requests, then waiting until all in-flight requests finish - then shutting down the server.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.