July 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1158) NullpointerException when trying to reuse KnowledgePackage into a new KnowledgeBase

by Juan Carlos Garcia (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1158?page=com.atlassian.jira.plugi... ] Juan Carlos Garcia commented on DROOLS-1158: -------------------------------------------- I will rework, the sample around the new KIE API and will look for the KIE Scanner options to monitor the changes. Will come back if the problem arise. > NullpointerException when trying to reuse KnowledgePackage into a new KnowledgeBase > ----------------------------------------------------------------------------------- > > Key: DROOLS-1158 > URL: https://issues.jboss.org/browse/DROOLS-1158 > Project: Drools > Issue Type: Bug > Affects Versions: 6.3.0.Final, 6.4.0.Final > Reporter: Juan Carlos Garcia > Assignee: Matteo Mortari > Attachments: drools-reusepackage.tar, screenshot-1.png > > > Having a set of DecisionTables which KnowledgePackages are cached in our application, after we detect a change in any of those XLS files, we build a KnowledgePackages from it, and then try to create a new KnowledgeBase with the new KnowledgePackages + the rest of the cached one that that were not modified, but it fails with a NPE internally in Drools (6.3.0 and 6.4.0) > This is not a problem for the drools version (6.0.1.Final) that we currently uses using in production. > After debugging and putting a breakpoint into the *MvelConstraint.java:619*, it shows that it is trying to look for a packageName which hasn't being loaded yet in the new kbase (but belong to others XLS). > I have attached a project with a testcase that shows the problem, it has 2 DecisionTable which i had to cut down a little bit (from our real files) and removes some sensitive information (replacing some of text with FOO-BAR). > {code} > java.lang.NullPointerException > at org.drools.core.rule.constraint.MvelConstraint.equals(MvelConstraint.java:619) > at org.drools.core.reteoo.AlphaNode.internalEquals(AlphaNode.java:199) > at org.drools.core.common.BaseNode.thisNodeEquals(BaseNode.java:194) > at org.drools.core.reteoo.CompositeObjectSinkAdapter.getMatchingNode(CompositeObjectSinkAdapter.java:531) > at org.drools.core.reteoo.builder.BuildUtils.attachNode(BuildUtils.java:121) > at org.drools.core.reteoo.builder.PatternBuilder.buildAlphaNodeChain(PatternBuilder.java:332) > at org.drools.core.reteoo.builder.PatternBuilder.attachAlphaNodes(PatternBuilder.java:313) > at org.drools.core.reteoo.builder.PatternBuilder.attachPattern(PatternBuilder.java:130) > at org.drools.core.reteoo.builder.PatternBuilder.build(PatternBuilder.java:78) > at org.drools.core.reteoo.builder.GroupElementBuilder$AndBuilder.build(GroupElementBuilder.java:108) > at org.drools.core.reteoo.builder.GroupElementBuilder.build(GroupElementBuilder.java:68) > at org.drools.core.reteoo.builder.ReteooRuleBuilder.addSubRule(ReteooRuleBuilder.java:161) > at org.drools.core.reteoo.builder.ReteooRuleBuilder.addRule(ReteooRuleBuilder.java:133) > at org.drools.core.reteoo.ReteooBuilder.addRule(ReteooBuilder.java:106) > at org.drools.core.impl.KnowledgeBaseImpl.addRule(KnowledgeBaseImpl.java:1567) > at org.drools.core.impl.KnowledgeBaseImpl.addRule(KnowledgeBaseImpl.java:1547) > at org.drools.core.impl.KnowledgeBaseImpl.internalAddPackages(KnowledgeBaseImpl.java:920) > at org.drools.core.impl.KnowledgeBaseImpl.access$000(KnowledgeBaseImpl.java:117) > at org.drools.core.impl.KnowledgeBaseImpl$1.run(KnowledgeBaseImpl.java:708) > at org.drools.core.impl.KnowledgeBaseImpl.enqueueModification(KnowledgeBaseImpl.java:716) > at org.drools.core.impl.KnowledgeBaseImpl.addPackages(KnowledgeBaseImpl.java:705) > at org.drools.core.impl.KnowledgeBaseImpl.addKnowledgePackages(KnowledgeBaseImpl.java:273) > at org.drools.impl.adapters.KnowledgeBaseAdapter.addKnowledgePackages(KnowledgeBaseAdapter.java:62) > at bug.demo.BugReloadableDecisionTableTest.addRuleSetToKnowledgeBase(BugReloadableDecisionTableTest.java:63) > at bug.demo.BugReloadableDecisionTableTest.testReuseKnowledgePackage(BugReloadableDecisionTableTest.java:53) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6843) Buttons at the end of modal panels get cut off

by Bartosz Baranowski (JIRA)

Bartosz Baranowski created WFLY-6843: ---------------------------------------- Summary: Buttons at the end of modal panels get cut off Key: WFLY-6843 URL: https://issues.jboss.org/browse/WFLY-6843 Project: WildFly Issue Type: Bug Components: Web Console Reporter: Bartosz Baranowski Assignee: Michal Petrov -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6842) Impossible to read/configure messaging provider journal directory path

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-6842?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski updated WFLY-6842: ------------------------------------- Component/s: Web Console > Impossible to read/configure messaging provider journal directory path > ---------------------------------------------------------------------- > > Key: WFLY-6842 > URL: https://issues.jboss.org/browse/WFLY-6842 > Project: WildFly > Issue Type: Bug > Components: Web Console > Reporter: Bartosz Baranowski > Assignee: Michal Petrov > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6842) Impossible to read/configure messaging provider journal directory path

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-6842?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski reassigned WFLY-6842: ---------------------------------------- Assignee: Bartosz Baranowski (was: Jason Greene) > Impossible to read/configure messaging provider journal directory path > ---------------------------------------------------------------------- > > Key: WFLY-6842 > URL: https://issues.jboss.org/browse/WFLY-6842 > Project: WildFly > Issue Type: Bug > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6842) Impossible to read/configure messaging provider journal directory path

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-6842?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski reassigned WFLY-6842: ---------------------------------------- Assignee: Michal Petrov (was: Bartosz Baranowski) > Impossible to read/configure messaging provider journal directory path > ---------------------------------------------------------------------- > > Key: WFLY-6842 > URL: https://issues.jboss.org/browse/WFLY-6842 > Project: WildFly > Issue Type: Bug > Reporter: Bartosz Baranowski > Assignee: Michal Petrov > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6842) Impossible to read/configure messaging provider journal directory path

