activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anders Aaberg (JIRA)" <>
Subject [jira] [Updated] (AMQ-5895) FilteredDestinations do not work when loaded by runtimeConfigurationPlugin
Date Fri, 17 Jul 2015 15:37:04 GMT


Anders Aaberg updated AMQ-5895:
    Attachment: activemq.patch

> FilteredDestinations do not work when loaded by runtimeConfigurationPlugin
> --------------------------------------------------------------------------
>                 Key: AMQ-5895
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.11.1
>         Environment: Both windows / linux, IBM java 6 / Oracle Java 7
>            Reporter: Anders Aaberg
>              Labels: runtime-configuration, virtualDestinations
>         Attachments: activemq.patch
> When adding a FilteredDestination to VirtualDestinations in activemq.xml, the runtimeConfigurationPlugin
will not update the configuration correct for the filteredDestination. The log does not give
any errors until we send a message towards the CompositeTopic/Queue that contains the FilteredDestination,
then the message is not forwarded and the following error is written in the log:
> java.lang.IllegalArgumentException: Unknown mapped destination type java.lang.Object@7a141450
>         at[activemq-broker-5.11.1.jar:5.11.1]
> It works if we restart activeMQ, because then the configuration is not loaded by the
runtimeConfigurationPlugin, however we really want to avoid that.
> Solution: It seems that the translation from JAXB objects to ActiveMQ objects is not
translating DtoFilteredDestination to FilteredDestinations in org.apache.activemq.plugin.JAXBUtils.
> When I added the following code to the method "inferTargetObject", then the problem was
> [...]
>         } else if (DtoFilteredDestination.class.isAssignableFrom(elementContent.getClass()))
>             return new FilteredDestination();
> [...]
> Why this matters: In my organisation we really like to use ActiveMQ VirtualDestinations
with FilteredDestinations, because it is a much more minimalistic than having to make many
simple subscriptions in Camel and it has many benefits compared to durable subscribers. However,
we do not wish to restart ActiveMQ every time we modify the VirtualDestinations, hence we
need to be able to updated the VirtualDestinations using runtimeConfigurationPlugin and this
does not work right now due to this bug.
> Perhaps I can also submit the bug fix myself if that can speed up the process.

This message was sent by Atlassian JIRA

View raw message