[
https://issues.jboss.org/browse/WFCORE-966?page=com.atlassian.jira.plugin...
]
James Perkins edited comment on WFCORE-966 at 5/31/19 1:32 PM:
---------------------------------------------------------------
I thought this would have been fixed by WFCORE-3337. However it does seem in
{{admin-only}} mode on standalone or on a non-active domain profile you can still add
invalid handler names. This is true for the loggers as well. Either capabilities can't
guard against this, which I don't think is true, or there's something missing in
the capability integration with the logging subsystem.
was (Author: jamezp):
I though this would have been fixed by WFCORE-3337. However it does seem in {{admin-only}}
mode on standalone or on a non-active domain profile you can still add invalid handler
names. This is true for the loggers as well. Either capabilities can't guard against
this, which I don't think is true, or there's something missing in the capability
integration with the logging subsystem.
In domain mode non existing subhandler is saved to attributes.
--------------------------------------------------------------
Key: WFCORE-966
URL:
https://issues.jboss.org/browse/WFCORE-966
Project: WildFly Core
Issue Type: Bug
Components: Logging
Environment: Running unsecured EAP 7.0.0 DR9 version in domain mode.
Reporter: Patrik Cyprian
Assignee: James Perkins
Priority: Major
When you in domain mode in created async handler add non existing sub handler to
attributes it is successfully saved. In standalone mode it is not possible (subhandler is
not saved - saving operation failed).
1.Run EAP in domain mode (default profile)
2.Create async handler
3.Try to add non existing subhandler to async handler attributes
4.Try the same in standalone mode with standalone-full-ha profile
--
This message was sent by Atlassian Jira
(v7.12.1#712002)