Re: Tomcat 4.1.12: access log corrupted

[Craig Longman]

On Thu, 2002-09-26 at 07:37, [EMAIL PROTECTED] wrote:
> Now with 4.1.12 have a look to a sample of what i see into it.
> (Sorry for the weird looking but it's full of control characters that when
> imbedded into the mail do strange things)
> I think i should open a bug. Do i?
> 
> 6"> 172.20.52.27 - - [26/Sep/2002:13:12:34 1000] "POST /home/checklogin.jsp
> HTTP/1.1" 302 -
> waveFlash"
>  - - [26/Sep/2002:13:12:41 1000] "GET /InfoTraffic/situazione_viabilita.jsp
> HTTP/1.1" 200 -

i think this might be related to the bug i posted about the requestURI
getting trashed when doing an PageContext.include(), the two problems
look very similar (the same sort of garbage as the 'url').

bug #12787

does anyone who is experiencing this know if their code does a
PageContext.include()?  actually, it needs to be an include() IF the
doStartTag() preceeding it returns EVAL_PAGE_INCLUDE.


-- 

 CraigL->Thx();




signature.asc
Description: This is a digitally signed message part

Re: Tomcat 4.1.12: access log corrupted

[Remy Maucherat]

[EMAIL PROTECTED] wrote:
> Well, i rechecked all twice, i't a new fresh install.
> The only old thing is the app context, that is not embedded into server.xml
> but as a standalone file.
> I still had a doubt about the jk module that was compiled for 4.1.10, but i
> downloaded 4.1.12 connectors and recompiled them.
> I tested both jk and jk2 with ajp3 connector with same results.
> Also the application was recompiled against 4.1.12.
> If nobody has any other hint, i'll open a bug.

According to my testing, this doesn't happen with Tomcat standalone on 
8080 (or you'll have to explain how to get the problems).

Since the requestURI buffer isn't used much in Tomcat, it is possible 
that Coyote JK2 mutates it, creating the incorrect logs.
Of course, if you use Apache + Tomcat, maybe you should use the native 
access logger instead (it should be much faster).

Remy


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Tomcat 4.1.12: access log corrupted

[gabriele . garuglieri]

Well, i rechecked all twice, i't a new fresh install.
The only old thing is the app context, that is not embedded into server.xml
but as a standalone file.
I still had a doubt about the jk module that was compiled for 4.1.10, but i
downloaded 4.1.12 connectors and recompiled them.
I tested both jk and jk2 with ajp3 connector with same results.
Also the application was recompiled against 4.1.12.
If nobody has any other hint, i'll open a bug.

BTW, sorry i posted the initial message both to user and dev lists breaking
the rules. I just changed my mind on where to send it, but hit the send
button too fast.

Regards,  Gabriele


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Tomcat 4.1.12: access log corrupted

[Christopher Watson]

Hello

Reading this message had me very worried, BUT

Just to let you know I DON'T get this bad behaviour.

I did have to uncomment the access log valve, but it behaves OK

Both as port 8080 and via IIS using tomcat's ISAPI using ajp13 port 8009

I wonder if you are using a different connector ..?

Also, have you upgraded everything? Made sure all the jars are up-to-date?
Cleared out the work directory

Hope this helps

Christopher

> -Original Message-
> From: Miguel Angel Mulero Martinez
> [mailto:[EMAIL PROTECTED]]
> Sent: 26 September 2002 12:49
> To: Tomcat Users List
> Subject: RE: Tomcat 4.1.12: access log corrupted
>
>
> I had look at my server.xml and it don't have a valve access log
> by default
> (I think remember older versions have it). I add one like yours,
> and I have
> got the same problem. Look at the first characters of each line:
>
> >
> 

RE: Tomcat 4.1.12: access log corrupted

[Miguel Angel Mulero Martinez]

I had look at my server.xml and it don't have a valve access log by default
(I think remember older versions have it). I add one like yours, and I have
got the same problem. Look at the first characters of each line:

>