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.