Bug 1021633 - Add OperationStepHandlers do not properly check if runtime steps should be added
Summary: Add OperationStepHandlers do not properly check if runtime steps should be added
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Logging
Version: TBD EAP 6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER7
: EAP 6.2.0
Assignee: James Perkins
QA Contact: Nikoleta Hlavickova
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-21 16:56 UTC by James Perkins
Modified: 2013-12-15 16:17 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-12-15 16:17:25 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-2357 0 Minor Resolved OperationStepHandlers do not properly check if runtime steps should be added 2014-08-13 10:50:50 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.