One thing that causes a significant performance degredation on Win32 is
fixed, we are looking at the second issue.
In APR, unbuffered writes were system-level flushing. I believe this
had to do with some early network testing and multiple-writer concurrency
issues, but the end result is unaccept
-8<-- Start Bug Report 8<--
1. Problem Description:
Calling $r->read($buf,0) result in an internal server error, and an entry
in error_log: The LENGTH argument can't be negative at .
2. Used Components and their Configuration:
*** mod_perl version
Tyler MacDonald wrote:
I have a function that does this to get database settings, to test an
apache2 handler that uses a database:
sub test_db {
my $build = Apache::TestMB->current;
return unless $build->notes('DBI_DSN');
return map {
defined $build->notes($_) ? $build->notes
Hi all,I'm porting some old perl code to a new installation of Apache/2.0.54 (Win32) mod_perl/2.0.1 on Windows 2003 Server. In testing some file locking code, I noticed that response seemed very slow when I dumped in multiple jobs via multiple browsers to the server. I added a timer and saw the scr
Sorry, it's an accident to reply to the list.
Harry
- Original Message -
From: "Harry Zhu" <[EMAIL PROTECTED]>
To: "Jonathan" <[EMAIL PROTECTED]>; "mod_perl List"
Sent: Monday, March 06, 2006 4:41 PM
Subject: Re: [OT] modperl vs. Ruby
- Original Message -
From: "Jonathan
- Original Message -
From: "Jonathan" <[EMAIL PROTECTED]>
To: "mod_perl List"
Sent: Saturday, February 25, 2006 6:26 PM
Subject: Re: [OT] modperl vs. Ruby
there's been a popular link critiquing rails floating around
http://discuss.joelonsoftware.com/default.asp?joel.3.309321.3
pe
On Mon, 2006-03-06 at 12:38 -0800, Gokul P. Nair wrote:
> Starting with the -X is certainly not an option in my case since the
> Apache server I'm using is maintained by another dept and all i have
> is access to start, stop or restart the server though a script.
Unless they've gone to a lot of t
Also, when I said "use Carp in every module", I meant 'call Carp::Cluck'. Sorry for that confusion. Gokul"Gokul P. Nair" <[EMAIL PROTECTED]> wrote: Well, here's the deal. I would like to view a stack trace of everything that's being called in my web application, starting from when the web page is
You may want to use the Apache::DProf module
from CPAN - http://search.cpan.org/~fwiles/Apache-DB-0.11/lib/Apache/DProf.pm.
I find it useful when I want to know that kind of information.
From: Gokul P. Nair
[mailto:[EMAIL PROTECTED]
Sent: Monday, March 06, 2006 2:39
PM
To: Perr
Well, here's the deal. I would like to view a stack trace of everything that's being called in my web application, starting from when the web page is loaded to browsing through the different pages. Starting with the -X is certainly not an option in my case since the Apache server I'm using is maint
i've never used the debugger, so this is a shot in the dark:
push the pid into a textfile / sql / sqlite
do a sql/sqlite lookup at the start of the request
attach the debugger if the current pid is in the result, detach/
notihing otherwise
On Mar 6, 2006, at 3:00 PM
On Mon, 2006-03-06 at 13:54 -0600, Chris Werner wrote:
> I don't think that is what he was asking... He asked if there was a
way to attache the
> DEBUGGER to a specific pid; he did not address the issue of getting
the correct input to
> that pid.
The one isn't much good without the other.
In theo
On 6 Mar 2006, at 19:54, Chris Werner wrote:
I don't think that is what he was asking... He asked if there was a
way to attache the DEBUGGER to a specific pid; he did not address
the issue of getting the correct input to that pid.
The point is that you could not know which pid to attach to - y
Title: RE: Apache::DB - What am I doing wrong?
I don't think that is what he was asking... He asked if there was a way to attache the DEBUGGER to a specific pid; he did not address the issue of getting the correct input to that pid.
I do not use the debugger [but embed debugging code to be sw
On Mon, 2006-03-06 at 11:31 -0800, Gokul P. Nair wrote:
> In other words, is there any way to attach the perl debugger with a
> specific httpd pid, without having to restart Apache in a single
> worker thread mode to ensure that the perl debugger attaches to the
> right httpd pid?
No. You have no
Since we are on this topic, is there any way to get Apache::DB to start the perl debugger without having to restart Apache with a single worker thread (i.e. httpd -X ... option)?In other words, is there any way to attach the perl debugger with a specific httpd pid, without having to restart Apache
Yeah, it turns out it works using the fixup handler. Odd thing is, it
works in the Init handler if I am debugging perl-status--just not
anything else.
Hi Steve,
>>
>>PerlInitHandler Apache::DB
>>
Just being curious:
I've seen PerlInitHandler Apache::DB a couple of times now, while the POD
recommends PerlFixupHandler +Apache::DB
Any specific reason for that?
-Thomas
18 matches
Mail list logo
