my advice is dive in and try to debug it, or hire someone with experience
debugging webapps.

there's no much others can do for you at this point, since it's debugging.
good luck.

peter


On 3/1/06, Tomasz Nowak <[EMAIL PROTECTED]> wrote:
>
> Tomasz Nowak <[EMAIL PROTECTED]> wrote:
> >
> > Hm. Here is my logging.properties:
> > http://www.biochip.pl/logging.properties.txt
> > The way new vhosts are added is pretty stupid for me but
> > lets forget about the semantics now.
> >
> > I've added swallowOutput attibute to serveral context.
> > How should it suppose to work? On my box it works in this way:
> > - The only file that actually logs anything that matters is
> > catalina.out
> > - Most of catalina.out inputs also appear in localhost.timstamp.log
> > - Nothing more then manager actions are logged to vhost logs
> > - After tomcat has stared, the only input logs are:
> >
> > a) useless:
> > INFO: Response already committed
> > Feb 28, 2006 10:59:22 PM org.apache.jk.core.MsgContext action
> > INFO: Response already committed
> > Feb 28, 2006 10:59:22 PM org.apache.jk.core.MsgContext action
> > INFO: Response already committed
> > Feb 28, 2006 10:59:22 PM org.apache.jk.core.MsgContext action
> > INFO: Response already committed
> > Feb 28, 2006 10:59:22 PM org.apache.jk.core.MsgContext action
> > INFO: Response already committed
> > Feb 28, 2006 10:59:22 PM org.apache.jk.core.MsgContext action
> > (repeted serveral times every single minute (!) on my machine)
> >
> > b) sth like:
> > Feb 28, 2006 11:00:03 PM org.apache.jk.core.MsgContext action
> > WARNING: Error sending end packet
> > java.net.SocketException: Broken pipe
> >         at java.net.SocketOutputStream.socketWrite0(Native Method)
> >         at
> > java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
> >         at
> > java.net.SocketOutputStream.write(SocketOutputStream.java:136)
> >         at
> > org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:518)
> >         at
> > org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:112)
> >         at org.apache.jk.core.MsgContext.action(MsgContext.java:293)
> >
> > So how can I:
> > - configure it to work similary to tomcat 4.1, I mean
> >   logs from different vhost go to different files
> > - configure Tomcat not to log anything that belongs to vhost
> >   to catalina.out
> > - turn of these useless jk infos
>
> Any help on above would be _really_ appreciated!
>
> --
> T.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to