tyvm. That link explains it nicely :)
I assume that it is not decremented for ActiveMQ performance just ignore
these messages ? No need to do any kind of "purging"?
Cheers
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ghost-topics-ActiveMQ-Advisory-Producer-Topic-xxx
Hi,
I have noticed that for some reason on my ActiveMQ setup for each topic I
have defined, 2 more topics get created. One with prefix
ActiveMQ.Advisory.Consumer.Topic and another with prefix
ActiveMQ.Advisory.Producer.Topic. For example if I define topic:
java:/topic/MyTopic
Than I would s
Hi Tim,
Sorry for not been clear enough.
AMQ1 has IP 10.0.1.53 and its configuration points to 10.0.1.200:61616
AMQ2 has IP 10.0.1.200 and its configuration points to 10.0.1.53:61616
The idea is to keep at least one of these two alive at all times... and if
one of them goes down, it woul
Hi,
I am getting this in my Wildfly logs:
2015-09-16 11:18:15,297 INFO
[org.apache.activemq.transport.failover.FailoverTransport] (ActiveMQ Task-1)
Successfully connected to tcp://10.0.0.252:61616
2015-09-16 11:18:15,314 INFO
[org.apache.activemq.transport.failover.FailoverTransport] (ActiveM
I am trying to make ActiveMQ 5.12 and Wildfly 8.2 work on AWS
I have came up with following configuration:
- two ActiveMQ servers (AMQ1, AMQ2) with static network connectors pointing
to each other.
- one ActiveMQ (AMQW1, AMQW2, ...) server per each Wildfly server (WF1, WF2,
...) with static netwo