Application session freeze [with javascript errors]
Added by Rob Van Dyck about 12 years ago
Hi,
I'm having a case where the session for one user freezes. It is reproduceable, but not in a small test-case yet.
I'm using 3.2.1.
The logs says:
[2012-May-08 10:38:09.988391] 26749 [/ Rheqv6XPWV91JNrO] [debug] "wthttp/async: 35: startAsyncWriteResponse"
[2012-May-08 10:38:09.988766] 26749 - [debug] "wthttp/async: 35: handleWriteResponse(): Success"
[2012-May-08 10:38:09.988975] 26749 - [debug] "wthttp/async: 35: handleWriteResponse() 1 0"
[2012-May-08 10:38:09.989034] 26749 - [debug] "wthttp: (sending: 1, reponseSent_: 0) nextContentBuffer: 7139"
[2012-May-08 10:38:09.989386] 26749 - [debug] "wthttp/async: 35: startAsyncWriteResponse"
[2012-May-08 10:38:09.989550] 26749 - [debug] "wthttp/async: 35: handleWriteResponse(): Success"
[2012-May-08 10:38:09.989601] 26749 - [debug] "wthttp/async: 35: handleWriteResponse() 1 0"
[2012-May-08 10:38:09.989641] 26749 - [debug] "wthttp: (sending: 1, reponseSent_: 1) nextContentBuffer: 0"
[2012-May-08 10:38:09.989820] 26749 - [debug] "wthttp/async: 35: startAsyncWriteResponse"
[2012-May-08 10:38:09.989937] 26749 - [debug] "wthttp/async: 35: handleWriteResponse(): Success"
[2012-May-08 10:38:09.989985] 26749 - [debug] "wthttp/async: 35: handleWriteResponse() 0 0"
[2012-May-08 10:38:09.990107] 26749 - [info] "WebRequest: took 3.311ms"
[2012-May-08 10:38:09.990222] 26749 - [debug] "wthttp/async: 35: startAsyncReadRequest"
127.0.0.1 - - [2012-May-08 10:38:09.990025] "POST /?wtd=Rheqv6XPWV91JNrO HTTP/1.1" 200 1902
[10:38:14.834607] +++ [TRACE]:Send keep alive signal
[2012-May-08 10:38:19.990434] 26749 - [debug] "wthttp/async: 35: handleReadRequest(): End of file"
[2012-May-08 10:38:19.990537] 26749 - [debug] "wthttp/async: 35: error: End of file"
[2012-May-08 10:38:19.990575] 26749 - [debug] "wthttp/async: 35: close()"
[2012-May-08 10:38:19.990619] 26749 - [debug] "wthttp/async: removed connection (#0)"
[2012-May-08 10:38:19.990659] 26749 - [debug] "wthttp/async: 35: stop()"
[2012-May-08 10:38:19.990701] 26749 - [debug] "wthttp/async: 35: closing socket"
[2012-May-08 10:38:19.990755] 26749 - [debug] "wthttp/async: ~Connection"
Firefox gives me:
Error: edit.wtValidate is undefined
Source File: http://localhost:8080/?wtd=FW7t8hcOup1yEj8J&sid=577377830&htmlHistory=true&deployPath=%2F&request=script&rand=692285797
Line: 736
That points to:
this.validate = function(edit) {
var v;
if (edit.options)
v = edit.options.item(edit.selectedIndex).text;
else
v = edit.value;
v = edit.wtValidate.validate(v);
if (v.valid) {
edit.removeAttribute('title');
$(edit).removeClass('Wt-invalid');
} else {
edit.setAttribute('title', v.message);
$(edit).addClass('Wt-invalid');
}
};
What is the best way to proceed, other then trying to make a small test case so I can submit it as a bug. It is probably something that is triggered in my code, but it is taking me a lot of effort in trying to figure it out. So I'm wandering whether there are ideas on what else to check.
Currently I can use a radiobutton instead of a spinbox in one location, then the issue does not occur.
Or I can disable the sorting of a menu when I add a new item (where I remove and re-add all items in a certain order), then the issue does not occur either.
When I use a spinbox AND I sort the menu I get the freeze.
Thanx for any hints,
Rob.