Re: JMSMessageID filtering

tabish...@gmail.com wrote > The broker won't be able to select on the MessageID as the AMQP message > ID is foreign to the broker and it must create its own internal instance > in order to properly function so the ID the client assigns wouldn't > match what the real broker side message has as

JMSMessageID filtering

ssageID formats - with/without 'ID::' prefix, with/without ':1:1:1-1' suffix, etc. Is this correct way how to filter MessageID ? I suppose AMQP filtering is not supported (for example: amqp.message_id)? Regards, Vavricka -- View this message in context: http://activemq.2283324.n4.nab

Re: [Artemis, Qpid JMS] Connection limit

Robbie Gemmell wrote > Credentials in this case means a username and password. > > The logs suggest the server offered PLAIN and ANONYMOUS mechs, the > client couldnt do PLAIN because it had no user details to do it with, > and so it selected ANONYMOUS. Thanks, PLAIN with username and password

Re: [Artemis, Qpid JMS] Connection limit

ber.truststore;trustStorePassword=123456 users.properties file: user1=CN=user1,O=Unknown,L=Unknown,ST=Unknown,C=Unknown groups.properties file: amq=user1 Am I doing everything right to get SSL connection working? Vavricka -- View this message in context: http://activemq.2283324.n4.nabb

Re: [Artemis] Set allowed SASL mechanisms

Yes, I meant SASL EXTERNAL mechanism for authentication. Vavricka Jakub Scholz wrote > I think he means the SASL EXTERNAL mechanism for authentication. > > J. -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-Set-allowed-SASL-mechanisms-tp4711889p471

[Artemis] Set allowed SASL mechanisms

Hi, I am trying to restrict SASL mechanisms. I could not find how to do it in documentation. Is it possible to restrict SASL mechanisms for instance to EXTERNAL only? Vavricka -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-Set-allowed-SASL-mechanisms

[Artemis, Qpid JMS] Connection limit

Hi, I am testing Artemis 1.3.0-SNAPSHOT with Qpid JMS 0.9.0 client. I manage to configure restriction for user "user2" by setting below in broker.xml. 5 When I try non-ssl connection, server correctly allow only 5 active connection. When

Exception when sending 10 kB message

(Thread.java:745) Vavricka -- View this message in context: http://activemq.2283324.n4.nabble.com/Exception-when-sending-10-kB-message-tp4701387.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Exception when sending 10 kB message

persistent and non_persistent messages and sending both messages ended with exception on the server. I also tried to remove jms.forceAsyncSend and amqp.idleTimeout from connection string with same result. Vavricka -- View this message in context: http://activemq.2283324.n4.nabble.com/Exception-when

Re: Artemis: Cannot send or receive to queue

server. After that I removed filter and durable parameters and I thought that queue will change accordingly. That was obviously bad guess. Hope this can help others in same situation. Thanks a lot for your help. Vavricka andytaylor wrote What client are you using to subscribe? If you provide

Artemis: Cannot send or receive to queue

Hi, I set up artemis broker by readme file. I successfully managed to get artemis broker working. When I want to test against JMS clients (http://mvnrepository.com/artifact/org.apache.qpid/qpid-jms-client/0.3.0 and http://mvnrepository.com/artifact/org.apache.qpid/qpid-amqp-1-0-client-jms/0.32)

Re: Artemis: Cannot send or receive to queue

to core queues defined in configuration file broker.xml. When defined as JMS queues or core queues created by clients, sending and receiving works fine. Unfortunately auto creation of queues is also not suitable for me. I need to define queues in configuration file. Thanks, Vavricka andytaylor