Re: [Artemis] [Bug] Consume from non-durable jms topic

2017-04-05 Thread abhijith
Thanks for the reply and thats interesting. Does this mean, in order to listen to a topic you would always need 2 roles? createNonDurableQueue and consume? Trying to understand difference with Queue. We don't need to have createDurableQueue role to consume from a queue..right? -- View this

Re: [Artemis] [Bug] Consume from non-durable jms topic

2017-04-05 Thread Justin Bertram
It looks to me like everything is working as it should. For a JMS client to create a consumer on a topic means that it has to create a subscription (i.e. a non-durable queue). If the user doesn't have permission to do this then it can't create a consumer on the topic. Justin - Original

[Artemis] [Bug] Consume from non-durable jms topic

2017-04-05 Thread abhijith
Hi, We are using Artemis 1.4.0 version and have a jms topic defined. We have defined two specific roles for all topics, one to send and another to consume artemis-roles.properties: sendtopic=testtopicuser consumetopic=testtopicuser broker.xml: When I try to send to this

Re: Apache Artemis - Stress-test time

2017-04-05 Thread Justin Bertram
I understand that you need TLS for your use-case. My desire is simply to determine what performance impact it is having. If SSL is your performance bottleneck then there's not a lot (if anything) the broker can change to increase performance. In any case, going much deeper with performance

Re: Apache Artemis - Stress-test time

2017-04-05 Thread francesco81
Hi Justin, unfortunately tls is mandatory for our use case :-( I can make a stress test session without it, but it wouldn't be so significative for the real case. Anyway, as you suggest, I'll try it just to see the difference in term of performances. Thanks -- View this message in context:

Re: Apache Artemis - Stress-test time

2017-04-05 Thread Justin Bertram
Have you tried your test without SSL? SSL can be pretty CPU intensive. Justin - Original Message - From: "francesco81" To: users@activemq.apache.org Sent: Wednesday, April 5, 2017 6:57:38 AM Subject: Re: Apache Artemis - Stress-test time Hi Martyn,

Re: EOFException in 5.14.0 - Standard Installation

2017-04-05 Thread Tim Bain
Another user had similar symptoms just a few days ago, and resolved the problem by setting keepalive=true on both the broker and the client. Does that solve the problem for you as well? On Apr 5, 2017 12:18 AM, "absie" wrote: > Hi > > I am new to ActiveMQ > > I have the

Re: Apache Artemis - Stress-test time

2017-04-05 Thread francesco81
Hi Martyn, after a while of stress-test sessions with the new 2.1.0-SNAPSHOT of Artemis, I'm fairly confident to say that ram consumption now seems ok. Currently, instead, we're facing some problems with cpu usage during clients connections. Our stress test program, at the beginning, initializes

EOFException in 5.14.0 - Standard Installation

2017-04-05 Thread absie
Hi I am new to ActiveMQ I have the vanilla set up of ActiveMQ on both a linux VM and a Windows box, with no changes to activemq.xml file. Everytime I try to connect with the HelloWorld Java example on the ActiveMQ page I get the following exception in the Client