Description of problem: When trying to change logging level of periodic file handler via JON, it fails with: {JBAS014653: Composite operation failed and was rolled back. Steps that failed:={Operation step-3=JBAS014746: file may not be null}}, rolled-back=true Version-Release number of selected component (if applicable): Version-Release number of selected component (if applicable): EAP 6.1.0.DR4 and JON 3.1.2 How reproducible: always Steps to Reproduce: 1. import EAP 6.1 standalone 2. create Periodic File Handler resource under logging subsystem 3. Configure this new resource (try updating logging level for example) Actual results: Configuration update fails with: {JBAS014653: Composite operation failed and was rolled back. Steps that failed:={Operation step-3=JBAS014746: file may not be null}}, rolled-back=true Expected results: successfully changed configuration level Additional info: I have no problem to change the attribute level via EAP 6.1 cli
I wonder if this changed between EAP6.0 and 6.1
I've just tried it with EAP 6.0.1 and it works as expected => it has to be caused by some change between EAP 6.0 and EAP 6.1
This is actually a bug in EAP 6.1 and is fixed in EAP 6.1.0.ER4 (https://bugzilla.redhat.com/show_bug.cgi?id=948264)