October 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1338) NPE happens in TupleSetsImpl.setNextTuple()

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1338?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-1338: -------------------------------- Comment: was deleted (was: [~hiroko] Where can I find a reproducer for this issue?) > NPE happens in TupleSetsImpl.setNextTuple() > ------------------------------------------- > > Key: DROOLS-1338 > URL: https://issues.jboss.org/browse/DROOLS-1338 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.4.0.Final > Reporter: Hiroko Miura > Assignee: Mario Fusco > Priority: Critical > Labels: support > > In customer's performance test case, NPE happens in TupleSetsImpl.setNextTuple() with the following stack. > java.lang.NullPointerException > at org.drools.core.common.TupleSetsImpl.setNextTuple(TupleSetsImpl.java:352) > at org.drools.core.common.TupleSetsImpl.removeInsert(TupleSetsImpl.java:168) > at org.drools.core.phreak.RuleNetworkEvaluator.deleteChildLeftTuple(RuleNetworkEvaluator.java:729) > at org.drools.core.phreak.RuleNetworkEvaluator.unlinkAndDeleteChildLeftTuple(RuleNetworkEvaluator.java:721) > at org.drools.core.phreak.PhreakNotNode.doRightUpdates(PhreakNotNode.java:343) > at org.drools.core.phreak.PhreakNotNode.doNode(PhreakNotNode.java:74) > at org.drools.core.phreak.RuleNetworkEvaluator.switchOnDoBetaNode(RuleNetworkEvaluator.java:524) > at org.drools.core.phreak.RuleNetworkEvaluator.evalBetaNode(RuleNetworkEvaluator.java:505) > at org.drools.core.phreak.RuleNetworkEvaluator.evalNode(RuleNetworkEvaluator.java:341) > at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:301) > at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:136) > at org.drools.core.phreak.AddRemoveRule.forceFlushLeftTuple(AddRemoveRule.java:692) > at org.drools.core.phreak.AddRemoveRule.flushLeftTupleIfNecessary(AddRemoveRule.java:629) > at org.drools.core.reteoo.NotNode.assertObject(NotNode.java:161) > at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:494) > at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:384) > at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:134) > at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:494) > at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:384) > at org.drools.core.reteoo.ObjectTypeNode.propagateAssert(ObjectTypeNode.java:304) > at org.drools.core.phreak.PropagationEntry$Insert.execute(PropagationEntry.java:132) > at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:82) > at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:72) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.flushPropagations(StatefulKnowledgeSessionImpl.java:2053) > at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:128) > at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:74) > at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:960) > at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1303) > at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1241) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1336) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1327) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1308) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1338) NPE happens in TupleSetsImpl.setNextTuple()

by Hiroko Miura (JIRA)

Hiroko Miura created DROOLS-1338: ------------------------------------ Summary: NPE happens in TupleSetsImpl.setNextTuple() Key: DROOLS-1338 URL: https://issues.jboss.org/browse/DROOLS-1338 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 6.4.0.Final Reporter: Hiroko Miura Assignee: Mario Fusco Priority: Critical In customer's performance test case, NPE happens in TupleSetsImpl.setNextTuple() with the following stack. java.lang.NullPointerException at org.drools.core.common.TupleSetsImpl.setNextTuple(TupleSetsImpl.java:352) at org.drools.core.common.TupleSetsImpl.removeInsert(TupleSetsImpl.java:168) at org.drools.core.phreak.RuleNetworkEvaluator.deleteChildLeftTuple(RuleNetworkEvaluator.java:729) at org.drools.core.phreak.RuleNetworkEvaluator.unlinkAndDeleteChildLeftTuple(RuleNetworkEvaluator.java:721) at org.drools.core.phreak.PhreakNotNode.doRightUpdates(PhreakNotNode.java:343) at org.drools.core.phreak.PhreakNotNode.doNode(PhreakNotNode.java:74) at org.drools.core.phreak.RuleNetworkEvaluator.switchOnDoBetaNode(RuleNetworkEvaluator.java:524) at org.drools.core.phreak.RuleNetworkEvaluator.evalBetaNode(RuleNetworkEvaluator.java:505) at org.drools.core.phreak.RuleNetworkEvaluator.evalNode(RuleNetworkEvaluator.java:341) at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:301) at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:136) at org.drools.core.phreak.AddRemoveRule.forceFlushLeftTuple(AddRemoveRule.java:692) at org.drools.core.phreak.AddRemoveRule.flushLeftTupleIfNecessary(AddRemoveRule.java:629) at org.drools.core.reteoo.NotNode.assertObject(NotNode.java:161) at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:494) at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:384) at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:134) at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:494) at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:384) at org.drools.core.reteoo.ObjectTypeNode.propagateAssert(ObjectTypeNode.java:304) at org.drools.core.phreak.PropagationEntry$Insert.execute(PropagationEntry.java:132) at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:82) at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:72) at org.drools.core.impl.StatefulKnowledgeSessionImpl.flushPropagations(StatefulKnowledgeSessionImpl.java:2053) at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:128) at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:74) at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:960) at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1303) at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1241) at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1336) at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1327) at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1308) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6500) wildfly-10.0.0.Final deployment crash

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFLY-6500?page=com.atlassian.jira.plugin.... ] jaikiran pai commented on WFLY-6500: ------------------------------------ {quote} Examination of the logs showed nothing more than the new deployment being rejected because a similar deployment was already registered. {quote} Can you paste that log message(s) here? Or better still, upload the server.log file? > wildfly-10.0.0.Final deployment crash > ------------------------------------- > > Key: WFLY-6500 > URL: https://issues.jboss.org/browse/WFLY-6500 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.Final > Reporter: Jason Morgan > Assignee: Jason Greene > > Having a war in the deployment directory and then "replacing" a deployment through the web console causes the server to crash without any logging on restart -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-773) ArrayIndexOutOfBoundsException occurs when a queue-length is 0 in the thread pool executor

