Is there a way to kill just the HTTP task in a Domino Server?

HCL Domino Domino Forum
1

Hi all, Is there a way to kill just the HTTP task in a Domino Server without killing the whole server in W2K?

The HTTP task hangs and when you try to stop it by using “tell http quit” or “tell http stop”, it waits for sessions to finish:

This is the console log:

"09/10/2003 13:50:38 HTTP Server: Waiting for session to finish: Session State [Processing Request] Session ID [45] GET /RCSS/EntTra.nsf/CE/6B71A8559397F318C1256DB1003FB0B1?OpenDocument& HTTP/1.1

sh ta

09/10/2003 13:50:59 HTTP Server: Waiting for session to finish: Session State [Processing Request] Session ID [45] GET /RCSS/EntTra.nsf/CE/6B71A8559397F318C1256DB1003FB0B1?OpenDocument& HTTP/1.1

09/10/2003 13:51:23 HTTP Server: Waiting for session to finish: Session State [Processing Request] Session ID [45] GET /RCSS/EntTra.nsf/CE/6B71A8559397F318C1256DB1003FB0B1?OpenDocument& HTTP/1.1

09/10/2003 13:51:43 HTTP Server: Waiting for session to finish: Session State [Processing Request] Session ID [45] GET /RCSS/EntTra.nsf/CE/6B71A8559397F318C1256DB1003FB0B1?OpenDocument& HTTP/1.1

09/10/2003 13:52:03 HTTP Server: Waiting for session to finish: Session State [Processing Request] Session ID [45] GET /RCSS/EntTra.nsf/CE/6B71A8559397F318C1256DB1003FB0B1?OpenDocument& HTTP/1.1

09/10/2003 13:52:23 HTTP Server: Waiting for session to finish: Session State [Processing Request] Session ID [45] GET /RCSS/EntTra.nsf/CE/6B71A8559397F318C1256DB1003FB0B1?OpenDocument& HTTP/1.1

09/10/2003 13:52:43 HTTP Server: Waiting for session to finish: Session State [Processing Request] Session ID [45] GET /RCSS/EntTra.nsf/CE/6B71A8559397F318C1256DB1003FB0B1?OpenDocument& HTTP/1.1

Thanks in advance,

miguel Angel

2

Subject: No

Even if you do manage to kill http (or any Domino task for that matter) you have permanently screwed your Domino session. The task may be holding shared resources that will never be freed. If you try to quit Domino it will hang forever because the server doesn’t know that the task is gone and waits forever for it.

In fact a similar discussion came up earlier because somebody expected Domino to panic when a process get killed and it did not. See this thread . This will probably be incorporated into a future release so that killing any process will immediately Panic the server.

Unfortunately I do not see any immediate relief from your problem other than using “nsd -kill” to terminate the entire server, then restarting it.

3

Subject: Is there a way to kill just the HTTP task in a Domino Server?

Have you tried killing the nhttp task in the Win2k task manager?

That usually does it.

Also, I have seen this in the past and performing a “Drop All” at the console before issuing the exit/quit seemed to help.

4

Subject: RE: Is there a way to kill just the HTTP task in a Domino Server?

Alan, I’m unable to finish the nhttp.exe task from the task manager. I receive a “Access is denied” message.

On the other side, “Drop all” doesn’t make the threads to finish.

Thanks,

Miguel Angel

5

Subject: RE: Is there a way to kill just the HTTP task in a Domino Server?

Search IBM support on “waiting for thread”

There are a couple of entries that talk directly to the problem. They both end that Lotus Support could not reproduce the problem.

There are numerous other entries that talk about additional items contributing (ex. java thread active).

I have seen this problem since 4.6.x trough 5.0.8. I have not seen it in 5.0.10/.12. But it looks like its back in 6.x.x

Sorry I could not be of more help.

6

Subject: RE: Is there a way to kill just the HTTP task in a Domino Server?

if an NT process will not ‘die’ because you are not authorized/access denied, try the following;

start a cmd prompt and type AT 14:23 /INTERACTIVE TASKMGR

when the system time reaches 14:23 taskmgr will be started with SYSTEM credentials which means you can kill any process you like.

7

Subject: And you will still hose your server

See my response

8

Subject: RE: And you will still hose your server

yep, i read it, i also presumed the OP had read it as well (i posted a couple of days after you), if someone really wants to screw up their server who am i to stop them :slight_smile: