Richard Foley wrote:
Thing is, it's not happening on another box, with a similar installation, and
the same code base, so I'm suspecting something environment oriented, odd
libraries or the like. The major thing that's different is the modperl
installation - which I installed against apache ma
I knew it was a stupid question :-)
Thing is, it's not happening on another box, with a similar installation, and
the same code base, so I'm suspecting something environment oriented, odd
libraries or the like. The major thing that's different is the modperl
installation - which I installed ag
Sumit Shah wrote:
What I want is that the Perl handler get the
jsp before the JSERV, do the processing and then pass it to the JSERV
Servlet.
You can't do that with apache 1. In apache 2, you could possibly set
one of them up as a filter to run after the other one.
If you have to use apache
Richard Foley wrote:
> On Wednesday 22 November 2006 16:21, Michael Peters wrote:
>> I've never seen anything like this before. Does it happen with all of your
>> modules or just some of them.
>>
> I'm only noticing it with a couple of modules out of a batch of perhaps a
> thousand...
>
>> Are
On Wednesday 22 November 2006 16:21, Michael Peters wrote:
>
> I've never seen anything like this before. Does it happen with all of your
> modules or just some of them.
>
I'm only noticing it with a couple of modules out of a batch of perhaps a
thousand...
> Are you using source filters?
>
I
Good morning,
Thanks for your reply.
> > I'm trying to build mod_perl 2.0.2 on a Tru64 (Digital
> UNIX) system V5.1B,
> > Apache 2.0.59, Perl 5.8.0.
> You knew I as going to say this, but preferably 5.8.8.
Sorry, I do not understand this.
> Make sure you are using the same compiler for mod_per
Richard Foley wrote:
> Now, the Class::CGI::Welcome module is loaded. I can even see the correct
> and
> up to date code entry under @{main::_<$pathtowelcomedotpm}, _but_, the code
> simply stops after 20 lines, so that the page() method is (clearly because
> it's not there) not found. Wha
Thanks Perrin. I will surely try the mentioned approach. Using Ethereal
I observed that the Perl Handler was not writing any packets onto the
socket stream once the connection was established. It kept giving me TCP
CHECKSUM INCORRECT. I came across Microsoft's patch for this behavior. I
will try to
Rereading my original post, it appears I may not have been explicit enough
about what the problem appears to be. Starting with the error message:
[error] Error executing run mode 'display': Can't locate object method
> "page" via package "Class::CGI::Welcome" at /classes/Class/CGI/Welcome.p
Foo JH wrote:
> William A. Rowe, Jr. wrote:
>> Foo JH wrote:
>>
>>> Yes! It's really (in)famous! :) The more detailed error message seems to
>>> be captured in the Event Application log instead. I wonder why error.log
>>> wasn't more verbose on this one.
>>
>> Because, once it crashes it's no lon
I'm seeing some strange behaviour with modperl, it appears to be truncating
the module code for certain files. Firstly, the code runs fine under CGI and
using a similar commandline setup. Next, there's a apache/conf/startup.pl
script which loads all the expected modules at startup, and the lib
Sorry to hear about your accident. Glad you're OK.
Your analysis seems to point to Perl being unable to free memory blocks
in Windows (will it happen in Linux as well?). Appending to my
experience, this problem happens when there is a huge block of memory to
release.
I'm not much of a C/C++
Not being an C/C++ programmer does this mean that the bug has been
found and solved?
Is it in mod_perl or Perl the bug is?
henrik
-Oprindelig meddelelse-
Fra: Issac Goldstand [mailto:[EMAIL PROTECTED]
Sendt: 22. november 2006 08:41
Til: mod_perl
Cc: Randy Kobes; Foo JH; Eyal Mande
13 matches
Mail list logo
