in case its helpful ill add that when i look at the move from 2.1.0 to
2.2.0 https://github.com/apache/activemq-artemis/compare/2.1.0...2.2.0 i
can go to "Files changed", find AddressSettings.java and on line 724 (on
the 2.2.0 side) i can see the broker trying to decode a policyStr and it
can allow
I am to blame for introducing the confusion across threads. Sorry
I know that when I am on 2.1.0 and I have Queues and address settings
defined via the API at runtime (so they are not defined in the broker.xml)
I absolutely cannot upgrade from 2.1.0 to 2.2.0, 2.3.0, 2.4.0, or 2.5.0. So
the issue m
Ouch. I crossed posts. I thought this was the 30 min load thing.
Still u sure this is not fixed beyond 2.1.0?
On Sat, Jul 21, 2018 at 2:26 PM Clebert Suconic
wrote:
> @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 i
@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 wrote:
> I'm looking at a possible solution to this issue. Please open a JIR
created https://issues.apache.org/jira/browse/ARTEMIS-1984 sorry for the
delay. i was trying to perform some due diligence and test on the latest
version but with how long my restarts are taking (another issue addressed
in another thread) it made validating the error a bit more time consuming.
tha
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
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 sho
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
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
