[JBoss JIRA] (WFCORE-2999) Logging subsystem bump & transformers for EAP7
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2999?page=com.atlassian.jira.plugi... ]
James Perkins commented on WFCORE-2999:
---------------------------------------
Sorry, missed a comment on the bonus point. I'll have a look, but I'd rather not do any refactoring at this stage of development. Something we can definitely do for Core 4 though.
> Logging subsystem bump & transformers for EAP7
> ----------------------------------------------
>
> Key: WFCORE-2999
> URL: https://issues.jboss.org/browse/WFCORE-2999
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: Tomaz Cerar
> Assignee: James Perkins
> Priority: Critical
>
> Currently model version of logging subsystem is 3.0.0 same as in EAP 7.0.
> but model diff reports changes to the model.
> So it needs model bump to 4.0.0, as well as transformers.
> As a bonus point, it would be really good performance wise if we could move transformers registration to use non deprecated ExtensionTransformerRegistration API.
> model diff:
> {noformat}
> ====== Resource root address: ["subsystem" => "logging"] - Current version: 3.0.0; legacy version: 3.0.0 =======
> --- Problems for relative address to root ["file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["log-file" => "*"]:
> Different 'type' for attribute 'stream'. Current: STRING; legacy: LONG
> --- Problems for relative address to root ["logging-profile" => "*","file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["logging-profile" => "*","log-file" => "*"]:
> Different 'type' for attribute 'stream'. Current: STRING; legacy: LONG
> --- Problems for relative address to root ["logging-profile" => "*","periodic-rotating-file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["logging-profile" => "*","periodic-size-rotating-file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["periodic-rotating-file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["periodic-size-rotating-file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-2999) Logging subsystem bump & transformers for EAP7
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2999?page=com.atlassian.jira.plugi... ]
James Perkins commented on WFCORE-2999:
---------------------------------------
There shouldn't be a model version bump required. The {{stream}} attribute change was a bug fix (WFCORE-1428). The {{path-info}} does look like a new operation so it will need a transformer, but that shouldn't require a schema bump AIUI.
> Logging subsystem bump & transformers for EAP7
> ----------------------------------------------
>
> Key: WFCORE-2999
> URL: https://issues.jboss.org/browse/WFCORE-2999
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: Tomaz Cerar
> Assignee: James Perkins
> Priority: Critical
>
> Currently model version of logging subsystem is 3.0.0 same as in EAP 7.0.
> but model diff reports changes to the model.
> So it needs model bump to 4.0.0, as well as transformers.
> As a bonus point, it would be really good performance wise if we could move transformers registration to use non deprecated ExtensionTransformerRegistration API.
> model diff:
> {noformat}
> ====== Resource root address: ["subsystem" => "logging"] - Current version: 3.0.0; legacy version: 3.0.0 =======
> --- Problems for relative address to root ["file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["log-file" => "*"]:
> Different 'type' for attribute 'stream'. Current: STRING; legacy: LONG
> --- Problems for relative address to root ["logging-profile" => "*","file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["logging-profile" => "*","log-file" => "*"]:
> Different 'type' for attribute 'stream'. Current: STRING; legacy: LONG
> --- Problems for relative address to root ["logging-profile" => "*","periodic-rotating-file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["logging-profile" => "*","periodic-size-rotating-file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["periodic-rotating-file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["periodic-size-rotating-file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-3000) Allow turning the security manager on on a per jvm basis
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3000?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-3000:
-------------------------------------
Fix Version/s: 4.0.0.Beta1
> Allow turning the security manager on on a per jvm basis
> --------------------------------------------------------
>
> Key: WFCORE-3000
> URL: https://issues.jboss.org/browse/WFCORE-3000
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Labels: domain-mode
> Fix For: 4.0.0.Beta1
>
>
> Turning on the security manager in a WildFly process is done by adding the -secmgr arg to org.jboss.modules.Main. But the jvm config settings in domain mode provide no mechanism for configuring args to Main; they only provide options for args to java. So there is no way to turn on the security manager for an individual jvm config (i.e. one or more servers) or if it is on for the HC there is no way to turn it off for a particular jvm config.
> The jvm config needs an attribute for this; default is undefined which should be documented as meaning the setting is derived from the HC's settings (i.e. the way it is now.)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-3000) Allow turning the security manager on on a per jvm basis
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3000?page=com.atlassian.jira.plugi... ]
Brian Stansberry reassigned WFCORE-3000:
----------------------------------------
Assignee: (was: Brian Stansberry)
> Allow turning the security manager on on a per jvm basis
> --------------------------------------------------------
>
> Key: WFCORE-3000
> URL: https://issues.jboss.org/browse/WFCORE-3000
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Brian Stansberry
> Labels: domain-mode
> Fix For: 4.0.0.Beta1
>
>
> Turning on the security manager in a WildFly process is done by adding the -secmgr arg to org.jboss.modules.Main. But the jvm config settings in domain mode provide no mechanism for configuring args to Main; they only provide options for args to java. So there is no way to turn on the security manager for an individual jvm config (i.e. one or more servers) or if it is on for the HC there is no way to turn it off for a particular jvm config.
> The jvm config needs an attribute for this; default is undefined which should be documented as meaning the setting is derived from the HC's settings (i.e. the way it is now.)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-3000) Allow turning the security manager on on a per jvm basis
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3000?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-3000:
-------------------------------------
Description:
Turning on the security manager in a WildFly process is done by adding the -secmgr arg to org.jboss.modules.Main. But the jvm config settings in domain mode provide no mechanism for configuring args to Main; they only provide options for args to java. So there is no way to turn on the security manager for an individual jvm config (i.e. one or more servers) or if it is on for the HC there is no way to turn it off for a particular jvm config.
The jvm config needs an attribute for this; default is undefined which should be documented as meaning the setting is derived from the HC's settings (i.e. the way it is now.)
> Allow turning the security manager on on a per jvm basis
> --------------------------------------------------------
>
> Key: WFCORE-3000
> URL: https://issues.jboss.org/browse/WFCORE-3000
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Labels: domain-mode
> Fix For: 4.0.0.Beta1
>
>
> Turning on the security manager in a WildFly process is done by adding the -secmgr arg to org.jboss.modules.Main. But the jvm config settings in domain mode provide no mechanism for configuring args to Main; they only provide options for args to java. So there is no way to turn on the security manager for an individual jvm config (i.e. one or more servers) or if it is on for the HC there is no way to turn it off for a particular jvm config.
> The jvm config needs an attribute for this; default is undefined which should be documented as meaning the setting is derived from the HC's settings (i.e. the way it is now.)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (ELY-1261) Revisit credentials key-store-reference and certificate from Elytron client configuration file
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/ELY-1261?page=com.atlassian.jira.plugin.s... ]
David Lloyd commented on ELY-1261:
----------------------------------
IEC/ISO-9798 uses these credentials.
> Revisit credentials key-store-reference and certificate from Elytron client configuration file
> ----------------------------------------------------------------------------------------------
>
> Key: ELY-1261
> URL: https://issues.jboss.org/browse/ELY-1261
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta52
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Critical
>
> It seems that only supported SASL mechanism in Elytron which is able to work with key/certificate is {{EXTERNAL}} mechanism. However this mechanism takes this information from SSL connection which means that credentials defined in {{configuration.authentication-client.authentication-configurations.configuration.credentials.key-store-reference}} or {{configuration.authentication-client.authentication-configurations.configuration.credentials.certificate}} from Elytron client configuration file are not used in this case.
> Is there any Elytron supported SASL mechanism which is currently able to work with these credentials? In this case please provide configuration and SASL mechanism which is able to work with {{key-store-reference}} and {{certificate}} credentials.
> Otherwise these {{key-store-reference}} and {{certificate}} should be removed from Elytron client configuration because they currently cannot be used by users (or tested by QA). They can be added to configuration again once Elytron will support mechanism which is able to work with key/certificate as credentials. This is basically the similar issue as ELY-1257.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (DROOLS-1624) Map Handling with Property Reactive Always Enabled
by KimJohn Quinn (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1624?page=com.atlassian.jira.plugi... ]
KimJohn Quinn commented on DROOLS-1624:
---------------------------------------
Thanks Mario. I appreciate the help.
> Map Handling with Property Reactive Always Enabled
> --------------------------------------------------
>
> Key: DROOLS-1624
> URL: https://issues.jboss.org/browse/DROOLS-1624
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.0.0.Final
> Environment: * JDK8
> * Docker running Alpine
> Reporter: KimJohn Quinn
> Assignee: Mario Fusco
> Priority: Minor
> Attachments: drools.zip
>
>
> Referencing a conversation on [Google Groups - Drools Usage|https://groups.google.com/forum/?fromgroups#!topic/drools-usage/G7r...] and as requested by Mario Fusco...
> We currently have a ruleset that relies heavily on Map facts. In Drools 6.5 we fire approximately 400 rules.
> In Drools 7.0 we get only about 50 rules unless we add the "<property key="drools.propertySpecific" value="ALLOWED"/>" to the kmodule.xml, in which case we fire the full 400 rules or by using @Watch(*) or @Watch(!*) on the rules. It "seems" like only the first evaluations of the rules are firing and then no others after that.
> Our flow generally follows something like below, within a stateful session, using rules only. We fire all rules per-request then close the session.
> Watch for changes to the Map properties
> If a certain property or properties exist a 'populate' rule fires (calls modify())
> The populate rule enriches the map fact. (calls modify())
> Based on #3, more rules fire when certain properties exist (calls modify())
> We are work heavily with rules that depend on loaded available facts up-front and computed properties throughout evaluation.
> I have a couple of usage questions regarding Drools 7, the default enabling of Property Reactive and using Maps as the facts:
> In general, how do maps work with property reactive and respond to modify/insert events? Does Drools look at the Map as a whole, any change re-evaluates the tree, or each individual property within the map re-evaluates the change?
> In Drools 7, by defaulting the property reactive setting, does that mean all rules need to be annotated or they should they work as is (dao or map-based facts) when using modify/insert?
> For reference, we are relying on this doco https://docs.jboss.org/drools/release/7.0.0.Final/drools-docs/html_single....
> I am looking into details or an example how to properly use Maps in Drools 7 with Property Reactive features always enabled (as suggested per the doco)....
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-2999) Logging subsystem bump & transformers for EAP7
by Tomaz Cerar (JIRA)
Tomaz Cerar created WFCORE-2999:
-----------------------------------
Summary: Logging subsystem bump & transformers for EAP7
Key: WFCORE-2999
URL: https://issues.jboss.org/browse/WFCORE-2999
Project: WildFly Core
Issue Type: Bug
Components: Logging
Reporter: Tomaz Cerar
Assignee: James Perkins
Priority: Critical
Currently model version of logging subsystem is 3.0.0 same as in EAP 7.0.
but model diff reports changes to the model.
So it needs model bump to 4.0.0, as well as transformers.
As a bonus point, it would be really good performance wise if we could move transformers registration to use non deprecated ExtensionTransformerRegistration API.
model diff:
{noformat}
====== Resource root address: ["subsystem" => "logging"] - Current version: 3.0.0; legacy version: 3.0.0 =======
--- Problems for relative address to root ["file-handler" => "*"]:
Missing operations in current: []; missing in legacy [path-info]
--- Problems for relative address to root ["log-file" => "*"]:
Different 'type' for attribute 'stream'. Current: STRING; legacy: LONG
--- Problems for relative address to root ["logging-profile" => "*","file-handler" => "*"]:
Missing operations in current: []; missing in legacy [path-info]
--- Problems for relative address to root ["logging-profile" => "*","log-file" => "*"]:
Different 'type' for attribute 'stream'. Current: STRING; legacy: LONG
--- Problems for relative address to root ["logging-profile" => "*","periodic-rotating-file-handler" => "*"]:
Missing operations in current: []; missing in legacy [path-info]
--- Problems for relative address to root ["logging-profile" => "*","periodic-size-rotating-file-handler" => "*"]:
Missing operations in current: []; missing in legacy [path-info]
--- Problems for relative address to root ["periodic-rotating-file-handler" => "*"]:
Missing operations in current: []; missing in legacy [path-info]
--- Problems for relative address to root ["periodic-size-rotating-file-handler" => "*"]:
Missing operations in current: []; missing in legacy [path-info]
{noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months