HTTP Server: Waiting for session to finish - Description/Solution (In all probability a bug in domino 8 ?(http task))

HCL Domino Domino Forum
1

After the domino updates from 7 to 8 we have recurring errors to the http task. On misc servers with different mail-dbs.The http server stops responding.

Description.

There is no error message, no crash-info. The cpu usage increases to the http task.

When Console → “tell http restart” the task does not restart. Then a error message is shown:

HTTP Server: Waiting for session to finish: Session State [Processing Request] Session ID [3964] Thread ID [4164 (0x1044)] GET /path/database.nsf/formname?readform HTTP/1.1

Domino can not kill this state. We have to kill the hanging threads with a process explorer or to restart domino and windows.

In some cases a fixup on the related nsf releases the sessions without a restart.

We spent very much time in analyzing and found this:

When in a form a WebQueryOpen triggered agent opens a view/folder and this view/folder needs a rebuild of the index the browser waits and nothing happens. Now, when the user closes the browser window the thread is not destroyed and goes in close-wait state on the server (to see on OS Level). This means the “waiting for sessions” message when a “restart http” is done.

Right now the http task is instable/faulty and many other sessions/threads will go in close-wait status too. Later all resources are busy and the http server stops responding.

In this case we had mail-dbs which inboxes were working strange (in Notes the refresh-button appeared always and the inbox; the index was refreshed whenever it was opened). Deleting the inbox and Design refresh solved this problem.

When this folder is accessed from the browser directly (not via webQueryOpen triggered agent) the browser waits. A closed browser does not create a close_wait session. All is ok.

This is handled correctly from the domino server.

Workaround:

There is to do a view refresh before reading the view with such an WebQueryOpen triggered agent.

Solution:

With Version 7 we did not have this problem.

It is not addressed in version 8.0.2

In my mind this is a domino version 8 bug which is to fix (perhaps IBM / Lotus can give an answer?)

2

Subject: Re: HTTP Server: Waiting for session to finish - solution?

Has anyone determined a solution for this problem? My http task is locking up about once a week.

3

Subject: Re: HTTP Server: Waiting for session to finish - solution?

MT,

Perhaps try setting your web agent timeout to a positive value (Domino Administrator-> Configuration → Current Server Document → Server Configuration-> Internet Protocols-> Domino Web Engine → Web agent and web services timeout). This way if you get a runaway web agent, the thread will be cleaned up by the Domino Web Engine.

Regards,

Ryan

4

Subject: xPages - calling java from SSJS

I am calling java from SSJS, this is working fine on my 8.5.2 64bit server, when running the same code in the same database from my other 32bit server I get this error as well, I am doing a Post call and this completely halts the http task and I need to restart the server to get back up.

is it possible to debug this?

Thomas

http://www.notessidan.se

5

Subject: Same problem

I found that with tell http refresh i can restart the http task.I saw similar posts with a solution is found by authorizing multiple threads. Will try this soon.

6

Subject: Solutions?

I have the same problem.

I talked to Lotus support and they gave me several suggestions to possibly help with these problems (have not tried yet, so don’t know yet if this will actually solve problems):

In server config doc under Internet Protocols/HTTP/Timeouts section: disable persistent connections (he said having this enabled is mainly only beneficial for extremely slow connections, eg, modems)

Under internet protocols/Domino Web Engine/Web agents and web services section–enter a reasonable timeout under web agents and web services timeout–0 means no timeout.

7

Subject: HTTP Server: Waiting for session to finish - Has anyone found a solution?

We experienced exactly the same problems as the post originator during an upgrade this weekend. Strangely, this problem does not appear on all our servers.

Three servers have successfully been upgraded from 7.0.3 to 8.0.2 FP2 and do not have any issues with the HTTP-task when accessing web-based applications or email through a web browser.

Two of the servers can not handle HTTP tasks after upgrade and the HTTP-task simply becomes unresponsive and suddenly takes up to 100% CPU on the machines. We had to revert to saved snapshots of the previous configuration 7.0.3 and now those two servers work well.

Unfortunately I can’t find any resolutions to this issue, would be wonderful if somebody knew what to do?

8

Subject: HTTP Server: Waiting for session to…

Same issues in 8.5

9

Subject: HTTP Server: Waiting for session to finish

Then what do you do?

At this point we’re not able to upgrade due to these issues, we have a big user community only working with webmail and this is impossible as long as this problem persists.

I’ve done some extensive searching online but I can’t seem to find any workarounds.

We’re going to do another upgrade on the 31st and collect some logs to send to IBM in a (vain?) hope that they can help us.

But ideas are still welcome!

10

Subject: Not a solution - just a cause…

