[jboss-jira] [JBoss JIRA] (WFLY-8621) JMS journal is not stored in JDBC persistence storage

[Jeff Mesnil (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-8621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Mesnil moved JBEAP-10478 to WFLY-8621:
-------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-8621  (was: JBEAP-10478)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: JMS
                           (was: ActiveMQ)
    Affects Version/s: 11.0.0.Alpha1
                           (was: 7.1.0.DR9)
                           (was: 7.1.0.DR15)


> JMS journal is not stored in JDBC persistence storage
> -----------------------------------------------------
>
>                 Key: WFLY-8621
>                 URL: https://issues.jboss.org/browse/WFLY-8621
>             Project: WildFly
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 11.0.0.Alpha1
>            Reporter: Jeff Mesnil
>            Assignee: Martyn Taylor
>            Priority: Blocker
>              Labels: KK-DR17, eap7.1-rfe-failure
>
> JMS journal which is by default stored in bindings directory (files with jms extension) is not stored in JDBC persistence storage but data are still persisted in local file system.
> JMS journal stores only data about JMS objects which are created via JMX management (what is not widely used feature), so this issue has no serious impact on regular use cases. However fixing this issue requires *modification* of configuration *model*, so *Blocker* priority was set.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)