tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Joelly <chris.joe...@unycom.com>
Subject Re: strange error messages in tomcat log and mod_jk2 log
Date Mon, 15 Dec 2003 08:30:35 GMT
Hi!

thanx for your reply. hm. it's a very strange thing.

some questions:

are you running your application under heavy load?
are the responses very big in size?
do you use the apache2/mod_jk2/tomcat4 config on a windows nt4 box?
does a dialogbox appear on the server with an error message stateing
that the apache.exe caused an internal error, and after pressing Ok the
apache2 server continues to run?

maybe we can find some similarities.

we have no idea what direction to look for, and the problem is very
critical because a very big application is crashing every few minutes,
so a production environment couldn't be setup... :-((

thx, Chris

Am Fri, Dec 12, 2003 at 01:46:13PM +0200, Altankov Peter meinte:
> Hi!
> Im gettting a similar traces in catalina.out:
> 
> Dec 11, 2003 8:00:03 PM org.apache.jk.server.JkCoyoteHandler action
> SEVERE: Error in action code
> 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:457)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:654)
>         at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:435)
>         at org.apache.coyote.Response.action(Response.java:222)
>         at org.apache.coyote.Response.finish(Response.java:343)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:314)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:387)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:673)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:615)
>         at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:786)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:666)
>         at java.lang.Thread.run(Thread.java:536)
> 
> Acompanied with this in mod_jk.log:
> [Thu Dec 11 20:38:39 2003]  [jk_ajp13_worker.c (381)]: Error ajp13_process_callback -
write failed
> (in my config they run on separate UNIX boxes and unfortunately the one is 38 minutes
ahead in time )
> 
> I have no clue what might be causing it. Posted it coupleof times but got no comments.
> Although my tomcat don?t seem to crash, I don?t consider it?s a normal situation.
> 
> Any ideas someone?
> Thanks in advance!

-- 
mit freundlichen Grüßen / with kind regards
 
Ing. Christian Jölly @ Solutions
unycom  Information Technology Services GmbH
A-8042 Graz | Schmiedlstraße 1 / III

Tel: ++43 (0)316 / 818 828 - 30
Fax: ++43 (0)316 / 818 828 - 38
chris.joelly@unycom.com
http://www.unycom.com

Ein Physiker, ein Mathematiker und ein Windows-Programmierer fahren in
einem Auto, als dieses plötzlich der Geist aufgibt. Der Physiker
schlägt vor, mal das Benzin zu kontrollieren.  Der Mathematiker sagt,
er verstehe nicht viel von Autos, aber man solle mal das Kühlwasser
überprüfen. Der Windows-Programmierer meint, er würde zuerst alle
Fenster schließen, aussteigen, erneut einsteigen und dann alle
Fenster wieder öffnen.

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


Mime
View raw message