Title: FW: problem w/ ajp13 - if Tomcat is shutdown
I'm having problem with mod_jk if ajp13 is used.
The problem is often reproduced when Tomcat is shut
down without Apache being shut down. When a request
is fired through Apache as soon as Tomcat starts,
I often get Internal Server Error.
doesn't know that TC has restarted).
>
> If anyone wants to work on this, you would have the undying
> thanks of the
> rest of the TC community -- having to restart Apache all the
> time bugs a
> *lot* of people.
>
> -Dan
>
> > Shinta Tjio wrote:
> >
&
k I got it working. I just need to clean up the code
some more.
shinta
> -Original Message-
> From: oliver2, andy [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, March 06, 2001 6:33 PM
> To: 'Shinta Tjio '; '[EMAIL PROTECTED] '
> Cc: ''Dan Milstei
Title: RE: FW: problem w/ ajp13 - if Tomcat is shutdown
> BTW we should redirect this to the tomcat-users list as I don't think
> its a development issue.
Sorry about that.
> I don't see anything wrong, and the only drastic difference from my
> previous setup was that I had used the defa
tc.
I have both of these solution prototyped and minimally
tested. They both Anyone care to comment which solution fits better
with the overall code? Anyone voluteer to review the code?
thanks,
shinta
> -Original Message-
> From: Shinta Tjio
> To: [EMAIL PROTECTED]
> Cc: &#
> the socket, this select() should return the socket
> > being read ready. When this happen, I issue a read()
> > of 1 bytes. If the read() comes back with return code
> > 0, this should be an indication that the socket was
> > closed on the remote end. Then I
x a problem.
But I think select() is supported on Windows.
> I'll try to take a more thorough look (and do some testing).
Do you have any comments as to which solution is better suited?
Just to recap, my action items are:
1. Merge fixes to 3.3 branch
2. Test & make sure no da
Title: RE: FW: problem w/ ajp13 - if Tomcat is shutdown
> I revue your patch and I notice :
>
> We could use select to determine if something happen to the
> connection, typically readfds will be set if something is to read.
> With ajp13 protocol where everything is consumed after reading t
Title: RE: Design Review for ajp13's changes: WAS problem w/ ajp13 - if Tomc at is shutdown
> > 3) For option (1), I have a few questions
> >
> > - Is there a way in which data could be lost? Specifically,
> >as you state,
> >the send() will return without error, and then it will only
>
Title: RE: FW: problem w/ ajp13 - if Tomcat is shutdown
Okay, I basically agree with you. I'll take out
the check for errno and just have recv() == -1
be considered a recoverable error (i.e: retry it).
However, I disagree with making the retry in a
loop for RETRIES times. This is because i
Title: RE: FW: problem w/ ajp13 - if Tomcat is shutdown
Hi, Dan,
I may not understand all of the issues here. But I really
don't think we should close all connections when we
detect one ECONNRESET. In my opinion, it is not necessary
to close all connections, since the next ECONNRESET
will clo
I had the same problem earlier too.
You just need to edit the build-unix.sh and add -DSOLARIS
to the APXS call. My apxs doesn't have that by default.
hope this helps
shinta
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Friday, March 09, 2001 11:22 PM
Title: RE: FW: problem w/ ajp13 - if Tomcat is shutdown
> 1) First off, I strongly believe that this work (which I think is an
> excellent feature, BTW), belongs in the 3.3 branch, and *not* in 3.2.
> Although it feels like a bug that we need to restart Apache
> every time we restart TC, it
---
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]
> Sent: Friday, March 09, 2001 3:31 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Design Review for ajp13's changes: WAS problem w/ ajp13 -
> if Tomc at is shutdown
>
>
> [EMAIL PROTECTED] (Shinta Tjio) writes:
&
Title: RE: FW: problem w/ ajp13 - if Tomcat is shutdown
Henri, Dan,
There are some discussions below about the usage
of msg/rmsg. What did you guys finally decide
on that? Just reuse msg? I'm seeing the problem
Dan mentioned on message larger than the ajp13
buffer (8K).
thanks,
shinta
> --
We are using Apache 1.3.26 and Tomcat 3.2.2. We've seen some
clients to be hanging Apache on SSL read. The cause of this
hang seems to be network/TCP/IP issue. The read will eventually
times out. When it times out, here's where the problem starts.
Tomcat seems to be grabbing some buffer that cont
16 matches
Mail list logo
