+1 on the parameter
I strongly agree with the not all users can use the MBean - if an optional parameter can be used here to clear the user scenario, and its properly documented as to what it does, than I'd have no issue with it existing. On Thu, Jul 26, 2018 at 3:23 PM jgenender <[email protected]> wrote: > > Hi Johan, > > That was exactly what that attribute was added for. I had a discussion with > Gary this morning (Gary please correct me if I am wrong on any points) was > that he felt that having an MBean that can do a full sweep instead of a > parameter would be better. Unfortunately for some, an MBean may not be > plausible. An attribute seems like a simple way to do this and acts almost > no differently than the > ignoreMissingJournalfiles/checkForCorruptJournalFiles parameters. The > attribute does the exact same thing as the MBean without the need to use the > MBean. The difference is that yes, its an attribute in the config file and > at second boot it executes again. But what if that is what you want? If > you don't want it, then you can remove it. > > I am in agreement with you that this seems like a decent enhancement and I > would be interested in what the technical reason is that this attribute > should not be included. I don't think that we should be only shoe-horning > the end user into a single way/method to clear out the preparedXA records > that are stuck. Offering multiple ways to do this only is advantageous to > the end user. Not everyone wants nor can use the MBean. So this allows > users to do the same en-masse with a parameter. > > Anyone have a solid technical reason not to implement AMQ-7015? > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html
