Re: [AOLSERVER] ns_mutex is likely causing our AOL web server to hung
In a message dated 1/27/2003 11:21:51 AM Eastern Standard Time, [EMAIL PROTECTED] writes:
proc_doc Y {} {
ns_share counter_A
ns_share counter_B
ns_share counter_mutex
ns_mutex lock $counter_mutex
foreach i_index [array names counter_A] {
set temp_counter_A($i_index) $conter_A($i_index)
set temp_counter_B($i_index) $conter_B($i_index)
unset $conter_A($i_index)
unset $conter_B($i_index)
}
Is the above the actual snippet from the code? If so, my guess is the typos ($conter_A, $conter_B instead of $counter_A $counter_B) are throwing errors and the mutex is not getting freed, causing deadlocking in your app. Removing the ns_mutex lines from the code wouldn't fix the errors, but the deadlocks would not occur. Are there any errors in your server log during the times the proc_doc Y runs?
~Rich
___
R i c h F r e d e r i c k s
Software Engineer
AOL Web Services Publishing
p: 703.265.0364
e: [EMAIL PROTECTED]
Re: [AOLSERVER] Error Pages
In a message dated 12/31/2002 7:01:19 AM Eastern Standard Time, [EMAIL PROTECTED] writes: 1) How do I use the ADP 'errorpage' - I can define it ok, but I've no idea what would typically be put in the ADP page specified. Ideally (during development) I'd like to be able to see the ADP error trace in the browser rather than have to go hunting in the server log - how might I do this? Does anyone have any example code they use in an ADP error page? Well, here's one easy way to do it: ### begin errorpage.adp % global errorInfo ns_puts \ " bOops, we have an error:/bbr pre[ns_quotehtml $errorInfo]/pre" % ### end errorpage.adp This will dump the tcl error trace to the page so you don't have to be looking at the server log to catch the error(s). I've been told that you can't always count on the "errorInfo" global tcl var, but I've personally never had any problems with it -- maybe someone else can speak to that. ~Rich ___ R i c h F r e d e r i c k s Software Engineer AOL Web Services Publishing e: [EMAIL PROTECTED]
