[ 
https://issues.apache.org/jira/browse/AMQ-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16559808#comment-16559808
 ] 

Jeff Genender commented on AMQ-7015:
------------------------------------

I'm sorry Gary, that is not a technical reason, its a procedural reason.  This 
does not affect the running broker and there are dozens of settings in ActiveMQ 
that changes the way the broker works.  This does not alter the handling of XA 
transactions unless it is set, and it alters the setting just like the mbean 
does.  So I disagree.

The sad part is you are not offering other possibilities to have all of this.  
You are digging in your heals.  There is now community support for this option:

http://activemq.2283324.n4.nabble.com/Discuss-AMQ7015-tp4741551.html

Unfortunately, unless you have a technical reason, your -1 doesn't stick and it 
goes in.  If you want to bring this to the PMC, we can discuss this there.

> 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)

Reply via email to