Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 337667

Summary:	[Discovery][ZooDiscovery] log4j not initialized when starting log4j
Product:	[RT] ECF	Reporter:	Wim Jongman <wim.jongman>
Component:	ecf.discovery	Assignee:	Wim Jongman <wim.jongman>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	bugs.eclipse.org, slewis
Version:	unspecified	Keywords:	helpwanted
Target Milestone:	3.7.0
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Wim Jongman

2011-02-20 12:15:50 EST

the log4j initialization doesn't seem to be configured...i.e.

log4j:WARN No appenders could be found for logger (org.apache.zookeeper.server.ZooKeeperServer).
log4j:WARN Please initialize the log4j system properly.

Comment 1 Wim Jongman

2011-03-05 10:38:37 EST

moving to 3.6

Comment 2 Markus Kuppe

2011-04-13 23:44:54 EDT

Would this be a candidate for ECF 3.5.1?

Comment 3 Scott Lewis

2011-05-11 10:51:33 EDT

Wim...should the target milestone for this be changed to 3.6...or should it stay with 3.5.1?

Comment 4 Wim Jongman

2011-05-16 02:15:44 EDT

Moving to 3.6. No time to fix this for 3.5.1 unfort.. I missed this one.

Comment 5 Scott Lewis

2011-08-09 01:27:26 EDT

Setting target to 3.5.2.  It seems to me this could be pretty easily fixed.

Comment 6 Wim Jongman

2011-10-30 15:29:55 EDT

we switched our dependency to the zookeeper implementation that is in orbit. 

closing as invalid

Comment 7 Wim Jongman

2012-12-04 08:42:59 EST

Help Wanted.

Comment 8 Wim Jongman

2013-10-08 16:19:30 EDT

if you get log4j errors then you are probably not running from the root of the server. Please update the (zooserver/eclipse).ini file to point the log4j.properties file to a absolute location.

e.g:

-Dlog4j.configuration=file:/c:/my/folder/log4j.properties