...@rmadilo.com
Subject: Re: [AOLSERVER] ns_adp_parse issue
To: AOLSERVER@LISTSERV.AOL.COM
Did I miss something?
Your script below does not contain a redirect and does not contain
ns_adp_abort. Why do you think this script tells you anything about
your problem?
But one thing seems
Francesco Petrarch wrote:
Ok, I got this, this time I really do, and it should be easily
replicated by anyone.
I have this filter:
ns_register_filter preauth GET /*.html decode_url
ns_register_filter preauth POST /*.html decode_url
ns_register_filter preauth HEAD /*.html decode_url
proc
the way up the callstack?
Is there a way to expire a thread before it's max_connections are met?
Does anyone have any other suggestions?
_Peter
Date: Tue, 7 Jul 2009 09:37:48 -0700
From: t...@rmadilo.com
Subject: Re: [AOLSERVER] ns_adp_parse issue
To: AOLSERVER@LISTSERV.AOL.COM
Francesco
: [AOLSERVER] ns_adp_parse issue
To: AOLSERVER@LISTSERV.AOL.COM
Francesco Petrarch wrote:
Ok, I got this, this time I really do, and it should be easily
replicated by anyone.
I have this filter:
ns_register_filter preauth GET /*.html decode_url
ns_register_filter preauth POST /*.html
Jeff Rogers wrote:
proc decode_url { why } {
set page [ns_adp_parse -file /www/website/template.adp]
ns_return 200 text/html $page
ns_adp_exception state
ns_log notice adp exception state is $state
catch {ns_adp_return}
return filter_return
}
Whoops, this won't
Jeff,
Thanks for that bit of help. As far as I can tell everything seems to
work correctly. I setup a slightly different test to demonstrate the
behavior.
Register filters in the private library:
proc ::test_adp_abort {arg why} {
switch -exact -- $arg {
file {
there is a ns_adp_unabort
_Peter
--
Date: Sun, 5 Jul 2009 18:50:53 -0700
From: t...@rmadilo.com
Subject: Re: [AOLSERVER] ns_adp_parse issue
To: AOLSERVER@LISTSERV.AOL.COM
On Sun, Jul 5, 2009 at 6:13 PM, Francesco Petrarch f_petra...@hotmail.com
wrote:
It's
imagine is now quite bloated and complex in
some areas, so instead of posting 1000 lines of code which may contain an
issue, I'll wait till I cannarrow it down a bit.
_Peter
Date: Mon, 6 Jul 2009 10:42:28 -0700
From: t...@rmadilo.com
Subject: Re: [AOLSERVER] ns_adp_parse issue
To: AOLSERVER
2009 10:42:28 -0700
From: t...@rmadilo.com
Subject: Re: [AOLSERVER] ns_adp_parse issue
To: AOLSERVER@LISTSERV.AOL.COM
Did I miss something?
Your script below does not contain a
redirect and does not contain ns_adp_abort. Why do you think this
script tells you anything about your problem?
But one
, 10 Jun 2009 00:08:36 +0200
From: neum...@wu.ac.at
Subject: Re: [AOLSERVER] ns_adp_parse issue
To: AOLSERVER@LISTSERV.AOL.COM
Francesco Petrarch schrieb:
Thanks for the suggestions, however they have not provided any
positive results.
ns_param StackSize 2048000 - only succeeding
On Sun, Jul 5, 2009 at 6:13 PM, Francesco Petrarch
f_petra...@hotmail.comwrote:
It's been awhile since I have looked into this and I think I have tracked
it down. In short, I now believe that ns_adp_abort aborts all current
threads/adps, not just the one currently executing the ns_adp_abort
not seem to duplicate the problem with just those functions. Also
I do not use ns_perms, I simply set a cookie once someone is logged in.
I don't suppose there is a ns_adp_unabort
_Peter
Date: Sun, 5 Jul 2009 18:50:53 -0700
From: t...@rmadilo.com
Subject: Re: [AOLSERVER] ns_adp_parse issue
Francesco Petrarch schrieb:
Thanks for the suggestions, however they have not provided any
positive results.
ns_param StackSize 2048000 - only succeeding in causing aolserver to
crash with could not allocate memory' errors after a day of running
i would not give up fast on that. What ist
for the help so far,
_Peter
Date: Fri, 29 May 2009 09:06:11 -0700
From: t...@rmadilo.com
Subject: Re: [AOLSERVER] ns_adp_parse issue
To: AOLSERVER@LISTSERV.AOL.COM
Maybe there is an error which is silently caught in ns_adp_parse.
Try this before sourcing your adp:
ns_adp_ctl stricterror
...@rmadilo.com
Subject: Re: [AOLSERVER] ns_adp_parse issue
To: AOLSERVER@LISTSERV.AOL.COM
Maybe there is an error which is silently caught in ns_adp_parse.
Try this before sourcing your adp:
ns_adp_ctl stricterror 1
tom jackson
On Fri, 2009-05-29 at 14:48 +, Francesco
On 6/5/09 4:56 PM, Francesco Petrarch wrote:
What puzzels me is that, as I mentioned, these 0 sized ns_adp_parse
calls seem to happen at random, when the page it happens on is reloaded
things work fine, so all the input data is the same.
Do you call ns_adp_trunc *anywhere* in your code, ever?
Nope, never used that function.
Date: Fri, 5 Jun 2009 20:10:34 -0400
From: do...@panoptic.com
Subject: Re: [AOLSERVER] ns_adp_parse issue
To: AOLSERVER@LISTSERV.AOL.COM
On 6/5/09 4:56 PM, Francesco Petrarch wrote:
What puzzels me is that, as I mentioned, these 0 sized ns_adp_parse
:01:23 -0700
From: t...@rmadilo.com
Subject: Re: [AOLSERVER] ns_adp_parse issue
To: AOLSERVER@LISTSERV.AOL.COM
I would try testing on a page from a local server so you can verify that
the server is returning what you expect.
Also, log the actual content when it is not what you expect. you
have surely been noticed by others.
_Peter
Date: Fri, 5 Jun 2009 17:01:23 -0700
From: t...@rmadilo.com
Subject: Re: [AOLSERVER] ns_adp_parse issue
To: AOLSERVER@LISTSERV.AOL.COM
I would try testing on a page from a local server so you can verify that
the server is returning what
I appear to be having a problem with ns_adp_parse and ns_adp_eval. I currently
run the latest code 4.5.1, upgraded from 3.13 with Jerry Asher's patches for
unix sockets for multiple hosts. Everything worked fine on 3.13 but now I have
intermittent issues with 4.5.1 (I had acutally upgraded
Maybe there is an error which is silently caught in ns_adp_parse.
Try this before sourcing your adp:
ns_adp_ctl stricterror 1
tom jackson
On Fri, 2009-05-29 at 14:48 +, Francesco Petrarch wrote:
I appear to be having a problem with ns_adp_parse and ns_adp_eval. I
currently run the
On 5/29/09 10:48 AM, Francesco Petrarch wrote:
However, seemly at random times (for a random connection), [ns_adp_parse
-file /www/website/template.adp] will return an empty string.
Are you scouring your server log for any uncaught Tcl errors? Without
knowing anything about your application
22 matches
Mail list logo
