Re: Avoid always creating a subscription to a topic when connecting as durable subscriber?

you will have to check on the server if you have the subscription. +1 on Tim Bain. about using JMX. If you were using ARtemis, you would be able to query for the existence of the queue using the core API as well. On Wed, Oct 26, 2016 at 3:11 PM, Tim Bain wrote: > You could determine if you have

ActiveMQ Locking down Web Console via LDAP

I'm in the process of setting up ActiveMQ to use LDAP on Active Directory. I have it working for the JMS connections but I'm running into some issues on the Web Console. I gone through all the doc's and email threads I can find on the subject. My setup is a Windows 10 desktop ActiveMQ loaded local

Re: Avoid always creating a subscription to a topic when connecting as durable subscriber?

You could determine if you have an existing subscription via JMX. http://activemq.apache.org/jmx.html On Oct 25, 2016 2:21 AM, "KrisVH" wrote: The broker is currently 5.13.1, and the client is a WSO2 ESB. The connection is made with Java code, this should be all the relevant code: -- View

Re: mqtt.js & artemis throws NPE on failed login

I confirm the problem, in particular using long passwords in MQTT causes NPE The issue is here https://issues.apache.org/jira/browse/ARTEMIS-826 Thanks Regards On Wed, Oct 26, 2016 at 2:56 PM, Clebert Suconic wrote: > Can you try a snapshot from master and open an issue if it still a problem?

Re: AW: Persistent messages and postgres backend

I second Art's suggestion to test whether the query is slow when run directly against the database. If so, is some other index used, or is a full table scan being done? If it's a full table scan even though the index was created, you need to figure out why not (which is a question for Postgres su

Re: mqtt.js & artemis throws NPE on failed login

Can you try a snapshot from master and open an issue if it still a problem? A test replicating it would be great. On Wednesday, October 26, 2016, Luca Capra wrote: > Hi all > I'm using a plain install of 1.4.0 and the node client "mqtt.js" > > I noticed that when a client fails a login I get >

mqtt.js & artemis throws NPE on failed login

Hi all I'm using a plain install of 1.4.0 and the node client "mqtt.js" I noticed that when a client fails a login I get 12:27:24,921 WARNING [io.netty.channel.DefaultChannelPipeline] An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handl