November 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4395) JDR collect free disk space

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-4395?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-4395: ----------------------------------- Component/s: JDR > JDR collect free disk space > --------------------------- > > Key: WFLY-4395 > URL: https://issues.jboss.org/browse/WFLY-4395 > Project: WildFly > Issue Type: Enhancement > Components: JDR > Reporter: Brad Maxwell > Assignee: Brad Maxwell > > JDR collect free disk space as server can throw errors when there is no free space. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-954) Removal of a rule having a sub-sub-network doesn't cleanup the outermost subnetwork

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-954?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-954: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1273087|https://bugzilla.redhat.com/show_bug.cgi?id=1273087] from ASSIGNED to MODIFIED > Removal of a rule having a sub-sub-network doesn't cleanup the outermost subnetwork > ----------------------------------------------------------------------------------- > > Key: DROOLS-954 > URL: https://issues.jboss.org/browse/DROOLS-954 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.4.x > > > Removal of a rule having a sub-sub-network (as in the following drl) doesn't cleanup the outermost subnetwork > {code} > rule R when > $l : List() > exists Integer( this == 1 ) from $l > exists Integer( this == 2 ) from $l > then > end > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[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: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1273087|https://bugzilla.redhat.com/show_bug.cgi?id=1273087] from ASSIGNED to MODIFIED > 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)

10 years, 8 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: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1273087|https://bugzilla.redhat.com/show_bug.cgi?id=1273087] from ASSIGNED to MODIFIED > 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)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4971) lots of warnings discarded message from different cluster

by Bertrand Donnet (JIRA)

[ https://issues.jboss.org/browse/WFLY-4971?page=com.atlassian.jira.plugin.... ] Bertrand Donnet commented on WFLY-4971: --------------------------------------- Paul, Thanks for the solution. Solved the problem for me. I think that the name is only "log_discard_msgs" without property at the end (probably a copy/paste) <stack name="udp"> <transport type="UDP" socket-binding="jgroups-udp"> <property name="*log_discard_msgs*">false</property> </transport> ... </transport> Thanks again > lots of warnings discarded message from different cluster > --------------------------------------------------------- > > Key: WFLY-4971 > URL: https://issues.jboss.org/browse/WFLY-4971 > Project: WildFly > Issue Type: Bug > Affects Versions: 9.0.0.Final > Reporter: Daniele Pirola > Assignee: Paul Ferraro > > I run the latest wildfly-9.0.0.Final. I have an environment with 2 host and 3 server per host. I noticed that there are a lot of warning like this > JGRP000012: discarded message from different cluster hq-cluster (our cluster is ee) > or this > JGRP000012: discarded message from different cluster ee (our cluster is hq-cluster) > With the same configuration in wildfly-8.2.0.Final I didn't noticed anything. > The strange thing is that warnings still appear even if I run only the domain controller with 1 server active. I think that the domain configuration (I used the default with full-ha profile) is missing something that can diffentiate jgroup channel but I don't know how -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4942) KeyAffinityService race condition on view change

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-4942?page=com.atlassian.jira.plugin.... ] Paul Ferraro closed WFLY-4942. ------------------------------ Fix Version/s: 10.0.0.Beta2 Resolution: Done This was fixed with the upgrade to Infinispan 8.0.0.CR1. > KeyAffinityService race condition on view change > ------------------------------------------------ > > Key: WFLY-4942 > URL: https://issues.jboss.org/browse/WFLY-4942 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Bartosz Baranowski > Assignee: Paul Ferraro > Fix For: 10.0.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4971) lots of warnings discarded message from different cluster

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-4971?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on WFLY-4971: ------------------------------------ [~witoldbolt] For WF9, you have 2 options: # Use a designated protocol stack for messaging-activemq. This entails using a unique transport socket-binding to isolate the 2 clusters. # Just configure jgroups to stop logging those warnings (they are harmless anyway). To do that, add this to your jgroups subsystem configuration: {code:xml} <stack name="udp"> <transport type="UDP"> <property name="log_discard_msgs property">false</property> </transport> </transport> {code} #2 is by far the simplest solution. > lots of warnings discarded message from different cluster > --------------------------------------------------------- > > Key: WFLY-4971 > URL: https://issues.jboss.org/browse/WFLY-4971 > Project: WildFly > Issue Type: Bug > Affects Versions: 9.0.0.Final > Reporter: Daniele Pirola > Assignee: Paul Ferraro > > I run the latest wildfly-9.0.0.Final. I have an environment with 2 host and 3 server per host. I noticed that there are a lot of warning like this > JGRP000012: discarded message from different cluster hq-cluster (our cluster is ee) > or this > JGRP000012: discarded message from different cluster ee (our cluster is hq-cluster) > With the same configuration in wildfly-8.2.0.Final I didn't noticed anything. > The strange thing is that warnings still appear even if I run only the domain controller with 1 server active. I think that the domain configuration (I used the default with full-ha profile) is missing something that can diffentiate jgroup channel but I don't know how -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 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 ASSIGNED > 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)

10 years, 8 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 ASSIGNED > 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)

10 years, 8 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 ASSIGNED > 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)

10 years, 8 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 November 2015