You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jörn Kottmann (JIRA)" <ui...@incubator.apache.org> on 2009/10/30 22:31:59 UTC
[jira] Created: (UIMA-1649) deployAsyncService.sh log4j warnings
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.
[jira] Commented: (UIMA-1649) deployAsyncService.sh log4j warnings
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773233#action_12773233 ]
Marshall Schor commented on UIMA-1649:
--------------------------------------
The appenders are specified in a .properties file. Any classes mentioned in that file are loaded in a very particular class loader, not the one you think. They are loaded in the 1st class loader set up by the initial "java" startup command (approximately). Can you provide information about how you started java, and what the log properties file specified as appenders, and whether or not those classes were visible on that initial class loader.
The class loader used, for Sun JVMs is the one obtained by ClassLoader.getSystemClassLoader(). For IBM Java 5 , it's a related one, but not necessarily that exact one.
Also, were you using a version of UIMA after the fix in UIMA-1631 which corrected an issue with the new uima jar loader/runner with respect to this?
> 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.
[jira] Commented: (UIMA-1649) deployAsyncService.sh log4j warnings
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780000#action_12780000 ]
Marshall Schor commented on UIMA-1649:
--------------------------------------
ACTIVEMQ_BASE purpose is to allow multiple brokers to share an activemq_home, but have separate configurations. See http://issues.apache.org/activemq/browse/AMQ-997. Looks like the default scripts for active mq set this == activemq home. We probably need to set it in our use of activemq in our various scripts, more consistently. (It is set in startBroker).
> 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.
[jira] Commented: (UIMA-1649) deployAsyncService.sh log4j warnings
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ 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.
[jira] Commented: (UIMA-1649) deployAsyncService.sh log4j warnings
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776639#action_12776639 ]
Marshall Schor commented on UIMA-1649:
--------------------------------------
I tried also adding to the CLASSPATH a folder containing one file - log4j.xml with a standard log-to-the-console configuration, and it started up nicely without any errors related to log4j.
I guess what's happening is that the spring framework is using log4j, and the user can set up this logging if they want/need to. I'm not sure what the "correct" behavior should be for UIMA-AS, here, though.
> 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.
[jira] Closed: (UIMA-1649) deployAsyncService.sh log4j warnings
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik closed UIMA-1649.
-------------------------------
Resolution: Fixed
> 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.
Re: [jira] Commented: (UIMA-1649) deployAsyncService.sh log4j warnings
Posted by Marshall Schor <ms...@schor.com>.
Jörn Kottmann (JIRA) wrote:
> [ 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.
>
file permissions issue? There was a recent change which set the
permissions to read-only for group/world for uima files...
-Marshall
> 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 ...
>>
>
>
[jira] Commented: (UIMA-1649) deployAsyncService.sh log4j warnings
Posted by "Jörn Kottmann (JIRA)" <ui...@incubator.apache.org>.
[ 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.
[jira] Commented: (UIMA-1649) deployAsyncService.sh log4j warnings
Posted by "Jörn Kottmann (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773547#action_12773547 ]
Jörn Kottmann commented on UIMA-1649:
-------------------------------------
Could it be that we simply missing a log4.properties file ?
If its set with "-Dlog4j.configuration=file:$UIMA_HOME/as_config/log4j.properties" it throws an exception related
to a log file which cannot be accessed, but that might be ok if this log4j.properties is used by activemq only.
> 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.
[jira] Closed: (UIMA-1649) deployAsyncService.sh log4j warnings
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ 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.
[jira] Commented: (UIMA-1649) deployAsyncService.sh log4j warnings
Posted by "Jörn Kottmann (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780572#action_12780572 ]
Jörn Kottmann commented on UIMA-1649:
-------------------------------------
Thanks, seems to work now :-)
> 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.
[jira] Reopened: (UIMA-1649) deployAsyncService.sh log4j warnings
Posted by "Jörn Kottmann (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jörn Kottmann reopened UIMA-1649:
---------------------------------
I updated my local workspace and now get the following exception when starting on Ubuntu Linux 9.10:
joern@karkand:~/uima-dev3/uimaj-distr/target/apache-uima$ bin/deployAsyncService.sh /home/joern/Infopaq/DTSearch/desc/Deploy_DTSearch.xml
log4j:ERROR setFile(null,true) call failed.
java.io.FileNotFoundException: /activemq-data/activemq.log (No such file or directory)
at java.io.FileOutputStream.openAppend(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:177)
at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
at org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
at org.apache.log4j.RollingFileAppender.setFile(RollingFileAppender.java:165)
at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:163)
at org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:256)
at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:132)
at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:96)
at org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:654)
at org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:612)
at org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:509)
at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:415)
at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:441)
at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:468)
at org.apache.log4j.LogManager.<clinit>(LogManager.java:122)
at org.apache.log4j.Category.getInstance(Category.java:519)
at org.apache.commons.logging.impl.Log4JCategoryLog.<init>(Log4JCategoryLog.java:100)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:502)
at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:285)
at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:255)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:381)
at org.springframework.util.ClassUtils.<clinit>(ClassUtils.java:67)
at org.springframework.core.io.DefaultResourceLoader.<init>(DefaultResourceLoader.java:52)
at org.springframework.context.support.AbstractApplicationContext.<init>(AbstractApplicationContext.java:184)
at org.springframework.context.support.AbstractRefreshableApplicationContext.<init>(AbstractRefreshableApplicationContext.java:80)
at org.springframework.context.support.AbstractXmlApplicationContext.<init>(AbstractXmlApplicationContext.java:58)
at org.springframework.context.support.FileSystemXmlApplicationContext.<init>(FileSystemXmlApplicationContext.java:91)
at org.springframework.context.support.FileSystemXmlApplicationContext.<init>(FileSystemXmlApplicationContext.java:77)
at org.apache.uima.adapter.jms.activemq.SpringContainerDeployer.deploy(SpringContainerDeployer.java:437)
at org.apache.uima.adapter.jms.service.UIMA_Service.deploy(UIMA_Service.java:169)
at org.apache.uima.adapter.jms.service.UIMA_Service.main(UIMA_Service.java:391)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.uima.bootstrap.UimaBootstrap.main(UimaBootstrap.java:98)
A short look at the specified log4j.properties file:
log4j.appender.out.file=${activemq.base}/activemq-data/activemq.log
It seems to that activemq.base is just an emtpy string and then it can not write
the log file because on my machine is no /activemq-data directory.
Would it be possible to write all log messages into the uima.log file ?
I noticed that log messages from activemq do not end up in that file.
> 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.
[jira] Commented: (UIMA-1649) deployAsyncService.sh log4j warnings
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ 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 ]
then
LOG4J_CONFIG_FILE=-Dlog4j.configuration=file:$UIMA_HOME/as_config/log4j.properties
fi
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 variable.
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.
[jira] Commented: (UIMA-1649) deployAsyncService.sh log4j warnings
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779598#action_12779598 ]
Jerry Cwiklik commented on UIMA-1649:
-------------------------------------
To silence this warning, I've modified runUimaClass.bat. Taking suggestion from Jorn, a one liner change was:
@rem Set default JVM opts
@set UIMA_JVM_OPTS=%UIMA_JVM_OPTS% -Dlog4j.configuration=file:%UIMA_HOME%/as_config/log4j.properties -Xms128M -Xmx800M
This seems to fix the problem.
> 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.