[
https://issues.apache.org/jira/browse/UIMA-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik closed UIMA-1649.
-------------------------------
Resolution: Fixed
Modified to define LOG4J_CONFIG_FILE in case the UIMA AS is not installed. It
is being set to a NO OP. It is only done to satisfy java command line parser.
The change is shown below:
@rem Check if Uima AS is installed, and if so set the default log4j
configuration file
@if EXIST "%UIMA_HOME%"\as_config (set
LOG4J_CONFIG_FILE=-Dlog4j.configuration=file:%UIMA_HOME%\as_config\log4j.properties)
else (set LOG4J_CONFIG_FILE=-DNoOp)
> 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.
