Re: Artemis and RESTeasy jar files

2018-02-22 Thread tcomprak
Here is my entire broker.xml file:

[vncuser@qa-centos7x64-102 broker1]$ cat etc/broker.xml 



http://www.w3.org/2001/XMLSchema-instance;
   xsi:schemaLocation="urn:activemq
/schema/artemis-configuration.xsd">

   http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation="urn:activemq:core ">

  0.0.0.0

  true

  
  ASYNCIO

  ./data/paging

  ./data/bindings

  ./data/journal

 
./data/large-messages

  true

  2

  -1

  10M
  
  
  36000


  
  4096
  

  

  
  

  
  

  
  

  
  




  
  5000

  
  90

  
  true

  12

  6

  HALT

  

  

 
 
 

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

 
 tcp://0.0.0.0:5672?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=AMQP;useEpoll=true;amqpCredits=1000;amqpMinCredits=300

 
 tcp://0.0.0.0:61613?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=STOMP;useEpoll=true

 
 tcp://0.0.0.0:5445?protocols=HORNETQ,STOMP;useEpoll=true

 
 tcp://0.0.0.0:1883?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=MQTT;useEpoll=true

 vm://0

  


  
 











 
  

  
 
 
DLQ
ExpiryQueue
0

-1
   
10
PAGE
true
true
true
true
 
 
 
DLQ
ExpiryQueue
0

-1
   
10
PAGE
true
true
true
true
 
  

  
 

   

 
 

   

 
 

   

 
  


   
  myQ
  false



   





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


Re: Artemis and RESTeasy jar files

2018-02-22 Thread tcomprak
This is the exception after adding the in-vm acceptor. Thanks for the
response about defaults, thatz what i thought, but just wanted to be really
sure.


12:01:30,129 WARN  [org.eclipse.jetty.webapp.WebAppContext] Failed startup
of context
o.e.j.w.WebAppContext@697446d4{/artemis-rest,file:///home/vncuser/artemis-brokers/broker1/tmp/jetty-localhost-8161-artemis-rest.war-_artemis-rest-any-1761735582786623780.dir/webapp/,UNAVAILABLE}{/home/vncuser/apache-artemis-2.4.0/web/artemis-rest.war}:
java.lang.RuntimeException:
ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007:
Cannot connect to server(s). Tried with all available servers.]
at
org.apache.activemq.artemis.rest.integration.RestMessagingBootstrapListener.contextInitialized(RestMessagingBootstrapListener.java:54)
[artemis-rest-2.4.0.jar:2.4.0]
at
org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:876)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:532)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:839)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:344)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1480)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1442)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:799)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:261)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at 
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:540)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:131)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:113)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:131)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at org.eclipse.jetty.server.Server.start(Server.java:452)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:105)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at org.eclipse.jetty.server.Server.doStart(Server.java:419)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.apache.activemq.artemis.component.WebServerComponent.start(WebServerComponent.java:134)
[artemis-web-2.4.0.jar:2.4.0]
at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:92)
[artemis-cli-2.4.0.jar:2.4.0]
at
org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:149)
[artemis-cli-2.4.0.jar:2.4.0]
at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:96)
[artemis-cli-2.4.0.jar:2.4.0]
at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:123)
[artemis-cli-2.4.0.jar:2.4.0]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[rt.jar:1.8.0_161]
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[rt.jar:1.8.0_161]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[rt.jar:1.8.0_161]
at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_161]
at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:129)
[artemis-boot.jar:2.4.0]
at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:49)
[artemis-boot.jar:2.4.0]
Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED

Re: Artemis and RESTeasy jar files

2018-02-22 Thread tcomprak
Thanks. I added that as well now as follows


 vm://0

  

Still get the same exception...

Is it necessary to do this REST configuration as described or would the
defaults automatically get picked up?

The Apache ActiveMQ Artemis REST implementation does have some configuration
options. These are configured via XML configuration file that must be in
your WEB-INF/classes directory. You must set the web.xml context-param
rest.messaging.config.file to specify the name of the configuration file.
Below is the format of the XML configuration file and the default values for
each.



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


