This could be completely unrelated, but let me throw something at you,
maybe it will help
btw. I prefer to run mod_proxy over mod_jk over http, much simpler, and
in *our* load tests has scaled much better during stress.
>Response already committed
This can happen if your servlet/jsp has code like this
....do some stuff
response.sendRedirect(url);
...do some more stuff
what has happened here, is that you are trying to write to the response
buffer even though you earlier indiciated (through sendRedirect or
sendError) that you wouldn't. To correct this, you would have to put a
return statement in your code
....do some stuff
response.sendRedirect(url);
return;
...do some more stuff
java.net.SocketException: Broken pipe
the apache mod_jk module has disconnected from tomcat before it was able to
send the entire message.
Filip
Tomasz Nowak 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!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
