Cleanup_register

2004-12-08 Thread Denis Banovic
Hi everybody! I have a small problem with the APR::Pool::cleanup_register; I get this error_message: ModPerl::Registry: Usage: APR::Pool::cleanup_register(p, cv, arg=Nullsv) at In script a.pl it works fine, in other one I get this error message. Here is the piece of code: use vars q

Re: [mp2] Ported 3rd-party Modules

2004-12-08 Thread Geoffrey Young
John D Groenveld wrote: > http://perl.apache.org/products/apache-modules.html#Porting_CPAN_modules_to_mod_perl_2_0_Status> > I've updated Apache::AuthenURL and Apache::DBILogin for mod_perl2. just a few notes: return MP2 ? Apache::OK : Apache::Constants::OK; if you don't use the -compile o

[mp2] Ported 3rd-party Modules

2004-12-08 Thread John D Groenveld
http://perl.apache.org/products/apache-modules.html#Porting_CPAN_modules_to_mod_perl_2_0_Status> I've updated Apache::AuthenURL and Apache::DBILogin for mod_perl2. Many apologies for not getting around to it sooner, particularly since a few of you have sent me patches and I also know it doesn't h

Re: Hanging Apache && Oracle Sessions with Apache::DBI, Apache::SessionManager, Oracle 9i,

2004-12-08 Thread Perrin Harkins
Tyler Rorabaugh wrote: I have noticed within the Apache::Session::Store::Oracle module that it uses a SELECT a_session FROM sessions WHERE id = ? FOR UPDATE If a user clicks the stop button in their browser during a process (IE during a session update or setting the session) and then clicks anot

Hanging Apache && Oracle Sessions with Apache::DBI, Apache::SessionManager, Oracle 9i,

2004-12-08 Thread Tyler Rorabaugh
  Dear mod_perl list,   Normally I would not bother the mod_perl list with questions but I have a problem with Apache::DBI, Apache::SessionManager and Apache::Sessions regarding hanging oracle sessions.   I have noticed within the Apache::Session::Store::Oracle module that it uses a SE

Re: Q about ProxyRemoteAddr

2004-12-08 Thread Stas Bekman
[EMAIL PROTECTED] wrote: Hi! I am having difficulty setting cookies once we changed our production modperl system. We changed from a single machine front-end/backend setup two a two machine setup Both use apache 2.x for the front server on ports 80 and 443, and modperl 1.3.x server running on ports

Re: pnotes

2004-12-08 Thread Arshavir Grigorian
Perrin Harkins wrote: Arshavir Grigorian wrote: I have module called Application which handles all the requests to the site (except for images, etc) and then dispatches the request to a different module based on the $r->path_info(). Apache::Dispatch could do this for you if you like. You could

Re: Fix perl/ithreads random failures

2004-12-08 Thread Stas Bekman
Gisle Aas wrote: I had to do tests with an older version of mod_perl_1.99 that still had the perl/ithreads* tests. I see that these tests was removed from the distribution in [1], but I think that if you apply the attached patch you can start distribution these tests again. [1] http://cvs.apache.

Re: Fix perl/ithreads random failures

2004-12-08 Thread Gisle Aas
Steve Hay <[EMAIL PROTECTED]> writes: > What was the problem that you had on HP/UX? Was it crashing or just > failing (as in "not ok")? It was not crashing, just ending up the the wrong value. The TEST_VERBOSE=1 output was this. perl/ithreads.1..4 # Running under perl version 5.008006 for

Re: Fix perl/ithreads random failures

2004-12-08 Thread Stas Bekman
Steve Hay wrote: Gisle Aas wrote: Steve Hay <[EMAIL PROTECTED]> writes: Gisle Aas wrote: I had to do tests with an older version of mod_perl_1.99 that still had the perl/ithreads* tests. I see that these tests was removed from the distribution in [1], but I think that if you apply the atta

Re: Fix perl/ithreads random failures

2004-12-08 Thread Stas Bekman
Gisle Aas wrote: I had to do tests with an older version of mod_perl_1.99 that still had the perl/ithreads* tests. I see that these tests was removed from the distribution in [1], but I think that if you apply the attached patch you can start distribution these tests again. [1] http://cvs.apache.

Re: Fix perl/ithreads random failures

2004-12-08 Thread Steve Hay
Gisle Aas wrote: >Steve Hay <[EMAIL PROTECTED]> writes: > > > >>Gisle Aas wrote: >> >> >> >>>I had to do tests with an older version of mod_perl_1.99 that still >>>had the perl/ithreads* tests. I see that these tests was removed from >>>the distribution in [1], but I think that if you apply

Re: Fix perl/ithreads random failures

2004-12-08 Thread Gisle Aas
Steve Hay <[EMAIL PROTECTED]> writes: > Gisle Aas wrote: > > >I had to do tests with an older version of mod_perl_1.99 that still > >had the perl/ithreads* tests. I see that these tests was removed from > >the distribution in [1], but I think that if you apply the attached > >patch you can start

Re: Fix perl/ithreads random failures

2004-12-08 Thread Steve Hay
Gisle Aas wrote: >I had to do tests with an older version of mod_perl_1.99 that still >had the perl/ithreads* tests. I see that these tests was removed from >the distribution in [1], but I think that if you apply the attached >patch you can start distribution these tests again. > >[1] >http://cv

Fix perl/ithreads random failures

2004-12-08 Thread Gisle Aas
I had to do tests with an older version of mod_perl_1.99 that still had the perl/ithreads* tests. I see that these tests was removed from the distribution in [1], but I think that if you apply the attached patch you can start distribution these tests again. [1] http://cvs.apache.org/viewcvs.cgi/