[JBoss JIRA] (ELY-494) DigestServerFactory should only use AvailableRealmsCallback to get realms, not the legacy property list
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/ELY-494?page=com.atlassian.jira.plugin.sy... ]
David Lloyd updated ELY-494:
----------------------------
Description:
We use a different delimiter for the {{com.sun.security.sasl.digest.realm}} property than the JDK, which uses commas, spaces, newlines, or tab characters. This makes it impossible to correctly emulate the property to the mechanism while using the callback to acquire the actual list. Since code changes would likely be required to use the new version with only a comma delimiter, it does not serve any compatibility purpose to continue to support this property.
Instead we should do three things:
* Eliminate property support from our DigestSaslServer
* Add a wrapping SaslServerFactory which detects when a mechanism is trying to acquire a realm list by reading the {{com.sun.security.sasl.digest.realm}} property, and uses the AvailableRealmsCallback to populate it -(with a flag to support transformation of spaces, tabs, and newlines to NBSP (0xA0), and remove commas)-
* Add a wrapping SaslServerFactory which allows legacy users to specify a value for {{com.sun.security.sasl.digest.realm}}, and uses it to support AvailableRealmsCallback if that property was set, with programmable delimiters
was:
We use a different delimiter for the {{com.sun.security.sasl.digest.realm}} property than the JDK, which uses commas, spaces, newlines, or tab characters. This makes it impossible to correctly emulate the property to the mechanism while using the callback to acquire the actual list. Since code changes would likely be required to use the new version with only a comma delimiter, it does not serve any compatibility purpose to continue to support this property.
Instead we should do three things:
* Eliminate property support from our DigestSaslServer
* Add a wrapping SaslServerFactory which detects when a mechanism is trying to acquire a realm list by reading the {{com.sun.security.sasl.digest.realm}} property, and uses the AvailableRealmsCallback to populate it (with a flag to support transformation of spaces, tabs, and newlines to NBSP (0xA0), and remove commas)
* Add a wrapping SaslServerFactory which allows legacy users to specify a value for {{com.sun.security.sasl.digest.realm}}, and uses it to support AvailableRealmsCallback if that property was set, with programmable delimiters
> DigestServerFactory should only use AvailableRealmsCallback to get realms, not the legacy property list
> -------------------------------------------------------------------------------------------------------
>
> Key: ELY-494
> URL: https://issues.jboss.org/browse/ELY-494
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SASL
> Reporter: David Lloyd
>
> We use a different delimiter for the {{com.sun.security.sasl.digest.realm}} property than the JDK, which uses commas, spaces, newlines, or tab characters. This makes it impossible to correctly emulate the property to the mechanism while using the callback to acquire the actual list. Since code changes would likely be required to use the new version with only a comma delimiter, it does not serve any compatibility purpose to continue to support this property.
> Instead we should do three things:
> * Eliminate property support from our DigestSaslServer
> * Add a wrapping SaslServerFactory which detects when a mechanism is trying to acquire a realm list by reading the {{com.sun.security.sasl.digest.realm}} property, and uses the AvailableRealmsCallback to populate it -(with a flag to support transformation of spaces, tabs, and newlines to NBSP (0xA0), and remove commas)-
> * Add a wrapping SaslServerFactory which allows legacy users to specify a value for {{com.sun.security.sasl.digest.realm}}, and uses it to support AvailableRealmsCallback if that property was set, with programmable delimiters
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JGRP-2044) RequestCorrelator causes frequent boxing and autoboxing by using a Map<Long, Request>
by Sanne Grinovero (JIRA)
Sanne Grinovero created JGRP-2044:
-------------------------------------
Summary: RequestCorrelator causes frequent boxing and autoboxing by using a Map<Long,Request>
Key: JGRP-2044
URL: https://issues.jboss.org/browse/JGRP-2044
Project: JGroups
Issue Type: Enhancement
Reporter: Sanne Grinovero
Assignee: Bela Ban
Priority: Minor
The JFR profiler is highlighting a significant amount of boxing and autoboxing, as the request is is treated as a {{long}} but this is used as an key for the {{Map<Long,Request>}}.
We could try to either consistently use {{Long}} rather than {{long}, or even better figure out an optimal data structure to replace the implementation of the Map to not require boxing of the keys.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (DROOLS-1115) IndexOutOfBoundException when using conditional break + query
by Massinissa BOUZIAD (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1115?page=com.atlassian.jira.plugi... ]
Massinissa BOUZIAD commented on DROOLS-1115:
--------------------------------------------
Yeeeees thank you ! I hope to switch ASAP to 6.4.0.Final
> IndexOutOfBoundException when using conditional break + query
> -------------------------------------------------------------
>
> Key: DROOLS-1115
> URL: https://issues.jboss.org/browse/DROOLS-1115
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.4.0.CR2
> Reporter: Massinissa BOUZIAD
> Assignee: Mario Fusco
> Priority: Blocker
> Fix For: 6.4.0.Final, 7.0.0.Final
>
>
> I got an java.lang.ArrayIndexOutOfBoundsException when I use conditionnal breaking and queries.
> I face this issue since 6.4.0.CR2 and not before this.
> Following the stack trace :
> java.lang.ArrayIndexOutOfBoundsException: 2
> at org.drools.core.reteoo.AbstractTerminalNode.getPathNodes(AbstractTerminalNode.java:304)
> at org.drools.core.reteoo.AbstractTerminalNode.getPathNodes(AbstractTerminalNode.java:311)
> at org.drools.core.phreak.PhreakQueryTerminalNode.checkAndTriggerQueryReevaluation(PhreakQueryTerminalNode.java:173)
> at org.drools.core.phreak.PhreakQueryTerminalNode.doLeftInserts(PhreakQueryTerminalNode.java:78)
> at org.drools.core.phreak.PhreakQueryTerminalNode.doNode(PhreakQueryTerminalNode.java:54)
> at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:282)
> at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:136)
> at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:94)
> at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:194)
> at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:73)
> at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1003)
> at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1346)
> at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1284)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1303)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1293)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1274)
> at com.darty.drools.CodicCriteriaTest.price(CodicCriteriaTest.java:53)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (ELY-494) DigestServerFactory should only use AvailableRealmsCallback to get realms, not the legacy property list
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/ELY-494?page=com.atlassian.jira.plugin.sy... ]
David Lloyd updated ELY-494:
----------------------------
Description:
We use a different delimiter for the {{com.sun.security.sasl.digest.realm}} property than the JDK, which uses commas, spaces, newlines, or tab characters. This makes it impossible to correctly emulate the property to the mechanism while using the callback to acquire the actual list. Since code changes would likely be required to use the new version with only a comma delimiter, it does not serve any compatibility purpose to continue to support this property.
Instead we should do three things:
* Eliminate property support from our DigestSaslServer
* Add a wrapping SaslServerFactory which detects when a mechanism is trying to acquire a realm list by reading the {{com.sun.security.sasl.digest.realm}} property, and uses the AvailableRealmsCallback to populate it (with a flag to support transformation of spaces, tabs, and newlines to NBSP (0xA0), and remove commas)
* Add a wrapping SaslServerFactory which allows legacy users to specify a value for {{com.sun.security.sasl.digest.realm}}, and uses it to support AvailableRealmsCallback if that property was set, with programmable delimiters
was:
We use a different delimiter for the {{com.sun.security.sasl.digest.realm}} property than the JDK, which uses commas, spaces, newlines, or tab characters. This makes it impossible to correctly emulate the property to the mechanism while using the callback to acquire the actual list. Since code changes would likely be required to use the new version with only a comma delimiter, it does not serve any compatibility purpose to continue to support this property.
Instead we should do three things:
* Eliminate property support from our DigestSaslServer
* Add a wrapping SaslServerFactory which detects when a mechanism is trying to acquire a realm list by reading the {{com.sun.security.sasl.digest.realm}} property, and uses the AvailableRealmsCallback to populate it
* Add a wrapping SaslServerFactory which allows legacy users to specify a value for {{com.sun.security.sasl.digest.realm}}, and uses it to support AvailableRealmsCallback if that property was set, with programmable delimiters
> DigestServerFactory should only use AvailableRealmsCallback to get realms, not the legacy property list
> -------------------------------------------------------------------------------------------------------
>
> Key: ELY-494
> URL: https://issues.jboss.org/browse/ELY-494
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SASL
> Reporter: David Lloyd
>
> We use a different delimiter for the {{com.sun.security.sasl.digest.realm}} property than the JDK, which uses commas, spaces, newlines, or tab characters. This makes it impossible to correctly emulate the property to the mechanism while using the callback to acquire the actual list. Since code changes would likely be required to use the new version with only a comma delimiter, it does not serve any compatibility purpose to continue to support this property.
> Instead we should do three things:
> * Eliminate property support from our DigestSaslServer
> * Add a wrapping SaslServerFactory which detects when a mechanism is trying to acquire a realm list by reading the {{com.sun.security.sasl.digest.realm}} property, and uses the AvailableRealmsCallback to populate it (with a flag to support transformation of spaces, tabs, and newlines to NBSP (0xA0), and remove commas)
> * Add a wrapping SaslServerFactory which allows legacy users to specify a value for {{com.sun.security.sasl.digest.realm}}, and uses it to support AvailableRealmsCallback if that property was set, with programmable delimiters
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (ELY-494) DigestServerFactory should only use AvailableRealmsCallback to get realms, not the legacy property list
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/ELY-494?page=com.atlassian.jira.plugin.sy... ]
David Lloyd updated ELY-494:
----------------------------
Description:
We use a different delimiter for the {{com.sun.security.sasl.digest.realm}} property than the JDK, which uses commas, spaces, newlines, or tab characters. This makes it impossible to correctly emulate the property to the mechanism while using the callback to acquire the actual list. Since code changes would likely be required to use the new version with only a comma delimiter, it does not serve any compatibility purpose to continue to support this property.
Instead we should do three things:
* Eliminate property support from our DigestSaslServer
* Add a wrapping SaslServerFactory which detects when a mechanism is trying to acquire a realm list by reading the {{com.sun.security.sasl.digest.realm}} property, and uses the AvailableRealmsCallback to populate it
* Add a wrapping SaslServerFactory which allows legacy users to specify a value for {{com.sun.security.sasl.digest.realm}}, and uses it to support AvailableRealmsCallback if that property was set, with programmable delimiters
was:
We use a different delimiter for the {{com.sun.security.sasl.digest.realm}} property than the JDK, which uses commas, spaces, newlines, or tab characters. This makes it impossible to correctly emulate the property to the mechanism while using the callback to acquire the actual list. Since code changes would likely be required to use the new version with only a comma delimiter, it does not serve any compatibility purpose to continue to support this property.
Instead we should do three things:
* Eliminate property support from our DigestSaslServer
* Add a wrapping SaslServerFactory which detects when a mechanism is trying to acquire a realm list by reading the {{com.sun.security.sasl.digest.realm}} property, and uses the AvailableRealmsCallback to populate it
* Add a wrapping SaslServerFactory which allows legacy users to specify a value for {{com.sun.security.sasl.digest.realm}}, and uses it to support AvailableRealmsCallback if that property was set
> DigestServerFactory should only use AvailableRealmsCallback to get realms, not the legacy property list
> -------------------------------------------------------------------------------------------------------
>
> Key: ELY-494
> URL: https://issues.jboss.org/browse/ELY-494
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SASL
> Reporter: David Lloyd
>
> We use a different delimiter for the {{com.sun.security.sasl.digest.realm}} property than the JDK, which uses commas, spaces, newlines, or tab characters. This makes it impossible to correctly emulate the property to the mechanism while using the callback to acquire the actual list. Since code changes would likely be required to use the new version with only a comma delimiter, it does not serve any compatibility purpose to continue to support this property.
> Instead we should do three things:
> * Eliminate property support from our DigestSaslServer
> * Add a wrapping SaslServerFactory which detects when a mechanism is trying to acquire a realm list by reading the {{com.sun.security.sasl.digest.realm}} property, and uses the AvailableRealmsCallback to populate it
> * Add a wrapping SaslServerFactory which allows legacy users to specify a value for {{com.sun.security.sasl.digest.realm}}, and uses it to support AvailableRealmsCallback if that property was set, with programmable delimiters
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (ELY-494) DigestServerFactory should only use AvailableRealmsCallback to get realms, not the legacy property list
by David Lloyd (JIRA)
David Lloyd created ELY-494:
-------------------------------
Summary: DigestServerFactory should only use AvailableRealmsCallback to get realms, not the legacy property list
Key: ELY-494
URL: https://issues.jboss.org/browse/ELY-494
Project: WildFly Elytron
Issue Type: Bug
Components: SASL
Reporter: David Lloyd
We use a different delimiter for the {{com.sun.security.sasl.digest.realm}} property than the JDK, which uses commas, spaces, newlines, or tab characters. This makes it impossible to correctly emulate the property to the mechanism while using the callback to acquire the actual list. Since code changes would likely be required to use the new version with only a comma delimiter, it does not serve any compatibility purpose to continue to support this property.
Instead we should do three things:
* Eliminate property support from our DigestSaslServer
* Add a wrapping SaslServerFactory which detects when a mechanism is trying to acquire a realm list by reading the {{com.sun.security.sasl.digest.realm}} property, and uses the AvailableRealmsCallback to populate it
* Add a wrapping SaslServerFactory which allows legacy users to specify a value for {{com.sun.security.sasl.digest.realm}}, and uses it to support AvailableRealmsCallback if that property was set
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (DROOLS-1118) Build: enforce banning of dependencies that only have a GPL and/or AGPL license
by Geoffrey De Smet (JIRA)
Geoffrey De Smet created DROOLS-1118:
----------------------------------------
Summary: Build: enforce banning of dependencies that only have a GPL and/or AGPL license
Key: DROOLS-1118
URL: https://issues.jboss.org/browse/DROOLS-1118
Project: Drools
Issue Type: Feature Request
Components: build
Reporter: Geoffrey De Smet
Assignee: Petr Široký
In the first phase, I 'd be happy with an exclusive approach: just ban GPL and AGPL.
In a later phase, we probably want an inclusive approach: only list the ones that we do accept (but due to license proliferation that's not easy).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (DROOLS-1115) IndexOutOfBoundException when using conditional break + query
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1115?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-1115:
--------------------------------
Fix Version/s: 6.4.0.Final
> IndexOutOfBoundException when using conditional break + query
> -------------------------------------------------------------
>
> Key: DROOLS-1115
> URL: https://issues.jboss.org/browse/DROOLS-1115
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.4.0.CR2
> Reporter: Massinissa BOUZIAD
> Assignee: Mario Fusco
> Priority: Blocker
> Fix For: 6.4.0.Final, 7.0.0.Final
>
>
> I got an java.lang.ArrayIndexOutOfBoundsException when I use conditionnal breaking and queries.
> I face this issue since 6.4.0.CR2 and not before this.
> Following the stack trace :
> java.lang.ArrayIndexOutOfBoundsException: 2
> at org.drools.core.reteoo.AbstractTerminalNode.getPathNodes(AbstractTerminalNode.java:304)
> at org.drools.core.reteoo.AbstractTerminalNode.getPathNodes(AbstractTerminalNode.java:311)
> at org.drools.core.phreak.PhreakQueryTerminalNode.checkAndTriggerQueryReevaluation(PhreakQueryTerminalNode.java:173)
> at org.drools.core.phreak.PhreakQueryTerminalNode.doLeftInserts(PhreakQueryTerminalNode.java:78)
> at org.drools.core.phreak.PhreakQueryTerminalNode.doNode(PhreakQueryTerminalNode.java:54)
> at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:282)
> at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:136)
> at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:94)
> at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:194)
> at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:73)
> at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1003)
> at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1346)
> at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1284)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1303)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1293)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1274)
> at com.darty.drools.CodicCriteriaTest.price(CodicCriteriaTest.java:53)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months