activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher L. Shannon (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-6544) ActiveMQ does not start up on karaf if offline (SAXParseException)
Date Mon, 19 Dec 2016 14:22:58 GMT

     [ https://issues.apache.org/jira/browse/AMQ-6544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Christopher L. Shannon resolved AMQ-6544.
-----------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 5.x)
                   5.14.3
                   5.15.0

> ActiveMQ does not start up on karaf if offline (SAXParseException)
> ------------------------------------------------------------------
>
>                 Key: AMQ-6544
>                 URL: https://issues.apache.org/jira/browse/AMQ-6544
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: OSGi/Karaf
>    Affects Versions: 5.14.2
>         Environment: Karaf, Offline
>            Reporter: Christian Schneider
>            Assignee: Christian Schneider
>             Fix For: 5.15.0, 5.14.3
>
>
> To reproduce:
> - Download, unpack and start karaf 4.0.8
>     feature:repo-add activemq 5.14.2
>     feature:install activemq-broker
> ActiveMQ start succesfully.
> Now stop karaf, go offline and start karaf again.
> This time the exception below can be found in the log and ActiveMQ fails to start.
> org.osgi.service.cm.ConfigurationException: null : Cannot start the broker
> Caused by: org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line
24 in XML document from URL [file:/home/cschneider/java/apache-karaf-4.0.8/etc/activemq.xml]
is invalid; nested exception is org.xml.sax.SAXParseException: cvc-elt.1.a: Cannot find the
declaration of element 'beans'.
> Caused by: org.xml.sax.SAXParseException: cvc-elt.1.a: Cannot find the declaration of
element 'beans'.
> Full stack trace can be found here http://apaste.info/PQSHZ
> The reason for this problem seems to be that the xsd can not be found. So I assume we
lack the correct mapping from urls to embedded xsds.
> I will work on a fix.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message