Eclipse Community Forums: Eclipse Process Manager (Stardust)

Home » Archived » Eclipse Process Manager (Stardust) » Unable to log in stardust(Logging)

Unable to log in stardust [message #909034]

Thu, 06 September 2012 08:51

Eclipse User

Hi,

I'm using the latest stardust codebase and my application (war) file is deployed in tomcat 6.0.29 and JDK 1.7.0_03.

I do get logging information in console, however there are no logs written to log directory.

My entries in carnot.properties is
Logging.Directory = C:/Projects/apache-tomcat-6.0.29_2/logs
Logging.LogLevel = ALL

Entries in log4j.properties is

log4j.rootCategory=DEBUG, default, console

log4j.appender.default=org.apache.log4j.DailyRollingFileAppender
log4j.appender.default.File=C:/Projects/apache-tomcat-6.0.29_2/logs/output.log
log4j.appender.default.DatePattern='.'yyyy-MM-dd
log4j.appender.default.layout = org.apache.log4j.PatternLayout
log4j.appender.default.layout.ConversionPattern = %d{yyyy-MM-dd HH:mm:ss} %-5.5p- [%-15.15t] %-25.25c{1} - %m%n
log4j.appender.default.Threshold=DEBUG

### direct log messages to stdout ###
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.Target=System.out
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=[%d{yyyy-MM-dd HH:mm:ss}]<%p> <%F:%L> - %m%n
log4j.appender.stdout.Threshold=DEBUG

### SPRING LOGGING ###
log4j.logger.org.springframework.aop.framework=DEBUG
log4j.logger.org.springframework.beans.factory=DEBUG
log4j.logger.org.springframework.web.context=DEBUG
log4j.logger.org.springframework.ws=DEBUG
log4j.logger.org.springframework.xml=DEBUG

log4j.appender.console = org.apache.log4j.ConsoleAppender
log4j.appender.console.layout = org.apache.log4j.PatternLayout
log4j.appender.console.layout.ConversionPattern = %d{yyyy-MM-dd HH:mm:ss} %-5.5p [%-10.10t] %-25.25c{1} - %m%n
log4j.appender.console.Threshold=DEBUG

log4j.category.com.icesoft.faces.application.ViewRootStateManagerImpl=DEBUG
log4j.logger.org.eclipse.stardust.engine.core.runtime.beans.interceptors.DebugInterceptor=DEBUG
log4j.logger.org.eclipse.stardust.engine.core.runtime.logging.Security=DEBUG
log4j.category.org=DEBUG
log4j.category.com=DEBUG
log4j.category.com.infinity.bpm.modeling.vcsconnector.subclipse=DEBUG
log4j.category.org.eclipse=DEBUG
log4j.category.com.infinity.bpm=DEBUG
log4j.category.org.eclipse.stardust.engine.runtime=DEBUG
log4j.category.org.eclipse.stardust.reporting=DEBUG
log4j.category.org.eclipse.datatools.connectivity.oda=DEBUG

I have commons-logging-1.1.1.jar, log4j-1.2.15.jar, slf4j-log4j12-1.5.11.jar in my WEB-INF\lib directory.

I suspect the problem is with my logging entries in log4j, any help over would be appreciated. Thank you.

Re: Unable to log in stardust [message #911920 is a reply to message #909034]

Wed, 12 September 2012 11:32

Eclipse User

Hi,

Assuming that this war is deployed on stand alone tomcat, can you check the following:

1) If the log file is generated in the tomcat\bin folder
2) If the deployment is within RAD can you check the eclipse base folder (where the eclipse.exe is located) if the log file is generated.
3) Check the folder permissions where you are trying to output the logs
4) Not sure if the two console appenders would make a difference in the log4j.properties, can you remove the spring defined console appenders and check

Re: Unable to log in stardust [message #912365 is a reply to message #911920]

Thu, 13 September 2012 08:41

Eclipse User

I found the problem. One of the jar files (jxls-reader-0.9.6.jar) had a file log4j.xml and that was getting loaded first and used as log4j logging property file and hence we did not receive the logs. I've removed the log4j.xml from the jar and it works perfectly fine.

Thank you!!

Previous Topic:	create schema in version 6.0.4 for mysql 5.5.27
Next Topic:	Accessing Configuration Variables in a Java class

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 11:44:24 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter