[
https://issues.apache.org/jira/browse/UIMA-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764224#action_12764224
]
Burn Lewis commented on UIMA-1607:
----------------------------------
I verified that the log is OK when using an old-style explicit classpath that
exactly matches the one loaded by UimaBootstrap.jar ... so it's not caused by
the order of loading.
> Wrong log formatter used in uima-as
> -----------------------------------
>
> Key: UIMA-1607
> URL: https://issues.apache.org/jira/browse/UIMA-1607
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.3
> Reporter: Burn Lewis
>
> When running the uima-as test described in section 3.4 of the README, the
> uima.log is always produced in the xml format. The problem appears to be
> caused by the bootstrap jar as just before the service start it outputs:
> log4j:WARN No appenders could be found for logger
> (org.springframework.context.support.FileSystemXmlApplicationContext).
> log4j:WARN Please initialize the log4j system properly.
> Perhaps the bootstrap program needs to be in uima-core.jar so it can find the
> specified log formatter: org.apache.uima.internal.util.UIMALogFormatter
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
