[
https://issues.apache.org/jira/browse/UIMA-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779685#action_12779685
]
Jörn Kottmann commented on UIMA-1649:
-------------------------------------
I kind of wonder if runUimaClass.sh is the right place, what happens if the
properties file is not there ?
That would be the case when someone runs uima without uima as.
Wouldn't it be a better place to set the UIMA_JVM_OPTS variable in the
deployAsyncService.sh/bat script ?
And in the test I did I notice that the log4j.properties file caused an error,
because it
somehow could not write to the log file, because there was something wrong with
the path to it.
Maybe that is not true on windows, only tested on Ubuntu.
Well, right now I do not have access to our cluster, I will test your changes
tomorrow when
I am back at the office and comment again on this issue.
> 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.