I’ve managed to cause this error message using a bad javascript “for loop” on an XPage.

Only way to stop it was to End the nHTTP Process in Task Manager, then do a “restart server”.

Now I just have to figure out why my for loop is looping!

11

Subject: Yep, same on 8.5 right to 8.5.1FP1

We are getting the same problems. Only started after going from 8.1 to 8.5

I have to ask the question, what kind of stupid server refuses to restart a task as its waiting on a session thread.

The whole point of restarting the http task it to RESTART IT, not sit there using 50% cpu and twiddling your thumbs.

This has been peeing me off for weeks now, and I am still no farther forwards

12

Subject: The same problem

CPU of Server may be up to 80%. Day and day must be restart server one time may be More…I have been config time out of Web service and agent, and disable HTTP persistent connections. But this problem is continuing

Log

HTTP server: waiting for session to finish: Session stat [processing request] …

solution?

Help us

13

Subject: Same issue - 8.5.1 FP2 seemed to work

Same issue after v7.02 upgrade to v8.5.1A reboot and install of 8.5.1 FP2 seemed to correct this.

14

Subject: I encountered the same problem

I encountered the same problem exactly.OS: windows 2003 server

Domino Release: 8.5.1 FP3

How can I get the clue to troubleshooting?

15

Subject: 10/14/2008 04:29:53 PM HTTP Server: Waiting for session to finish: Session State [Processing Request] Session ID [147] Thread ID [2808388496 (0xa7649b90)] GET /tvsite.nsf/Fronta?OpenForm&Fr=TV HTTP/1.1

In my case we are using

Domino 8.0.2 on Linux.

We got the following messages:

10/14/2008 04:29:53 PM HTTP Server: Waiting for session to finish: Session State [Processing Request] Session ID [147] Thread ID [2808388496 (0xa7649b90)] GET /tvsite.nsf/Fronta?OpenForm&Fr=TV HTTP/1.1

10/14/2008 04:29:53 PM HTTP Server: Waiting for session to finish: Session State [Processing Request] Session ID [149] Thread ID [2807331728 (0xa7547b90)] GET /tvsite.nsf/Front?OpenForm HTTP/1.1

10/14/2008 04:29:53 PM HTTP Server: Waiting for session to finish: Session State [Processing Request] Session ID [159] Thread ID [2802047888 (0xa703db90)] GET /tvsite.nsf/vAdminOrdersByUNIDMasked/716D94B5884EC47F862574BF00566ED1?EditDocument HTTP/1.1

The Domino server is working OK, but the HTTP server hangs when we try to access specific databases while other DBs work fine.

The error was because of a call, to the NotesLog class in the “Sub Delete” of an object, to log its status. We moved the code to the “Sub Terminate” of the agent and the error stopped.

16

Subject: HTTP Server: Waiting for session to finish

We finally had a breakthrough in this and have now managed to upgrade our servers successfully with no HTTP task locking up and eating up all CPU.

Although I’m sure this solution will not help everyone, for us the solution was uninstalling Sametime Limited Use and then installing 8.0.2 + FP2

It worked like a charm and we’re having no problems whatsoever since.

17

Subject: Solution

Just type ‘Quit’ on the console. That will immediately kill HTTP threads.

18

Subject: Any Luck? Regarding this issue

I am facing same issue on Linux OS with Domino Server 8.5.3 FP 6. I am using SSJS libararies to process different business rules. Moreover I have diagnosed and don’t see any issue with the code because apparently evething is running perfectly fine in most of the cases but in some case this happen. Should I keep refresh index of my lookup views as an automatic and refresh view before look or getting document or collection.

Please guide me and help me. Your prompt response in this regard will be highly appreciated.

Thanks,

Qaiser

19

Subject: RE: HTTP Server: Waiting for session to finish - Description/Solution (In all probability a bug in domino 8 ?(http task))

I think we may be seeing this issue as well.

But for us it is when calling of agents via a URL (like …/database/Agent?openagent). This agent access views and folders in mailfiles. We are getting the same session errors when trying to restart HTTP. We are also getting notifications that agents, that should take only a few seconds at most, are getting stuck for thousands of seconds. Like you we didn’t have this problem until the server was upgraded to 8.0.x from 7.0.x.

I will be trying your suggested workaround.

Has anyone opened a Support call on this? If so do you have a SPR number, or could you get one from your support person? It might be helpful for getting this fixed, if we referenced the that same SPR when we open a ticket.

20

Subject: The same issue

We have the same…

http://www-10.lotus.com/ldd/nd8forum.nsf/5f27803bba85d8e285256bf10054620d/2451d8677b6f736c852574a30025eec2

and still - no solution