[jira] Reopened: (UIMA-1649) deployAsyncService.sh log4j warnings
[
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:
jo...@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
[jira] Created: (UIMA-1671) UIMA AS client fails to localize exception message when executed in an OSGI server
UIMA AS client fails to localize exception message when executed in an OSGI server -- Key: UIMA-1671 URL: https://issues.apache.org/jira/browse/UIMA-1671 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Reporter: Jörn Kottmann Assignee: Jörn Kottmann Fix For: 2.3AS An UIMA AS client executed in an OSGI server fails to localize exception messages. The uima runtime bundle uses org.apache.uima.internal.util.I18nUtil to localize exception messages, this fails because the runtime bundle cannot see the classpath of the uima as osgi runtime bundle. To solve the issue the classpath of the uima as osgi runtime bundle should be made visible to the uima runtime bundle with Eclipse-RegisterBuddy which fixs the issue in a Spring DM Server. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1671) UIMA AS client fails to localize exception message when executed in an OSGI server
[ https://issues.apache.org/jira/browse/UIMA-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörn Kottmann closed UIMA-1671. --- Resolution: Fixed UIMA AS client fails to localize exception message when executed in an OSGI server -- Key: UIMA-1671 URL: https://issues.apache.org/jira/browse/UIMA-1671 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Reporter: Jörn Kottmann Assignee: Jörn Kottmann Fix For: 2.3AS An UIMA AS client executed in an OSGI server fails to localize exception messages. The uima runtime bundle uses org.apache.uima.internal.util.I18nUtil to localize exception messages, this fails because the runtime bundle cannot see the classpath of the uima as osgi runtime bundle. To solve the issue the classpath of the uima as osgi runtime bundle should be made visible to the uima runtime bundle with Eclipse-RegisterBuddy which fixs the issue in a Spring DM Server. -- 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
[ https://issues.apache.org/jira/browse/UIMA-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1278#action_1278 ] 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
[
https://issues.apache.org/jira/browse/UIMA-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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.
UIMA AS client connection to broker lost issue
Hi, right now I am testing the camel uima driver for error handling, for this I have an AE which just throws an exception when it get a CAS. The error handling is just the default, which means that the worker node just reports the error back to the uima as client. Thats fine, the camel route is configured to retry for every in this scenario, thats also fine. But after a while the system just hangs and stops retrying it took me a while to figure out why. The uima driver assumes that every CAS it sends causes a result to be returned, but once in a while it gets back a CAS with a different/new reference id than the one which was sent. This causes the allocated control thread to wait, when this happens to all control threads it just hangs. First of all can it be assumed that for every sent CAS a status comes back with the same reference id (when using timeouts) ? Here is the error I get back in case the reference id does not match the one of the send CAS: org.apache.uima.jms.error.handler.BrokerConnectionException: Unable To Deliver CAS:-7fbfaf13:1250d5b260d:-7ffa To Destination. Connection To Broker failover:(tcp://XXX1:61616,tcp://XXX2:61616)?randomize=false Has Been Lost Jörn
[jira] Commented: (UIMA-1649) deployAsyncService.sh log4j warnings
[ https://issues.apache.org/jira/browse/UIMA-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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.
