[jira] Created: (UIMA-1645) uimaj-as-camel needs a timeout parameter
uimaj-as-camel needs a timeout parameter Key: UIMA-1645 URL: https://issues.apache.org/jira/browse/UIMA-1645 Project: UIMA Issue Type: Bug Affects Versions: 2.3AS Reporter: Jörn Kottmann Assignee: Jörn Kottmann Fix For: 2.3AS Add the timeout parameter to the configuration string -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1644) uimaj-as-camel throws a NullPointerException when a null status is returned on initializationComplete
[ https://issues.apache.org/jira/browse/UIMA-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörn Kottmann closed UIMA-1644. --- Resolution: Fixed uimaj-as-camel throws a NullPointerException when a null status is returned on initializationComplete - Key: UIMA-1644 URL: https://issues.apache.org/jira/browse/UIMA-1644 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Reporter: Jörn Kottmann Assignee: Jörn Kottmann Fix For: 2.3AS Add a null check to prevent it from throwing the NPE. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Using failover in broker URL causes XML exception
Hi, in the deployment descriptor the broker URL is specified as failover:(tcp://10.45.2.100:61616,tcp://10.45.2.101:61616)?randomize=false and that causes on startup of the worker node the attached exception. Jörn org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 14 in XML document from URL [file:/tmp/UIMAdd2springOutput63279.xml] is invalid; nested exception is org.xml.sax.SAXParseException: Attribute value qBroker_failover_c_(tcp_c__ss_10.45.2.100_c_61616,tcp_c__ss_10.45.2.101_c_61616) of type ID must be a name. Caused by: org.xml.sax.SAXParseException: Attribute value qBroker_failover_c_(tcp_c__ss_10.45.2.100_c_61616,tcp_c__ss_10.45.2.101_c_61616) of type ID must be a name. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:131) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:384) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:318) at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.validateDTDattribute(XMLDTDValidator.java:1427) at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(XMLDTDValidator.java:1333) at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.handleStartElement(XMLDTDValidator.java:1940) at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.startElement(XMLDTDValidator.java:764) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1359) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2747) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107) at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:225) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:283) at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:76) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:351) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:303) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:280) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:131) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:147) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:173) at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:112) at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:79) at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:101) at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:389) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:324) at org.springframework.context.support.FileSystemXmlApplicationContext.init(FileSystemXmlApplicationContext.java:93) at org.springframework.context.support.FileSystemXmlApplicationContext.init(FileSystemXmlApplicationContext.java:77) at org.apache.uima.adapter.jms.activemq.SpringContainerDeployer.deploy(SpringContainerDeployer.java:434) at org.apache.uima.adapter.jms.service.UIMA_Service.deploy(UIMA_Service.java:165) at org.apache.uima.adapter.jms.service.UIMA_Service.main(UIMA_Service.java:387) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at
[jira] Created: (UIMA-1646) Using failover in broker URL causes XML exception
Using failover in broker URL causes XML exception - Key: UIMA-1646 URL: https://issues.apache.org/jira/browse/UIMA-1646 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Environment: Ubuntu Sevrer 8.10, Java 1.6 Reporter: Jörn Kottmann Assignee: Marshall Schor Priority: Blocker Fix For: 2.3AS In the deployment descriptor the broker URL is specified as failover:(tcp://10.45.2.100:61616,tcp://10.45.2.101:61616)?randomize=false and that causes on startup of the worker node the following exception: org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 14 in XML document from URL [file:/tmp/UIMAdd2springOutput63279.xml] is invalid; nested exception is org.xml.sax.SAXParseException: Attribute value qBroker_failover_c_(tcp_c__ss_10.45.2.100_c_61616,tcp_c__ss_10.45.2.101_c_61616) of type ID must be a name. Caused by: org.xml.sax.SAXParseException: Attribute value qBroker_failover_c_(tcp_c__ss_10.45.2.100_c_61616,tcp_c__ss_10.45.2.101_c_61616) of type ID must be a name. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:131) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:384) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:318) at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.validateDTDattribute(XMLDTDValidator.java:1427) at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(XMLDTDValidator.java:1333) at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.handleStartElement(XMLDTDValidator.java:1940) at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.startElement(XMLDTDValidator.java:764) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1359) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2747) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107) at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:225) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:283) at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:76) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:351) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:303) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:280) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:131) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:147) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:173) at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:112) at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:79) at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:101) at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:389) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:324) at org.springframework.context.support.FileSystemXmlApplicationContext.init(FileSystemXmlApplicationContext.java:93) at org.springframework.context.support.FileSystemXmlApplicationContext.init(FileSystemXmlApplicationContext.java:77) at org.apache.uima.adapter.jms.activemq.SpringContainerDeployer.deploy(SpringContainerDeployer.java:434) at
[jira] Resolved: (UIMA-1646) Using failover in broker URL causes XML exception
[ https://issues.apache.org/jira/browse/UIMA-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor resolved UIMA-1646. -- Resolution: Fixed Jörn, can you test this? Using failover in broker URL causes XML exception - Key: UIMA-1646 URL: https://issues.apache.org/jira/browse/UIMA-1646 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Environment: Ubuntu Sevrer 8.10, Java 1.6 Reporter: Jörn Kottmann Assignee: Marshall Schor Priority: Blocker Fix For: 2.3AS In the deployment descriptor the broker URL is specified as failover:(tcp://10.45.2.100:61616,tcp://10.45.2.101:61616)?randomize=false and that causes on startup of the worker node the following exception: org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 14 in XML document from URL [file:/tmp/UIMAdd2springOutput63279.xml] is invalid; nested exception is org.xml.sax.SAXParseException: Attribute value qBroker_failover_c_(tcp_c__ss_10.45.2.100_c_61616,tcp_c__ss_10.45.2.101_c_61616) of type ID must be a name. Caused by: org.xml.sax.SAXParseException: Attribute value qBroker_failover_c_(tcp_c__ss_10.45.2.100_c_61616,tcp_c__ss_10.45.2.101_c_61616) of type ID must be a name. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:131) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:384) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:318) at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.validateDTDattribute(XMLDTDValidator.java:1427) at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(XMLDTDValidator.java:1333) at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.handleStartElement(XMLDTDValidator.java:1940) at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.startElement(XMLDTDValidator.java:764) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1359) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2747) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107) at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:225) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:283) at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:76) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:351) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:303) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:280) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:131) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:147) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:173) at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:112) at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:79) at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:101) at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:389) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:324) at
Using failover in broker URL causes XML exception
Hi, in the deployment descriptor the broker URL is specified as failover:(tcp://10.45.2.100:61616,tcp://10.45.2.101:61616)?randomize=false and that causes on startup of the worker node the attached exception. Jörn org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 14 in XML document from URL [file:/tmp/UIMAdd2springOutput63279.xml] is invalid; nested exception is org.xml.sax.SAXParseException: Attribute value qBroker_failover_c_(tcp_c__ss_10.45.2.100_c_61616,tcp_c__ss_10.45.2.101_c_61616) of type ID must be a name. Caused by: org.xml.sax.SAXParseException: Attribute value qBroker_failover_c_(tcp_c__ss_10.45.2.100_c_61616,tcp_c__ss_10.45.2.101_c_61616) of type ID must be a name. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:131) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:384) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:318) at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.validateDTDattribute(XMLDTDValidator.java:1427) at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(XMLDTDValidator.java:1333) at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.handleStartElement(XMLDTDValidator.java:1940) at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.startElement(XMLDTDValidator.java:764) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1359) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2747) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107) at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:225) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:283) at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:76) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:351) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:303) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:280) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:131) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:147) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:173) at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:112) at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:79) at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:101) at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:389) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:324) at org.springframework.context.support.FileSystemXmlApplicationContext.init(FileSystemXmlApplicationContext.java:93) at org.springframework.context.support.FileSystemXmlApplicationContext.init(FileSystemXmlApplicationContext.java:77) at org.apache.uima.adapter.jms.activemq.SpringContainerDeployer.deploy(SpringContainerDeployer.java:434) at org.apache.uima.adapter.jms.service.UIMA_Service.deploy(UIMA_Service.java:165) at org.apache.uima.adapter.jms.service.UIMA_Service.main(UIMA_Service.java:387) 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
[jira] Closed: (UIMA-1646) Using failover in broker URL causes XML exception
[ https://issues.apache.org/jira/browse/UIMA-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörn Kottmann closed UIMA-1646. --- Thanks, seems to work now the worker node can connect to the broker, but I did not test for correct failover handling. Using failover in broker URL causes XML exception - Key: UIMA-1646 URL: https://issues.apache.org/jira/browse/UIMA-1646 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Environment: Ubuntu Sevrer 8.10, Java 1.6 Reporter: Jörn Kottmann Assignee: Marshall Schor Priority: Blocker Fix For: 2.3AS In the deployment descriptor the broker URL is specified as failover:(tcp://10.45.2.100:61616,tcp://10.45.2.101:61616)?randomize=false and that causes on startup of the worker node the following exception: org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 14 in XML document from URL [file:/tmp/UIMAdd2springOutput63279.xml] is invalid; nested exception is org.xml.sax.SAXParseException: Attribute value qBroker_failover_c_(tcp_c__ss_10.45.2.100_c_61616,tcp_c__ss_10.45.2.101_c_61616) of type ID must be a name. Caused by: org.xml.sax.SAXParseException: Attribute value qBroker_failover_c_(tcp_c__ss_10.45.2.100_c_61616,tcp_c__ss_10.45.2.101_c_61616) of type ID must be a name. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:131) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:384) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:318) at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.validateDTDattribute(XMLDTDValidator.java:1427) at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(XMLDTDValidator.java:1333) at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.handleStartElement(XMLDTDValidator.java:1940) at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.startElement(XMLDTDValidator.java:764) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1359) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2747) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107) at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:225) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:283) at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:76) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:351) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:303) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:280) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:131) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:147) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:173) at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:112) at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:79) at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:101) at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:389) at
[jira] Created: (UIMA-1647) Scripts fail to call runUimaClass.sh
Scripts fail to call runUimaClass.sh - Key: UIMA-1647 URL: https://issues.apache.org/jira/browse/UIMA-1647 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Environment: Ubuntu Server 8.10, Java 1.6 Reporter: Jörn Kottmann Priority: Blocker Fix For: 2.3AS Executing deployAsyncService.sh fails with the following error message: .: 28: runUimaClass.sh: not found deployAsyncService.sh calls runUimaClass.sh with . runUimaClass.sh ..., in an older version this script called setUimaClassPath.sh, but that was done with the absolute path: . $UIMA_HOME/bin/setUimaClassPath.sh I suggest that we change all our .sh scripts to use the absolute path like it was done before for at least the deployAsyncService.sh script. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1647) Scripts fail to call runUimaClass.sh
[ https://issues.apache.org/jira/browse/UIMA-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12772079#action_12772079 ] Jörn Kottmann commented on UIMA-1647: - For me it works if . runUimaClass.sh is replaces with sh $UIMA_HOME/bin/runUimaClass.sh, maybe it should be sh $UIMA_HOME/bin/runUimaClass.sh to not fail if the UIMA_HOME contains spaces. When the dot notation is used to run runUimaClass.sh it seems to get the parameter passed which is passed to deployAsyncService.sh and not the params intended for it in the deployAsyncService.sh script. It then fails because it cannot find a class with the name of the deployment descriptor in my case: bin/deployAsync.sh descritpor.xml, where descriptor.xml is not a valid class name. Scripts fail to call runUimaClass.sh - Key: UIMA-1647 URL: https://issues.apache.org/jira/browse/UIMA-1647 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Environment: Ubuntu Server 8.10, Java 1.6 Reporter: Jörn Kottmann Priority: Blocker Fix For: 2.3AS Executing deployAsyncService.sh fails with the following error message: .: 28: runUimaClass.sh: not found deployAsyncService.sh calls runUimaClass.sh with . runUimaClass.sh ..., in an older version this script called setUimaClassPath.sh, but that was done with the absolute path: . $UIMA_HOME/bin/setUimaClassPath.sh I suggest that we change all our .sh scripts to use the absolute path like it was done before for at least the deployAsyncService.sh script. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1647) Scripts fail to call runUimaClass.sh
[ https://issues.apache.org/jira/browse/UIMA-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12772084#action_12772084 ] Burn Lewis commented on UIMA-1647: -- This was an attempt to simplify the scripts since we assumed that the UIMA bin directory must be in the path for the deployAsyncService script to be found. But of course this is not required were you running with UIMA_HOME set but not UIMA_HOME/bin in the path? We also used to check for UIMA_HOME being set but now that check is in runUimaClass ... should we also restore that check? Or should we provide a test-setup script that verifies that UIMA_HOME actually refers to a UIMA installation? Maybe adjustExamplePaths? -Burn Scripts fail to call runUimaClass.sh - Key: UIMA-1647 URL: https://issues.apache.org/jira/browse/UIMA-1647 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Environment: Ubuntu Server 8.10, Java 1.6 Reporter: Jörn Kottmann Priority: Blocker Fix For: 2.3AS Executing deployAsyncService.sh fails with the following error message: .: 28: runUimaClass.sh: not found deployAsyncService.sh calls runUimaClass.sh with . runUimaClass.sh ..., in an older version this script called setUimaClassPath.sh, but that was done with the absolute path: . $UIMA_HOME/bin/setUimaClassPath.sh I suggest that we change all our .sh scripts to use the absolute path like it was done before for at least the deployAsyncService.sh script. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1648) UIMA AS lib path contains duplicate entries
UIMA AS lib path contains duplicate entries --- Key: UIMA-1648 URL: https://issues.apache.org/jira/browse/UIMA-1648 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Reporter: Jörn Kottmann Priority: Minor Fix For: 2.3AS After starting with deployAsyncService.sh the LIB_PATH is traced to the console, but it contains the same entries over and over again: + JVM LIB_PATH:/usr/lib/jvm/java-6-sun-1.6.0.10/jre/lib/amd64/server:/usr/lib/jvm/java-6-sun-1.6.0.10/jre/lib/amd64:/usr/lib/jvm/java-6-sun-1.6.0.10/jre/../lib/amd64:/home/uadmin/apache-uima-asNEW/uimacpp/lib:/home/uadmin/apache-uima-asNEW/uimacpp/examples/tutorial/src:/home/uadmin/apache-uima-asNEW/uimacpp/lib:/home/uadmin/apache-uima-asNEW/uimacpp/examples/tutorial/src:/home/uadmin/apache-uima-asNEW/uimacpp/lib:/home/uadmin/apache-uima-asNEW/uimacpp/examples/tutorial/src:/home/uadmin/apache-uima-asNEW/uimacpp/lib:/home/uadmin/apache-uima-asNEW/uimacpp/examples/tutorial/src:/home/uadmin/apache-uima-asNEW/uimacpp/lib:/home/uadmin/apache-uima-asNEW/uimacpp/examples/tutorial/src:/home/uadmin/apache-uima-asNEW/uimacpp/lib:/home/uadmin/apache-uima-asNEW/uimacpp/examples/tutorial/src:/home/uadmin/apache-uima-asNEW/uimacpp/lib:/home/uadmin/apache-uima-asNEW/uimacpp/examples/tutorial/src:/home/uadmin/apache-uima-asNEW/uimacpp/lib:/home/uadmin/apache-uima-asNEW/uimacpp/examples/tutorial/src::/usr/java/packages/lib/amd64:/lib:/usr/lib -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1647) Scripts fail to call runUimaClass.sh
[ https://issues.apache.org/jira/browse/UIMA-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12772096#action_12772096 ] Burn Lewis commented on UIMA-1647: -- I don't think we should be using . since it inherits the calling environment including the arguments. Dropping it or replacing with sh should be OK. Scripts fail to call runUimaClass.sh - Key: UIMA-1647 URL: https://issues.apache.org/jira/browse/UIMA-1647 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Environment: Ubuntu Server 8.10, Java 1.6 Reporter: Jörn Kottmann Priority: Blocker Fix For: 2.3AS Executing deployAsyncService.sh fails with the following error message: .: 28: runUimaClass.sh: not found deployAsyncService.sh calls runUimaClass.sh with . runUimaClass.sh ..., in an older version this script called setUimaClassPath.sh, but that was done with the absolute path: . $UIMA_HOME/bin/setUimaClassPath.sh I suggest that we change all our .sh scripts to use the absolute path like it was done before for at least the deployAsyncService.sh script. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1647) Scripts fail to call runUimaClass.sh
[ https://issues.apache.org/jira/browse/UIMA-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12772099#action_12772099 ] Jörn Kottmann commented on UIMA-1647: - Yes UIMA_HOME/bin is not in my path, so thats why it cannot find runUimaClass.sh, but I think its common not to have UIMA_HOME/bin in the path, right ? Then we have to add the check for UIMA_HOME to every shell script ... maybe the other way around would have been better, e.g. having one script to call other scripts like run.sh COMMAND. Scripts fail to call runUimaClass.sh - Key: UIMA-1647 URL: https://issues.apache.org/jira/browse/UIMA-1647 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Environment: Ubuntu Server 8.10, Java 1.6 Reporter: Jörn Kottmann Priority: Blocker Fix For: 2.3AS Executing deployAsyncService.sh fails with the following error message: .: 28: runUimaClass.sh: not found deployAsyncService.sh calls runUimaClass.sh with . runUimaClass.sh ..., in an older version this script called setUimaClassPath.sh, but that was done with the absolute path: . $UIMA_HOME/bin/setUimaClassPath.sh I suggest that we change all our .sh scripts to use the absolute path like it was done before for at least the deployAsyncService.sh script. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[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.
