December 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-951) Removing 2 or more rules does not retract justified objects

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-951?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-951: ------------------------------------------------ Marek Winkler <mwinkler(a)redhat.com> changed the Status of [bug 1273087|https://bugzilla.redhat.com/show_bug.cgi?id=1273087] from ON_QA to VERIFIED > Removing 2 or more rules does not retract justified objects > ----------------------------------------------------------- > > Key: DROOLS-951 > URL: https://issues.jboss.org/browse/DROOLS-951 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.3.0.Final > Reporter: Zvonimir Bošnjak > Assignee: Mario Fusco > Fix For: 6.4.x > > > When removing rules from knowledge which have logically inserted (justified) objects, only one object (from first removed rule) will be retracted. > In example from AddRemoveRule#184: as it removes the first rule, it re-initializes all other path memories and, in particular, marks them as unlinked (AbstractTerminalNode#204) > Later, when it tries to flush the deletions (AddRemoveRule#280), the unlinked status prevents the propagation from taking place. > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-950) Problem when a rule removal causes the merge of 2 segments and the first of the 2 haven't been initialized yet

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-950?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-950: ------------------------------------------------ Marek Winkler <mwinkler(a)redhat.com> changed the Status of [bug 1273087|https://bugzilla.redhat.com/show_bug.cgi?id=1273087] from ON_QA to VERIFIED > Problem when a rule removal causes the merge of 2 segments and the first of the 2 haven't been initialized yet > -------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-950 > URL: https://issues.jboss.org/browse/DROOLS-950 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.4.x > > > When a rule removal causes the merge of 2 segments and the first of the 2 haven't been initialized yet, the merged segment only has the nodes of the second segment while the ones of the first are totally skipped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-891) Missing alpha node removal when the only rule using it is removed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-891?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-891: ------------------------------------------------ Marek Winkler <mwinkler(a)redhat.com> changed the Status of [bug 1273087|https://bugzilla.redhat.com/show_bug.cgi?id=1273087] from ON_QA to VERIFIED > Missing alpha node removal when the only rule using it is removed > ----------------------------------------------------------------- > > Key: DROOLS-891 > URL: https://issues.jboss.org/browse/DROOLS-891 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.3.0.CR2 > > > When an alpha node has more than one sink and it is used by only one rule doesn't get removed when the rule itself is removed. The following test case demonstrates the problem. > {code} > @Test > public void testRemoveHasSameConElement() { > String packageName = "test"; > String rule1 = "package " + packageName + ";" + > "import java.util.Map; \n" + > "rule 'rule1' \n" + > "when \n" + > " Map(this['type'] == 'Goods' && this['brand'] == 'a') \n" + > " Map(this['type'] == 'Goods' && this['category'] == 'b') \n" + > "then \n" + > "System.out.println('test rule 1'); \n"+ > "end"; > KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder(); > kbuilder.add( ResourceFactory.newByteArrayResource( rule1.getBytes() ), ResourceType.DRL ); > if ( kbuilder.hasErrors() ) { > fail( kbuilder.getErrors().toString() ); > } > KnowledgeBase kbase = KnowledgeBaseFactory.newKnowledgeBase(); > kbase.addKnowledgePackages( kbuilder.getKnowledgePackages() ); > kbase.removeKnowledgePackage(packageName); > StatelessKnowledgeSession session = kbase.newStatelessKnowledgeSession(); > session.execute(new HashMap()); > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-801) Attempt to remove KnowledgePackage causes ClassCastException

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-801?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-801: ------------------------------------------------ Marek Winkler <mwinkler(a)redhat.com> changed the Status of [bug 1273087|https://bugzilla.redhat.com/show_bug.cgi?id=1273087] from ON_QA to VERIFIED > Attempt to remove KnowledgePackage causes ClassCastException > ------------------------------------------------------------ > > Key: DROOLS-801 > URL: https://issues.jboss.org/browse/DROOLS-801 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.2.0.Final > Reporter: Tom Hartwell > Assignee: Mario Fusco > Fix For: 6.3.0.Beta2 > > Attachments: class-cast-exception-trace-log.txt, ClassCastExceptionTest.java > > > Running the JUnit attached to this issue causes a Java ClassCastException -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-930) ClassCastException after segment split during incremental compilation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-930?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-930: ------------------------------------------------ Marek Winkler <mwinkler(a)redhat.com> changed the Status of [bug 1273087|https://bugzilla.redhat.com/show_bug.cgi?id=1273087] from ON_QA to VERIFIED > ClassCastException after segment split during incremental compilation > --------------------------------------------------------------------- > > Key: DROOLS-930 > URL: https://issues.jboss.org/browse/DROOLS-930 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.4.x > > > A segment split during an incremental compilation as in the following test case > {code} > @Test > public void testSegmentSplitOnIncrementalCompilation() throws Exception { > String drl = > "import " + Person.class.getCanonicalName() + "\n" + > "rule R1 when\n" + > " $s : String()" + > " Person( name == $s ) \n" + > "then\n" + > " System.out.println(\"Triggered: R1\");\n" + > "end\n" + > "rule R2 when\n" + > " $s : String()" + > " Person( name == $s ) \n" + > "then\n" + > " System.out.println(\"Triggered: R2\");\n" + > "end\n" + > "rule R3 when\n" + > " $s : String()" + > " Person( name != $s ) \n" + > "then\n" + > " System.out.println(\"Triggered: R3\");\n" + > "end\n"; > KieServices ks = KieServices.Factory.get(); > ReleaseId releaseId1 = ks.newReleaseId("org.kie", "test-upgrade", "1.1.1"); > KieModule km = createAndDeployJar(ks, releaseId1); > KieContainer kc = ks.newKieContainer(km.getReleaseId()); > KieSession ksession = kc.newKieSession(); > kc.updateToVersion(releaseId1); > ksession.insert(new Person("John", 26)); > ksession.insert( "John" ); > ksession.fireAllRules(); > ReleaseId releaseId2 = ks.newReleaseId("org.kie", "test-upgrade", "1.1.2"); > km = createAndDeployJar(ks, releaseId2, drl); > kc.updateToVersion(releaseId2); > ksession.fireAllRules(); > } > {code} > may cause the following ClassCastException during the subsequent network evaluation > {code} > java.lang.ClassCastException: org.drools.core.reteoo.RuleTerminalNode cannot be cast to org.drools.core.reteoo.LeftInputAdapterNode > at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:99) > 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:978) > at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1292) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1294) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1281) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1260) > at org.drools.compiler.integrationtests.IncrementalCompilationTest.testSegmentSplit(IncrementalCompilationTest.java:2001) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-893) Segment memory prototypes are not invalidated correctly during an incremental compilation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-893?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-893: ------------------------------------------------ Marek Winkler <mwinkler(a)redhat.com> changed the Status of [bug 1273087|https://bugzilla.redhat.com/show_bug.cgi?id=1273087] from ON_QA to VERIFIED > Segment memory prototypes are not invalidated correctly during an incremental compilation > ----------------------------------------------------------------------------------------- > > Key: DROOLS-893 > URL: https://issues.jboss.org/browse/DROOLS-893 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.3.0.CR2 > > > Segment memory prototypes are not invalidated correctly during an incremental compilation -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5473) Session.invalidate() does not invalidate SSO context for non-distributable applications

by Richard Janík (JIRA)

[ https://issues.jboss.org/browse/WFLY-5473?page=com.atlassian.jira.plugin.... ] Richard Janík commented on WFLY-5473: ------------------------------------- Fix version has changed to 10.0.0.CR5. That has not been released yet either, but the master branch already contains the fix from https://github.com/wildfly/wildfly/pull/8326 . The issue is still present in master branch (commit 1ed22f0de64b258a7205c253aee7eace3f96f4e4). Based on Pauls previous comment, I'll not reopen the issue until I can reproduce it with fix version, when it is released. Note: master at the above mentioned commit depends on wildfly-core 2.0.3, which depends on Undertow 1.3.7, which means that https://github.com/undertow-io/undertow/pull/340/commits should be in as well. > Session.invalidate() does not invalidate SSO context for non-distributable applications > --------------------------------------------------------------------------------------- > > Key: WFLY-5473 > URL: https://issues.jboss.org/browse/WFLY-5473 > Project: WildFly > Issue Type: Bug > Components: Clustering, Web (Undertow) > Reporter: Richard Janík > Assignee: Paul Ferraro > Priority: Blocker > Fix For: 10.0.0.CR5 > > > See "Steps to Reproduce" for detailed description. > According to my limited knowledge, this was also the core issue in https://bugzilla.redhat.com/show_bug.cgi?id=924456 which has been dispatched as a one-off to a customer. Thus, I'm setting the priority to blocker as this is a regression against 6.4.x. No exceptions have been observed in the server output however. > Adding Clustering component as I've been trying this with standalone-ha.xml and BZ 924456 relates to clustering. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1177) Service can't be installed if the path contains a closed bracket

by Paul Wildberg (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1177?page=com.atlassian.jira.plugi... ] Paul Wildberg updated WFCORE-1177: ---------------------------------- Description: Problem: If you start "service.bat install" in e.g. in C:\Program Files (x86)\wildfly-9.0.1.Final\bin\service you will get: Using the X86-64bit version of prunsrv "\wildfly-9.0.1.Final\domain\log" can not be used syntatically at this point (don't know if it is correct, I translated it from german. Original it is "kann syntaktisch an dieser Stelle nicht verarbeitet werden.") Cause: This is because of the ) in "Program Files (x86)" and this is a problem because in the service.bat in line 175 and 179 (set LOGPATH=%JBOSS_HOME%\domain\log and LOGPATH=%JBOSS_HOME%\standalone\log- in version 9.0.1 and 9.0.2 - in Version 10 it may be in another line) path is not set in double quotation marks. All other paths are set in double quotation marks. Solution: Set the variable and path in double quotation marks: set "LOGPATH=%JBOSS_HOME%\...\log" was: Problem: If you start "service.bat install" in e.g. in C:\Program Files (x86)\wildfly-9.0.1.Final\bin\service you will get: Using the X86-64bit version of prunsrv "\wildfly-9.0.1.Final\domain\log" can not be used syntatically at this point (don't know if it is correct, I translated it from german. Original it is "kann syntaktisch an dieser Stelle nicht verarbeitet werden.") Cause: This is because of the ) in "Program Files (x86)" and this is a problem because in the service.bat in line 175 and 179 (set LOGPATH=%JBOSS_HOME%\domain\log - in version 9.0.1 and 9.0.2 - in Version 10 it may be in another line) the path is not set in double quotation marks. All other paths are set in double quotation marks. Solution: Set the path in double quotation marks: set "LOGPATH=%JBOSS_HOME%\domain\log" > Service can't be installed if the path contains a closed bracket > ---------------------------------------------------------------- > > Key: WFCORE-1177 > URL: https://issues.jboss.org/browse/WFCORE-1177 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Environment: all Windows versions > Reporter: Paul Wildberg > Priority: Critical > Labels: jboss > > Problem: > If you start "service.bat install" in e.g. in C:\Program Files (x86)\wildfly-9.0.1.Final\bin\service you will get: > Using the X86-64bit version of prunsrv > "\wildfly-9.0.1.Final\domain\log" can not be used syntatically at this point (don't know if it is correct, I translated it from german. Original it is "kann syntaktisch an dieser Stelle nicht verarbeitet werden.") > Cause: > This is because of the ) in "Program Files (x86)" and this is a problem because in the service.bat in line 175 and 179 (set LOGPATH=%JBOSS_HOME%\domain\log and LOGPATH=%JBOSS_HOME%\standalone\log- in version 9.0.1 and 9.0.2 - in Version 10 it may be in another line) path is not set in double quotation marks. > All other paths are set in double quotation marks. > Solution: > Set the variable and path in double quotation marks: > set "LOGPATH=%JBOSS_HOME%\...\log" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1177) Service can't be installed if the path contains a closed bracket

