Thanks for the pointer to cronolog. We do use log4j - the log messages in
question appear to be coming from the apache product itself. On further
inspection it appears that we need to increase plim_fd_cur and plim_fd_max
on our Solaris server as we are receiving the wonderful "Too many open
files" exception. Once again thanks for the pointer to cronolog.
Cheers,
James
> -----Original Message-----
> From: Tim Funk [mailto:[EMAIL PROTECTED]
> Sent: 2003 June 24 09.15
> To: Tomcat Users List
> Subject: Re: Huge catalina.out file
>
>
> See this recent thread:
> http://marc.theaimsgroup.com/?l=tomcat-user&m=105640876032532&w=2
>
> Also - shoot your developers who use System.out without
> regard to the issues
> that it raises when the app goes to production. ;) If that is
> the case - get
> them to swithc to log4j so logging can be turned down and you
> can use the
> rotation facilities that log4j provides.
>
>
>
> -Tim
>
> Brown, James wrote:
> > We recently experienced a problem where the catalina.out
> file had reached ~
> > 2GB in size and filled the file system in only a few days.
> Is there any
> > means of reducing the output to this file? I have looked
> in web.xml and all
> > of the <param-name>debug</param-name> values are set to 0 -
> which from my
> > understanding signifies that debug logging is disabled.
> >
> > Cheers,
> > James
> >
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
