[
https://issues.apache.org/jira/browse/AMQ-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16559856#comment-16559856
]
Christopher L. Shannon commented on AMQ-7015:
---------------------------------------------
No problem, I was just pointing out he wasn't -1 so we can just leave it as for
the 5.15.5 release because you guys feel strongly about it.
And I don't want to get into a big long thing about this so this is the last
thing I will say....yes they are users and sure their opinion counts of course.
But since I've been part of the community for the past 3-4 years it has been
pointed out numerous times that the community is everyone and more than one
vendor. So I agree their opinion counts but strongly disagree that based on
that you can make a blanket statement and say there is "community support"
without anyone else's opinion. (Although you could probably make the argument
that there is lazy consensus since no one said they disagree)
> Startup performance improvement when log contains prepared transactions.
> ------------------------------------------------------------------------
>
> Key: AMQ-7015
> URL: https://issues.apache.org/jira/browse/AMQ-7015
> Project: ActiveMQ
> Issue Type: New Feature
> Affects Versions: 5.15.4
> Reporter: Heath Kesler
> Assignee: Jeff Genender
> Priority: Minor
> Fix For: 5.16.0, 5.15.5
>
>
> I have a KahaDB that's performing a recovery on each startup.
> Digging deeper into it I've found that the issue is that the db.log contains
> prepared transactions.
> The MessageDatabase will discard those entries in memory, however it does not
> remove transaction info from those messages (I believe that's by design). So
> on each restart, the broker will find those entries and again discard them in
> memory.
> If I access the broker via JMX, I can go to the prepared XAs and execute a
> clear on them one by one.
> When i restart my broker, i don't have a recovery attempted again.
> Performing a remove operation for each message can be very time consuming, so
> i'd like to introduce an optional parameter to allow all prepared XAs to be
> removed on recovery.
> Please see my forth coming patch with unit test.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
