Exclude journal type MAPPED from allowed journal type values ------------------------------------------------------------ Key: WFLY-8520 URL: https://issues.jboss.org/browse/WFLY-8520 Project: WildFly Issue Type: Bug Components: JMS Reporter: Jeff Mesnil Assignee: Jeff Mesnil Priority: Minor CLI shows value {{MAPPED}} as allowed for parameter {{journal-type}}. {code} /subsystem=messaging-activemq/server=default:read-resource-description {code} {panel} "journal-type" => { "type" => STRING, "description" => "The type of journal to use.", "attribute-group" => "journal", "expressions-allowed" => true, "required" => false, "nillable" => true, "default" => "ASYNCIO", "allowed" => [ "NIO", "ASYNCIO", {color:#d04437}"MAPPED"{color} ], "access-type" => "read-write", "storage" => "configuration", "restart-required" => "all-services" }, {panel} This feature is not supported. Choosing journal type MAPPED results in following exception {code} 14:26:10,232 ERROR [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 73) AMQ224000: Failure in initialisation: java.lang.IllegalArgumentException: AMQ119051: Invalid journal type MAPPED at org.apache.activemq.artemis.core.persistence.impl.journal.JournalStorageManager.init(JournalStorageManager.java:140) [artemis-server-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1] at org.apache.activemq.artemis.core.persistence.impl.journal.AbstractJournalStorageManager.<init>(AbstractJournalStorageManager.java:216) [artemis-server-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1] at org.apache.activemq.artemis.core.persistence.impl.journal.JournalStorageManager.<init>(JournalStorageManager.java:104) [artemis-server-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1] at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.createStorageManager(ActiveMQServerImpl.java:1863) [artemis-server-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1] at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart1(ActiveMQServerImpl.java:2000) [artemis-server-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1] at org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:62) [artemis-server-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1] at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:520) [artemis-server-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1] at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:469) [artemis-server-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1] at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:412) [artemis-jms-server-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1] at org.wildfly.extension.messaging.activemq.jms.JMSService.doStart(JMSService.java:199) [wildfly-messaging-activemq-7.1.0.Alpha1-redhat-15.jar:7.1.0.Alpha1-redhat-15] at org.wildfly.extension.messaging.activemq.jms.JMSService.access$000(JMSService.java:63) [wildfly-messaging-activemq-7.1.0.Alpha1-redhat-15.jar:7.1.0.Alpha1-redhat-15] at org.wildfly.extension.messaging.activemq.jms.JMSService$1.run(JMSService.java:97) [wildfly-messaging-activemq-7.1.0.Alpha1-redhat-15.jar:7.1.0.Alpha1-redhat-15] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_65] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_65] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_65] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_65] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_65] at org.jboss.threads.JBossThread.run(JBossThread.java:320) [jboss-threads-2.2.1.Final-redhat-1.jar:2.2.1.Final-redhat-1] {code} From user experience point of view, this MAPPED should be excluded from allowed values for attribute {{journal-type}}.