You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2008/09/08 16:55:55 UTC
[jira] Updated: (AMQ-1303) CommandAgent fails broker start if
security is enabled
[ https://issues.apache.org/activemq/browse/AMQ-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully updated AMQ-1303:
----------------------------
Fix Version/s: 5.3.0
(was: 5.2.0)
> CommandAgent fails broker start if security is enabled
> ------------------------------------------------------
>
> Key: AMQ-1303
> URL: https://issues.apache.org/activemq/browse/AMQ-1303
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.0.0
> Reporter: Mario Siegenthaler
> Priority: Minor
> Fix For: 5.3.0
>
> Attachments: commandagent.patch
>
>
> If the command agent configured in the activemq.xml (it is by default; <commandAgent xmlns="http://activemq.org/config/1.0"/>) 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 'org.apache.activemq.broker.util.CommandAgent' 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.