Mar 13, 2015, 7:22 AM
11 Posts

How to kill HTTP-Task?

  • Category: Administration
  • Platform: All Platforms
  • Release: 9.0.1
  • Role: Administrator
  • Tags: http
  • Replies: 8


sometimes our HTTP-Task gets very slow and the cpu-utilization in the domino admin has no value anymore. If this happens, the only way to solve the problem is to restart the domino server service.

I have readed a lot on the ibm pages and i found the reason for this. This happens, if a LS-Agent is triggered by the http task and gets an error - maybe a lookup to a drefect view. However... this is very difficult to find and sometimes the search for the reason causes further errors, that shoot the http task in the same way. But this is not my problem, because this is very inftrequently and seldom.

Now, if i restart the service (windows, Domino-console "restart server"), the http task blocks it. After 5 minutes a timeout terminate the http task and the server restart begins. My question is, how can i accelerate it? Is there a way to kill the http-task, that the restart can go on quickly?



Mar 13, 2015, 8:05 AM
191 Posts
It's possible to use nsd -kill to terminate the Domino tasks (including HTTP), but it's not recommended in the case where they will eventually shut down gracefully. Have you tried simply running "restart task http" while Domino is running instead of restarting the entire Domino server?
Mar 13, 2015, 8:32 AM
11 Posts

Yes, i have tryed it. In this case the termination of the task does not work. The domino console alerts something like "HTTP - waiting for all tasks to quit..." for every minute and the http service terminates. But it don't restart, only the alerts are there. Some day, I have tryed it for an hour - and nothing changes.

The next time, i try to kill it like you described. Thanks!

Mar 13, 2015, 9:37 AM
82 Posts
OS Restart

Sounds like you really have a bad memory leak on your application.

Are you able to schedule a server restart on nightly basis? I am talking about the OS restart.


Mar 13, 2015, 1:35 PM
122 Posts
Re: How to kill HTTP-Task?
Hello Bernd!

I am strongly encourage you to open a PMR with IBM Support to analyze the root cause of the hang of HTTP Task.

Maybe an issue with version/configuration,etc.

Best Regards!

Rodrigo San Vicente
Mar 13, 2015, 6:18 PM
145 Posts
Take several manual nsds and send that data to support before the nsd -kill (eom)
Mar 14, 2015, 9:17 AM
212 Posts
stop HTTP

have you tried to use the cmmand "Tell HTTP QUIT"?

Mar 14, 2015, 9:17 AM
212 Posts
stop HTTP

have you tried to use the cmmand "Tell HTTP QUIT"?

Mar 20, 2015, 8:54 AM
11 Posts
Maybe solved...?

Hello and sorry for tis late response,

yes, i have tried out "Tell HTTP quit". The result is, that every minute the alert "waiting for all tasks to quit" came on the console. The http service terminates at first, but the task runs and sends these alerts out. And this state does not stop. "Load HTTP" does not work in this moment because of the not really terminated HTTP-Task. The only way to terminate this situation is "restart server" - and also in this case i have to wait for the timeout in 5 minutes.

Now i have tested and tryed out a lot and in this moment the HTTP runs since 4 days without any error. I am very sure, that it was a defect (and big) fulltext index. Search queries to this index are sent in our system from a web triggered agent. Normally this index has a size about 1.2GB. As i looked at it, the size was 1.5GB. In recent years i have often found errors in this index. As we know, indizes with big size are very fragile. This is the reason, why i scheduled a updall -X on it every night. But this scheduling - it seems so - does not repair this. The only way is to delete it manually and set it new... :-(

Hope that it works now....

Thanks, Bernd