uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry Cwiklik (JIRA)" <uima-...@incubator.apache.org>
Subject [jira] Commented: (UIMA-1649) deployAsyncService.sh log4j warnings
Date Thu, 19 Nov 2009 20:57:39 GMT

    [ https://issues.apache.org/jira/browse/UIMA-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780265#action_12780265

Jerry Cwiklik commented on UIMA-1649:

After more discussion, the committed changes are as follows:

the runUimaClass.sh and runUimaClass.bat were modified to include:

if [ -e "$UIMA_HOME"/as_config ] 

the above tests for existence of UIMA AS specific directory, and only if it exists a variable
pointing to log4j property file is set. The launch command was changed to include LOG4J_CONFIG_FILE

Modified default log4j.properties included in the UIMA AS distribution to create a log file
in a directory from which a program is started (current directory).  Also, reduced the log
level in log4j to WARN since at INFO it logs excessively when a broker is not available. It
just spins and logs continuously filling logs quickly.

Let me know if this JIRA can be closed, but dont close it yet since if these changes work
we need to modify README to describe this new variable.

> 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.

View raw message