activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Albert Barmettler (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-5132) Broker can't be started
Date Thu, 03 Apr 2014 16:36:14 GMT

    [ https://issues.apache.org/jira/browse/AMQ-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13958943#comment-13958943
] 

Albert Barmettler commented on AMQ-5132:
----------------------------------------

Looks related to AMQ-5105.

> 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.2#6252)

Mime
View raw message