[
https://issues.apache.org/jira/browse/UIMA-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776639#action_12776639
]
Marshall Schor commented on UIMA-1649:
--------------------------------------
I tried also adding to the CLASSPATH a folder containing one file - log4j.xml
with a standard log-to-the-console configuration, and it started up nicely
without any errors related to log4j.
I guess what's happening is that the spring framework is using log4j, and the
user can set up this logging if they want/need to. I'm not sure what the
"correct" behavior should be for UIMA-AS, here, though.
> deployAsyncService.sh log4j warnings
> -------------------------------------
>
> Key: UIMA-1649
> URL: https://issues.apache.org/jira/browse/UIMA-1649
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.3AS
> Reporter: Jörn Kottmann
> Priority: Trivial
> Fix For: 2.3AS
>
>
> When starting with deployAsyncService.sh there is log4j warning:
> log4j:WARN No appenders could be found for logger
> (org.springframework.context.support.FileSystemXmlApplicationContext).
> log4j:WARN Please initialize the log4j system properly.
> Maybe I am doing something wrong ? Otherwise I think a default
> log4j.properties should be provided ...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
