activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Resolved] (AMQ-2521) Some JMX operations fail with SecurityException with secured broker
Date Fri, 02 Nov 2012 15:05:13 GMT


Timothy Bish resolved AMQ-2521.

       Resolution: Fixed
    Fix Version/s: 5.6.0

This has since been fixed and works in at least 5.6 and 5.7+
> Some JMX operations fail with SecurityException with secured broker
> -------------------------------------------------------------------
>                 Key: AMQ-2521
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.3.0
>         Environment: I've reproduced this on OS X and Linux
>            Reporter: Phil Pickett
>            Priority: Minor
>             Fix For: 5.7.0, 5.6.0
> I've started a secured broker using the sample configuration as follows:
> ./activemq xbean:file:../conf/activemq-security.xml
> After the broker was started, I used the example ProducerTool to put 2000 messages on
the TEST.FOO queue.  For this to work, I modified the ProducerTool to use username/password
as follows:
>     private String user = "system";
>     private String password = "manager";
> I then connected to the broker using jconsole, and created a new queue using the Broker's
addQueue MBean operation.  As a test, I also used the TEST.FOO queue's removeMessage MBean
operation to remove a message from the queue.
> The problem is that certain MBean operations fail with "Problem invoking moveMessageTo
: java.lang.SecurityException: User is not authenticated."  I have seen this with a queue's
sendTextMessage and moveMessageTo operations.
> The full exception as logged by the broker for the failed sendTextMessage operation is:
>  WARN | Failed to add Connection
> java.lang.SecurityException: User name or password is invalid.
> 	at
> 	at
> 	at
> 	at
> 	at org.apache.activemq.command.ConnectionInfo.visit(
> 	at
> 	at$1.onCommand(
> 	at org.apache.activemq.transport.ResponseCorrelator.onCommand(
> 	at org.apache.activemq.transport.TransportFilter.onCommand(
> 	at org.apache.activemq.transport.vm.VMTransport.iterate(
> 	at org.apache.activemq.thread.DedicatedTaskRunner.runTask(
> 	at org.apache.activemq.thread.DedicatedTaskRunner$
> This seems similar to AMQ-2516.  I've tried this using the 5.3.1 and 5.4 SNAPSHOTs and
see the same thing.

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

View raw message