yes, that's it.
It works now. I did not knew, that there is a correlation between acceptor
and connector.
Thank you very much
-Sebastian
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Artemis-Automatic-failback-does-not-work-tp4713190p4713231.html
Sent from the ActiveM
OK, I found the problem. It's browser related. Actually it's a problem of an
extension of firefox which makes hyper link from text. It makes link
'DLQ.com' from the dead letter queue name 'DLQ.com.xxx.xxx' and then caused
the display problem. I can view the page correctly in IE.
However, there is
I noticed some old data files(generated 2 days ago) are not get cleaned up.
So I referred the doc to check which queue is using them. I found they are
reserved for one busy queue. The queue has several hundreds of messages
going through every second. There couldn't be any old message left there. I
OK, I will try to do that next time it occurs
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Queues-with-empty-name-appear-in-web-console-tp4713148p4713228.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hello,
I am getting the below error while posting the message to jms queue.
I have gone through the link http://activemq.apache.org/objectmessage.html
provided in the error message. But I could not resolve the issue.
I am using TomEE 7.0 server
1) I have added this in Tomee 7.0's cata
Sebastian,
Looks like there's a mistake in your slave.xml. If you change your
acceptor port to match the configured connector (or visa versa), I think
you'll be good to go.
Please let me know if this resolves your problem.
Regards
Martyn
---
tcp://192.168.50.1:61617
tcp://192.168.
Hi, I am running ActiveMQ 5.11.0. We have configured as per instructions we
got to configure the TLS 1.2 but we are not sure is it really that's the
case.
Wondering anyone can share some tips as in how we can verify and confirmed
the ActiveMQ is really running TLS1.2?
We tried to use some open SS
Hi, I am running ActiveMQ 5.11.0. We have configured as per instructions we
got to configure the TLS 1.2 but we are not sure is it really that's the
case.
Wondering anyone can share some tips as in how we can verify and confirmed
the ActiveMQ is really running TLS1.2?
We tried to use some open SS
How many messages do you have in the broker when this happens? There is a
sync period which may take a short while, particularly if there's a lot of
data in the broker or the connection between the live and backup is slow.
Essentially what is happening during this period is.
1. Master starts up
Hi Martyn,
I tried it now with version 1.3.0.
Same behavior.
I waited a couple of minutes, but the failback does not happen.
Instead both permanently post: AMQ212034: There are more than one servers on
the network broadcasting the same node id.
I'll send you my broker.xml files.
Thanks in advanc
Hi Sebastian,
There is a period where both servers will be up at the same time during
when using replication, so you might see the "more than one server with the
same ID" message for a period. This is normal.
Which version of Apache Artemis are you using. There were several fixes
around replica
Hello,
I'm trying to use Artemis with automatic failover.
I have two Servers, one is Master the other is Slave.
I'm using them in "replication" mode, not shared file.
Master has also "check-for-live-server" enabled.
Slave has "allow-failback" enabled.
Failover works fine, but when the master is a
Could it have anything to do with preferences you might have set in your
browser for how to display followed and unfollowed links? If you save the
page source and open that HTML in an entirely different browser (e.g. if
you were using Chrome, try Firefox or Opera or...), does the behavior
change?
There could be a bug in this case with displaying the name, based on your
description. You could file a Jira but the web console doesn't get much
attention anymore so you might want to see if you can track down the issue
if you have time. Contributions are always welcome if you can figure out
the
14 matches
Mail list logo
