Description of problem: Version-Release number of selected component (if applicable): JON 3.1.2.GA+ EAP 6.1.DR4 How reproducible:always Steps to Reproduce: 1. import EAP 6.1 standalone 2. create Async Handler resource under logging subsystem 3. Configure this new resource (try updating queue-length for example) Actual results: Configuration update fails - EAP reports {JBAS014653: Composite operation failed and was rolled back. Steps that failed:={Operation step-4=JBAS014746: queue-length may not be null}}, rolled-back=true Expected results: configuration update should be successfull Additional info:
I was not even able to create the Async Handler from RHQ. Did you create it straight from the JBoss CLI?
I did it using JON UI. Did the 'creation operation' fail for you? or the resource just didn't show up? Note that when you import EAP6 discovery scan takes long time (up 10 minutes) and if you create a resource right after import you must wait till the already-running discovery scan finishes and resource-post-creation scan runs (and founds your resource)
Looks like a problem in EAP 6.1.DR4: if you open JBoss CLI and try to update the value from there it also fails with same message. [standalone@localhost:10631 async-handler=ASYNC] :write-attribute(name=queue-length,value=511) { "outcome" => "failed", "failure-description" => "JBAS014746: queue-length may not be null", "rolled-back" => true }
Added dependency on BZ912805
Closing as this was bug in EAP 6 which was fixed in EAP 6.1.0.ER4 build, not a bug in JON EAP6 plugin