how to configure 2 nodes with HA / Replication

[Fabien JALABERT]

Hello,

I'm trying to configure a simple cluster with HA master slave 
replication. My goal is only to implement an easy failover, I do not 
have load requirements.


My two node configurations are below (amq-n1 as  master and amq-n2 as 
slave host).


1) When I success to post a message on the n1 queue, then the message is 
not visible on the n2, so that means that replications seems not working.


2) How can I manage that the shutdown of the n1 should switch on n2 ? 
It's autotic when connecting with ha parameter ? When I try using a "2 
tcp connection", I cannot send a message, that only works when I put 
only one host in the URL:


jms.broker.url=(tcp://amq-n1:61616,tcp://amq-n2:61616)?ha=true=1000=1.0=-1 
--> does not work


jms.broker.url=tcp://amq-n1:61616?ha=true=1000=1.0=-1 
--> works


Thanks for your help.

MASTER CONF :

  
tcp://0.0.0.0:61616 


tcp://amq-n2:61616
 

      name="netty-acceptor">tcp://0.0.0.0:61616?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=CORE,AMQP,STOMP,HORNETQ,MQTT,OPENWIRE;useEpoll=true;amqpCredits=1000;amqpLowCredits=300 



      
         
netty-connector
            
 netty-backup-connector
            
         
      

   
         
            
 true
            
         
      


SLAVE CONF:

      
tcp://0.0.0.0:61616 


tcp://amq-n1:61616
 
   
         name="netty-acceptor">tcp://0.0.0.0:61616?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=CORE,AMQP,STOMP,HORNETQ,MQTT,OPENWIRE;useEpoll=true;amqpCredits=1000;amqpLowCredits=300 


      

         
            
               true
               

 0
            
         
      

   
         
netty-connector
            
 netty-live-connector
            
         
      

[ANNOUNCE] ActiveMQ Artemis 2.8.1 Released

[Clebert Suconic]

I'm pleased to announce the release of ActiveMQ Artemis


Downloads are now available at
http://activemq.apache.org/components/artemis/download/


This is basically a bug fix release containing a change required for
JMS compatibility on Wildfly, and a number of other updates and fixes.


Many thanks for all the contributors to this release.

-- 
Clebert Suconic

Artemis 2.7.0 Cluster Redistribution Issue

[ldebello]

Hi guys,

We are trying to migrate from 2.6.3 to 2.7.0 and we hit an issue with
cluster redistribution, I have filed a jira ticket
https://issues.apache.org/jira/browse/ARTEMIS-2355 and create an automatic
test, I am trying to debug the issue but I would like some lights to
understand where can I start looking I am almost sure the issue is related
to routing type.

Thanks in advance.

Regards,
Luis



--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Artemis and Wildfly16

[Justin Bertram]

In my opinion the greatest power and flexibility comes when running the
broker standalone. Then you can scale up if necessary (e.g. "horizontally"
via clustering or "vertically" via better hardware), configure high
availability, easily add support for other protocols, etc. without having
to deal with an application layer that's tied to the broker. Then your
applications (e.g. your MQTT devices, your project running in Wildfly,
etc.) can access the broker however they need.


Justin


On Thu, May 23, 2019 at 1:23 PM Rafael Fernandez  wrote:

> Hi Justin.
>
> Let me a last question.
>
> The idea of useing Wildfly as an application server comes from a personal
> project I developed a couple of years ago. It was a JEE application
> software
> for tracking vehicles. The comunication with tracking devices was based on
> Web services. Now the trend in tracking devices in Mqtt so I am thinking
> about to migrate my project from web services to mqtt.
>
> I would like to know your opinion, wether I should use Wildfly Artemis as a
> MOM or it would be better to use Artemis standalone and subscribe to it
> from
> my project running in Wildfly
>
> Regards
>
> Rafael
>
>
>
>
>
> --
> Sent from:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
>

Re: Artemis and Wildfly16

[Rafael Fernandez]

Hi Justin.

Let me a last question.

The idea of useing Wildfly as an application server comes from a personal
project I developed a couple of years ago. It was a JEE application software
for tracking vehicles. The comunication with tracking devices was based on
Web services. Now the trend in tracking devices in Mqtt so I am thinking
about to migrate my project from web services to mqtt.

I would like to know your opinion, wether I should use Wildfly Artemis as a
MOM or it would be better to use Artemis standalone and subscribe to it from
my project running in Wildfly

Regards

Rafael





--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Artemis and Wildfly16

[Justin Bertram]

Thanks for the update.

I think everything you said is correct. The initial confusion may have been
caused by the way the messaging subsystem in Wildfly exposes the Artemis
configuration. It's really meant to be used only as a JMS server so the
messaging subsystem configuration is geared towards that use-case. It's not
as flexible or abstract as the configuration for the standalone Artemis
broker.


Justin

On Thu, May 23, 2019 at 12:30 PM Rafael Fernandez 
wrote:

> Hi Justin
>
> Thank you for yours advise. It gave me the clue to solve the problem.
> Setting the Wildfly log to debug provided usefull info.
>
> After an in deep reading of  Apache Artemis user manual, and having carried
> out many tests and configurations on both, standalone and wildfly16
> embedded, I have been able to run the Artemis in Wildfly with Mqtt support.
>
> As I mentioned in my original question there was impossible to subscribe to
> a queue or topic from mqtt client, however it was possible to send messages
> to that queue/topic.
>
> If you read the Artemis manual, the information regarding the subscriptions
> to queues or topics clearly explains how subscription and publishing it is
> carried out.
>
> In Artemis there are addresses and queues, the topic concept does not
> exists.
>
> If autocreate-address and autocreate-queues is enabled, clients when
> publish
> will create the addresses and queues.
>
> The clients when subscribe will create address and queues as well. If there
> is more than one subscribers each one will create an queue attached to the
> address.
>
> So when a client publish, sends messages to the address and Artemis routes
> the messages to the attached queues.
>
> There are statics addresses and queues that are defined in broker.xml. A
> client can subscribe to those static addresses and will create a dinamic
> queue each one to receive messages. Or If the programmer desires can code
> the client so as to attached to a static queue defined in broker.xml by
> means of the fully qualyfied name.
>
> broker.xml  static addres and queue
>  
>  
> 
>
> 
> 
>
> client, field for fully qualyfied name
>   private String topic = "test::T1";
>
> So in conclusion if you want to subscribe to a Wildfly16 Artemis from a
> Mqtt
> client you should set the standalone-full.xml to allow autocreation of
> queues.
>
>  expiry-address="jms.queue.ExpiryQueue" max-size-bytes="10485760"
> page-size-bytes="2097152" message-counter-history-day-limit="10"
> auto-create-queues="true" auto-delete-queues="true"
> auto-create-addresses="true" auto-delete-addresses="true"/>
>
> And that is all, allow the clients to create their own queues atached to
> the
> addresses.
>
>
> Now I will try to set SSL support for Artemis in Wildfly16
>
> Rafael
>
>
>
>
> --
> Sent from:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
>

Re: Artemis and Wildfly16

[Rafael Fernandez]

Hi Justin

Thank you for yours advise. It gave me the clue to solve the problem.
Setting the Wildfly log to debug provided usefull info.

After an in deep reading of  Apache Artemis user manual, and having carried
out many tests and configurations on both, standalone and wildfly16
embedded, I have been able to run the Artemis in Wildfly with Mqtt support.

As I mentioned in my original question there was impossible to subscribe to
a queue or topic from mqtt client, however it was possible to send messages
to that queue/topic.

If you read the Artemis manual, the information regarding the subscriptions
to queues or topics clearly explains how subscription and publishing it is
carried out.

In Artemis there are addresses and queues, the topic concept does not
exists.

If autocreate-address and autocreate-queues is enabled, clients when publish
will create the addresses and queues.

The clients when subscribe will create address and queues as well. If there
is more than one subscribers each one will create an queue attached to the
address.

So when a client publish, sends messages to the address and Artemis routes
the messages to the attached queues.

There are statics addresses and queues that are defined in broker.xml. A
client can subscribe to those static addresses and will create a dinamic
queue each one to receive messages. Or If the programmer desires can code
the client so as to attached to a static queue defined in broker.xml by
means of the fully qualyfied name.

broker.xml  static addres and queue
 
 

   



client, field for fully qualyfied name 
  private String topic = "test::T1";

So in conclusion if you want to subscribe to a Wildfly16 Artemis from a Mqtt
client you should set the standalone-full.xml to allow autocreation of
queues.



And that is all, allow the clients to create their own queues atached to the
addresses.


Now I will try to set SSL support for Artemis in Wildfly16

Rafael




--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Failed to start ActiveMQ

[norinos2]

Hi

I use ActiveMQ 5.13.1.

When I start ActiveMQ, An java.util.ConcurrentModificationException occured,
and failed to start MQ.

The following log was output.

-
 INFO  | Recovery replayed 1 operations from the journal in 0.02 seconds. |
org.apache.activemq.store.kahadb.MessageDatabase | main
 INFO  | PListStore:[///tmp_storage] started |
org.apache.activemq.store.kahadb.plist.PListStoreImpl | main
 INFO  | Apache ActiveMQ 5.13.1 (imapsbroker_push_imaps0,
ID:---0:1) is starting |
org.apache.activemq.broker.BrokerService | main
 INFO  | Listening for connections at: mqtt+ssl://:8155 |
org.apache.activemq.transport.TransportServerThreadSupport | main
 INFO  | Connector mqtt+ssl started |
org.apache.activemq.broker.TransportConnector | main
 ERROR | Failed to start Apache ActiveMQ ([imapsbroker_push_imaps0,
ID:---0:1], java.util.ConcurrentModificationException) |
org.apache.activemq.broker.BrokerService | main
 INFO  | Apache ActiveMQ 5.13.1 (, ID:---0:1) is shutting
down | org.apache.activemq.broker.BrokerService | main
-


When this problem occurred, MQ was started with multiple connection
requests.
Is this the cause?






--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html