Re: Artemis 2.0 upgrade Shared datastore

One thing is certain. It should work. If not we should fix it. On Wed, May 17, 2017 at 7:33 PM Clebert Suconic wrote: > I think it will work. > > That's an area Justin Bertram and Martyn Taylor worked closer. I will let > them answer. > > > I can do some research

Re: Artemis 2.0 upgrade Shared datastore

I think it will work. That's an area Justin Bertram and Martyn Taylor worked closer. I will let them answer. I can do some research about it tomorrow if they are out tomorrow for any reason. On Wed, May 17, 2017 at 6:53 PM abhijith wrote: > Thanks for the info.

Re: Artemis 2.0 upgrade Shared datastore

Thanks for the info. I am assuming you are referring to `data` option present on server/bin/artemis and not distribution. Please let me know if both are same. Another question on migration, Will 1.4 clients work with 2.0 or they have to migrate. I was hoping they can continue to work with 1.4

Re: Artemis 2.0 upgrade Shared datastore

there's also the convert tool for the config. I recommend you testing (of course) the migration path somewhere outside of production. On Wed, May 17, 2017 at 4:26 PM, abhijith wrote: > Hi, > > We have a shared datastore setup and are currently running v1.4. We are

Re: Artemis 2.0 upgrade Shared datastore

It's not. You have to export and import it again. The address names won't require prefixes. On Wed, May 17, 2017 at 4:39 PM abhijith wrote: > Hi, > > We have a shared datastore setup and are currently running v1.4. We are > planning to upgrade to v2.1 with the

Artemis 2.0 upgrade Shared datastore

Hi, We have a shared datastore setup and are currently running v1.4. We are planning to upgrade to v2.1 with the same configuration. One of the question which came up was if datastore itself compatible with 2 major versions? If we have to rollback v2.1 for some reason will it work seamlessly

Re: QueueReceiver only receives first 400 messages

I found a destination policy of maxBrowsePageSize (set to 400 by default) was introduced in some release after 5.9.0 that is causing this behavior. I've raised that limit and now a QueueBrowser will return the correct number of messages. Now I'm trying to figure out what we should set the max

Re: [Apachecon] Artemis presentation today

Hi Clebert, Would be great if you could repost here once you have a link to the recording. Much appreciated, M On Wed, May 17, 2017 at 7:42 PM, Clebert Suconic wrote: > There was a camera recording the event. > > However I don't know how to recover the recording

Re: Connection to activemq broker is lost within one second

Hi, Related to what Ragoubi is experiencing, I posted a message a few days ago with this title: *Experiencing constant reconnects with paho Java client v1.1.1 and broker Active MQ 5.14.3.* I am basically seeing constant reconnects for both MqttClient instances (one subscriber and one publisher)

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

I'm not sure what you mean by appealing... Did you look into artemis at least? http://activemq.apache.org/artemis/ We have been working quite hard to make it a great broker beyond any sort of hypes... it's a solid codebase and being proof to be high performant. The AMQP protocol has been

Support for stomp over ws support? (Withouth port)

Hi! I was trying to make a stomp over websocket java client to connect me to url ws//my-ws-server/stomp (withouth port) with user/pwd credentials to subscribe me to topic/hello topic. To make this i was making an activeconnectionFactory this way: ActiveMQConnectionFactory

Re: Connection to activemq broker is lost within one second

This at the end of code, I am getting the problem just when I connect (IMqttToken token = sampleClient.connect(connOpts);). When I debug, I stop just after the connection line, and first the connectComplete(boolean reconnect, String serverURI) method of the callback is invoked and just after a

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

Thank you everyone for the help. After our analysis we have decided to move away from ActiveMQ as find its competitors more appealing. Special thanks to Gordon, I have given word of his project. I wish you all good luck. -- View this message in context:

Re: Connection to activemq broker is lost within one second

Uh, what about this line? "sampleClient.disconnect();" On May 17, 2017 7:30 AM, "aragoubi" wrote: > No, I am not closing connection, this is the client code and the broker > files(ra.xml, ironjacamar.xml, broker-config.xml): > > client.txt

Re: Connection to activemq broker is lost within one second

No, I am not closing connection, this is the client code and the broker files(ra.xml, ironjacamar.xml, broker-config.xml): client.txt broker-config.xml

Re: Connection to activemq broker is lost within one second

I know very little about MQTT (Tim Bish knows that code much better, so it's good that he's been involved in this thread so far), but I notice the following in the log you attached: 11:31:43,850 DEBUG [org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection] (qtp764114829-245) Filled 10

Re: Connection to activemq broker is lost within one second

I upgraded to activemq 5.14.3, and I changed log level to debug. Client still loosing connection just 1 second after connection. Here is my server.log file : server.log -- View this message in context: