[jboss-jira] [JBoss JIRA] (WFLY-8335) User should be informed when switching between JDBC and journal store in transactions subsystem

[ https://issues.jboss.org/browse/WFLY-8335?page=com.atlassian.jira.plugin.... ] Romain Pelisse commented on WFLY-8335: -------------------------------------- 1) Issues with alternatives is now fixed: {code:java} "use-hornetq-store" => { "type" => BOOLEAN, "description" => "Use the journal store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file system file per transaction log.It's alternative to jdbc based store.", "expressions-allowed" => false, "required" => false, "nillable" => true, "default" => false, "alternatives" => [ "use-jdbc-store", "use-journal-store" ],... "use-jdbc-store" => { "type" => BOOLEAN, "description" => "Use the jdbc store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file file per transaction log. It's alternative to journal based store.", "expressions-allowed" => false, "required" => false, "nillable" => true, "default" => false, "alternatives" => [ "use-journal-store", "use-hornetq-store" ], "requires" => ["jdbc-store-datasource"], "access-type" => "read-write", "storage" => "configuration", "restart-required" => "jvm" }, ... "use-journal-store" => { "type" => BOOLEAN, "description" => "Use the journal store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store creates normally one file system file per transaction log. The journal one consists from one file for all the transactions. It's alternative to jdbc based store.", "expressions-allowed" => false, "required" => false, "nillable" => true, "default" => false, "alternatives" => [ "use-jdbc-store", "use-hornetq-store" ], "access-type" => "read-write", "storage" => "configuration", "restart-required" => "jvm" } {code} 2) I could not reproduce the issue with batch in both standalone and domain mode: {code} [standalone@localhost:9990 /] batch [standalone@localhost:9990 / #] /subsystem=transactions:write-attribute(name=use-journal-store,value=true) [standalone@localhost:9990 / #] /subsystem=transactions:write-attribute(name=jdbc-store-datasource, value=java:jboss/datasources/ExampleDS) [standalone@localhost:9990 / #] /subsystem=transactions:write-attribute(name=use-jdbc-store,value=true) [standalone@localhost:9990 / #] run-batch The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed: Step: step-3 Operation: /subsystem=transactions:write-attribute(name=use-jdbc-store,value=true) Failure: WFLYCTL0105: use-journal-store is invalid in combination with use-jdbc-store {code} ----- {code} [domain@localhost:9990 /] batch [domain@localhost:9990 / #] /profile=default/subsystem=transactions:write-attribute(name=jdbc-store-datasource, value=java:jboss/datasources/ExampleDS) [domain@localhost:9990 / #] /profile=default/subsystem=transactions:write-attribute(name=use-journal-store,value=true) [domain@localhost:9990 / #] /profile=default/subsystem=transactions:write-attribute(name=use-jdbc-store,value=true) [domain@localhost:9990 / #] run-batch The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-3" => "WFLYCTL0105: use-journal-store is invalid in combination with use-jdbc-store"}} {code} Nevertheless I added a test for this use case in the testsuite. -- This message was sent by Atlassian JIRA (v7.2.3#72005)