Massively Large Log File

I just noticed that my admin-console.log file is being rapidly filled by the following pair of messages every ten seconds. Any insight as to why and/or how to prevent it would be greatly appreciated. Thanks for the help.

22:45:27.142 TRACE [Acceptor ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=9090]] org.mortbay.util.LogSupport.ignore(LogSupport.java:36) >03> IGNORED

java.net.SocketTimeoutException: Accept timed out

at java.net.PlainSocketImpl.socketAccept(Native Method)

at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)

at java.net.ServerSocket.implAccept(ServerSocket.java:450)

at java.net.ServerSocket.accept(ServerSocket.java:421)

at org.mortbay.util.ThreadedServer.acceptSocket(ThreadedServer.java:432)

at org.mortbay.util.ThreadedServer$Acceptor.run(ThreadedServer.java:634)

22:45:30.214 TRACE [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=9091]]] org.mortbay.util.LogSupport.ignore(LogSupport.java:36) >03> IG

java.net.SocketTimeoutException: Accept timed out

at java.net.PlainSocketImpl.socketAccept(Native Method)

at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)

at java.net.ServerSocket.implAccept(ServerSocket.java:450)

at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.accept(SSLServerSocketImpl.jav a:259)

at org.mortbay.util.ThreadedServer.acceptSocket(ThreadedServer.java:432)

at org.mortbay.util.ThreadedServer$Acceptor.run(ThreadedServer.java:634)

There is already a discussion on this here and possible answer to your question. Hope this is helpful.

Hi,

it may help to disable the debug log file within Wildfire.

LG

It seems there is no solution in that thread for this problem. And, I cannot disable my debug.log file as I reference it on a regular basis. Any other suggestions on this? Gato???

Hi,

I could also think of a fifo called admin-console.log and a Perl script which reads it and filters these TRACE messages and writes clean-admin-console.log. You could also use such a Perl program to rotate this file.

LG

I suppose I could use a Perl script if necessary. However, I am still curious to the nature of this error and how to resolve it properly. Is it a known bug, or perhaps a fault in my configuration? Thanks again for the support.

there have been many posts about the admin-console.log file (39 to be exact) and it seems that when ever this issue comes up no one has an actual solution. the only thing that seems to work is to disable the debug log. you stated that you reference this often, the question would be why? there may be another way to get the information you require.

my question for the jive dev would be is there a system property we could add some where that would disable only the admin-console.log.

you could also attempt disabling the write permissions to the log file, I have suggested this but no one has given me any feedback about it.

according to these you only need to disable the debug log.

http://www.jivesoftware.org/community/thread.jspa?messageID=111472&#111472

http://www.jivesoftware.org/community/thread.jspa?messageID=110258&#110258

http://www.jivesoftware.org/community/thread.jspa?messageID=113479&#113479

http://www.jivesoftware.org/community/thread.jspa?messageID=112998&#112998

no solution

http://www.jivesoftware.org/community/thread.jspa?messageID=116032&#116032

http://www.jivesoftware.org/community/thread.jspa?messageID=109471&#109471

Hey guys,

I just checked in a small improvement that will let you disable the Jetty logging information even when Log.debug is enabled. The property to set is jetty.debug.enabled and should be set to false. You can find the improvement in the next nightly build.

Thanks,

– Gato

Hi Gato,

would you please provide a undocumended.txt file where one can read about all the system properties?

LG