[
https://issues.apache.org/jira/browse/UIMA-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773233#action_12773233
]
Marshall Schor commented on UIMA-1649:
--------------------------------------
The appenders are specified in a .properties file. Any classes mentioned in
that file are loaded in a very particular class loader, not the one you think.
They are loaded in the 1st class loader set up by the initial "java" startup
command (approximately). Can you provide information about how you started
java, and what the log properties file specified as appenders, and whether or
not those classes were visible on that initial class loader.
The class loader used, for Sun JVMs is the one obtained by
ClassLoader.getSystemClassLoader(). For IBM Java 5 , it's a related one, but
not necessarily that exact one.
Also, were you using a version of UIMA after the fix in UIMA-1631 which
corrected an issue with the new uima jar loader/runner with respect to this?
> 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.
