Bug 1021633

Summary: Add OperationStepHandlers do not properly check if runtime steps should be added
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: James Perkins <jperkins>
Component: LoggingAssignee: James Perkins <jperkins>
Status: CLOSED CURRENTRELEASE QA Contact: Nikoleta Hlavickova <nziakova>
Severity: unspecified Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: TBD EAP 6CC: brian.stansberry, pkremens
Target Milestone: ER7   
Target Release: EAP 6.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-15 16:17:25 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:
Embargoed:

Description James Perkins 2013-10-21 16:56:56 UTC 
The org.jboss.as.logging.LoggingOperations.LoggingAddOperationStepHandler uses OperationContext.getProcessType().isServer() to determine if runtime steps should be added. The OperationContext.isNormalServer() should be used instead otherwise runtime steps may get executed in ADMIN_ONLY mode.
Comment 2 JBoss JIRA Server 2013-10-29 17:06:21 UTC 
James Perkins <jperkins> made a comment on jira WFLY-2357

Pull request merged
Comment 3 Petr Kremensky 2013-11-15 14:02:27 UTC 
Verified on EAP 6.2.0.CR1.