tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Angelov, Rossen" <Rossen.Ange...@thomsonmedia.com>
Subject RE: Is this normal for Tomcat?
Date Fri, 30 May 2003 17:46:59 GMT
Well, I gave you wrong information. The line with categoryFactory is not
being used. That was the old configuration.

All I have in the code is org.apache.log4j.Logger.getLogger and
PropertyConfigurator.configure(log4jfile), there is no categoryFactory
involved.

It's not only the cookies but the whole response. 

Is there some kind of server caching that Tomcat might be doing?

I have disabled caching on HTTP level:
		response.setHeader("pragma", "no-cache");
		response.setHeader("Cache-Control", "no-cache");
		response.setDateHeader("Expires", 0);

Ross

-----Original Message-----
From: Shapira, Yoav [mailto:Yoav.Shapira@mpi.com]
Sent: Friday, May 30, 2003 12:33 PM
To: Tomcat Users List
Subject: RE: Is this normal for Tomcat?



Howdy,
Are you actually specifying a categoryFactory?  Is it a custom one?
What version of log4j are you using?

I still have no clue as to the shared cookies issue.

Yoav Shapira
Millennium ChemInformatics


>-----Original Message-----
>From: Angelov, Rossen [mailto:Rossen.Angelov@thomsonmedia.com]
>Sent: Friday, May 30, 2003 1:28 PM
>To: 'Tomcat Users List'
>Subject: RE: Is this normal for Tomcat?
>
>Sorry, I meant, I'm not using Apache's FileLogger to log this data.
>
>Both are using FileAppender with different log4j.appender.LOG.File
>property.
>
>The categoryFactory, rootCategory, PatternLayout and ConversionPattern
are
>the same.
>
>-----Original Message-----
>From: Shapira, Yoav [mailto:Yoav.Shapira@mpi.com]
>Sent: Friday, May 30, 2003 12:19 PM
>To: Tomcat Users List
>Subject: RE: Is this normal for Tomcat?
>
>
>
>Howdy,
>How is log4j writing to a file if you're not using
>FileAppender?
>
>Yoav Shapira
>Millennium ChemInformatics
>
>
>>-----Original Message-----
>>From: Angelov, Rossen [mailto:Rossen.Angelov@thomsonmedia.com]
>>Sent: Friday, May 30, 2003 1:15 PM
>>To: 'Tomcat Users List'
>>Subject: RE: Is this normal for Tomcat?
>>
>>No, they are completely different:
>>
>>webapps -> context1 -> WEB-INF -> classes -> com/context1 ....
>>webapps -> context2 -> WEB-INF -> classes -> com/context2 ....
>>
>>I don't have anything in common/lib or common/classes used by these
>>servlets.
>>log4j has two different paths for the log files. I'm not using
>>FileAppender,
>>the servlets read in the log4j properties from a separate
configuration
>>files passed as <param-value> when the servlet starts.
>>
>>
>>
>>-----Original Message-----
>>From: Shapira, Yoav [mailto:Yoav.Shapira@mpi.com]
>>Sent: Friday, May 30, 2003 12:08 PM
>>To: Tomcat Users List
>>Subject: RE: Is this normal for Tomcat?
>>
>>
>>
>>Howdy,
>>Do you have any code in the common/lib or common/classes repository
>that
>>these two contexts share?  Is the File destination for log4j's
>>FileAppender configured to be the same for the two contexts?
>>
>>Yoav Shapira
>>Millennium ChemInformatics
>>
>>
>>>-----Original Message-----
>>>From: Angelov, Rossen [mailto:Rossen.Angelov@thomsonmedia.com]
>>>Sent: Friday, May 30, 2003 1:01 PM
>>>To: 'Tomcat Users List'
>>>Subject: Is this normal for Tomcat?
>>>
>>>Hi,
>>>
>>>I'm using Tomcat 4.1.12 running on Solaris 5.7
>>>
>>>Issue #1:
>>>There are two different contexts with different paths and different
>>>docBase.
>>>Two different servlets using two different log files (log4j). I was
>>>browsing
>>>the pages from the same browser window (IE 5.5) switching between
both
>>>contexts when I noticed both servlets are writing to the same log
>file.
>>>Theoretically it's not supposed to happen because they use different
>>>configuration files and I haven't changed them for days. These
>servlets
>>are
>>>completely independent from each other.
>>>
>>>Issue #2:
>>>Sometimes when multiple users access pages happen to share the same
>>http
>>>responses: User1 can see the cookies and the pages that user2
>>requested.
>>>
>>>How is all this possible?
>>>
>>>Ross
>>
>>
>>
>>
>>This e-mail, including any attachments, is a confidential business
>>communication, and may contain information that is confidential,
>>proprietary
>>and/or privileged.  This e-mail is intended only for the individual(s)
>to
>>whom it is addressed, and may not be saved, copied, printed, disclosed
>or
>>used by anyone else.  If you are not the(an) intended recipient,
please
>>immediately delete this e-mail from your computer system and notify
the
>>sender.  Thank you.
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
>
>This e-mail, including any attachments, is a confidential business
>communication, and may contain information that is confidential,
>proprietary
>and/or privileged.  This e-mail is intended only for the individual(s)
to
>whom it is addressed, and may not be saved, copied, printed, disclosed
or
>used by anyone else.  If you are not the(an) intended recipient, please
>immediately delete this e-mail from your computer system and notify the
>sender.  Thank you.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org



This e-mail, including any attachments, is a confidential business
communication, and may contain information that is confidential, proprietary
and/or privileged.  This e-mail is intended only for the individual(s) to
whom it is addressed, and may not be saved, copied, printed, disclosed or
used by anyone else.  If you are not the(an) intended recipient, please
immediately delete this e-mail from your computer system and notify the
sender.  Thank you.


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message