Skip to content
Permalink
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
82 lines (54 sloc) 2.23 KB

Provide CLI operation which returns used journal type -NIOxASYNCIO.

Overview

When configuring the use of ASYNCIO for journal persistence, the Artemis server may fall back to NIO if the libaio binaries are not located. This state is not displayed to the user so he doesn’t know the effective journal type that is used. Adding a new runtime-journal-type attribute to read the effective journal type.

Issue Metadata

Issue

Dev Contacts

QE Contacts

Testing By

[X] Engineering

[ ] QE

Affected Projects or Components

  • Wildfly

  • ActiveMQ Artemis (finished)

Other Interested Projects

Requirements

  • Add a new `runtime-journal-type`read-only attribute to the /subsystem=messaging-activemq/server resource to obtain the effective journal type. The authorized values are

  • NONE: persistence disabled

  • NIO: Java NIO used

  • ASYNCIO: AsyncIO used with libaio

  • DATABASE: JDBC persistence

CLI to read the attribute:

/subsystem=messaging-activemq/server=default:read-attribute(name=runtime-journal-type)

Hard Requirements

Nice-to-Have Requirements

Non-Requirements

Test Plan

  • Changes in Wildfly management model will be covered in WF testsuite.

  • Checking the effective value on fall back will be tested in WF testsuite.

Community Documentation

  • Covered by attribute description in management model.

You can’t perform that action at this time.