yes, I understand. It certainly looks like that :-)
But, since artemis has mqtt-support (according the documentation anyway, as
I said I didn't try it myself), and since the protocols (stomp, amps, ...)
in artemis are pluggable, it might just work in wildfly too.
I must say that the wildfly docume
Queues named like "$.artemis.internal.sf." are internal queues used to move
messages between nodes for things like server-side message load-balancing
or message redistribution. As long as the cluster is formed properly then
messages should not accumulate there but should land there for just a
mome
a quick note and then i will work on providing a more reproducible use set
of artifacts.
> How did you test that?
Three things i notice. 1) in the JMX console (viewed via Hawtio/jolokia
api in 2.1, and the skinned version of such in the new 2.3 console [very
nice BTW]) the slave will typically N
The only scenario I can think here on the loss of address/queues , noting that
somehow your slave is thinking it can active as master (aka acceptors start up)
is that auto-delete-queues/auto-delete-address is kicking in (which default is
true I believe) as it deletes queue on no subscription and
I’ve just tested manually (in a HA setup) that if you set delete policy to OFF
which by default it is set to OFF, then queues and address do not get
undeployed on reload. Eg queues and addresses if created in GUI or CLI remain.
Only if you change/override that to FORCE would it remove an addres
I guess my point is that you *don't* have one available in the Wildfly that
you're using due to these issues you're running into (regardless of whether
or not they are legitimate bugs).
Wildfly embeds Artemis in order to fulfill the JMS implementation
requirement of Java EE. Wildfly isn't trying
> If I make any change at all to the slave broker.xml file the
"configuration reload" feature takes effect and starts/enables the
acceptors on the Slave.
How did you test that? Looking at the code it appears the configuration
reload logic shouldn't touch the acceptors. Also, I just tested this o
No, I haven't actually.
It is not usefull for me. I don't want an 'out-of-process' MQTT broker, when
I have one available in the wildfly that I'm using.
Thomas
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Have you tried using standalone Artemis 2.3.0?
Justin
On Thu, Sep 21, 2017 at 2:01 PM, thoutekier
wrote:
> As suggested on the jboss-forum, I created an issue for this on both
> wildfly
> and artemis projects, with steps to reproduce the problem.
> https://issues.apache.org/jira/browse/ARTEMIS
As suggested on the jboss-forum, I created an issue for this on both wildfly
and artemis projects, with steps to reproduce the problem.
https://issues.apache.org/jira/browse/ARTEMIS-1430
https://issues.jboss.org/browse/WFLY-9372
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User
Quick Summary: If I make any change at all to the slave broker.xml file the
"configuration reload" feature takes effect and starts/enables the
acceptors on the Slave. This causes the slave to stop backing up the master
and start accepting its own connections. also address and security settings
that
Thank you Tim, I will make these changes appreciate it ! Yes only some of our
producers are setting persistent property. I will also make that required
for all our producer apps to make sure we don't lose messages from our
queues on a broker re-start. Thank you !
--
Sent from: http://activemq.22
don’t believe everything someone writes on his blog especially not if it’s an
IBM employee who writes his product would be the best ;-)
> Am 21.09.2017 um 16:37 schrieb Justin Bertram :
>
> If you're starting from scratch then I would recommend ActiveMQ Artemis.
> Artemis' feature set is on par
If you're starting from scratch then I would recommend ActiveMQ Artemis.
Artemis' feature set is on par with the ActiveMQ 5.x code-base and
performance is better.
FWIW, I personally think the article you referenced is almost entirely FUD
[1].
Justin
[1] https://en.wikipedia.org/wiki/Fear,_uncer
Hi,
We have requirement of queuing mechanism and therefore planning to make use
of Apache ActiveMQ. While researching on Apache ActiveMQ we observed the
subproject namely Apache artemis.
We have also noticed the below mentioned links with regards to Apache future
direction is towards Apache Arte
I can only see warning message in broker logs:
[2017-09-16 14:15:59.540-0400] [ActiveMQ NIO Worker 3]
[org.apache.activemq.broker.TransportConnection] [WARN]
[TransportConnection.java:org.apache.activemq.broker.TransportConnection:processAddConnection()::858]
[Failed to add Connection
id=ID:
Hello,
I have a newbie question.
I'm playing with artemis clustering, and have simple setup like this:
pruducerartemis-server1consumer1
|
artemis-server2consumer2
Messages are balanced to server2 exactly as described in documentation. The
only issu
17 matches
Mail list logo