by Petr Jurak (JIRA)

[ https://issues.jboss.org/browse/WFCORE-773?page=com.atlassian.jira.plugin... ] Petr Jurak commented on WFCORE-773: ----------------------------------- Yes, this legacy system is not used anymore. The intention was to make this change because the source code still contains the old code. > ArrayIndexOutOfBoundsException occurs when a queue-length is 0 in the thread pool executor > -------------------------------------------------------------------------------------------- > > Key: WFCORE-773 > URL: https://issues.jboss.org/browse/WFCORE-773 > Project: WildFly Core > Issue Type: Bug > Reporter: Enrique González Martínez > Assignee: Petr Jurak > > BoundedQueueThreadPool does not support zero length queue setup. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6500) wildfly-10.0.0.Final deployment crash

by Michael Peoples (JIRA)

[ https://issues.jboss.org/browse/WFLY-6500?page=com.atlassian.jira.plugin.... ] Michael Peoples commented on WFLY-6500: --------------------------------------- The Camunda fix is for 7.6, which is still in Alpha testing. I'll see about doing a manual setup. And get back to you. I'm not sure this condition is consistently reproducible, unless someone has a specific sequence of steps to cause it. Examination of the logs showed nothing more than the new deployment being rejected because a similar deployment was already registered. Even switching version numbers didn't help. However, I'm not sure what circumstances are required to reproduce the server crash. > wildfly-10.0.0.Final deployment crash > ------------------------------------- > > Key: WFLY-6500 > URL: https://issues.jboss.org/browse/WFLY-6500 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.Final > Reporter: Jason Morgan > Assignee: Jason Greene > > Having a war in the deployment directory and then "replacing" a deployment through the web console causes the server to crash without any logging on restart -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7351) JAX-RS Http Client does not support SNI even though underlying Apache HttpClient version supports it

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-7351?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on WFLY-7351: --------------------------------------- need to check, likely related to https://issues.jboss.org/browse/RESTEASY-1431 (which is in 3.1 only) > JAX-RS Http Client does not support SNI even though underlying Apache HttpClient version supports it > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-7351 > URL: https://issues.jboss.org/browse/WFLY-7351 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 10.1.0.Final > Environment: N/A > Reporter: Edvin Syse > Assignee: Alessio Soldano > Labels: httpclient, https, jax-rs > Attachments: httpclient-sni-bug.zip > > > When creating a JAX-RS client using ClientBuilder.newClient() and accessing an SSL resource configured with SNI, the request fails. > When the request is made you get the default certificate for the ip as it is configured on the web server instead of the certificate corresponding to the host name you entered. > Attached is a simple Maven project with a rest endpoint that will make a request to https://www.syse.no/, which is a host configured with SNI. If you access this host with a client that is not SNI capable, you will get the default certificate instead of the one corresponding to www.syse.no. (That cert is actually expired, so that is the underlying cause reported by the http client in this case. In other cases you will most probably just get a name mismatch type of error). > This effectively prevents the Http client from being used reliably against a rapidly growing number of SSL enabled sites, as SNI is the new standard "everywhere" SSL is configured these days. > The underlying Apache HttpClient version does indeed support SNI. I have tested the version of Apache HttpClient that is bundled with Wildfly 10.1 and it works correctly. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6500) wildfly-10.0.0.Final deployment crash

by Frank Langelage (JIRA)

[ https://issues.jboss.org/browse/WFLY-6500?page=com.atlassian.jira.plugin.... ] Frank Langelage commented on WFLY-6500: --------------------------------------- Next version of Camunda will we packaged with Wildfly 10.1. See https://app.camunda.com/jira/browse/CAM-6790. > wildfly-10.0.0.Final deployment crash > ------------------------------------- > > Key: WFLY-6500 > URL: https://issues.jboss.org/browse/WFLY-6500 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.Final > Reporter: Jason Morgan > Assignee: Jason Greene > > Having a war in the deployment directory and then "replacing" a deployment through the web console causes the server to crash without any logging on restart -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-658) OAuth2 Resource Owner Password Credentials CallbackHandler

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-658?page=com.atlassian.jira.plugin.sy... ] Pedro Igor updated ELY-658: --------------------------- Description: We must be able to allow OAuth2 SASL clients to obtain tokens on behalf of an user using the Resource Owner Password Credentials Grant Type [1]. To do that we should provide a {{CallbackHandler}} that could be used to handle all the necessary logic related with this grant type. This should also allow Elytron to support other grant types defined by OAuth2 in the future. Configuration wise, we must be able to obtain the necessary configuration to integrate with an OAuth2/OpenID Connect identity provider. Where this configuration should be purely based on standard options such as those specified by OpenID Connect Discovery [2]. [1] https://tools.ietf.org/html/rfc6749#page-9 [2] https://openid.net/specs/openid-connect-discovery-1_0.html was: We must be able to allow OAuth2 SASL clients to obtain tokens on behalf of an user using the Resource Owner Password Credentials Grant Type [1]. To do that we should provide a {{CallbackHandler}} that could be used to handle all the necessary logic related with this grant type. This should also allow Elytron to support other grant types defined by OAuth2 in the future. Configuration wise, we must be able to obtain the necessary configuration to integrate with an OAuth2/OpenID Connect identity provider. Where this configuration should be purely based on standard options such as those specified by OpenID Connect Discovery [2]. In fact, maybe we should change our current OAuth2 SASL Client and Servers to refer to OpenID Connect instead. As we are basically addressing authentication and that is what OpenID Connect really provides, differently than OAuth2 that is basically a authorization and delegation protocol. [1] https://tools.ietf.org/html/rfc6749#page-9 [2] https://openid.net/specs/openid-connect-discovery-1_0.html > OAuth2 Resource Owner Password Credentials CallbackHandler > ---------------------------------------------------------- > > Key: ELY-658 > URL: https://issues.jboss.org/browse/ELY-658 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Callbacks > Affects Versions: 1.1.0.Beta10 > Reporter: Pedro Igor > Assignee: Pedro Igor > > We must be able to allow OAuth2 SASL clients to obtain tokens on behalf of an user using the Resource Owner Password Credentials Grant Type [1]. To do that we should provide a {{CallbackHandler}} that could be used to handle all the necessary logic related with this grant type. > This should also allow Elytron to support other grant types defined by OAuth2 in the future. > Configuration wise, we must be able to obtain the necessary configuration to integrate with an OAuth2/OpenID Connect identity provider. Where this configuration should be purely based on standard options such as those specified by OpenID Connect Discovery [2]. > [1] https://tools.ietf.org/html/rfc6749#page-9 > [2] https://openid.net/specs/openid-connect-discovery-1_0.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-675) OAuth2 Client Credentials CallbackHandler

by Pedro Igor (JIRA)

Pedro Igor created ELY-675: ------------------------------ Summary: OAuth2 Client Credentials CallbackHandler Key: ELY-675 URL: https://issues.jboss.org/browse/ELY-675 Project: WildFly Elytron Issue Type: Feature Request Components: Callbacks Affects Versions: 1.1.0.Beta11 Reporter: Pedro Igor Assignee: Pedro Igor -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6500) wildfly-10.0.0.Final deployment crash

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6500?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-6500: ----------------------------------- you can manually install camuda into 10.1, see docs on how to do that https://docs.camunda.org/manual/7.5/installation/full/jboss/manual/ > wildfly-10.0.0.Final deployment crash > ------------------------------------- > > Key: WFLY-6500 > URL: https://issues.jboss.org/browse/WFLY-6500 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.Final > Reporter: Jason Morgan > Assignee: Jason Greene > > Having a war in the deployment directory and then "replacing" a deployment through the web console causes the server to crash without any logging on restart -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2016