geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevan Miller (JIRA)" <>
Subject [jira] [Commented] (GERONIMO-6333) Unable to create JMS broker from admin console
Date Sun, 22 Apr 2012 15:19:34 GMT


Kevan Miller commented on GERONIMO-6333:

ActiveMQ config is updated in 3.0. Don't think we have the same level of admin console support
as we had in earlier releases. To do this right now, you could edit repository/org/apache/geronimo/configs/activemq-broker-blueprint/3.0-beta-1/

And update the <amq:transportConnectors> to look something like:

            <amq:transportConnector name="openwire" uri="tcp://${ServerHostname}:${ActiveMQPort
+ PortOffset}"/>
            <amq:transportConnector name="stomp" uri="stomp://${ServerHostname}:${61613
+ PortOffset}"/>

After updating, you'll need to clear var/cache and start/restart the server. E.g. './geronimo
run --clean'
> Unable to create JMS broker from admin console
> ----------------------------------------------
>                 Key: GERONIMO-6333
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: ActiveMQ
>    Affects Versions: 3.0-beta-1
>         Environment: Linux (Debian testing, x64), IBM J9 1.6, Geronimo 3.0-beta-1
>            Reporter: Moritz Hoffmann
> The documentation says that an ActiveMQ JMS broker can be created from the console. See
> When I run Geronimo, I do not see the "Add JMS Broker" link that is shown in the documentation,
thus I cannot create a new broker.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message