Guten Tag Steve Hay,
am Montag, 19. August 2019 um 14:37 schrieben Sie:
> I will need to get a new Apache-Test released with the dot-in-INC fix
> included, and then I'm back on track for getting 2.0.11 RC1 out :-)
That's great news, thanks!
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorst
On Wed, 31 Jul 2019 at 19:40, Thorsten Schöning wrote:
>
> Guten Tag Steve Hay,
> am Mittwoch, 31. Juli 2019 um 19:48 schrieben Sie:
>
> > I ran into this myself recently.
>
> Do you see anything like a timeout happening as well or is your test
> app failing fast?
>
> > https://bz.apache.org/bugzi
Guten Tag Steve Hay,
am Mittwoch, 31. Juli 2019 um 19:48 schrieben Sie:
> I ran into this myself recently.
Do you see anything like a timeout happening as well or is your test
app failing fast?
> https://bz.apache.org/bugzilla/show_bug.cgi?id=51560
At least in my case I'm not using any Active D
On Wed, 31 Jul 2019 at 18:07, Thorsten Schöning wrote:
>
> Hi all,
>
> I recently started to have a look at supporting mod_perl for our
> WebApp on Windows again and implemented a very simple PoC pre-loading
> our app during start of HTTPd using "PerlPostConfigRequire". During
> implementation I r
Hi all,
I recently started to have a look at supporting mod_perl for our
WebApp on Windows again and implemented a very simple PoC pre-loading
our app during start of HTTPd using "PerlPostConfigRequire". During
implementation I ran into the following problem with my setup.
My HTTPd is NOT running
Hello,
I'm trying to use ModPerl::RegistryLoader to compile my app at server
startup.
I have the code below in my startup.pl. I can see that the program is
loaded at startup, but
when I hit the url it is executed as a normal CGI.
What am I doing wrong?
sub trans {
my $uri =
On 26.7.2011 16:08, Perrin Harkins wrote:
2011/7/26 Jiří Pavlovský:
That is probably it, I store db handle in a singleton.
That, unfortunately is something I cannot change easily
Apache::DBI should make this unnecessary. You could change your
singleton code to DBI->connect every time and it wo
2011/7/26 Jiří Pavlovský :
> That is probably it, I store db handle in a singleton.
> That, unfortunately is something I cannot change easily
Apache::DBI should make this unnecessary. You could change your
singleton code to DBI->connect every time and it would just pull the
cached handle from Apa
On 25.7.2011 22:18, Perrin Harkins wrote:
2011/7/22 Jiří Pavlovský:
On 22.7.2011 18:15, Perrin Harkins wrote:
However this doesn't work as Apache is segfaulting.
That makes it sound like it is working but there's something in your
scripts that doesn't like being loaded in the parent process.
On Monday, 25 July 2011 23:31:04 McCarrell, Jeff wrote:
> I am not sure if this directly applies to your issue, but I got
> segfaults in DBI when I just opened the DB handle once in the parent,
> reusing the DBH in child processes (a bug). The issue went away when
> I ensured that every child proc
I am not sure if this directly applies to your issue, but I got segfaults
in DBI when I just opened the DB handle once in the parent, reusing the
DBH in child processes (a bug). The issue went away when I ensured that
every child process did its own DBI->connect.
HTH
On 7/22/11 11:17 AM, "Jiří P
2011/7/22 Jiří Pavlovský :
> On 22.7.2011 18:15, Perrin Harkins wrote:
>>>
>>> However this doesn't work as Apache is segfaulting.
>>
>> That makes it sound like it is working but there's something in your
>> scripts that doesn't like being loaded in the parent process. Are you
>> opening up datab
On 22.7.2011 18:15, Perrin Harkins wrote:
However this doesn't work as Apache is segfaulting.
That makes it sound like it is working but there's something in your
scripts that doesn't like being loaded in the parent process. Are you
opening up database handles or files on the first hit and then
Hi Jiri,
i am not sure what you are trying to do with ModPerl::RegistryLoader,
but what me helped to improve performance was :
1. Preload almost every library on startup:
PerlPostConfigRequire /xyz/startup.pl (
-
use Apache2::RequestRec();
use Apache2::RequestIO();
use Apache2
2011/7/21 Jiří Pavlovský :
> I did RTFM, but the man page was not clear to me, so I asked on the list.
Asking on the list is encouraged! We just need specific questions
> However this doesn't work as Apache is segfaulting.
That makes it sound like it is working but there's something in your
scr
On 21.7.2011 18:41, Perrin Harkins wrote:
So I was looking a solution and found ModPerl::RegistryLoader. I'm just not
sure I understand it completely. Is this the "compile once at startup"
solution?
Yes, that's what it's for.
Thanks, so I'm on correct tra
2011/7/21 Jiří Pavlovský :
> So I was looking a solution and found ModPerl::RegistryLoader. I'm just not
> sure I understand it completely. Is this the "compile once at startup"
> solution?
Yes, that's what it's for.
> Do I just put " my $rlbb = ModPerl:
I don't know about ModPerl::RegistryLoader, but the simplest solution is just
to "preload" the interpreters either manually or through a script whenever you
restart Apache. In your httpd.conf file, you control how many interpreters are
running and how many hits each interpreter
In my case the difference is huge (2s versus tenths of ms) which makes
notable difference for the user experience for the various autocomplete
inputs etc.
So I was looking a solution and found ModPerl::RegistryLoader. I'm just
not sure I understand it completely. Is this the "comp
On Fri, 2006-08-18 at 14:03 -0400, Perrin Harkins wrote:
> You can't do that. These are APIs to apache internals. They don't work
> without the httpd environment.
Ah, okay. Thanks for the explanation. Changing it to
Apache2::ServerUtil->server_root would probably at least make it work at
On Fri, 2006-08-18 at 11:00 -0700, Max Kanat-Alexander wrote:
> This is not a problem when Apache uses the module, only when you try to
> compile a command-line script that uses ModPerl::RegistryLoader.
You can't do that. These are APIs to apache internals. They don't
thread-multi/ModPerl/RegistryLoader.pm
line 74.
However, the script properly uses Apache2::ServerUtil, which does
indeed have a subroutine called server_root.
This is not a problem when Apache uses the module, only when you try to
compile a command-line script that uses ModPerl::Registry
I'm sure i'm doing something wrong, but when i perl
-MModPerl::RegistryLoader -e 'print 1;' i get the following error;
Bareword "Apache2::ServerUtil::server_root" not allowed while "strict
subs" in use at
/usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi/ModPerl/RegistryLoader.pm
line
23 matches
Mail list logo