by Paul Wildberg (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1177?page=com.atlassian.jira.plugi... ] Paul Wildberg edited comment on WFCORE-1177 at 12/2/15 7:43 AM: ---------------------------------------------------------------- news: With the workaround I was able to install the service - but I couldn't start it. So I dived some more into it. If you change it to set "LOGPATH=%JBOSS_HOME%\...\log" (difference is the double quotation mark in front of "LOGPATH" and not in front of "%JBOSS_HOME%") you can install the service and start it. I edited the workaround. I don't think all lines are like this so maybe there need a lot more lines (maybe even in other files) to be changed than this two. was (Author: wildberg): news: With the workaround I was able to install the service - but I couldn't start it. So I dived some more into it. If you change it to set "LOGPATH=%JBOSS_HOME%\domain\log" (difference is the double quotation mark in front of "LOGPATH" and not in front of "%JBOSS_HOME%") you can install the service and start it. I edited the workaround. I don't think all lines are like this so maybe there need to be a lot more lines (maybe even in other files) to be changed than this two. > Service can't be installed if the path contains a closed bracket > ---------------------------------------------------------------- > > Key: WFCORE-1177 > URL: https://issues.jboss.org/browse/WFCORE-1177 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Environment: all Windows versions > Reporter: Paul Wildberg > Priority: Critical > Labels: jboss > > Problem: > If you start "service.bat install" in e.g. in C:\Program Files (x86)\wildfly-9.0.1.Final\bin\service you will get: > Using the X86-64bit version of prunsrv > "\wildfly-9.0.1.Final\domain\log" can not be used syntatically at this point (don't know if it is correct, I translated it from german. Original it is "kann syntaktisch an dieser Stelle nicht verarbeitet werden.") > Cause: > This is because of the ) in "Program Files (x86)" and this is a problem because in the service.bat in line 175 and 179 (set LOGPATH=%JBOSS_HOME%\domain\log - in version 9.0.1 and 9.0.2 - in Version 10 it may be in another line) the path is not set in double quotation marks. > All other paths are set in double quotation marks. > Solution: > Set the path in double quotation marks: > set "LOGPATH=%JBOSS_HOME%\domain\log" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1177) Service can't be installed if the path contains a closed bracket

