Re: Error with SocketHubAppender
If you must configure log4j programmatically, I believe you need to
call activateOptions in each appender.
Can you configure log4j using a config file instead?
Scott
On Mar 28, 2011, at 5:56 AM, Amit Oberoi aobe...@techmahindra.com
wrote:
Hi,
I am new to Log4J and trying to configure my Unit tests with a
SocketHubAppender. My problem is that while executing my tests
though I
am able to receive logs on Chainsaw I am getting below errors for each
test case. Can anyone suggest how to avoid this.
log4j:ERROR exception setting timeout, shutting down server socket.
java.net.SocketException: Unrecognized Windows Sockets error: 0:
JVM_Bind
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$ServerMonitor.run
(SocketHubAppend
er.java:324)
at java.lang.Thread.run(Thread.java:619)
log4j:ERROR exception setting timeout, shutting down server socket.
java.net.SocketException: Unrecognized Windows Sockets error: 0:
JVM_Bind
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$ServerMonitor.run
(SocketHubAppend
er.java:324)
at java.lang.Thread.run(Thread.java:619)
log4j:ERROR exception setting timeout, shutting down server socket.
java.net.SocketException: Unrecognized Windows Sockets error: 0:
JVM_Bind
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$ServerMonitor.run
(SocketHubAppend
er.java:324)
at java.lang.Thread.run(Thread.java:619)
log4j:ERROR exception setting timeout, shutting down server socket.
java.net.SocketException: Unrecognized Windows Sockets error: 0:
JVM_Bind
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$ServerMonitor.run
(SocketHubAppend
er.java:324)
at java.lang.Thread.run(Thread.java:619)
log4j:ERROR exception setting timeout, shutting down server socket.
java.net.SocketException: Unrecognized Windows Sockets error: 0:
JVM_Bind
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$ServerMonitor.run
(SocketHubAppend
er.java:324)
at java.lang.Thread.run(Thread.java:619)
log4j:WARN No appenders could be found for logger (com.btw).
log4j:WARN Please initialize the log4j system properly.
log4j:ERROR exception setting timeout, shutting down server socket.
java.net.SocketException: Unrecognized Windows Sockets error: 0:
JVM_Bind
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$ServerMonitor.run
(SocketHubAppend
er.java:324)
at java.lang.Thread.run(Thread.java:619)
I am using the below code to instantiate the logger.
public class TestLogger {
private Logger log;
private FileAppender appender;
private ConsoleAppender console;
private SocketHubAppender socket;
private HTMLLayout layout;
private PatternLayout pat;
public TestLogger(Class clazz) {
String pattern = %d{dd MMM yyy HH:mm:ss, SSS} - %m%n;
try {
Logger.getRootLogger().setLevel(Level.OFF);
Logger.getLogger(com.btw).setLevel(Level.INFO);
log = Logger.getLogger(clazz);
log.setAdditivity(false);
layout = new HTMLLayout();
layout.setTitle(Log for + clazz.getSimpleName());
appender =
Log4j debug for one method in application
Hi, Just want to check can we set debug for any specific method in the applciation using log4j. This will be very useful if we have this feature in log4j so trying to check on this. I have a application running on production and to check on one very complicated issue want to check if we can set debug for any specific method. Due to volume and performance we dont want to do debug at applciation level on production and we are not able to reproduce that on our test environment. -- View this message in context: http://old.nabble.com/Log4j-debug-for-one-method-in-application-tp31261571p31261571.html Sent from the Log4j - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
Why There isn't a Log File?
I have used log4j before with the property file configuration. For this
new project, I have the XML configuration. The console output seems to be
fine. Any changes on log level and layout will reflect on log messages on
the console right away.
I, however, can't get any log file for some reasons. To my understanding,
to use a log file, I need to use the
log4j-user-subscr...@logging.apache.org class and what is the name is
important.
The followings are the xml configuration and the dtd. Can someone tell me
what is wrong?
?xml version=1.0 encoding=UTF-8?
!-- !DOCTYPE log4j:configuration PUBLIC -//LOGGER log4j.dtd --
!DOCTYPE log4j:configuration PUBLIC -//log4j/log4j Configuration//EN
log4j.dtd
log4j:configuration xmlns:log4j=http://jakarta.apache.org/log4j/;
!-- log4j:configuration debug=true --
!-- Appenders --
appender name=console class=org.apache.log4j.ConsoleAppender
param name=Target value=System.out /
layout class=org.apache.log4j.PatternLayout
param name=ConversionPattern value=%-5p: %c{1}:%L -
%m%n /
/layout
/appender
appender name=file class=org.apache.log4j.RollingFileAppender
param name=maxFileSize value=100KB /
param name=maxBackupIndex value=5 /
param name=File value=c:\myproj\myapp\logs\mylog.log /
param name=Append value=true /
layout class=org.apache.log4j.PatternLayout
param name=ConversionPattern value=%d %-5p [%t] %C{2}
(%F:%L)
- %m%n/
/layout
/appender
!-- Application Loggers --
logger name=com.mycom.myapp
level value=debug /
/logger
!-- 3rdparty Loggers --
...
!-- Root Logger --
root
priority value=warn /
appender-ref ref=console /
/root
/log4j:configuration
?xml version=1.0 encoding=UTF-8 ?
!-- A configuration element consists of optional renderer
elements,appender elements, categories and an optional root
element. --
!ELEMENT log4j:configuration (renderer*, appender*,(category|logger)*,root?,
categoryFactory?)
!-- The threshold attribute takes a level value such that all --
!-- logging statements with a level equal or below this value are --
!-- disabled. --
!-- Setting the debug enable the printing of internal log4j logging --
!-- statements. --
!-- By default, debug attribute is null, meaning that we not do touch --
!-- internal log4j logging settings. The null value for the threshold --
!-- attribute can be misleading. The threshold field of a repository--
!-- cannot be set to null. The null value for the threshold attribute --
!-- simply means don't touch the threshold field, the threshold field --
!-- keeps its old value.--
!ATTLIST log4j:configuration
xmlns:log4j CDATA #FIXED http://jakarta.apache.org/log4j/;
threshold(all|debug|info|warn|error|fatal|off|null) null
debug(true|false|null) null
!-- renderer elements allow the user to customize the conversion of --
!-- message objects to String. --
!ELEMENT renderer EMPTY
!ATTLIST renderer
renderedClass CDATA #REQUIRED
renderingClass CDATA #REQUIRED
!-- Appenders must have a name and a class. --
!-- Appenders may contain an error handler, a layout, optional parameters
--
!-- and filters. They may also reference (or include) other appenders. --
!ELEMENT appender (errorHandler?, param*, layout?, filter*, appender-ref*)
!ATTLIST appender
name ID #REQUIRED
class CDATA #REQUIRED
!ELEMENT layout (param*)
!ATTLIST layout
class CDATA #REQUIRED
!ELEMENT filter (param*)
!ATTLIST filter
class CDATA #REQUIRED
!-- ErrorHandlers can be of any class. They can admit any number of --
!-- parameters. --
!ELEMENT errorHandler (param*, root-ref?, logger-ref*, appender-ref?)
!ATTLIST errorHandler
classCDATA #REQUIRED
!ELEMENT root-ref EMPTY
!ELEMENT logger-ref EMPTY
!ATTLIST logger-ref
ref IDREF #REQUIRED
!ELEMENT param EMPTY
!ATTLIST param
name CDATA #REQUIRED
value CDATA #REQUIRED
!-- The priority class is org.apache.log4j.Level by default --
!ELEMENT priority (param*)
!ATTLIST priority
class CDATA #IMPLIED
value CDATA #REQUIRED
!-- The level class is org.apache.log4j.Level by default --
!ELEMENT level (param*)
!ATTLIST level
class CDATA #IMPLIED
value CDATA #REQUIRED
!-- If no level element is specified, then the configurator MUST not --
!-- touch the level of the named category. --
!ELEMENT category (param*,(priority|level)?,appender-ref*)
!ATTLIST category
class CDATA #IMPLIED
name CDATA
Re: Log4j debug for one method in application
You could set it to debug for a specific class logger without issue, no? Wouldn't you be using that same logger for all methods in the class anyway? Otherwise, create multiple logger named after the class and method and enable debug for the one you care about. Jake On 3/28/2011 1:46 PM, log4jlog4j wrote: Hi, Just want to check can we set debug for any specific method in the applciation using log4j. This will be very useful if we have this feature in log4j so trying to check on this. I have a application running on production and to check on one very complicated issue want to check if we can set debug for any specific method. Due to volume and performance we dont want to do debug at applciation level on production and we are not able to reproduce that on our test environment. - To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
RE: Error with SocketHubAppender
Scott, Many thanks for your prompt response. I tired setting the activateOptions however the problem still persists. I agree that the best way to configure Log4J is to have configuration file however I have requirement to capture logs on per class basis. Is there anyway we can set the FileAppender log file name programmatically where-in putting the remaining configurations in the configuration file. Thanks Amit Oberoi -Original Message- From: Scott Deboy [mailto:scott.de...@gmail.com] Sent: Monday, March 28, 2011 7:15 PM To: Log4J Users List Cc: log4j-user@logging.apache.org Subject: Re: Error with SocketHubAppender If you must configure log4j programmatically, I believe you need to call activateOptions in each appender. Can you configure log4j using a config file instead? Scott On Mar 28, 2011, at 5:56 AM, Amit Oberoi aobe...@techmahindra.com wrote: Hi, I am new to Log4J and trying to configure my Unit tests with a SocketHubAppender. My problem is that while executing my tests though I am able to receive logs on Chainsaw I am getting below errors for each test case. Can anyone suggest how to avoid this. log4j:ERROR exception setting timeout, shutting down server socket. java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind 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$ServerMonitor.run (SocketHubAppend er.java:324) at java.lang.Thread.run(Thread.java:619) log4j:ERROR exception setting timeout, shutting down server socket. java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind 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$ServerMonitor.run (SocketHubAppend er.java:324) at java.lang.Thread.run(Thread.java:619) log4j:ERROR exception setting timeout, shutting down server socket. java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind 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$ServerMonitor.run (SocketHubAppend er.java:324) at java.lang.Thread.run(Thread.java:619) log4j:ERROR exception setting timeout, shutting down server socket. java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind 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$ServerMonitor.run (SocketHubAppend er.java:324) at java.lang.Thread.run(Thread.java:619) log4j:ERROR exception setting timeout, shutting down server socket. java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind 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$ServerMonitor.run (SocketHubAppend er.java:324) at java.lang.Thread.run(Thread.java:619) log4j:WARN No appenders could be found for logger (com.btw). log4j:WARN Please initialize the log4j system properly. log4j:ERROR exception setting timeout, shutting down server socket. java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:365) at java.net.ServerSocket.bind(ServerSocket.java:319) at
