activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-27) Database Implementation
Date Tue, 05 Jan 2016 16:13:39 GMT


ASF GitHub Bot commented on ARTEMIS-27:

GitHub user mtaylor opened a pull request:

    Add JDBC Storage Support

    This is the inital work towards ARTEMIS-27, adding Database storage support in Artemis.
    This is not yet finished, I'm opening this PR so people can start looking at the solution.
    There are still several areas that need to be completed (firstly this patch needs rebasing
on top of master), I'll also split this up into functional commits.  This patch currently
only adds support for journal persistence in JDBC, Paging and Large Messages still use regular
    So far, only Derby embedded DB has been tested.  See /home/mtaylor/dev/activemq-artemis/artemis-server/src/test/resources/database-store-config.xml
for an example of how to configure the database store.
    Also, look at the /home/mtaylor/dev/activemq-artemis/tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/persistence
tests for lower level examples.

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

    $ git pull JDBC2016

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

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

    This closes #295
commit d14330adb4748a2b8d6e5bb82fe2845fb9b976ae
Author: Paul Gallagher <>
Date:   2015-12-22T15:38:51Z

    Fix for missing dependencies at the top level pom

commit 27ca80b8f3a0bc7a91fdf8d7c4036464be3863e7
Author: Martyn Taylor <>
Date:   2015-08-04T14:41:54Z

    ARTEMIS-27 Add support for JDBC Journal


> Database Implementation
> -----------------------
>                 Key: ARTEMIS-27
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>            Reporter: clebert suconic
>            Assignee: Martyn Taylor
>            Priority: Critical
>             Fix For: 1.3.0
> Notice that I'm not calling this JDBC. It's Database:
> The storage interface here should take in consideration NoSQL databases as possible options.
> My idea is that we should have a Callback interface optimizing locking times and using
recator pattern through the OperationContext.
> Instead of using a single Executore could have multiple DB-Executors all capable of handling
multiple client connections.
> If we deal this with being Database centric (not JDBC centric) features from the NoSQL
could become available here for free

This message was sent by Atlassian JIRA

View raw message