]
Stefano Maestri moved JBEAP-9186 to WFLY-8259:
----------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-8259 (was: JBEAP-9186)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JCA
(was: JCA)
Affects Version/s: (was: 7.1.0.DR11)
CLI Batch mode doesn't do roll back correctly during adding of
distributed-workmanager of JCA
---------------------------------------------------------------------------------------------
Key: WFLY-8259
URL:
https://issues.jboss.org/browse/WFLY-8259
Project: WildFly
Issue Type: Bug
Components: JCA
Reporter: Stefano Maestri
Assignee: Stefano Maestri
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