You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Christopher L. Shannon (JIRA)" <ji...@apache.org> on 2017/02/06 14:36:41 UTC

[jira] [Closed] (AMQ-5132) Broker can't be started

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

Christopher L. Shannon closed AMQ-5132.
---------------------------------------
    Resolution: Won't Fix

LevelDB has been deprecated and is no longer supported.

> Broker can't be started
> -----------------------
>
>                 Key: AMQ-5132
>                 URL: https://issues.apache.org/jira/browse/AMQ-5132
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.10.0
>         Environment: Windows 7, LevelDB enabled
>            Reporter: Albert Barmettler
>         Attachments: activemq.log, activemq.xml
>
>
> I just checked out and built a 5.10-SNAPSHOT version of the AMQ to run my test against it, as requested in AMQ-5125.
> I always get an exception when starting the broker.
> I used the built ZIP package as I would use an officially downloaded version (unzip, adapt config file, start broker with the activemq.bat file). The only file I have modified is activemq.xml.
> First thing that stands out is that the activemq.bat can’t be called as in 5.9, where it just started the broker. Instead it terminates, obviously missing some options. So I figured I’d have to run "activemq-admin.bat" start or "activemq.bat start" instead, where I get mentioned exception.
> Starting works fine though with KahaDB.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)