by Paul Wildberg (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1177?page=com.atlassian.jira.plugi... ] Paul Wildberg updated WFCORE-1177: ---------------------------------- Description: Problem: If you start "service.bat install" in e.g. in C:\Program Files (x86)\wildfly-9.0.1.Final\bin\service you will get: Using the X86-64bit version of prunsrv "\wildfly-9.0.1.Final\domain\log" can not be used syntatically at this point (don't know if it is correct, I translated it from german. Original it is "kann syntaktisch an dieser Stelle nicht verarbeitet werden.") Cause: This is because of the ) in "Program Files (x86)" and this is a problem because in the service.bat in line 175 and 179 (set LOGPATH=%JBOSS_HOME%\domain\log - in version 9.0.1 and 9.0.2 - in Version 10 it may be in another line) the path is not set in double quotation marks. All other paths are set in double quotation marks. Solution: Set the path in double quotation marks: set "LOGPATH=%JBOSS_HOME%\domain\log" was: Problem: If you start "service.bat install" in e.g. in C:\Program Files (x86)\wildfly-9.0.1.Final\bin\service you will get: Using the X86-64bit version of prunsrv "\wildfly-9.0.1.Final\domain\log" can not be used syntatically at this point (don't know if it is correct, I translated it from german. Original it is "kann syntaktisch an dieser Stelle nicht verarbeitet werden.") Cause: This is because of the ) in "Program Files (x86)" and this is a problem because in the service.bat in line 175 and 179 (set LOGPATH=%JBOSS_HOME%\domain\log - in version 9.0.1 and 9.0.2 - in Version 10 it may be in another line) the path is not set in double quotation marks. All other paths are set in double quotation marks. Solution: Set the path in double quotation marks: set LOGPATH="%JBOSS_HOME%\domain\log" > Service can't be installed if the path contains a closed bracket > ---------------------------------------------------------------- > > Key: WFCORE-1177 > URL: https://issues.jboss.org/browse/WFCORE-1177 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Environment: all Windows versions > Reporter: Paul Wildberg > Priority: Critical > Labels: jboss > > Problem: > If you start "service.bat install" in e.g. in C:\Program Files (x86)\wildfly-9.0.1.Final\bin\service you will get: > Using the X86-64bit version of prunsrv > "\wildfly-9.0.1.Final\domain\log" can not be used syntatically at this point (don't know if it is correct, I translated it from german. Original it is "kann syntaktisch an dieser Stelle nicht verarbeitet werden.") > Cause: > This is because of the ) in "Program Files (x86)" and this is a problem because in the service.bat in line 175 and 179 (set LOGPATH=%JBOSS_HOME%\domain\log - in version 9.0.1 and 9.0.2 - in Version 10 it may be in another line) the path is not set in double quotation marks. > All other paths are set in double quotation marks. > Solution: > Set the path in double quotation marks: > set "LOGPATH=%JBOSS_HOME%\domain\log" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2015