Bug 1327229

Summary: [EAP7] updating configuration for async handler fails
Product: [JBoss] JBoss Operations Network Reporter: Radim Hatlapatka <rhatlapa>
Component: Plugin -- JBoss EAP 7Assignee: Ruben Vargas Palma <rvargasp>
Status: CLOSED CURRENTRELEASE QA Contact: Sunil Kondkar <skondkar>
Severity: medium Docs Contact:
Priority: medium    
Version: JON 3.3.5CC: fbrychta, hrupp, loleary, lzoubek, mfoley, rhatlapa, rhq-maint, rvargasp, skondkar, spinder, theute
Target Milestone: CR01Keywords: Triaged
Target Release: One-off release   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-06 18:57:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1314853    

Description Radim Hatlapatka 2016-04-14 14:16:38 UTC 
Description of problem:

Updating async handler fails with [1]. Note in EAP 7 async handler really doesn't have formatter attribute.

Version-Release number of selected component (if applicable):
EAP 7.0.0 JON 3.3.5 with JON EAP plugin update ER1 from BZ#1314853

How reproducible: always


Steps to Reproduce:
1. have EAP 7.0.0 standalone imported
2. create a new 'Async Handler' within logging subsystem 
3. update it's configuration (e.g. changing Queue Length)
  
It should be successful, but it fails with [1]


[1] {WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:={Operation step-1=WFLYCTL0201: Unknown attribute 'formatter'}}, rolled-back=true
Comment 1 Ruben Vargas Palma 2016-04-14 21:27:45 UTC 
commit 75605c9840c14592f0d76bc2290a539206756ca0
Author: Ruben Vargas <rvargasp>
Date:   Thu Apr 14 15:05:19 2016 -0500

    Bug 1327229 - [EAP7] updating configuration for async handler fails
Comment 7 Sunil Kondkar 2016-04-29 10:18:05 UTC 
Verified on eap-update04-CR01

Configuration update for Async Handler is successful in configuration history. and there are no errors in logs. The modified Queue Length value appears in current configuration.