Hi
i am getting log4j error as below. can you please
provide pointers if any to fix this issue.
log4j:ERROR Could not connect to remote log4j server
at [localhost]. We will try again later.
java.net.ConnectException: Connection refused
at
java.net.PlainSocketImpl.socketConnect(Native
There are methods for isDebugEnabled and isInfoEnabled, but how do you
check for isFatalEnabled or any of the other levels? I've used
isEnabledFor(Priority.level), but Priority.FATAL and the rest are
deprecated, so what's the best way to test for the unrepresented
isLevelEnabled levels?
Thanks,
Bret Schuhmacher wrote:
There are methods for isDebugEnabled and isInfoEnabled, but how do you
check for isFatalEnabled or any of the other levels? I've used
isEnabledFor(Priority.level), but Priority.FATAL and the rest are
deprecated, so what's the best way to test for the unrepresented
Hi Scott,
thanks for your consideration.
below are my appenders and chainsaw reciever config files.
appenders in log4j config files,
#TEST
#Level=ALL, Facility=USER
log4j.debug=true
log4j.rootLogger=all,Chainsaw1,Chainsaw2,STDOUT,R
It's best to check for isDebugEnabled, etc., externally if performance
is a consideration, since an external test avoids the time-consuming
concatenating and formatting strings if it won't be used. If you use
the test inside log4j, you will pay the penalty for these operations,
even if they
Hi
I am trying to configure log4j to log to Chainsaw on a remote host using
Multicast.
I have a MultiCastReceiver set up on Chainsaw and I have the following
config on my client
appender name=Multicast class=org.apache.log4j.net.MulticastAppender
param name=RemoteHost value=232.10.0.0/
There is a bug in this appender that is preventing it from processing
events (as you mentioned, the log4j framework thinks the appender is
inactive).
I'll make a commit to fix this on the trunk.
If you have the code locally and would like to fix it, after the
constructor of the MulticastSocket
