Details
-
Bug
-
Resolution: Done
-
Major
-
7.1.0.DR11
-
None
Description
CLI Batch mode doesn't do roll back correctly during adding of distributed-workmanager of JCA
Steps to reproduce:
- ./standalone.sh -c standalone-ha.xml
- ./jboss-cli.sh -c
- # batch
- /subsystem=jca/distributed-workmanager=newdwm:add(name=newdwm)
- /subsystem=jca/distributed-workmanager=newdwm/short-running-threads=newdwaaaaaaaaaa:add(queue-length=20,max-threads=20)
- run-batch
- # error is printed, correct, management commands were wrong
- list-batch
- discard-batch
- batch
- list-batch
- /subsystem=jca/distributed-workmanager=newdwm:add(name=newdwm)
- /subsystem=jca/distributed-workmanager=newdwm/short-running-threads=newdwm:add(queue-length=20,max-threads=20)
- list-batch
- run-batch
- # error is printed, wrong, because management commands are correct. Previous batch command probably doesn't do roll back correctly
- discard-batch
- reload
- batch
- /subsystem=jca/distributed-workmanager=newdwm:add(name=newdwm)
- /subsystem=jca/distributed-workmanager=newdwm/short-running-threads=newdwm:add(queue-length=20,max-threads=20)
- run-batch
- # works correctly, but only after reload
Attachments
Issue Links
- is cloned by
-
WFLY-8259 CLI Batch mode doesn't do roll back correctly during adding of distributed-workmanager of JCA
- Closed
- is related to
-
JBEAP-4610 "default" as default name for long-running-threads and short-running-threads leads to thread groups with the same name default-threads
- Closed