tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Damien Corbishley" <>
Subject mod_jk errors and http status code 503 under load
Date Thu, 06 Sep 2007 14:07:57 GMT

 I'm getting stuck with an error we are seeing on our production server
under load. 

 I've googled and found many posts on similar topics but I haven't found
an answer yet, 

 I was hoping somebody here could shed some light on my issue:


We upgraded our combination of Apache,Tomcat,Java all running on Solaris
10 to 

Apache 2_2.0.55.build2

Tomcat 5.5.23

Java 1.5.0_06-b05


Our Apache Tomcat connector is AJP/1.3.


It's all installed on the same server, we have no tomcat clusters and no
load balancers.


With a few (10) concurrent users accessing the various JSP's everything
worked as expected, all our functional tests passed.

We opened more up live traffic to the server and starting seeing the
following error message:


[Thu Sep 06 02:23:00 2007] [error] ajp_service::jk_ajp_common.c (1758):
Error connecting to tomcat. Tomcat is probably not started or is
listening on the wrong port. worker=worker1 failed


On the client side this was being reported as a 503 and our
"intelligent" browser was re-submitting the request and generally, 

on the second time, the request would be successful. 

After an hour we then had a Solaris panic, and after analyzing the crash
using scat I can see that the cause was:


panic string:   BAD TRAP: type=9 rp=2a1015332d0 addr=0 mmu_fsr=0


and looking further into the trap, it seems to be network related.


<trap>ip:tcp_conn_request+0x894 (0x4, 0x2000, 0x136ec00, 0x3a2b9a44040,
0x40e03960300, 0x40dedc247c0)

ip:squeue_drain+0xe4 (0x300015ddec0, 0x40e2021c1c0, 0x411666de,
0x135f2c0, 0x3a2b9a44040, 0x3)

ip:squeue_enter+0x358 (0x300015ddec0, 0x38fca5e0d80, 0x3000426b640,
0x3a2bd674c00, 0x0, 0x1)

ip:tcp_wput - frame recycled


I am still trying to work out if the crash is a symptom of the browsers
resubmitting the failed requests and we've hit a Solaris bug that we
haven't got a patch for,

Or if the two errors are unrelated and it was coincidence that we
panicked whilst having mod_jk errors. 



Any help/pointers in resolving the mod_jk error would be appreciated, I
included the brief crash information as it may be relevant. 




This e-mail transmission may contain information that is proprietary, privileged and/or confidential
and is intended exclusively for the person(s) to whom it is addressed. Any use, copying, retention
or disclosure by any person other than the intended recipient or the intended recipient's
designees is strictly prohibited. If you are the intended recipient, you must treat the information
in confidence and in accordance with all laws related to the privacy and confidentiality of
such information.  If you are not the intended recipient or their designee, please notify
the sender immediately by return e-mail and delete all copies of this email, including all

Intervoice, Inc. 17811 Waterview Parkway Dallas, TX 75252 USA

Intervoice Limited, Registered in England and Wales with number 2601740, 50 Park Road, Gatley,
Cheshire, SK8 4HZ. VAT Number: 560421375

Intervoice GmbH, Hagenauer Straße 55, 65203 Wiesbaden, Sitz der Gesellschaft: Wiesbaden, Handelsregister:
HRB 8186 (Amtsgericht Wiesbaden), Geschäftsführer: Richard Arnold.
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message