@Justin why open a new JIRA? I’m pretty sure this is an issue I fixed beyond 2.2.0.
So unless this proves to be a new issue. Just have the user trying the new version ? On Fri, Jul 20, 2018 at 6:00 PM Justin Bertram <jbert...@apache.org> wrote: > I'm looking at a possible solution to this issue. Please open a JIRA as > previously requested. > > In the mean-time I think you could just use the "data" command to export > your 2.2.0 journal and then import into a new instance of 2.6.2 (or > whatever). Make sure your 2.2.0 instance is not running then from your > 2.2.0 instance's "bin" directory run: > > ./artemis data exp > /path/to/export.xml > > Delete the first line from export.xml (errant logging makes it into the > output). Then start the new instance and run this from the new instance's > "bin" directory: > > ./artemis data imp --input /path/to/export.xml > > Then shutdown the new broker instance and copy your address-settings, etc. > over. > > > Justin > > On Tue, May 15, 2018 at 3:51 PM, Dan Langford <danlangf...@gmail.com> > wrote: > > > i have been heads down for a few weeks with a couple big production > deploys > > and unable to come back to this until now. > > > > would you still like me to make a ticket in jira? > > > > @Clebert, you said you added compatibility tests in 2.5.0 "that should > > cover moving forward" does that mean that you think i should be able to > > move to 2.5 or i should be able to move up AFTER 2.5? > > > > also, is there anything you guys think of that i can do to upgrade my > 2.1.0 > > without destroying all my queues and rebuilding them on a newer version > > > > On Wed, May 9, 2018 at 8:11 PM Clebert Suconic < > clebert.suco...@gmail.com> > > wrote: > > > > > I have added compatibility tests in 2.5.0. That should cover moving > > > forward. > > > > > > > > > Any other issues we can add more compatibility tests. > > > > > > On Tue, May 1, 2018 at 3:03 AM michael.andre.pearce < > > > michael.andre.pea...@me.com> wrote: > > > > > > > This seems genuine bug for the upgrade from 2.1 to 2.2 suprised no > one > > > > else has seen it though including ourselves (we upgraded a long while > > > back > > > > and don't remember such issue), can you raise a Jira for this. > > > > > > > > > > > > > > > > > > > > Sent from my Samsung Galaxy smartphone. > > > > -------- Original message --------From: Dan Langford < > > > > danlangf...@gmail.com> Date: 30/04/2018 22:12 (GMT+00:00) To: > > > > users@activemq.apache.org Subject: [Artemis] upgrade from 2.1.0 > > getting > > > > errors around config-delete-queues > > > > we are running 2.1.0 and i tried to upgrade to 2.5.0 and ran into > some > > > > problems. in an attempt to isolate the problem i rolled things back > and > > > > just attempted to upgrade to 2.2.0. The startup exception i saw on > both > > > > 2.5.0 and 2.2.0 are quite similar. > > > > > > > > 2.5.0 > > > > ==== > > > > > > > > ERROR [org.apache.activemq.artemis.core.server] AMQ224000: Failure in > > > > initialisation: java.lang.NegativeArraySizeException > > > > at > > > > > > > > > > > org.apache.activemq.artemis.api.core.SimpleString. > > readSimpleString(SimpleString.java:182) > > > > [artemis-commons-2.5.0.jar:2.5.0] > > > > at > > > > > > > > > > > org.apache.activemq.artemis.api.core.SimpleString. > > readSimpleString(SimpleString.java:171) > > > > [artemis-commons-2.5.0.jar:2.5.0] > > > > at > > > > > > > > > > > org.apache.activemq.artemis.api.core.SimpleString. > > readNullableSimpleString(SimpleString.java:158) > > > > [artemis-commons-2.5.0.jar:2.5.0] > > > > at > > > > > > > > > > > org.apache.activemq.artemis.core.buffers.impl.ChannelBufferWrapper. > > readNullableSimpleString(ChannelBufferWrapper.java:69) > > > > [artemis-commons-2.5.0.jar:2.5.0] > > > > at > > > > > > > > > > > org.apache.activemq.artemis.core.settings.impl.AddressSettings.decode( > > AddressSettings.java:736) > > > > [artemis-server-2.5.0.jar:2.5.0] > > > > > > > > 2.2.0 > > > > ==== > > > > ERROR [org.apache.activemq.artemis.core.server] AMQ224000: Failure in > > > > initialisation: java.lang.NegativeArraySizeException > > > > at > > > > > > > > > > > org.apache.activemq.artemis.api.core.SimpleString. > > readSimpleString(SimpleString.java:149) > > > > [artemis-commons-2.2.0.jar:2.2.0] > > > > at > > > > > > > > > > > org.apache.activemq.artemis.api.core.SimpleString. > > readNullableSimpleString(SimpleString.java:143) > > > > [artemis-commons-2.2.0.jar:2.2.0] > > > > at > > > > > > > > > > > org.apache.activemq.artemis.core.buffers.impl.ChannelBufferWrapper. > > readNullableSimpleString(ChannelBufferWrapper.java:69) > > > > [artemis-commons-2.2.0.jar:2.2.0] > > > > at > > > > > > > > > > > org.apache.activemq.artemis.core.settings.impl.AddressSettings.decode( > > AddressSettings.java:724) > > > > [artemis-server-2.2.0.jar:2.2.0] > > > > > > > > i went and looked at the source code for those and it appears during > > the > > > > decode when trying to read a value for config-delete-queues. I see > that > > > > this value was added in 2.2.0. > > > > > > > > How do i upgrade from 2.1.0? All of my addresses and queues are > defined > > > at > > > > runtime with the API (meaning they are not defined in the broker.xml > > > file). > > > > Is upgrade possible? did others run into this back when 2.2.0 was > > > released? > > > > > > > > thanks > > > > > > > -- > > > Clebert Suconic > > > > > > -- Clebert Suconic
