Re: problems with master slave set up artemis 2.0

Thank you Justin for the reply. For the third case, i did both kill -9 and normal stop, and the symptom is the same, basically the "idle" backup was not able to become an "active" backup. For the first two cases, if it is expected behavior, how would we expect the replication delay or even data l

Re: Artemis v2.0 JDK8 dependency

> Question: Can I use anycast prefix to still have 'jms.queue' appended? Yes, I believe that will work. Justin - Original Message - From: "abhijith" To: users@activemq.apache.org Sent: Wednesday, May 10, 2017 3:02:56 PM Subject: Re: Artemis v2.0 JDK8 dependency Thanks for the clarific

Re: Artemis v2.0 JDK8 dependency

Thanks for the clarification. I will use CLI tool. Question: Can I use anycast prefix to still have 'jms.queue' appended? We have built some conventions around this prefix and checking if we have change it. -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-v2-0

Re: Integration between Node.js and ActiveMQ - how to use

On 10/05/17 08:36, pedro-masterasp wrote: Regarding my questions I found some of the answers: Q1: Given that STOMP is a protocol, if I find a NPM library for any of the other protocols, can I use Node.js with that given protocol? A1: The answer is yes. For example, using a MQTT library for Node

Re: Artemis v2.0 JDK8 dependency

Actually, using in broker.xml *is* still supported. You just need to add a reference to the artemis-jms.xsd in the "schemaLocation" of your broker.xml. To be clear, queues and topics defined in won't be prefixed with "jms.queue." and "jms.topic." respectively. In general it is recommended tha

Re: Artemis v2.0 JDK8 dependency

Pull request ? :) On Wed, May 10, 2017 at 1:35 PM abhijith wrote: > You have downgrade dependencies to be JDK7 compatible. You could just > include > http://www.mojohaus.org/extra-enforcer-rules/enforceBytecodeVersion.html > and > it will flag any issues including dependencies. > > > > -- > V

Re: Artemis v2.0 JDK8 dependency

You have downgrade dependencies to be JDK7 compatible. You could just include http://www.mojohaus.org/extra-enforcer-rules/enforceBytecodeVersion.html and it will flag any issues including dependencies. -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-v2-0-JDK8-d

Re: Artemis v2.0 JDK8 dependency

We can probably fix 1.5.x.. I'm not sure about the dependencies. On Wed, May 10, 2017 at 1:11 PM, abhijith wrote: > Another note which is on v1.5.4. This version also suffers from same > bytecode compatibility issues. > > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce) @ > credit-artemi

Re: Artemis v2.0 JDK8 dependency

Another note which is on v1.5.4. This version also suffers from same bytecode compatibility issues. [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce) @ credit-artemis-client --- [INFO] Restricted to JDK 1.7 yet org.apache.activemq:artemis-journal:jar:1.5.4:test contains org/apache/activemq

Re: Artemis v2.0 JDK8 dependency

below are the files ➜ activemq-artemis git:(master) grep -rnw . -e "" ./artemis-cli/src/test/resources/broker-reload.xml:25: ./artemis-cli/src/test/resources/broker.xml:25: ./artemis-features/src/main/resources/artemis.xml:28: ./artemis-junit/src/test/resources/embedded-artemis-jms-only.

Re: Artemis v2.0 JDK8 dependency

On Wed, May 10, 2017 at 11:16 AM, abhijith wrote: > Thanks for the clarification. > > Since we are talking about upgrade had one more question. > > Is defining JMS queues using tag in broker.xml not valid anymore in > Artemis v2.0? Yes.. it's not valid any longer... you may use the import confi

Re: Artemis v2.0 JDK8 dependency

Thanks for the clarification. Since we are talking about upgrade had one more question. Is defining JMS queues using tag in broker.xml not valid anymore in Artemis v2.0? I looked at JMS examples and it has been moved to new model. But I could still see bunch of references of it under tests/

Re: Artemis v2.0 JDK8 dependency

If you don't need AMQP and just JMS I would stick with 1.5.5. If you need AMQP or other clients beyond Java then get 2.0 and use an 1.5.5 client for what you need. On Wed, May 10, 2017 at 9:53 AM abhijith wrote: > sorry, any suggestion here? > > > > - > View this message in context: > http://ac

Re: Artemis v2.0 JDK8 dependency

sorry, any suggestion here? -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-v2-0-JDK8-dependency-tp4725798p4725888.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: ActiveMQ REST Api with HTTP

Hello, Point 1: I insert the the 4 following messages curl -u admin:admin -d "hello world 1" -H "Content-Type: text/plain" -XPOST "http://localhost:8161/api/message?destination=queue://Test_Kovac&&clientId=KovacIP1"; curl -u admin:admin -d "test selector" -H "selector test" -H "Content-Type: te

Re: ActiveMQ REST Api with HTTP

Hello Tim, First of all, thank you very much for replying. Concerning point 1: I have read your answer and I believe you are right. The clientID is not a filter. My Question: What is the function of the clientID, since I can asssign any value to it and it will work? Bottom line, I don't underst

Re: Virtual Destination fowarding with Selectors in ActiveMQ 5.14

that would require a different plugin. one thought, you could have a wildcard consumer of sorts that would cause a match (if it is possible to exclude all other know selector properties) and the selector cache plugin would keep that chap alive. In that way these messages could get trapped in a dest

Virtual Destination fowarding with Selectors in ActiveMQ 5.14

I have got it working very nicely as per http://activemq.apache.org/virtual-destinations.html Question: When a message is sent, which doesn't match any of the selectors, it is dropped - but this isn't logged. - What, if any config tweaks can be made, to log it? - Or does this require a new plugi

[org.apache.activemq.broker.TransportConnection.Transport] (qtp749972657-157) Transport Connection to: MQTTSocket_2052272783 failed: java.io.IOException: Invalid CONNECT encoding

I integrated activeMQ broker into my jboss in such a way that the broker is launched when jboss launch. This is transport connectors defined in my broker's config file: I tried a mqtt client using java paho mqttv3, this is how I tried to connect to my broker:

Re: org.apache.activemq.broker.TransportConnection.Transport - Transport Connection to: tcp://XX.XX.XXX.XXX:5445 failed: java.io.EOFException

Hi Tim, After quite long time, I got the thread dumps. I attach only one of 'master' ActiveMQ machine. thread_dump.log Here are weird info I noticed from thread_dump: - There are 4955 threads in WAITING state. - Most of them (

Re: Integration between Node.js and ActiveMQ - how to use

Hello Tim, Thank you for your reply. I highly appreciate it. Regarding my questions I found some of the answers: Q1: Given that STOMP is a protocol, if I find a NPM library for any of the other protocols, can I use Node.js with that given protocol? A1: The answer is yes. For example, using a