Re: Artemis and RESTeasy jar files

2018-02-22 Thread tcomprak
When I start the artemis service, I see this

11:21:32,464 INFO  [io.hawt.system.ProxyWhitelist] Initial proxy whitelist:
[localhost, 127.0.0.1, 10.140.129.24, qa-centos7x64-102.sv.splunk.com]
11:21:33,763 WARN  [org.eclipse.jetty.webapp.WebAppContext] Failed startup
of context
o.e.j.w.WebAppContext@27494e46{/artemis-rest,file:///home/vncuser/artemis-brokers/broker1/tmp/jetty-localhost-8161-artemis-rest.war-_artemis-rest-any-1297401241729321808.dir/webapp/,UNAVAILABLE}{/home/vncuser/apache-artemis-2.4.0/web/artemis-rest.war}:
java.lang.RuntimeException:
ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007:
Cannot connect to server(s). Tried with all available servers.]
at
org.apache.activemq.artemis.rest.integration.RestMessagingBootstrapListener.contextInitialized(RestMessagingBootstrapListener.java:54)
[artemis-rest-2.4.0.jar:2.4.0]
at
org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:876)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:532)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:839)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:344)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1480)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1442)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:799)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:261)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:540)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:131)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:113)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:131)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at org.eclipse.jetty.server.Server.start(Server.java:452)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:105)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at org.eclipse.jetty.server.Server.doStart(Server.java:419)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
[jetty-all-9.4.3.v20170317-uber.jar:9.4.3.v20170317]
at
org.apache.activemq.artemis.component.WebServerComponent.start(WebServerComponent.java:134)
[artemis-web-2.4.0.jar:2.4.0]
at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:92)
[artemis-cli-2.4.0.jar:2.4.0]
at
org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:149)
[artemis-cli-2.4.0.jar:2.4.0]
at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:96)
[artemis-cli-2.4.0.jar:2.4.0]
at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:123)
[artemis-cli-2.4.0.jar:2.4.0]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[rt.jar:1.8.0_161]
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[rt.jar:1.8.0_161]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[rt.jar:1.8.0_161]
at java.lang.reflect.Method.invoke(Method.java:498)
[rt.jar:1.8.0_161]
at
org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:129)
[artemis-boot.jar:2.4.0]
at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:49)
[artemis-boot.jar:2.4.0]
Caused by: 

Re: Artemis and RESTeasy jar files

2018-02-22 Thread tcomprak
I had missed artemis-rest earlier in the request. Now I get a service
unavailable though.

[vncuser@qa-centos7x64-102 broker1]$ curl --get
http://localhost:8161/artemis-rest/queues/myQ



Error 503 Service Unavailable


HTTP ERROR 503

Problem accessing /artemis-rest/queues/myQ. Reason:
Service Unavailable Powered by Jetty://
9.4.z-SNAPSHOT   



[vncuser@qa-centos7x64-102 broker1]



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


Re: Artemis and RESTeasy jar files

2018-02-22 Thread tcomprak
Thanks. I configured a queue in the broker.xml file and re started artemis.
Added the queue element inside the core element like this




   
  myQ
  false





and I get this

[vncuser@qa-centos7x64-102 broker1]$ curl --head
http://localhost:8161/queues/myQ
HTTP/1.1 404 Not Found
Date: Thu, 22 Feb 2018 18:54:20 GMT
Cache-Control: must-revalidate,no-cache,no-store
Content-Type: text/html;charset=iso-8859-1
Content-Length: 325
Server: Jetty(9.4.z-SNAPSHOT)





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


Artemis backup configuration and sending messages to backup server

2018-02-21 Thread tcomprak
If I configure artemis in a cluster where there is only 1 live server and a
few backup server, do the clients explicitly have to know the live server's
IP address to interact or can the clients interact even with the backup
servers and artemis would forward it to the live appropriately?



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


Re: Artemis and RESTeasy jar files

2018-02-21 Thread tcomprak
Thanks Justin. I did what you mentioned below

