[
https://issues.apache.org/jira/browse/UIMA-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780132#action_12780132
]
Jerry Cwiklik commented on UIMA-1649:
-------------------------------------
After discussing this with Marshall, for release 2.3.3 I can modify
log4j.properties file found in $UIMA_HOME/as_config to change the path to the
log file. Instead of:
log4j.appender.out.file=${activemq.base}/activemq-data/activemq.log
I propose just using this:
log4j.appender.out.file=activemq.log
This will create activemq.log in the current directory, consistent with where
uima logs are created.
If there are multiple services started, their activemq logging goes to the same
log. Tested this on CentOS and Windows. Jorn please test this on Ubuntu.
I still use this:
@set UIMA_JVM_OPTS=%UIMA_JVM_OPTS%
-Dlog4j.configuration=file:%UIMA_HOME%/as_config/log4j.properties -Xms128M
-Xmx800M
in the runUimaClass.sh. Although, Jorn's point is correct, if someone just
installs uima core (no uima as) and his code needs log4j the above setting will
cause a problem. If this is an issue, we need set
UIMA_JVM_OPTS in all uima_as scripts instead of runUimaClass
> 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.
