I am using below code to create publisher and and every creating it
whenever a ineed to add message in topic but some it will through
exceptionso please how resolve this problem
j
*avax.jms.InvalidClientIDException: Broker: localhost - Client:
AthenaPublisher already connec
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
BridgeNotifications
Notifications
I wasn't clear enough ;)
We are a service provider.
This particular DR scenario is: if the clients lose the data/transactions (on
their end) and need a replay of the transactions (messages). Clients have
independent platforms to us.
(Our DR, on our sites, is having 2 data centers and replicatio
Thanks. It's running in a Docker container, so I "docker stop" it. I can
see the log output as the slave takes over and starts up, and then I can log
into the old slave's ActiveMQ management console. And, I can see that the
client detects the down master and attempts reconnects.
Having said tha
One more thing...
Since you're using share-store then you either need to really kill the
broker (e.g. kill -9 ) to trigger failover or set
true if you're stopping the
broker gracefully, e.g.:
true
Justin
On Mon, Jul 8, 2019 at 3:03 PM bob.sandif
Sorry about the code not showing up. I edited the post to put it in.
Thanks for the reply - a simple usage of your suggestion didn't work - but
it did change the behaviour, so I'll pursue the possible values for the
query params on the url specification.
Bob.
--
Sent from: http://activemq.228
> Have I missed anything?
Perhaps I have misunderstood your requirements, but what you're describing
(i.e. making a copy of the message to keep on the *same* broker) doesn't
conform with what I understand to be "disaster recovery." If a "disaster"
strikes that broker then the backup-request and ba
None of the code or configuration came through on your first email. In the
second email it didn't come through either, but some of it is visible on
the Nabble web page.
That said, I think the problem is the URL you're using (i.e.
"(tcp://activemq-1:61616,tcp://activemq-2:61616)"). You aren't speci
Sorry - a couple of other things.
The exception I get on the client (when I shut down the master ActiveMQ) and
try to send a message to ActiveMQ is:
I'm using a URL like this:
I tried:
but got an exception like this:
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f234
I have a (I think) simple master / slave setup of ActiveMQ servers, using
shared file system. When I shut down the current master, it fails over to
the slave, and when I then restart the original master, it becomes the
standby - which is all just fine.
I'm having problems on the client side, thou
I think as a project we need to be clear in direction here with one roadmap. To
avoid users confusion.
I was on the understanding that as a community and PMC a roadmap was already
agreed.
And this was for artemis to become activemq 6 was agreed and once it has all
features (and more) of
> Will Artemis store (in journal) 1 copy of the message body and use
pointers to refer to that message body in diverted/copied messages?
No, the new message is a deep copy.
> Artemis divert will change the message-ID. It would be nice to keep the
existing message-ID. If the transformer plugin sets
A follow on question:
When are messages ACKed in this scenario?
Is the ACK to the producer only sent when the message has been persisted to
both original and diverted to queues/addresses?
Hi guys,
I am trying to upgrade fro 2.6.3 to 2.9.0 but after run some tests a hit
NPE. I am trying to create a test to reproduce it but I am not being able to
do it. So maybe someone can point me out something viewing the stack trace.
Some details in my current config:
2 Instances in cluster. Ano
14 matches
Mail list logo