- Copied the .war file to the web directory
root@sh3:~/apache-artemis-2.4.0/web# ls
activemq-branding.war  activemq-rest.war  api  artemis-plugin.war 
console.war examples  hacking-guide  images  index.html  META-INF  styles 
user-manual
root@sh3:~/apache-artemis-2.4.0/web#

- Created a new broker and added the web element in its etc/bootstrap.xml
file as follows
 
   http://localhost:8161; path="web">
   
   
   
   
   

- after which I started the broker
root@sh3:/var/lib/mybroker# ./bin/artemis-service start
Starting artemis-service
artemis-service is now running (31401)
root@sh3:/var/lib/mybroker#

But I'm unable to access it from my browser
http://10.141.65.248:8080/activemq-rest/queues



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


Re: Artemis and REST interface

2018-02-20 Thread tcomprak
I have the .war file now and I also have a artemis broker service running ?
Can you please help me with what I do from here - How do I deploy this .war
file with a linux process ?



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


Re: Artemis and RESTeasy jar files

2018-02-20 Thread tcomprak
I figured out the error part, I had by mistaked named WEB-INF as WEB_INF.
Renamed it and that fixed it.

Still would like to know which RESTEasy jar files have to be picked. For
now, I added this and the mvn install completed

  
  org.jboss.resteasy
  resteasy-jaxrs
  2.3.2.Final
  

Is this good enough ?

My .war file looks like this

root@sh3:~/artemis-rest/target# ls
artemis-rest-1.0-SNAPSHOT  artemis-rest-1.0-SNAPSHOT.war  maven-archiver
root@sh3:~/artemis-rest/target#

Now, the documentation says "For example, if you've constructed a WAR as
described above named "activemq-rest.war" then clients will access it at,
e.g. http://localhost:8080/activemq-rest/[queues|topics]"

I'm lost what exactly I would do with this .war file now...



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


Artemis and RESTeasy jar files

2018-02-20 Thread tcomprak
https://activemq.apache.org/artemis/docs/latest/rest.html

The documentation above has this line "If RESTEasy is not installed within
your environment, you must add the RESTEasy jar files within the lib
directory as well"

Which RESTEasy jar files are exactly needed ?

Also, when I tried to generate the .war file, I got this - what does this
error mean ?

[INFO] Packaging webapp
[INFO] Assembling webapp [artemis-rest] in
[/root/artemis-rest/target/artemis-rest-1.0-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/root/artemis-rest/src/main/webapp]
[INFO] Webapp assembled in [35 msecs]
[INFO] Building war: /root/artemis-rest/target/artemis-rest-1.0-SNAPSHOT.war
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 14.064 s
[INFO] Finished at: 2018-02-20T23:37:51+00:00
[INFO] Final Memory: 15M/331M
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-war-plugin:2.2:war (default-war) on project
artemis-rest: Error assembling WAR: webxml attribute is required (or
pre-existing WEB-INF/web.xml if executing in update mode) -> [Help 1]



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


Re: Artemis and REST interface

2018-02-20 Thread tcomprak
Thanks Justin. What threw me off is this

"Apache ActiveMQ Artemis's REST interface is installed as a Web archive
(WAR). It depends on the RESTEasy project and can currently only run within
a servlet container. Installing the Apache ActiveMQ Artemis REST interface
is a little bit different depending whether Apache ActiveMQ Artemis is
already installed and configured for your environment (e.g. you're deploying
within Wildfly) or you want the ActiveMQ Artemis REST WAR to startup and
manage the Apache ActiveMQ Artemis server (e.g. you're deploying within
something like Apache Tomcat)."

I presumed that this complicates the entire REST setup. Let us say I have
started a process with an artemis broker instantiated. On top of this, if I
have to get the REST service up, what minimal steps are needed ? Sorry, I'm
new to all these Web technologies - I really do appreciate your time and
effort in answering my questions. Thanks Justin.



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


Re: Artemis and REST interface

