Re: Artemis 2.1.0 compatibility with 1.5.x

We really need the backwards comparability. Please let me know whether and how I can create a jira for this issue. Thanks. -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Artemis 2.1.0 compatibility with 1.5.x

Thanks but these all sound pretty foreign to me. First, are you saying, as a user, we should create a JIRA when we find a bug? Second, what is this VOTE process you are speaking of? -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Artemis 2.1.0 compatibility with 1.5.x

We see that Artemis 2.4.0 has been released. Has the compatibility issue with 1.5.5 resolved? -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Artemis 2.1.0 compatibility with 1.5.x

We are not mixing core version and jms version. -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-2-1-0-compatibility-with-1-5-x-tp4727741p4728629.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Artemis 2.1.0 compatibility with 1.5.x

It appears that you were able to reproduce the issue. Is there a plan to fix the problem? If so, what is your estimated time of completion? -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-2-1-0-compatibility-with-1-5-x-tp4727741p4728257.html Sent from the ActiveMQ

Re: Artemis 2.1.0 compatibility with 1.5.x

Justin Bertram, Yes, we can confirm we received the same error message when sending a text message from 2.1 and receiving at 1.5.5. -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-2-1-0-compatibility-with-1-5-x-tp4727741p4728032.html Sent from the ActiveMQ - User

Re: Artemis 2.1.0 compatibility with 1.5.x

Sorry, we don't. Any specific file/setting you need, let us know. -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-2-1-0-compatibility-with-1-5-x-tp4727741p4728029.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Artemis 2.1.0 compatibility with 1.5.x

We managed to reproduce our message size change problem with simple java programs (see QueueReader.java and QueueWriter.java ) based on your QueueExampl

Re: Artemis 2.1.0 compatibility with 1.5.x

nigro_franz, we have downloaded the branch you provided, compiled and tested but the same issue still exists. On the sending side (2.1.0), in org.apache.activemq.artemis.jms.client.ActiveMQMessageProducer.doSendx, jmsMessage.bodyLength=178; On the receiving side (1.5.1), in org.apache.activemq.ar

Artemis 2.1.0 compatibility with 1.5.x

We have been using Artemis 1.5.1. Recently we upgrade the server to 2.1.0. While it can communicate with 2.1.0 client successfully, it does not seem to work properly with 1.5.1 client. We are passing messages in protobuf format. The end result is the receiving end can no longer deserialize the pr

Re: Dynamic broker.xml - include properties

Yes, I am talking about the URI for acceptor element. For example, tcp://0.0.0.0:?sslEnabled=true;keyStorePath=${hornetq.remoting.netty.ssl.keystore.path};keyStorePassword=${xxx};trustStorePath=${hornetq.remoting.netty.ssl.truststore.path};trustStorePassword=${xxx} Here if ${hornetq.remotin

Re: Dynamic broker.xml - include properties

Ok. The properties appear to be working until I need to define a path and the path contains a whitespace (e.g. c:\program files\...) in it. -- View this message in context: http://activemq.2283324.n4.nabble.com/Dynamic-broker-xml-include-properties-tp4718825p4718861.html Sent from the ActiveMQ

Re: Dynamic broker.xml - include properties

I added the links. -- View this message in context: http://activemq.2283324.n4.nabble.com/Dynamic-broker-xml-include-properties-tp4718825p4718834.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Dynamic broker.xml - include properties

I am working on migrating from HornetQ server to Artemis. In our hornetq-configuration.xml, we had our acceptors defined with params. For example, I don't see an equivalent in broker.xml since now URI is used. Can I do something like the following? -- View this message in context: http://ac

Re: HornetQ client connect to Artemis server

I am all set. My problem was when we embedded the Artemis server, we missed the jar arttemis-hornetq-protocol-1.x.0.jar. Thanks. -- View this message in context: http://activemq.2283324.n4.nabble.com/HornetQ-client-connect-to-Artemis-server-tp4717861p4718084.html Sent from the ActiveMQ - User m

Re: HornetQ client connect to Artemis server

Thanks for your response. I looked into the extra-tests you talked about. I created a simple application acting as the hornetq client, using the code in the test. Here is my java code. package hornetqTest; import java.util.HashMap; import java.util.Map; import java.ut

HornetQ client connect to Artemis server

We are in the process upgrading from HornetQ (2.4.7) to Artemis (1.4.0). Artemis server migration itself is working - server running and Artemis client can talk to server. However, we still need to support clients who use HornetQ client. We need HornetQ clients to be able to talk to the Artemis ser