You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-user@logging.apache.org by Stadelmann Josef <jo...@axa-winterthur.ch> on 2012/08/08 17:33:01 UTC

how can we preventing tomcat to parse log4j on a shutdown cycle?

I have Chainsaw in use, greate tool.

When my Tomcat starts, it parses and executes error free through my
log4j.property file. proofe by debug=true! 
However when I like top stop Tomcat, by matters of Tomcat the same
log4j.properties file is parsed one more time
and hence, the exception below is only nature to ocure. How can I
prenvent it? What can I tell Tomcat's or it's 
shutdown  agent calling tomcat on the shutdown port that no
log4j.properties file is to be parsed?

Josef

log4j:ERROR exception setting timeout, shutting down server socket.
java.net.BindException: address already in use   (errno:48)
        at java.net.PlainSocketImpl.socketBind(Native Method)
        at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:365)
        at java.net.ServerSocket.bind(ServerSocket.java:319)
        at java.net.ServerSocket.<init>(ServerSocket.java:185)
        at java.net.ServerSocket.<init>(ServerSocket.java:97)
        at
org.apache.log4j.net.SocketHubAppender.createServerSocket(SocketHubAppen
der.java:365)
        at
org.apache.log4j.net.SocketHubAppender$ServerMonitor.run(SocketHubAppend
er.java:433)
        at java.lang.Thread.run(Thread.java:619)
Tomcat Logicals and Classpaths are cleared
IA64-2>