activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mario Siegenthaler (JIRA)" <>
Subject [jira] Updated: (AMQ-1303) CommandAgent fails broker start if security is enabled
Date Sat, 30 Jun 2007 18:51:32 GMT


Mario Siegenthaler updated AMQ-1303:

    Attachment: commandagent.patch

Fix for the command agent that allows the user to specify a username and a password for the
command agent with the following syntax:

  <commandAgent xmlns="" brokerUser="admin" brokerPassword="veryverysecret"/>

The two parameters are optional, if they're not specified the broker connects without authentication.

Futher this path changes to usage of vm://localhost to a lookup via the broker registry (just
like in the web-console).

> CommandAgent fails broker start if security is enabled
> ------------------------------------------------------
>                 Key: AMQ-1303
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.0.0
>            Reporter: Mario Siegenthaler
>            Priority: Minor
>         Attachments: commandagent.patch
> If the command agent configured in the activemq.xml (it is by default; <commandAgent
xmlns=""/>) and the security/logon for the broker is enabled
then the broker fails to start with the following error message:
> ERROR: java.lang.RuntimeException: Failed to execute start task. Reason: org.springframework.beans.factory.BeanCreationException:
Error creating bean with name '' defined in class
path resource [activemq.xml]: Invocation of init method failed;
> nested exception is javax.jms.JMSException: User name or password is invalid.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message