Re: Removing values appended by Artemis in message body when doing a message copy in Interceptor

hi Justin, I am using version - apache-artemis-2.4.0. and for the Java dependency i am importing "*org.apache.activemq:artemis-core-client:2.2.0*" as you can see above the, Packet which is cast to the type Ses

Re: Removing values appended by Artemis in message body when doing a message copy in Interceptor

What version of Artemis are you using? It looks like 1.x. However, even in 1.x the org.apache.activemq.artemis.api.core.Message interface (which is what is returned by org.apache.activemq.artemis.core.protocol.core.impl.wireformat.SessionSendMessage.getMessage()) doesn't have a method named copy(

Removing values appended by Artemis in message body when doing a message copy in Interceptor

hi , I am trying to intercept a message in Artemis using my own interceptor code, but when i intercept the message a i make a copy of the message so the consumer still receives the actual message on the other end of Artemis. i make a copy as follows: *if (packet instanceof SessionSendMessage) {

[SOLVED] Re: Forget about disconnected brokers/subscribers

It turned out there's a configuration setting on the broker that causes it to timeout remote durable subscribers: I'm not creating any durable subscribers in my application code, but it appears that when you use a broker as a network bridge it creates durable subscriptions on behalf of the topic s

Dockerizing Apache Active MQ Artemis Master/Slave config not working

I was able to successfully setup Apache ActiveMQ Artemis Master/Slave replication on my 2 VM cluster. VM1 : 172.29.219.89 VM2 : 172.29.219.104 My broker.xml for Master node is : tcp://172.29.219.89:61616 tcp://172.29.219.104:61616 cluster-user cluster-password *

Dockerizing Apache Active MQ Artemis Master/Slave config not working

I was able to successfully setup Apache ActiveMQ Artemis Master/Slave replication on my 2 VM cluster. VM1 : 172.29.219.89 VM2 : 172.29.219.104 My broker.xml for Master node is : tcp://172.29.219.89:61616 tcp://172.29.219.104:61616 cluster-user cluster-password *

ERROR: Detected missing journal files - When upgrading from 5.9 to 5.15.3

A part of the stack trace is given below. As the subject says, I am upgrading from ActiveMQ 5.9 to 5.15.3. I do see someone raised a similar issue for 5.14 upgrade, but there were no good solutions apart from removing the journals (I guess the db*.log files are what are being referred to as journa

Graceful disabling of ActiveMQ scheduler

What will happen to messages persisted in the scheduler store when scheduler support is disable? If there are undelivered message and scheduler is disabled permanently, in that case it seems messages will stuck forever in scheduler store. Is there any facility built into activemq, to disable sc

Re: java.lang.OutOfMemoryError: GC overhead limit exceeded

Thanks a lot for your reply Tim, Below is the metrics details i grabbed from the server. ActiveMQ: 5.15.0 non-persistent Running consumer -> singleton -> onMessage() -> submit callables -> callables send updated message to destination messages -> 600/hour me