When i have started My IS i am getting an error like this that is to initialize the log4j properly, Waht is this log4j,what is it going to do and how we can initialize it...??? please rply me....
My server log is as follows…
Nov 17, 2010 10:33:54 AM com.webMethods.sc.config.ConfigurationLogger log
INFO: Out-of-band file changes will be monitored every ‘60000’ milliseconds
log4j is pretty much industry standard by apache org, webMethods used the same for different audit logs say server logs, deployer logs, installer log, jdbc etc…
from the error it seems that log4j.jar file is missing from your installation image… which should be available in \softwareAG\Common\lib\ext directory…please check!
hmmm error says log4j.jar was not initialised, did you have multiple versions of this jar in system… also cross check the log4j property file in config\caching directory…
What do you mean by multiple versions of log4j , according to my knowledge i think there are no multiple versions of this file in my sytem, how can i fix this and i am getting another error as [COLOR="DarkOrange"]Error in recoverJoinTimers: java.lang.NullPointerException[/color]
did you checked the log4j.jar in IS/common/lib/ext/jars there… make sure you that you have the jar file there and your classpath is properly set in environment variable (through setenvironment.bat) …
Hey… I could see log4j.jar in the path C:\webMethods7\common\lib\ext.
Also I ran serEnv.bat located at C:\webMethods7\common\db\bin.
I got the following.
The problem is resolved after restarting my system with the below settings in server.bat file.
set JAVA_MIN_MEM=512M
set JAVA_MAX_MEM=1G
set JAVA_MAX_PERM_SIZE=128M
Probably, a Max_mem of 512M also might work. will ty and let u know.
I think setting the class path is the key, and restarting the system after that would suffice.
I experienced the same problem ages ago (though, I don’t recall seeing any NullPointerException in my logs), but I didn’t have to do anything in the end to resolve it. All I needed to do, was to wait until the server start up process is fully completed. I had to wait for about 5 minutes in the end… The issue may be memory-related?? Did you get any useful solution in the end??