2018-02-20 Thread tcomprak
Just a bit more information on what I'm trying to do. I want to create a new
process that will host REST end points for creating topics/queue and for
publishing messages. This will just be a plain old linux process. I don't
want to making WAR / servelet containers as described in the documentation.
All I need is for a lightweight HTTP service to start as well when the
process starts which will allow me to define my own topic create / queue
create / publish message end points.



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


Re: Artemis and REST interface

2018-02-20 Thread tcomprak
However, I can say that Artemis already embeds the Jetty HTTP 
server which is how it currently serves stuff like the REST management API 
and the web console.  You might just be able to use that

> Sorry, I have a related question. Would using this server entail
> installing and configuring REST as described in
> https://activemq.apache.org/artemis/docs/1.0.0/rest.html ? The problem
> I have is that my use case does not allow for any kind of WAR /
> servelet deployments. What I need is something very simple where the
> HTTP service can be started programmatically and I am able to define
> some end points.



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


Re: Artemis and REST interface

2018-02-20 Thread tcomprak
I see. Thanks Justin



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


Re: Artemis and REST interface

2018-02-20 Thread tcomprak
Thanks, I actually have an use case where I have to define some more custom
REST end points. Is it technically possible to package Apache httpd along
with Artemis so I have a lightweight REST server - any thoughts ?



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


Artemis and REST interface

2018-02-20 Thread tcomprak
After having read this -
https://activemq.apache.org/artemis/docs/1.0.0/rest.html

I see that there are REST APIs to produce and consume messages, are there
APIs as well to manage topics/queues - for e.g. to create/delete
topics/queues ?



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


Re: Artemis and asynchronous consumer

2018-02-20 Thread tcomprak
Using JMS.



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


Artemis and asynchronous consumer

2018-02-20 Thread tcomprak
Is there an example of how artemis can used whereby subscribers can be
notified when messages arrive on a topic/queue? I want to use Artemis with
the pub-sub messaging with subscribers getting notified when messages arrive
on the queue.



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


Artemis HA master/slave

2018-02-16 Thread tcomprak
I have  a few questions about Artemis' HA feature

- When multiple backups are configured, does replication happen to all the
backups from the live server?
- Is there a way to prioritize the slaves as to who can become live when the
current live server goes down?
- Under normal scenarios, how long does it take for a backup to realize that
the live is down and make itself live?

Thanks



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


Artemis and Python Client implementation

2018-02-15 Thread tcomprak
Where can I find Python Client implementation APIs for Artemis. Is there a
python library which one can use to pub/sub from Artemis queues? Thanks.



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


Re: ActiveMQ Artemis Clustering

2018-02-15 Thread tcomprak
Thanks Justin. I presume one could then have 1 live + "n" backups and still
there wouldn't be any load balancing / redistribution. Is my understanding
correct ?



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


ActiveMQ Artemis Clustering

2018-02-14 Thread tcomprak
Is there a way to set up Artemis clustering just for HA purposes. I don't
need server side message load balancing or client side load balancing or
message redistribution. Will setting message-load-balancing to off suffice ?
Thanks.



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


Artemis and Python

2018-02-14 Thread tcomprak
I am contemplating using Artemis as a message broker. My use case is the
following:

- Messages are not published at a very high scale. Probably a few thousand
messages every minute or so
- Need persistent messages with guaranteed delivery
- Need a HA solution (There is no shared storage, so will have to be
replication) so that client can failover and continue publishing/subscribing
messages
- Should do not depend on any external services (like zookeeper) - the
deployment must be extremely simple
- Clustering is not a must, but if it's required for replication, it's setup
must be very simple

Based on the above and after reading the Artemis user manual, it seems like
Artemis would be a good fit. I however have a few questions

- Does Artemis support Python client APIs ? The user manual does not say it
explicitly, but I want to be really sure
- I understand that no external services are needed - Can someone please
confirm?
- If I need HA with replication policy, is clustering a must ?
- Is setting up a cluster straightforward with Artemis?
- Does Artemis work well or windows platforms ? Any known weirdness/quirks?



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