Jason Shepherd created AMQ-4953:
-----------------------------------
Summary: Virutal Destination is not auto created when using
Composite Destination
Key: AMQ-4953
URL: https://issues.apache.org/jira/browse/AMQ-4953
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.9.0
Environment: JBoss A-MQ 6.1.0.redhat-306
Reporter: Jason Shepherd
Priority: Minor
When creating a composite queue (by editing activemq.xml) it doesn't seem like
the queue is actually created.
When I try to connect to the composite queue (from another server), the
folowing Exception is thrown:
Caused by: java.lang.SecurityException: User alice is not authorized to create:
queue://FOO.BAR
We doesn't allow the user ('alice') to create queues so this seems to indicate
that the queue doesn't exist according to A-MQ.
Part from my activemq.xml:
<broker xmlns="http://activemq.apache.org/schema/core"
brokerName="${broker-name}"
dataDirectory="${data}"
advisorySupport="false"
start="false">
...
<plugins>
<jaasAuthenticationPlugin configuration="karaf" />
<authorizationPlugin>
<map>
<authorizationMap
groupClass="org.apache.karaf.jaas.boot.principal.RolePrincipal">
<authorizationEntries>
<authorizationEntry queue=">" read="admin,alice"
write="admin,alice" admin="admin" />
<authorizationEntry topic=">" read="admin,alice"
write="admin,alice" admin="admin" />
<authorizationEntry topic="ActiveMQ.Advisory.>"
read="admin,alice" write="admin,alice" admin="admin,alice" />
</authorizationEntries>
</authorizationMap>
</map>
</authorizationPlugin>
</plugins>
...
<destinations>
<queue physicalName="FOO.BAR.COM"/>
</destinations>
<destinationInterceptors>
<virtualDestinationInterceptor>
<virtualDestinations>
<compositeQueue name="FOO.BAR">
<forwardTo>
<queue physicalName="FOO.BAR.COM"/>
</forwardTo>
</compositeQueue>
</virtualDestinations>
</virtualDestinationInterceptor>
</destinationInterceptors>
</broker>
** Note: This is destinct from AMQ-4320 which was about the destinations
contained within the Composite Destinations, not being created.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)