by Bartosz Baranowski (JIRA)

Bartosz Baranowski created WFLY-6842: ---------------------------------------- Summary: Impossible to read/configure messaging provider journal directory path Key: WFLY-6842 URL: https://issues.jboss.org/browse/WFLY-6842 Project: WildFly Issue Type: Bug Reporter: Bartosz Baranowski Assignee: Jason Greene Priority: Critical -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2090) JGRP000027: failed passing message up

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2090?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2090: --------------------------- Fix Version/s: 3.6.11 4.0 > JGRP000027: failed passing message up > ------------------------------------- > > Key: JGRP-2090 > URL: https://issues.jboss.org/browse/JGRP-2090 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.10 > Reporter: Will Wright > Assignee: Bela Ban > Fix For: 3.6.11, 4.0 > > > The JGroups library is generating NullPointerExceptions when attempting to process incoming messages. From what I can tell this is due to it looking for an incorrect message header. > The TP object has a protocol id of 75 despite being a TUNNEL which ought to have an id of 24. The id is being correctly assigned to 24 at the Protocol.id member variable declaration, but is then subsequently changed to 75 by the TP.init method. This seems to have been caused by commit [6bc167f7e0181af32e1930935d8cf0efdc1e82f0|https://github.com/belaban/JGrou...] which has the message "Added TP to jg-protocols.xml". If I backout this change to the TP.init method so as to not update the id then my application receives the incoming messages fine. > java.lang.NullPointerException: null > at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1872) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6726) Add help text about jboss.undefinded.host for the wsdl-host attribute

by Claudio Miranda (JIRA)

[ https://issues.jboss.org/browse/WFLY-6726?page=com.atlassian.jira.plugin.... ] Claudio Miranda updated WFLY-6726: ---------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/9047 > Add help text about jboss.undefinded.host for the wsdl-host attribute > --------------------------------------------------------------------- > > Key: WFLY-6726 > URL: https://issues.jboss.org/browse/WFLY-6726 > Project: WildFly > Issue Type: Enhancement > Components: Web Services > Reporter: Claudio Miranda > Assignee: Alessio Soldano > > would be doable to add the text to the > resource-description of wsdl-url, related to the use of > jboss.undefined.host ? > The path > /deployment=*/subsystem=webservices/endpoint=*:read-resource-description > I ask that because HAL consumes and exposes the resource-description > of each attribute and having the help text about the > jboss.undefined.host in wsdl-host also helps CLI users. > A suggestion for the text: > "Webservice endpoint WSDL URL. If wsdl-host is set to > jbossws.undefined.host, Wildfly uses the requester's host when > rewriting the <soap:address>" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6841) Add backup service support for singleton services

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-6841?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-6841: ------------------------------- Description: Currently, singleton services are started on the primary node only - no service is started on the backup nodes. We can generalize this use case by building a singleton service using 2 services: one to be started on the primary node, and the other to be installed on backup nodes. When a node is elected as the primary provider, we stop the backup service, and start the primary service. Conversely, when a primary node loses a re-election, it stops its primary service and starts its backup service. (was: Currently, singleton services are started on the primary node only - no service is started on the backup node. We can generalize this use case by building a singleton service using 2 services: one to be started on the primary node, and the other to be installed on backup nodes. When a node is elected as the primary provider, we stop the backup service, and start the primary service. Conversely, when a primary node loses a re-election, it stops its primary service and starts its backup service.) > Add backup service support for singleton services > ------------------------------------------------- > > Key: WFLY-6841 > URL: https://issues.jboss.org/browse/WFLY-6841 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.Alpha1 > > > Currently, singleton services are started on the primary node only - no service is started on the backup nodes. We can generalize this use case by building a singleton service using 2 services: one to be started on the primary node, and the other to be installed on backup nodes. When a node is elected as the primary provider, we stop the backup service, and start the primary service. Conversely, when a primary node loses a re-election, it stops its primary service and starts its backup service. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-314) FormAuthenticator duplicates original request GET parameters

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWEB-314?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBWEB-314: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1302434, https://bugzilla.redhat.com/show_bug.cgi?id=1357678 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1302434) > FormAuthenticator duplicates original request GET parameters > ------------------------------------------------------------ > > Key: JBWEB-314 > URL: https://issues.jboss.org/browse/JBWEB-314 > Project: JBoss Web > Issue Type: Bug > Reporter: Dominik Pospisil > Assignee: Remy Maucherat > Attachments: FormAuthenticator.diff > > > The FormAuthenticator duplicates original request GET parameters. This is a regression since rev. 2320. > The FormAuth does saved.addParameter(name, val) which results in parameter value stored twice. > request.getParameter(String name) retutns the original value which is fine > but request.getParameterValues(String name) returns String[] {val,val} incorrectly. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2016