GitHub user clebertsuconic opened a pull request:

    https://github.com/apache/activemq-6/pull/120

    Changes about storage order and few doc changes

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/clebertsuconic/activemq-6 master-journal-order

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-6/pull/120.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #120
    
----
commit a977c930e1cb86355ece031b6306aa9e490878f5
Author: Clebert Suconic <[email protected]>
Date:   2015-02-26T20:12:36Z

    Fixing when the storage is stopped for the storage manager
    
    In some cases the ID Generator will be called after the JournalStorage was 
stopped.
    AS a result you could have cases where the ID generator is called and the 
journal storage is stopped.
    
    Also I added some check to IDs and added some code to cleanup old IDS on 
the BatchIDManager

commit 1a007e59d301b3200dbb00a601e5209b66bb17ac
Author: Clebert Suconic <[email protected]>
Date:   2015-02-27T03:20:17Z

    adding note about paging / queue / filters

commit 67f6bf8709d82d065998b4bcaf1797497f792128
Author: Clebert Suconic <[email protected]>
Date:   2015-02-27T03:23:06Z

    Changes on configuring-transport:
    
    I - Removing note about deprecated properties. Our configs are using it
    II - useNIO property is irrelevant since we always use NIO now with the new 
netty

commit ff3e8aacc09c4a905b022125f29ad8a2def69eca
Author: Clebert Suconic <[email protected]>
Date:   2015-02-27T03:41:37Z

    adding wording about Camel

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to