I was able to reproduce it manually but not in an automatic test, there is
one previous test which is very similar but I have to be missing something.
The issue is generating when trying to configure the routing type using the
divert config
<divert name="framework-notifications-divert">
<address>BridgeNotifications</address>
<forwarding-address>Notifications</forwarding-address>
<transformer-class-name>com.company.NotificationsTransformer</transformer-class-name>
<routing-type>MULTICAST</routing-type>
<exclusive>true</exclusive>
</divert>
If I changed this to specific logic in the Transformer it starts working.
The test is
https://github.com/apache/activemq-artemis/blob/master/tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/amqp/AmqpBridgeApplicationPropertiesTest.java
Broker configs:
https://filebin.net/3n0mzcrk53fu8fna
Maybe someone can help me to detect which is different between my brokers
xml files and the config in the test.
Exception:
upId='null'}, extraProperties = TypedProperties[_AMQ_AD=Notifications]]:
java.lang.RuntimeException
at
org.apache.activemq.artemis.protocol.amqp.broker.AMQPMessage.toCore(AMQPMessage.java:695)
[artemis-amqp-protocol-2.9.0.jar:2.9.0]
at
org.apache.activemq.artemis.core.protocol.core.impl.CoreSessionCallback.sendMessage(CoreSessionCallback.java:123)
[artemis-server-2.9.0.jar:2.9.0]
at
org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.deliverStandardMessage(ServerConsumerImpl.java:1168)
[artemis-server-2.9.0.jar:2.9.0]
at
org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.proceedDeliver(ServerConsumerImpl.java:510)
[artemis-server-2.9.0.jar:2.9.0]
at
org.apache.activemq.artemis.core.server.impl.QueueImpl.proceedDeliver(QueueImpl.java:3294)
[artemis-server-2.9.0.jar:2.9.0]
at
org.apache.activemq.artemis.core.server.impl.QueueImpl.deliver(QueueImpl.java:2669)
[artemis-server-2.9.0.jar:2.9.0]
at
org.apache.activemq.artemis.core.server.impl.QueueImpl.access$2300(QueueImpl.java:117)
[artemis-server-2.9.0.jar:2.9.0]
at
org.apache.activemq.artemis.core.server.impl.QueueImpl$DeliverRunner.run(QueueImpl.java:3613)
[artemis-server-2.9.0.jar:2.9.0]
at
org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
[artemis-commons-2.9.0.jar:2.9.0]
at
org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
[artemis-commons-2.9.0.jar:2.9.0]
at
org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:66)
[artemis-commons-2.9.0.jar:2.9.0]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[rt.jar:1.8.0_192]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[rt.jar:1.8.0_192]
at
org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
[artemis-commons-2.9.0.jar:2.9.0]
Caused by: java.lang.NullPointerException
at
org.apache.activemq.artemis.protocol.amqp.broker.AMQPMessage.scanForMessageSection(AMQPMessage.java:347)
[artemis-amqp-protocol-2.9.0.jar:2.9.0]
at
org.apache.activemq.artemis.protocol.amqp.broker.AMQPMessage.getBody(AMQPMessage.java:309)
[artemis-amqp-protocol-2.9.0.jar:2.9.0]
at
org.apache.activemq.artemis.protocol.amqp.broker.AMQPMessage.toCore(AMQPMessage.java:693)
[artemis-amqp-protocol-2.9.0.jar:2.9.0]
... 13 more
In this case the examples is two broker using a simple bridge, the original
setup is the same but using clustering config.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
