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
