Ajp13 connector doesn't start listening on port 8009
Platform: Intel PIII, debian testing/unstable (sarge) Blackdown JDK 1.3.1 (j2sdk 1.3.1.0b-2), tomcat4 4.1.16-1, apache 1.3.26-1.1, apache-ssl 1.3.26+1.48-2 My problem is that when I do /etc/init.d/tomcat4 start there is nothing listening on port 8009. Or rather: there is _sometimes_ nothing listening on port 8009. When I have started and stopped tomcat and apache and apache-ssl, I have sometimes been able to find something listening on port 8009. I haven't changed anything in the configuration for this to happen. Just started and stopped services. But the listening to port 8009 has gone away as mysteriously as it appeared. I haven't found anything conclusive in the logs about this. There seems to be stuff in /var/log/tomcat4/catalina.out related to Ajp13, but I can't make sense of it (see log fragments below). Has anyone else seen this, or similar behaviour? I have used the commands lsof | grep 8009 and telnet localhost 8009 to determine if something is listening to port 8009. Right now the first return no matches, and the latter prints out: Trying 127.0.0.1... telnet: Unable to connect to remote host: Connection refused I have tried both the Coyote Ajp13 connector, with the following in server.xml: And the old Ajp13 connector with the following config: But the behaviour is the same. I have wondered if there is a problem with both apache and apache-ssl accessing the same Ajp13 connector in tomcat. But I've stopped apache-ssl a while back, and I still haven't seen any change in the behaviour. Thanx! - Steinar Log fragments. The last things that mention "Ajp" in /var/log/tomcat4/catalina.out: [...] 2371 [main] INFO common.ChannelSocket - JK2: ajp13 listening on tcp port 8009 2483 [main] INFO server.JkMain - Jk running ID=0 time=46/168 config=/usr/share/tomcat4/conf/jk2.properties [ Closing connection to 172.21.206.140:2809 ] [ Closing connection to 127.0.0.1:2809 ] [ Closing connection to 172.21.206.140:1221 ] 350125 [Thread-4] WARN common.ChannelSocket - server has closed the current connection (-1) 350306 [Thread-12] WARN common.ChannelSocket - server has closed the current connection (-1) 356237 [Thread-12] WARN common.ChannelSocket - server has closed the current connection (-1) 356266 [Thread-4] WARN common.ChannelSocket - server has closed the current connection (-1) 362458 [Thread-4] WARN common.ChannelSocket - server has closed the current connection (-1) 362490 [Thread-12] WARN common.ChannelSocket - server has closed the current connection (-1) 364300 [Thread-6] WARN common.ChannelSocket - server has closed the current connection (-1) 368480 [Thread-11] WARN common.ChannelSocket - server has closed the current connection (-1) 368768 [Thread-4] WARN common.ChannelSocket - server has closed the current connection (-1) 374591 [Thread-12] WARN common.ChannelSocket - server has closed the current connection (-1) 374679 [Thread-11] WARN common.ChannelSocket - server has closed the current connection (-1) 415008 [Thread-5] WARN common.ChannelSocket - server has closed the current connection (-1) [...] Call org.apache.struts.action.ActionServlet.addServletMapping(action/java.lang.String,*.do/java.lang.String) 3257 [main] INFO common.ChannelSocket - JK2: ajp13 listening on localhost/127.0.0.1:8009 3430 [main] INFO server.JkMain - Jk running ID=0 time=11/227 config=/usr/share/tomcat4/conf/jk2.properties WebappClassLoader: Resource '/WEB-INF/classes/com/tandbergtv/idl/TPS/PortalServiceOperations.class' was modified; Date is now: Wed Jan 08 12:49:51 CET 2003 Was: Tue Jan 07 12:39:32 CET 2003 [...] 2614852 [Thread-8] ERROR common.MsgAjp - BAD packet signature 65524 ff f4 ff fd 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00
Ajp13 connector doesn't start listening on port 8009
Platform: Intel PIII, debian testing/unstable (sarge) Blackdown JDK 1.3.1 (j2sdk 1.3.1.0b-2), tomcat4 4.1.16-1, apache 1.3.26-1.1, apache-ssl 1.3.26+1.48-2 My problem is that when I do /etc/init.d/tomcat4 start there is nothing listening on port 8009. Or rather: there is _sometimes_ nothing listening on port 8009. When I have started and stopped tomcat and apache and apache-ssl, I have sometimes been able to find something listening on port 8009. I haven't changed anything in the configuration for this to happen. Just started and stopped services. But the listening to port 8009 has gone away as mysteriously as it appeared. I haven't found anything conclusive in the logs about this. There seems to be stuff in /var/log/tomcat4/catalina.out related to Ajp13, but I can't make sense of it (see log fragments below). Has anyone else seen this, or similar behaviour? I have used the commands lsof | grep 8009 and telnet localhost 8009 to determine if something is listening to port 8009. Right now the first return no matches, and the latter prints out: Trying 127.0.0.1... telnet: Unable to connect to remote host: Connection refused I have tried both the Coyote Ajp13 connector, with the following in server.xml: And the old Ajp13 connector with the following config: But the behaviour is the same. I have wondered if there is a problem with both apache and apache-ssl accessing the same Ajp13 connector in tomcat. But I've stopped apache-ssl a while back, and I still haven't seen any change in the behaviour. Thanx! - Steinar Log fragments. The last things that mention "Ajp" in /var/log/tomcat4/catalina.out: [...] 2371 [main] INFO common.ChannelSocket - JK2: ajp13 listening on tcp port 8009 2483 [main] INFO server.JkMain - Jk running ID=0 time=46/168 config=/usr/share/tomcat4/conf/jk2.properties [ Closing connection to 172.21.206.140:2809 ] [ Closing connection to 127.0.0.1:2809 ] [ Closing connection to 172.21.206.140:1221 ] 350125 [Thread-4] WARN common.ChannelSocket - server has closed the current connection (-1) 350306 [Thread-12] WARN common.ChannelSocket - server has closed the current connection (-1) 356237 [Thread-12] WARN common.ChannelSocket - server has closed the current connection (-1) 356266 [Thread-4] WARN common.ChannelSocket - server has closed the current connection (-1) 362458 [Thread-4] WARN common.ChannelSocket - server has closed the current connection (-1) 362490 [Thread-12] WARN common.ChannelSocket - server has closed the current connection (-1) 364300 [Thread-6] WARN common.ChannelSocket - server has closed the current connection (-1) 368480 [Thread-11] WARN common.ChannelSocket - server has closed the current connection (-1) 368768 [Thread-4] WARN common.ChannelSocket - server has closed the current connection (-1) 374591 [Thread-12] WARN common.ChannelSocket - server has closed the current connection (-1) 374679 [Thread-11] WARN common.ChannelSocket - server has closed the current connection (-1) 415008 [Thread-5] WARN common.ChannelSocket - server has closed the current connection (-1) [...] Call org.apache.struts.action.ActionServlet.addServletMapping(action/java.lang.String,*.do/java.lang.String) 3257 [main] INFO common.ChannelSocket - JK2: ajp13 listening on localhost/127.0.0.1:8009 3430 [main] INFO server.JkMain - Jk running ID=0 time=11/227 config=/usr/share/tomcat4/conf/jk2.properties WebappClassLoader: Resource '/WEB-INF/classes/com/tandbergtv/idl/TPS/PortalServiceOperations.class' was modified; Date is now: Wed Jan 08 12:49:51 CET 2003 Was: Tue Jan 07 12:39:32 CET 2003 [...] 2614852 [Thread-8] ERROR common.MsgAjp - BAD packet signature 65524 ff f4 ff fd 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 00
