Address already in use & lt; null... is reported when Tomcat is started in Linux.

Address already in use <null... the problem is that the port is occupied, but the first start is successful. After it is disabled, an error is reported when it is restarted. The error code is as follows: 012010-10-24 18:12:23 org. apache. catalina. core. aprLifecycleListener init02Message: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java. library. path:/usr/local/jdk1.5.0 _ 06/jre/lib/i386/server:/usr/local/jdk1.5.0 _ 06/jre/lib/i386 :/Usr/local/jdk1.5.0 _ 06/jre /.. /lib/i386:/opt/sybase/OCS-12_5/lib:/opt/sybase/OCS-12_5/lib3p:/opt/sybase/SQLRemote/lib: /opt/sybase/ASE-12_5/lib:/opt/sybase/OCS-12_5/lib:/opt/sybase/OCS-12_5/lib3p:/opt/sybase/SQLRemote/lib: /opt/sybase/ASE-12_5/lib: 03 www.2cto.com 2010-10-24 18:12:23 org. apache. coyote. http11.Http11Protocol init04Fatal: Error initializing endpoint05java.net. bindException: Address alre Ady in use <null>: 808006 at org.apache.tomcat.util.net. JIoEndpoint. init (JIoEndpoint. java: 502) 07 at org. apache. coyote. http11.Http11Protocol. init (Http11Protocol. java: 176) 08 at org. apache. catalina. connector. connector. initialize (Connector. java: 1058) 09 at org. apache. catalina. core. standardService. initialize (StandardService. java: 677) 10 at org. apache. catalina. core. standardServer. initialize (StandardServer. j Java: 795) 11 at org. apache. catalina. startup. catalina. load (Catalina. java: 530) 12 at org. apache. catalina. startup. catalina. load (Catalina. java: 550) 13 at sun. reflect. nativeMethodAccessorImpl. invoke0 (Native Method) 14 at sun. reflect. nativeMethodAccessorImpl. invoke (NativeMethodAccessorImpl. java: 39) 15 at sun. reflect. delegatingMethodAccessorImpl. invoke (DelegatingMethodAccessorImpl. java: 25) 16 at java. lang. refle Ct. method. invoke (Method. java: 585) 17 at org. apache. catalina. startup. bootstrap. load (Bootstrap. java: 260) 18 at org. apache. catalina. startup. bootstrap. main (Bootstrap. java: 412) 192010-10-24 18:12:23 org. apache. catalina. startup. catalina load20Fatal: Catalina. start21LifecycleException: Protocol handler initialization failed: java.net. bindException: Address already in use <null>: 808022 at org. apache. catalina. Connector. connector. initialize (Connector. java: 1060) 23 at org. apache. catalina. core. standardService. initialize (StandardService. java: 677) 24 at org. apache. catalina. core. standardServer. initialize (StandardServer. java: 795) 25 at org. apache. catalina. startup. catalina. load (Catalina. java: 530) 26 at org. apache. catalina. startup. catalina. load (Catalina. java: 550) 27 at sun. reflect. nativeMethodAccessorImpl. invoke0 (Na Tive Method) 28 at sun. reflect. nativeMethodAccessorImpl. invoke (NativeMethodAccessorImpl. java: 39) 29 at sun. reflect. delegatingMethodAccessorImpl. invoke (DelegatingMethodAccessorImpl. java: 25) 30 at java. lang. reflect. method. invoke (Method. java: 585) 31 at org. apache. catalina. startup. bootstrap. load (Bootstrap. java: 260) 32 at org. apache. catalina. startup. bootstrap. main (Bootstrap. java: 412) 33 www.2cto.com 2010-10- 24 18:12:23 org. apache. catalina. startup. catalina load34Message: Initialization processed in 574 ms. That's because your tomcat has started the closed script that comes with tomcat. Sometimes it seems to have been successfully closed, but it hasn't actually been closed. You can run the following command to view the process list: 1 ps-ef | grep java if the java Process is still running, use the following command to manually close all of them, and then start tomcat. 1 kill-9 pid where the PID must be replaced with the process number. In addition, you can use the command ps-ef | grep java to view five or six processes at the same time. You need to disable them one by one, then restart tomcat and the above error will not be reported. Author: Bairrfhoinn