[JBoss JIRA] (DROOLS-2495) NullPointerException in Declaration.getHashCode() when getter in LHS and serialize/deserialize package
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2495?page=com.atlassian.jira.plugi... ]
Mario Fusco resolved DROOLS-2495.
---------------------------------
Resolution: Done
Fixed by https://github.com/kiegroup/drools/commit/8c4f9267ea4d3ee53a8729c70734374...
> NullPointerException in Declaration.getHashCode() when getter in LHS and serialize/deserialize package
> ------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-2495
> URL: https://issues.jboss.org/browse/DROOLS-2495
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.7.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Mario Fusco
> Labels: support
>
> Under the condition:
> - A rule uses a getter method in LHS. e.g. "Cheese(type == $p.getName())"
> - A package is serialized/deserialized
> executing the rule throws NullPointerException.
> {noformat}
> java.lang.NullPointerException: null
> at org.drools.core.rule.Declaration.getHashCode(Declaration.java:267)
> at org.drools.core.util.AbstractHashTable$FieldIndex.hashCodeOf(AbstractHashTable.java:333)
> at org.drools.core.util.AbstractHashTable$SingleIndex.hashCodeOf(AbstractHashTable.java:397)
> at org.drools.core.util.index.TupleIndexHashTable.getOrCreate(TupleIndexHashTable.java:392)
> at org.drools.core.util.index.TupleIndexHashTable.add(TupleIndexHashTable.java:358)
> at org.drools.core.phreak.PhreakJoinNode.doLeftInserts(PhreakJoinNode.java:95)
> at org.drools.core.phreak.PhreakJoinNode.doNode(PhreakJoinNode.java:71)
> at org.drools.core.phreak.RuleNetworkEvaluator.switchOnDoBetaNode(RuleNetworkEvaluator.java:552)
> at org.drools.core.phreak.RuleNetworkEvaluator.evalBetaNode(RuleNetworkEvaluator.java:538)
> at org.drools.core.phreak.RuleNetworkEvaluator.evalNode(RuleNetworkEvaluator.java:373)
> at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:333)
> at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:169)
> at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:127)
> at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:212)
> at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:87)
> at org.drools.core.concurrent.AbstractRuleEvaluator.internalEvaluateAndFire(AbstractRuleEvaluator.java:34)
> at org.drools.core.concurrent.SequentialRuleEvaluator.evaluateAndFire(SequentialRuleEvaluator.java:43)
> at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1067)
> at org.drools.core.common.DefaultAgenda.internalFireAllRules(DefaultAgenda.java:1014)
> at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1006)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1315)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1306)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1290)
> at org.drools.compiler.integrationtests.SerializedPackageMergeTest.testBuildAndSerializePackagesWithGetterInLHS(SerializedPackageMergeTest.java:220)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFCORE-3767) Ability to configure each aggregated realm separately
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3767?page=com.atlassian.jira.plugi... ]
Darran Lofthouse commented on WFCORE-3767:
------------------------------------------
[~jdenise] Do you have some example commands or configuration available to illustrate what you are seeing?
> Ability to configure each aggregated realm separately
> -----------------------------------------------------
>
> Key: WFCORE-3767
> URL: https://issues.jboss.org/browse/WFCORE-3767
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Security
> Reporter: Jean-Francois Denise
> Assignee: Darran Lofthouse
>
> The use-case is EXTERNAL + role derived from mgmt-groups.properties. To achieve this use-case a realm aggregate is needed. Each aggregated realm can't be configured with its own principal-transformer. So each realm is impacted by the transformer set on the aggregation.
> Allowing to configure each realm separately would offer the flexibility to isolate principal transformation for authorisation and not impact authentication.
> Authentication impact is quite important, an alias in the trust-store and the decoded principal must match exactly. Something that shouldn't be made mandatory in this case.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFCORE-3767) Ability to configure each aggregated realm separately
by Jean-Francois Denise (JIRA)
Jean-Francois Denise created WFCORE-3767:
--------------------------------------------
Summary: Ability to configure each aggregated realm separately
Key: WFCORE-3767
URL: https://issues.jboss.org/browse/WFCORE-3767
Project: WildFly Core
Issue Type: Enhancement
Components: Security
Reporter: Jean-Francois Denise
Assignee: Darran Lofthouse
The use-case is EXTERNAL + role derived from mgmt-groups.properties. To achieve this use-case a realm aggregate is needed. Each aggregated realm can't be configured with its own principal-transformer. So each realm is impacted by the transformer set on the aggregation.
Allowing to configure each realm separately would offer the flexibility to isolate principal transformation for authorisation and not impact authentication.
Authentication impact is quite important, an alias in the trust-store and the decoded principal must match exactly. Something that shouldn't be made mandatory in this case.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFLY-10295) java.lang.IllegalStateException: UT000139: Exchange already complete
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-10295?page=com.atlassian.jira.plugin... ]
Stuart Douglas updated WFLY-10295:
----------------------------------
Component/s: Web (Undertow)
(was: Application Client)
> java.lang.IllegalStateException: UT000139: Exchange already complete
> --------------------------------------------------------------------
>
> Key: WFLY-10295
> URL: https://issues.jboss.org/browse/WFLY-10295
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 12.0.0.Final
> Environment: Wildfly12, JDK1.8.762
> Reporter: Cora Kwok
> Assignee: Stuart Douglas
>
> java.lang.IllegalStateException: UT000139: Exchange already complete
> 2018-04-25 18:34:27,584 ERROR [io.undertow.request] (default task-7) UT005023: Exception handling request to /XXXX/clientconfigcheck/CCC_001_checkOpenWindow.action: java.lang.IllegalStateException: UT000139: Exchange already complete
> at io.undertow.server.HttpServerExchange.addExchangeCompleteListener(HttpServerExchange.java:941)
> at org.wildfly.mod_cluster.undertow.metric.RunningRequestsHttpHandler.handleRequest(RunningRequestsHttpHandler.java:59)
> at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135)
> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
> at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1526)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1526)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1526)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1526)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1526)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:360)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFLY-10295) java.lang.IllegalStateException: UT000139: Exchange already complete
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-10295?page=com.atlassian.jira.plugin... ]
Stuart Douglas commented on WFLY-10295:
---------------------------------------
Do you have a reproducer for this?
> java.lang.IllegalStateException: UT000139: Exchange already complete
> --------------------------------------------------------------------
>
> Key: WFLY-10295
> URL: https://issues.jboss.org/browse/WFLY-10295
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 12.0.0.Final
> Environment: Wildfly12, JDK1.8.762
> Reporter: Cora Kwok
> Assignee: Stuart Douglas
>
> java.lang.IllegalStateException: UT000139: Exchange already complete
> 2018-04-25 18:34:27,584 ERROR [io.undertow.request] (default task-7) UT005023: Exception handling request to /XXXX/clientconfigcheck/CCC_001_checkOpenWindow.action: java.lang.IllegalStateException: UT000139: Exchange already complete
> at io.undertow.server.HttpServerExchange.addExchangeCompleteListener(HttpServerExchange.java:941)
> at org.wildfly.mod_cluster.undertow.metric.RunningRequestsHttpHandler.handleRequest(RunningRequestsHttpHandler.java:59)
> at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135)
> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
> at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1526)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1526)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1526)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1526)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1526)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:360)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (SWSQE-189) Namespace Label is not being shown on Service Graph Page
by Guilherme Baufaker Rêgo (JIRA)
Guilherme Baufaker Rêgo created SWSQE-189:
---------------------------------------------
Summary: Namespace Label is not being shown on Service Graph Page
Key: SWSQE-189
URL: https://issues.jboss.org/browse/SWSQE-189
Project: Kiali QE
Issue Type: Bug
Reporter: Guilherme Baufaker Rêgo
Assignee: Michael Foley
Attachments: Screenshot_20180425_145123.png
{panel:title=Kiali Version}
"status": {
"Kiali console version": "0.2.10-SNAPSHOT.777-local-e8c9425385581594cdf9dcd67b10f57ec190b8ef",
"Kiali core commit hash": "a70624bf1b14b116b52f9c0eb78ed6ea43cdac8d",
"Kiali core version": "0.1.0.Final-SNAPSHOT",
"Kiali state": "running"
},
"products": [
{
"name": "Istio",
"version": "0.7.1"
},
{
"name": "Prometheus",
"version": "2.0.0"
},
{
"name": "Kubernetes",
"version": "v1.9.1+a0ce1bc657"
}
]
}
{panel}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (SWSQE-189) Namespace Label is not being shown on Service Graph Page
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-189?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo updated SWSQE-189:
------------------------------------------
Description:
{code}
"status": {
"Kiali console version": "0.2.10-SNAPSHOT.777-local-e8c9425385581594cdf9dcd67b10f57ec190b8ef",
"Kiali core commit hash": "a70624bf1b14b116b52f9c0eb78ed6ea43cdac8d",
"Kiali core version": "0.1.0.Final-SNAPSHOT",
"Kiali state": "running"
},
"products": [
{
"name": "Istio",
"version": "0.7.1"
},
{
"name": "Prometheus",
"version": "2.0.0"
},
{
"name": "Kubernetes",
"version": "v1.9.1+a0ce1bc657"
}
]
}
{codel}
was:
{panel:title=Kiali Version}
"status": {
"Kiali console version": "0.2.10-SNAPSHOT.777-local-e8c9425385581594cdf9dcd67b10f57ec190b8ef",
"Kiali core commit hash": "a70624bf1b14b116b52f9c0eb78ed6ea43cdac8d",
"Kiali core version": "0.1.0.Final-SNAPSHOT",
"Kiali state": "running"
},
"products": [
{
"name": "Istio",
"version": "0.7.1"
},
{
"name": "Prometheus",
"version": "2.0.0"
},
{
"name": "Kubernetes",
"version": "v1.9.1+a0ce1bc657"
}
]
}
{panel}
> Namespace Label is not being shown on Service Graph Page
> --------------------------------------------------------
>
> Key: SWSQE-189
> URL: https://issues.jboss.org/browse/SWSQE-189
> Project: Kiali QE
> Issue Type: Bug
> Reporter: Guilherme Baufaker Rêgo
> Assignee: Michael Foley
> Attachments: Screenshot_20180425_145123.png
>
>
> {code}
> "status": {
> "Kiali console version": "0.2.10-SNAPSHOT.777-local-e8c9425385581594cdf9dcd67b10f57ec190b8ef",
> "Kiali core commit hash": "a70624bf1b14b116b52f9c0eb78ed6ea43cdac8d",
> "Kiali core version": "0.1.0.Final-SNAPSHOT",
> "Kiali state": "running"
> },
> "products": [
> {
> "name": "Istio",
> "version": "0.7.1"
> },
> {
> "name": "Prometheus",
> "version": "2.0.0"
> },
> {
> "name": "Kubernetes",
> "version": "v1.9.1+a0ce1bc657"
> }
> ]
> }
> {codel}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months