You could set an nsv that shows the thread state, and then examine the nsv
from another request. Kind of building your own ns_telemetry.
On Thu, 10 Jan 2002, David Walker wrote:
Is there a way to determine what the thread is doing? I'm trying to
troubleshoot some long running scripts here.
Bugs item #502452, was opened at 2002-01-11 11:31
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=103152aid=502452group_id=3152
Category: Other: Documentation
Group: aolserver4_0
Status: Open
Resolution: None
Priority: 5
Submitted By: Vinod Kurup (vkurup)
Assigned
Saw this today in my access log:
XX.XX.XX.XX - - [11/Jan/2002:18:38:07 -0800] 400 534
It's a Bad Request error, but the logging is goofed up - no space after the URL.
This error was caused by telneting into AS 3.4 and not sending any data.
Jim
