[JBoss JIRA] (WFLY-5943) Picketlink federation and idm subsystems have no parsers for their 1.1 schemas
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-5943?page=com.atlassian.jira.plugin.... ]
Brian Stansberry moved JBEAP-2586 to WFLY-5943:
-----------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-5943 (was: JBEAP-2586)
Workflow: GIT Pull Request workflow (was: CDW v1)
Component/s: Security
(was: Security)
Target Release: (was: 7.0.0.GA)
> Picketlink federation and idm subsystems have no parsers for their 1.1 schemas
> -------------------------------------------------------------------------------
>
> Key: WFLY-5943
> URL: https://issues.jboss.org/browse/WFLY-5943
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Brian Stansberry
> Assignee: Pedro Igor
> Priority: Critical
>
> EAP 6.4 has a 1.1 xsd version for these subsystems, while WF 10 / EAP 7 has a 2.0. A quick glance leads me to believe the contents are the same except for the number. But the WF 10 / EAP 7 code will fail if a document with the 1.1 namespace is presented.
> If the xsds are the same, likely this can be fixed simply by adding another case for 1.1 to the switch block that calls the 2.0 parser. Otherwise the 1.1 parser from the EAP 6 branch should be forward ported.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-5890) Default mod_cluster load metric cpu (AverageSystemLoadMetric) is not supported on Windows
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5890?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-5890:
---------------------------------
Priority: Critical (was: Major)
> Default mod_cluster load metric cpu (AverageSystemLoadMetric) is not supported on Windows
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-5890
> URL: https://issues.jboss.org/browse/WFLY-5890
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.0.0.CR5
> Reporter: Michal Karm Babacek
> Assignee: Radoslav Husar
> Priority: Critical
> Labels: ux
>
> h3. Problem
> Wildfly 10's default load metric changed from *busyness* to *cpu*. Although otherwise fine, this change has a one major drawback: It doesn't work on Windows JDKs: MODCLUSTER-234. This fact has been known and acknowledged since 2011.
> {code}
> <subsystem xmlns="urn:jboss:domain:modcluster:2.0">
> <mod-cluster-config advertise-socket="modcluster" connector="ajp">
> <dynamic-load-provider>
> <load-metric type="cpu"/>
> </dynamic-load-provider>
> </mod-cluster-config>
> </subsystem>
> {code}
> Instead of a valid Load value, subsystem returns 0 and prints: {{MODCLUSTER000045: AverageSystemLoadMetric is not supported on this system and will be disabled.}}
> h3. Example
> {code}
> C:\Users\Administrator>groovy https://gist.githubusercontent.com/Karm/be36292ae52ded419b46/raw/addd6abf...
> load: -1.0
> avail. processors: 4
> {code}
> {code}
> mbabacek@localhost:~$ groovy https://gist.githubusercontent.com/Karm/be36292ae52ded419b46/raw/addd6abf...
> load: 0.67
> avail. processors: 4
> {code}
> h3. Call to action
> IMHO, this is a Major user experience failure, the default should provide meaningful values on all major platforms.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFCORE-1273) Can not add property after change of class in custom log formatter.
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1273?page=com.atlassian.jira.plugi... ]
James Perkins moved JBEAP-2581 to WFCORE-1273:
----------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1273 (was: JBEAP-2581)
Workflow: GIT Pull Request workflow (was: CDW v1)
Component/s: Logging
(was: Logging)
Target Release: (was: 7.0.0.GA)
> Can not add property after change of class in custom log formatter.
> -------------------------------------------------------------------
>
> Key: WFCORE-1273
> URL: https://issues.jboss.org/browse/WFCORE-1273
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Environment: Running unsecured EAP 7.0. DR9 version in standalone mode with standalone-full-ha profile
> Reporter: James Perkins
> Assignee: James Perkins
>
> When you create custom formater - XMLFormatter {{/subsystem=logging/custom-formatter=XMLFormatter:add(class=java.util.logging.XMLFormatter, module=org.jboss.logmanager)}} and then in web console edit class of formatter to *org.jboss.logmanager.formatters.PatternFormatter* then save and try to add properties - *pattern=%s%E%n*. Property is not saved.
> When you create new formatter with *org.jboss.logmanager.formatters.PatternFormatter* class and then try to add same property, saving is successful.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-5613) Fix transaction subsystem resource descriptions
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/WFLY-5613?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated WFLY-5613:
--------------------------------
Fix Version/s: 10.0.0.Final
(was: 11.0.0.CR1)
> Fix transaction subsystem resource descriptions
> -----------------------------------------------
>
> Key: WFLY-5613
> URL: https://issues.jboss.org/browse/WFLY-5613
> Project: WildFly
> Issue Type: Enhancement
> Components: Transactions
> Reporter: Ondřej Chaloupka
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 10.0.0.Final
>
> Attachments: jts-tooltip-700.DR132.png
>
>
> I would like ask for changing text in transaction configuration helper tooltip (_Need Help?
> _). First there is an issue of not having an information that jts to be fully enabled is need to set subsystem of iiop orb as well (the same issue was for 6.4.0 https://bugzilla.redhat.com/show_bug.cgi?id=995439).
> Nevertheless I would like ask for a bit more general change of the text in the help webconsole tooltip
> Current text is
> {noformat}
> Default timeout: The default timeout.
> Enable tsm status: Whether the transaction status manager (TSM) service, needed for out of process recovery, should be provided or not..
> Journal store enable async io: Whether AsyncIO should be enabled for the journal store. Default is false. The server should be restarted for this setting to take effect.
> Jts: If true this enables the Java Transaction Service.
> Node identifier: Used to set the node identifier on the core environment.
> Statistics enabled: Whether statistics should be enabled.
> Use journal store: Use the journal store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file system file per transaction log. The server should be restarted for this setting to take effect. It's alternative to jdbc based store.
> {noformat}
> {noformat}
> Process id uuid: Indicates whether the transaction manager should use a UUID based process id.
> Process id socket binding: The name of the socket binding configuration to use if the transaction manager should use a socket-based process id. Will be 'undefined' if 'process-id-uuid' is 'true'; otherwise must be set.
> Process id socket max ports: The maximum number of ports to search for an open port if the transaction manager should use a socket-based process id. If the port specified by the socket binding referenced in 'process-id-socket-binding' is occupied, the next higher port will be tried until an open port is found or the number of ports specified by this attribute have been tried. Will be 'undefined' if 'process-id-uuid' is 'true'.
> {noformat}
> {noformat}
> Socket binding: Used to reference the correct socket binding to use for the recovery environment.
> Status socket binding: Used to reference the correct socket binding to use for the transaction status manager.
> Recovery listener: Used to specify if the recovery system should listen on a network socket or not.
> {noformat}
> {noformat}
> Object store path: Denotes a relative or absolute filesystem path denoting where the transaction manager object store should store data. By default the value is treated as relative to the path denoted by the "relative-to" attribute.
> Object store relative to: References a global path configuration in the domain model, defaulting to the JBoss Application Server data directory (jboss.server.data.dir). The value of the "path" attribute will treated as relative to this path. Use an empty string to disable the default behavior and force the value of the "path" attribute to be treated as an absolute path.
> {noformat}
> {noformat}
> Use jdbc store: Use the jdbc store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file system file per transaction log. The server should be restarted for this setting to take effect. It's alternative to Horneq based store
> Jdbc action store drop table: Configure if jdbc action store should drop tables. Default is false. The server should be restarted for this setting to take effect.
> Jdbc action store table prefix: Optional prefix for table used to write transcation logs in configured jdbc action store. The server should be restarted for this setting to take effect.
> Jdbc communication store drop table: Configure if jdbc communication store should drop tables. Default is false. The server should be restarted for this setting to take effect.
> Jdbc communication store table prefix: Optional prefix for table used to write transcation logs in configured jdbc communication store. The server should be restarted for this setting to take effect.
> Jdbc state store drop table: Configure if jdbc state store should drop tables. Default is false. The server should be restarted for this setting to take effect.
> Jdbc state store table prefix: Optional prefix for table used to write transcation logs in configured jdbc state store. The server should be restarted for this setting to take effect.
> Jdbc store datasource: Jndi name of non-XA datasource used. Datasource sghould be define in datasources subsystem. The server should be restarted for this setting to take effect.
> {noformat}
> I would propose the following changes in the tooltip text
> *Attributes*
> * Default timeout
> ** The default timeout for a transaction managed by the transaction manager.
> * Enable tsm status
> ** Whether the transaction status manager (TSM) service, needed for out of process recovery, should be provided or not.
> * Journal store enable async io
> ** Whether AsyncIO should be enabled for the journal store. Default is false. For this settings being active journal natives libraries needs to be available. The server should be restarted for this setting to take effect.
> * Jts
> ** If true this enables the Java Transaction Service. Use of the JTS needs configuration in IIOP OpenJDK where Transactions parameter needs to be set to full. The server should be restarted for this setting to take effect.
> * Node identifier
> ** Used to set the node identifier on the core environment. Each server should have this identifier unique. It's an identifier which differentiates XA transactions as created by this node. The server should be restarted for this setting to take effect.
> * Statistics enabled
> ** Whether transaction statistics should be enabled. The transaction statistics could be seen in section Runtime > Monitor > Subsystems > Transactions. The server should be reloaded for this setting to take effect.
> * Use journal store
> ** Use the journal store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store creates normally one file file per transaction log. The journal one consists from one file for all the transactions. It's alternative to jdbc based store. The server should be restarted for this setting to take effect.
> *Process ID* + *Recovery*
> Add information that for settings these attributes taking effect the server needs to be reloaded.
> *Path*
> * Object store path
> ** Denotes a relative or absolute filesystem path denoting where the transaction manager object store should store data. By default the value is treated as relative to the path denoted by the "relative-to" attribute. This settings is valid when default or journal store is used. It's not used when jdbc journal store is used. The server should be reloaded for this setting to take effect.
> * Object store relative to
> ** References a global path configuration in the domain model, defaulting to the Application Server data directory (jboss.server.data.dir). The value of the "Object store path" attribute will treated as relative to this path. Use an empty string to disable the default behavior and force the value of the "Object store path" attribute to be treated as an absolute path. The server should be reloaded for this setting to take effect.
> *JDBC*
> * Use jdbc store
> ** Use the jdbc store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file file per transaction log. It's alternative to journal based store. The server should be restarted for this setting to take effect.
> * Jdbc store datasource
> ** Jndi name of non-XA datasource used. Datasource sghould be define in datasources subsystem. For this would work the non-XA datasource has to be marked as jta="false". The server should be restarted for this setting to take effect.
> ...the rest of the information is ok from my point of view
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (DROOLS-1021) Add method on KieContainer to get the KieBase for an ksessionName (without instantiating the KieSession)
by Geoffrey De Smet (JIRA)
Geoffrey De Smet created DROOLS-1021:
----------------------------------------
Summary: Add method on KieContainer to get the KieBase for an ksessionName (without instantiating the KieSession)
Key: DROOLS-1021
URL: https://issues.jboss.org/browse/DROOLS-1021
Project: Drools
Issue Type: Enhancement
Components: core engine
Affects Versions: 6.3.0.Final
Reporter: Geoffrey De Smet
Assignee: Mario Fusco
OptaPlanner is switching from using KieBase (with a drl classpath resource to retrieve the rules) to KContainer (with ksessionName to retrieve the rules), so it can function as part of a kjar.
During bootstrap, it needs to check the rules if a specific Global is defined.
Currently *it needs to instantiate a throwaway KieSession* to do that which is bad:
{code}
KieSession kieSession = kieContainer.newKieSession(ksessionName); // BAD
KieBase kieBase = kieSession.getKieBase();
checkIfGlobalScoreHolderExists(kieBase);
{code}
It would be much nicer if we could do this instead:
{code}
KieBase kieBase = kieContainer.getKieBaseForKsessionName(ksessionName);
checkIfGlobalScoreHolderExists(kieBase);
{code}
So the proposal is to add that new method kieContainer.getKieBaseForKsessionName(String ksessionName)
For the record, here's that check method that's being called at bootstrap:
{code}
protected void checkIfGlobalScoreHolderExists(KieBase kieBase) {
boolean hasGlobalScoreHolder = false;
for (KiePackage kiePackage : kieBase.getKiePackages()) {
for (Global global : kiePackage.getGlobalVariables()) {
if (DroolsScoreDirector.GLOBAL_SCORE_HOLDER_KEY.equals(global.getName())) {
hasGlobalScoreHolder = true;
break;
}
}
}
if (!hasGlobalScoreHolder) {
throw new IllegalArgumentException("The kieBase with kiePackages (" + kieBase.getKiePackages()
+ ") has no global field called " + DroolsScoreDirector.GLOBAL_SCORE_HOLDER_KEY + ".\n"
+ "Check if the rule files are found and if the global field is spelled correctly.");
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (ELY-383) Update ServerAuthenticationContext to carry an identity from start to end
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/ELY-383?page=com.atlassian.jira.plugin.sy... ]
David Lloyd resolved ELY-383.
-----------------------------
Resolution: Done
> Update ServerAuthenticationContext to carry an identity from start to end
> -------------------------------------------------------------------------
>
> Key: ELY-383
> URL: https://issues.jboss.org/browse/ELY-383
> Project: WildFly Elytron
> Issue Type: Task
> Components: API / SPI
> Reporter: David Lloyd
> Assignee: David Lloyd
> Fix For: 1.1.0.Beta4
>
> Attachments: Blank Flowchart - ServerAuthenticationContext.png
>
>
> The {{ServerAuthenticationContext}} should capture the identity in force for its domain when it is constructed. Any authorization attempt should always apply to the current identity - either the captured identity, or whatever the last successfully authorized identity was in the context.
> The attached state diagram should accurately summarize how authorization identity flows through. Authentication identity is only available during the "NAME ASSIGNED" state; once authorization occurs, the authentication identity is no longer useful and is disposed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months