jean-frederic clere wrote:
>
> Bojan Smojver wrote:
> >
> > Bojan Smojver wrote:
> > >
> > > Unfortunately, the problem is still there... Let me run gdb on the thing
> > > again and then I'll send you the backtrace.
> > >
> > > Bojan
> >
> > Slighty different problem this time, but along the line
jean-frederic clere wrote:
>
> Bojan Smojver wrote:
> >
> > Bojan Smojver wrote:
> > >
> > > Unfortunately, the problem is still there... Let me run gdb on the thing
> > > again and then I'll send you the backtrace.
> > >
> > > Bojan
> >
> > Slighty different problem this time, but along the line
Bojan Smojver wrote:
>
> Bojan Smojver wrote:
> >
> > Unfortunately, the problem is still there... Let me run gdb on the thing
> > again and then I'll send you the backtrace.
> >
> > Bojan
>
> Slighty different problem this time, but along the lines of the previous
> one:
DARN, That is the same
Bojan Smojver wrote:
>
> Just a little trivial problem with the new source: it doesn't build
> because file common/jk_uri_worker_map.c has an unintentional comment end
> (the * after apache) in line 312:
>
> * I have fixed jk_mount_context() in apache*/mod_jk.c so we should
>
> The comment actu
Bojan Smojver wrote:
>
> Unfortunately, the problem is still there... Let me run gdb on the thing
> again and then I'll send you the backtrace.
>
> Bojan
Slighty different problem this time, but along the lines of the previous
one:
--
Program receive
Unfortunately, the problem is still there... Let me run gdb on the thing
again and then I'll send you the backtrace.
Bojan
jean-frederic clere wrote:
>
> Clere Jean-Frederic FSC EP LP COM 5 wrote:
> >
> > Bojan Smojver wrote:
> > >
> > > jean-frederic clere wrote:
> > > >
> > > > Bojan Smojver
Just a little trivial problem with the new source: it doesn't build
because file common/jk_uri_worker_map.c has an unintentional comment end
(the * after apache) in line 312:
* I have fixed jk_mount_context() in apache*/mod_jk.c so we should
The comment actually ends in line 314.
Bojan
Bojan S
Bojan Smojver wrote:
>
> jean-frederic clere wrote:
> >
> > Bojan Smojver wrote:
> > >
> > > jean-frederic clere wrote:
> > > >
> > > > Bojan Smojver wrote:
> > > > >
> > > > > Don't want to be a pain in the back side... but (there is always at
> > > > > least one of those :-), is anyone checking
Bojan Smojver wrote:
>
> jean-frederic clere wrote:
> >
> > Bojan Smojver wrote:
> > >
> > > Don't want to be a pain in the back side... but (there is always at
> > > least one of those :-), is anyone checking this one out?
> > >
> > > I had a peek into the code and that NULL pointer is a variabl
jean-frederic clere wrote:
>
> Bojan Smojver wrote:
> >
> > jean-frederic clere wrote:
> > >
> > > Bojan Smojver wrote:
> > > >
> > > > Don't want to be a pain in the back side... but (there is always at
> > > > least one of those :-), is anyone checking this one out?
> > > >
> > > > I had a peek
Don't want to be a pain in the back side... but (there is always at
least one of those :-), is anyone checking this one out?
I had a peek into the code and that NULL pointer is a variable called
'uwr->context'. Don't know much about mod_jk, but this one gets
initialised in the same file, function
GOMEZ Henri wrote:
>
> >Just realised that the core I have was compiled without -g option. VERY
> >useful. I also wanted to replicate the core dump with the
> >httpd that was
> >compiled with -g, but that didn't work. Now I'm starting to think that
> >the core file I had was a result of a differe
GOMEZ Henri wrote:
>
> >Just realised that the core I have was compiled without -g option. VERY
> >useful. I also wanted to replicate the core dump with the
> >httpd that was
> >compiled with -g, but that didn't work. Now I'm starting to think that
> >the core file I had was a result of a differe
jean-frederic clere wrote:
>
> GOMEZ Henri wrote:
> >
> > >Just realised that the core I have was compiled without -g option. VERY
> > >useful. I also wanted to replicate the core dump with the
> > >httpd that was
> > >compiled with -g, but that didn't work.
>
> What did not work? -It does not
GOMEZ Henri wrote:
> Ask to Apache specialist in new-http list, may be JF Clere could
> forward your question to them ?
I'll subscribe to the list and try to find out how it's done. Then
(hopefully) I'll be able to send over something you can work with.
Bojan
GOMEZ Henri wrote:
>
> >Just realised that the core I have was compiled without -g option. VERY
> >useful. I also wanted to replicate the core dump with the
> >httpd that was
> >compiled with -g, but that didn't work.
What did not work? -It does not core any more?
> > Now I'm starting to think
>Just realised that the core I have was compiled without -g option. VERY
>useful. I also wanted to replicate the core dump with the
>httpd that was
>compiled with -g, but that didn't work. Now I'm starting to think that
>the core file I had was a result of a different crash (I was
>experimenting
GOMEZ Henri wrote:
>
> >> >> Good information, and could send us a strace ?
> >> >
> >> >This may sound strange to all you Apache experts, but how
> >do I do that?
> >> >How do I run strace on a detached process?
> >>
> >> strace httpd -f (follow forks)
> >
> >Thanks for the tip. The log file (bz
>> >> Good information, and could send us a strace ?
>> >
>> >This may sound strange to all you Apache experts, but how
>do I do that?
>> >How do I run strace on a detached process?
>>
>> strace httpd -f (follow forks)
>
>Thanks for the tip. The log file (bziped) is attached.
I didn't locate th
jean-frederic clere wrote:
>
> Bojan Smojver wrote:
> >
> > GOMEZ Henri wrote:
> > >
> > > >> Good information, and could send us a strace ?
> > > >
> > > >This may sound strange to all you Apache experts, but how do I do that?
> > > >How do I run strace on a detached process?
> > >
> > > strace
Bojan Smojver wrote:
>
> GOMEZ Henri wrote:
> >
> > >> Good information, and could send us a strace ?
> > >
> > >This may sound strange to all you Apache experts, but how do I do that?
> > >How do I run strace on a detached process?
> >
> > strace httpd -f (follow forks)
>
> Thanks for the tip.
GOMEZ Henri wrote:
>
> >> Good information, and could send us a strace ?
> >
> >This may sound strange to all you Apache experts, but how do I do that?
> >How do I run strace on a detached process?
>
> strace httpd -f (follow forks)
Thanks for the tip. The log file (bziped) is attached.
Bojan
>> Good information, and could send us a strace ?
>
>This may sound strange to all you Apache experts, but how do I do that?
>How do I run strace on a detached process?
strace httpd -f (follow forks)
>> Good information, and could send us a strace ?
>
>Just occurred to me that I have the dumped core of Apache when it died.
>Would that help you?
May be send a gdb where output ?)
GOMEZ Henri wrote:
>
> >Now I have some new info here. After recompiling everything clean, I've
> >taken out PHP altogether. So it's not part of the equation. It is
> >sufficient to compile mod_jk in and use static pages only (ie. no
> >JSP's/VM at all). If you gracefully restart the server a
> >
GOMEZ Henri wrote:
>
> >Now I have some new info here. After recompiling everything clean, I've
> >taken out PHP altogether. So it's not part of the equation. It is
> >sufficient to compile mod_jk in and use static pages only (ie. no
> >JSP's/VM at all). If you gracefully restart the server a
> >
>Now I have some new info here. After recompiling everything clean, I've
>taken out PHP altogether. So it's not part of the equation. It is
>sufficient to compile mod_jk in and use static pages only (ie. no
>JSP's/VM at all). If you gracefully restart the server a
>number of times
>(the number va
Bojan Smojver wrote:
>
> GOMEZ Henri wrote:
> >
> > >Just did a DSO version and couldn't replicate the problem (BTW, I've
> > >recompiled/statically linked Apache and mod_jk again since then and the
> > >problem was still there). So, maybe it has to do with statically linking
> > >Apache after al
GOMEZ Henri wrote:
>
> >Just did a DSO version and couldn't replicate the problem (BTW, I've
> >recompiled/statically linked Apache and mod_jk again since then and the
> >problem was still there). So, maybe it has to do with statically linking
> >Apache after all...
>
> Strange problem. What's t
GOMEZ Henri wrote:
> >I still have to distribute this DSO version of Apache and mod_jk to some
> >slower machines to see if that makes any difference at all. The machine
> >that didn't produce any errors is a 1 GHz Athlon, so timing issues could
> >have been resolved by brute force, who knows...
>
GOMEZ Henri wrote:
>
> >Just did a DSO version and couldn't replicate the problem (BTW, I've
> >recompiled/statically linked Apache and mod_jk again since then and the
> >problem was still there). So, maybe it has to do with statically linking
> >Apache after all...
>
> Strange problem. What's t
>Just did a DSO version and couldn't replicate the problem (BTW, I've
>recompiled/statically linked Apache and mod_jk again since then and the
>problem was still there). So, maybe it has to do with statically linking
>Apache after all...
Strange problem. What's the difference between static and d
Bojan Smojver wrote:
> As for DSO, I'll have to work on that, so probably some time tomorrow
> (Sydney time).
Just did a DSO version and couldn't replicate the problem (BTW, I've
recompiled/statically linked Apache and mod_jk again since then and the
problem was still there). So, maybe it has to
OOPS! Sorry :-(
jk.conf (called from httpd.conf)
-
###
# Apache JK Configuration
File#
###
> After including it in Apache 1.3.20, statically compiled/linked for
> RedHat Linux 7.0, the error messages 'child pid x exit signal
> Segmentation fault (11)' start appearing in the error log file of
> Apache. mod_jk from Tomcat 3.3 M3 works fine with both Tomcat M3 and
> the
> latest 3.3 CV
35 matches
Mail list logo
