If I counted right, it's referring to the quote character after the =.
That URL looks fishy, like some extra content got shoehorned in where it
doesn't belong. I'd check your config file for the cothent starting
'org.apache.activemq.artemis:broker' and see why it might be showing up in
the URL.
T
Can you be more specific about what you're testing? Is this 2 live nodes in
a cluster or a live/backup pair in an HA configuration? Providing specific
configuration is always helpful.
Also, how are you inspecting the cluster topology and what are you doing to
cause a "network split"?
Lastly, what
In case of a network split, and the split is removed, do we not have
failbacks at all? I see that the node is removed from the cluster topology
completly, and unless i restart the brokers, they wouldn't connect to each
other. So, even after I remove the network split, there are no changes in
the cl
I'm trying to have 3 masters and 3 slaves with 2 brokers in each JVM instance
using a colocated approach. I wanted to know if I'm supposed to use in-vm
connectors or acceptors for it. What all should I add under static
connectors?
Also, what does do? Does work?
I've set to 2, but it keeps
The error message appears to be referring to the '=" character, but I don't
know why that would be considered an illegal character.
What exactly did you do to deploy the Hawtio war file in ActiveMQ Artemis?
The web-console should be present by default unless you excluded it for
some reason when cr
This appears to be a duplicate of a message I answered recently on the
list. Please follow-up on the other thread, and we can abandon this one.
Justin
On Wed, Mar 27, 2019 at 12:17 AM naveen wrote:
> Dear,
>
> I am using 2 live brokers say LIVEA and LIVEB and I am using 2 Backup
> brokers say
The handshake timeout ERROR message was a feature added to help users
identify when ill-behaved or malicious clients connect to the broker and to
clean up any resources such clients leave behind. This work was done as
part of ARTEMIS-1420. The timeout is configurable so that the ERROR
messages aren
The configuration looks OK aside from the fact that the formatting makes it
difficult to read. Do you have logs or a test-case to demonstrate what is
actually happening?
Have you verified that simpler cases work before moving to more complex
cases? For example, does a single live/backup pair work
You would just add a policyEntry for your topics to what you have. Although
it doesn't show mixing queue and topic policyEntry elements,
http://activemq.apache.org/per-destination-policies.html shows the idea.
Tim
On Wed, Mar 27, 2019, 3:19 AM W.Y wrote:
> that for the reply, i found the reson.
The following security vulnerability was reported against Apache
ActiveMQ 5.15.8 and older versions.
Please check the following document and see if you’re affected by the issue.
http://activemq.apache.org/security-advisories.data/CVE-2019-0222-announcement.txt
Apache ActiveMQ 5.15.9 has been rel
i also changed code a little bit, first example code works, second example
code does not work
### it works for redelivery ###
RedeliveryPolicy queuePolicy =connectionFactory.getRedeliveryPolicy();
queuePolicy.setInitialRedeliveryDelay(0);
queuePolicy.setRedeliveryDelay(3000);
queuePolicy.setUseEx
that for the reply, i found the reson. then modified the activemq.xml like
below , it works
then question is , the policyEntries i used is only for queue.
destinationPolicy is only for queue.
is there a example configuration of destinationPolicy for both of topic and
queue ?
http://activemq.
Dear,
I am using 2 live brokers say LIVEA and LIVEB and I am using 2 Backup
brokers say BACKUPA and BACKUPB accordingly.
LIVEA and BACKUPA are belongs to group node1
LIVEB and BACKUPB are belongs to group node2
My assumption is that whenever I stop LIVEA, BACKUPA should come live and
simil
13 matches
Mail list logo