activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jdanekrh <>
Subject [GitHub] activemq-artemis pull request #566: Add info on JDBC Persistence
Date Tue, 07 Jun 2016 13:14:41 GMT
Github user jdanekrh commented on a diff in the pull request:
    --- Diff: docs/user-manual/en/ ---
    @@ -360,13 +360,31 @@ Using aptitude, (e.g. on Ubuntu or Debian system):
     ## Apache ActiveMQ Artemis JDBC Persistence
    -The Apache ActiveMQ Artemis JDBC persistence store is still under development and only
supports persistence of standard messages and bindings (this is everything except large messages
and paging).  The JDBC store uses a JDBC connection to store messages and bindings data in
records in database tables.  The data stored in the database tables is encoded using Apache
ActiveMQ Artemis journal encoding.
    +WARNING: The Apache ActiveMQ Artemis JDBC persistence store is under development and
is included for evaluation purposes.
    +The Apache ActiveMQ Artemis JDBC persistence layer offers the ability to store broker
state (Messages, Addresses and other
    +application state) using a database.  N.B. Address full policy Paging (See: [The section
on Paging]( is currently not
    +supported with the JDBC persistence layer.
    +Using the ActiveMQ Artemis File Journal is the recommended configuration as it offers
higher levels of performance and is
    +more mature.  The JDBC persistence layer is targetted to those users who must use a database
e.g. due to internal company
    +ActiveMQ Artemis currently has support for a limited number of database vendors (older
versions may work but mileage may
    +1. PostGres 9.4.x
    --- End diff --
    PostgreSQL or possibly Postgres (

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 or file a JIRA ticket
with INFRA.

View raw message