Re: Tomcat Shutdown Unexpectedly
Hi, We've recently had something very similar with Tomcat and Apache Web Server. Have a look here (read all in threads): http://www.mail-archive.com/users@tomcat.apache.org/msg09335.html http://marc.theaimsgroup.com/?l=tomcat-userm=106193808515738w=2 We changed configuration of Tomcat and Apache Web Server to be in sync. Few days passed after fix's been placed, but it looks ok now. Hope it'll help you. Cheers, Vasily On 5/11/06, zhann [EMAIL PROTECTED] wrote: Hello. We are having a strange Tomcat issue on one of our client's machines. The problem is that it shuts down randomly. There is nothing in the Tomcat Log to indicate why this is occuring, and the Windows Event Manager simply states that the process shut down unexpectedly. We have tried recreating this problem in-house, but have absolutely no luck. We are running tomcat 5.x and Java 1.4.x. The machine that this is installed on is Windows 2003 with all the latest updates. One other thing to note, this installation of tomcat is using Load ballancing. If anyone can point me in a direction of where to look, it would be very helpful. I have scoured the internet and the newsgroups but can't find a similar problem anywhere. Thanks in advance Dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
InstanceAlreadyExistsException on Tomcat load
Hello, Every time we run tomcat (4.1.31) there is an error in logs: = 2006-05-08 10:46:34,762 [TP-Processor23] Registry ERROR - Error registering Catalina:type=RequestProcessor,worker=jk-8009,name=JkRequest25 javax.management.InstanceAlreadyExistsException: Catalina:type=RequestProcessor,worker=jk-8009,name=JkRequest25 at mx4j.server.MBeanServerImpl.register(MBeanServerImpl.java:1123) at mx4j.server.MBeanServerImpl.registerImpl(MBeanServerImpl.java:1054) at mx4j.server.MBeanServerImpl.registerMBeanImpl(MBeanServerImpl.java:1002) at mx4j.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:978) at org.apache.commons.modeler.Registry.registerComponent(Registry.java:871) at org.apache.jk.common.ChannelSocket.registerRequest(ChannelSocket.java:436) at org.apache.jk.common.HandlerRequest.decodeRequest(HandlerRequest.java:443) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:352) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:675) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) at java.lang.Thread.run(Thread.java:534) 2006-05-08 10:46:34,764 [TP-Processor23] ChannelSocket WARN - Error registering request = What does it mean? Thank you. Regards, Vasily - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat 4.1.13 dies every 3-4 days
Hello, We are running J2EE web-application under Apache Server/Tomcat 4.1.31 on Linux. At any point of time we've got around 250 active open sessions and around 100 active threads running on server. The problem is that tomcat occasionally gets dead every 3-4 days without reporting any error to logs. There are 2Gb of memory allocated to tomcat. And memory usage is normally 5-10%. Some logs and server.xml attached. I can not reproduce this in the dev environment. Logs: Here is the error from the mod_jk.log: === [Mon May 08 10:25:14 2006] worker1 appl.company.com.au 0.004600 [Mon May 08 10:25:15 2006] worker1 appl.company.com.au 0.002706 [Mon May 08 10:25:15 2006] worker1 appl.company.com.au 0.013406 [Mon May 08 10:25:15 2006] worker1 appl.company.com.au 0.008658 [Mon May 08 10:25:15 2006] worker1 appl.company.com.au 0.002049 [Mon May 08 10:25:16 2006] worker1 appl.company.com.au 0.335327 [Mon May 08 10:25:16 2006] worker1 appl 0.009130 [Mon May 08 10:25:16 2006] worker1 appl.company.com.au 1.030997 [Mon May 08 10:25:16 2006] worker1 appl 0.008127 [Mon May 08 10:25:16 2006] worker1 appl 0.019742 [Mon May 08 10:25:16 2006] worker1 appl 0.007065 [Mon May 08 10:25:16 2006] worker1 appl.company.com.au 4.910941 [Mon May 08 10:25:17 2006] worker1 appl.company.com.au 6.059512 [Mon May 08 10:25:18 2006] [info] ajp_process_callback::jk_ajp_common.c (1363): Connection aborted or network problems [Mon May 08 10:25:18 2006] [info] ajp_service::jk_ajp_common.c (1706): Receiving from tomcat failed, because of client error without recovery in send loop 0 [Mon May 08 10:25:18 2006] worker1 appl.company.com.au 10.370808 [Mon May 08 10:25:18 2006] [info] jk_handler::mod_jk.c (1968): Aborting connection for worker=worker1 [Mon May 08 10:25:18 2006] worker1 appl.company.com.au 2.020834 [Mon May 08 10:25:18 2006] worker1 appl.company.com.au 2.062616 [Mon May 08 10:25:18 2006] [info] ajp_process_callback::jk_ajp_common.c (1363): Connection aborted or network problems [Mon May 08 10:25:18 2006] [info] ajp_service::jk_ajp_common.c (1706): Receiving from tomcat failed, because of client error without recovery in send loop 0 [Mon May 08 10:25:18 2006] worker1 appl.company.com.au 7.267761 [Mon May 08 10:25:18 2006] [info] jk_handler::mod_jk.c (1968): Aborting connection for worker=worker1 [Mon May 08 10:25:20 2006] worker1 appl.company.com.au 1.804931 [Mon May 08 10:25:20 2006] [info] ajp_process_callback::jk_ajp_common.c (1363): Connection aborted or network problems [Mon May 08 10:25:20 2006] [info] ajp_service::jk_ajp_common.c (1706): Receiving from tomcat failed, because of client error without recovery in send loop 0 [Mon May 08 10:25:20 2006] worker1 appl.company.com.au 5.307884 [Mon May 08 10:25:20 2006] [info] jk_handler::mod_jk.c (1968): Aborting connection for worker=worker1 [Mon May 08 10:25:20 2006] worker1 appl.company.com.au 7.851162 [Mon May 08 10:25:21 2006] worker1 appl.company.com.au 0.229151 [Mon May 08 10:25:21 2006] [info] ajp_process_callback::jk_ajp_common.c (1363): Connection aborted or network problems [Mon May 08 10:25:21 2006] [info] ajp_service::jk_ajp_common.c (1706): Receiving from tomcat failed, because of client error without recovery in send loop 0 [Mon May 08 10:25:21 2006] worker1 appl.company.com.au 13.170979 [Mon May 08 10:25:21 2006] [info] jk_handler::mod_jk.c (1968): Aborting connection for worker=worker1 [Mon May 08 10:25:25 2006] worker1 appl.company.com.au 6.087992 [Mon May 08 10:25:25 2006] worker1 appl.company.com.au 0.006206 [Mon May 08 10:25:25 2006] worker1 appl.company.com.au 11.215213 [Mon May 08 10:25:25 2006] worker1 appl.company.com.au 1.396763 [Mon May 08 10:25:26 2006] [error] ajp_connection_tcp_get_message::jk_ajp_common.c (949): ERROR: can't receive the response message from tomcat, network problems or tomcat is down (127.0.0.1:8009), err=-2 [Mon May 08 10:25:26 2006] [error] ajp_get_reply::jk_ajp_common.c (1479): Tomcat is down or network problems. No response has been sent to the client (yet) [Mon May 08 10:25:26 2006] [info] ajp_service::jk_ajp_common.c (1696): Receiving from tomcat failed, recoverable operation attempt=0 [Mon May 08 10:25:26 2006] [info] ajp_service::jk_ajp_common.c (1724): Sending request to tomcat failed, recoverable operation attempt=1 [Mon May 08 10:25:26 2006] [info] jk_open_socket::jk_connect.c (433): connect to 127.0.0.1:8009 failed with errno=111 [Mon May 08 10:25:26 2006] [info] ajp_connect_to_endpoint::jk_ajp_common.c (877): Failed connecting to tomcat. Tomcat is probably not started or is listening on the wrong host/port (127.0.0.1:8009). Failed errno = 111 [Mon May 08 10:25:26 2006] [info] ajp_send_request::jk_ajp_common.c (1227): Error connecting to the Tomcat process. [Mon May 08 10:25:26 2006] [info] ajp_service::jk_ajp_common.c (1724): Sending request to tomcat failed, recoverable operation attempt=2 [Mon May 08 10:25:26 2006] [info] jk_open_socket::jk_connect.c
Re: Tomcat 4.1.13 dies every 3-4 days
This is an update from our system administrator:
From what I can tell from the errors and the research I have done the
ajp_process_callback from the jk_ajp_common.c function is failing
because it is not recieving a close code from the apache instance -
possibly when a sender (browser) stopped sending data before the end -
certainly in a big post. This means that the client closed the browser
before all data has been set (sent). There is probably a setting
somewhere in tomcat that handles this.
This is the section of code from jk_ajp_common.c that produces this
error:
if ((len = ajp_read_fully_from_server(r, read_buf, len)) 0) {
jk_log(l, JK_LOG_INFO,
ERROR: receiving data from client failed.
Connection aborted or network problems\n);
return JK_CLIENT_ERROR;
}
What is that setting somewhere in tomcat?
Thank you.
Regards,
Vasily
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
