November 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1973) FRAG2: message corruption when thread pools are disabled

by Bela Ban (JIRA)

Bela Ban created JGRP-1973: ------------------------------ Summary: FRAG2: message corruption when thread pools are disabled Key: JGRP-1973 URL: https://issues.jboss.org/browse/JGRP-1973 Project: JGroups Issue Type: Bug Affects Versions: 3.6.6 Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.6.7 When disabling the thread pools (regular, OOB) and using {{UDP}}, fragments of a message get corrupted as a single buffer ({{UDP.receive_buf}}) is reused. * If we send a message of 1000 bytes, and {{FRAG2.frag_size}} is set to 600, then {{FRAG2}} sends 2 fragments: f1 (offset=0, length=600) and f2 (offset=600, length=400). * f1 is received and placed into {{receive_buf}}, then sent up the stack *without copying* as the {{DirectExecutor}} thread pool doesn't copy the data * f1 is received by {{FRAG2}} and added to the fragments list at index 0. The buffer of the message points to {{receive_buf}} * f2 is received and *overwrites* f1 in {{receive_buf}} ! * f2 is received by {{FRAG2}} and added to the fragments list at index 1. The buffer of the message points to {{receive_buf}} * {{FRAG2}} now creates a new message whose buffer is {{receive_buf}}[0-600] and {{receive_buf}}[600-1000]. * The problem here is that {{receive_buf}} contains only f2, which overwrote f1, so the resulting message will be incorrect ! This probably affects {{FRAG}}, too. Not too critical, as thread pools are enabled by default, and disabling them might even be removed in the future. SOLUTION: -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-784) LdapExtLoginModule cannot find custom ldap socket factory

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-784?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-784: -------------------------------------------------- Ondrej Lukas <olukas(a)redhat.com> changed the Status of [bug 1052644|https://bugzilla.redhat.com/show_bug.cgi?id=1052644] from ON_QA to VERIFIED > LdapExtLoginModule cannot find custom ldap socket factory > --------------------------------------------------------- > > Key: SECURITY-784 > URL: https://issues.jboss.org/browse/SECURITY-784 > Project: PicketBox > Issue Type: Feature Request > Components: PicketBox > Affects Versions: PicketBox_4_0_19.Final > Reporter: Derek Horton > Assignee: Pedro Igor > Attachments: SECURITY-784.patch > > > LdapExtLoginModule cannot find custom ldap socket factory. > Passing the "java.naming.ldap.factory.socket" property in as an > module-option: > <module-option name="java.naming.ldap.factory.socket" value="org.jboss.example.CustomSocketFactory"/> > results in a ClassNotFoundException: > Caused by: javax.naming.CommunicationException: 192.168.1.8:389 [Root exception is java.lang.ClassNotFoundException: org/jboss/example/CustomSocketFactory] > at com.sun.jndi.ldap.Connection.<init>(Connection.java:226) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:136) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1608) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2698) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:316) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:193) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:211) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:154) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:84) [rt.jar:1.7.0_45] > at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684) [rt.jar:1.7.0_45] > at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307) [rt.jar:1.7.0_45] > at javax.naming.InitialContext.init(InitialContext.java:242) [rt.jar:1.7.0_45] > at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:153) [rt.jar:1.7.0_45] > at org.jboss.security.auth.spi.LdapExtLoginModule.constructInitialLdapContext(LdapExtLoginModule.java:767) [picketbox-4.0.17.SP2-redhat-2.jar:4.0.17.SP2-redhat-2] > I tried making the custom socket factory into a jboss module and adding the module as a dependency to picketbox and > sun.jdk. Unfortunately, that did not work. I also added the socket > factory jar to the jre/lib/ext directory. That didn't work either. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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: ------------------------------------------------ Ryan Zhang <rzhang(a)redhat.com> changed the Status of [bug 1273087|https://bugzilla.redhat.com/show_bug.cgi?id=1273087] from MODIFIED to ON_QA > 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, 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: ------------------------------------------------ Ryan Zhang <rzhang(a)redhat.com> changed the Status of [bug 1273087|https://bugzilla.redhat.com/show_bug.cgi?id=1273087] from MODIFIED to ON_QA > 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, 6 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: ------------------------------------------------ Ryan Zhang <rzhang(a)redhat.com> changed the Status of [bug 1273087|https://bugzilla.redhat.com/show_bug.cgi?id=1273087] from MODIFIED to ON_QA > 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, 6 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: ------------------------------------------------ Ryan Zhang <rzhang(a)redhat.com> changed the Status of [bug 1273087|https://bugzilla.redhat.com/show_bug.cgi?id=1273087] from MODIFIED to ON_QA > 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, 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: ------------------------------------------------ Ryan Zhang <rzhang(a)redhat.com> changed the Status of [bug 1273087|https://bugzilla.redhat.com/show_bug.cgi?id=1273087] from MODIFIED to ON_QA > 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, 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: ------------------------------------------------ Ryan Zhang <rzhang(a)redhat.com> changed the Status of [bug 1273087|https://bugzilla.redhat.com/show_bug.cgi?id=1273087] from MODIFIED to ON_QA > 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)

10 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: ------------------------------------------------ Ryan Zhang <rzhang(a)redhat.com> changed the Status of [bug 1273087|https://bugzilla.redhat.com/show_bug.cgi?id=1273087] from MODIFIED to ON_QA > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5536) Recovery manager is not able to recover MDB and shows warnings on each run.

by Andy Taylor (JIRA)

[ https://issues.jboss.org/browse/WFLY-5536?page=com.atlassian.jira.plugin.... ] Andy Taylor commented on WFLY-5536: ----------------------------------- [~jmesnil] your fix is fine, there was another issue related to https://issues.apache.org/jira/browse/ARTEMIS-292 which ive fixed and the test works. > Recovery manager is not able to recover MDB and shows warnings on each run. > --------------------------------------------------------------------------- > > Key: WFLY-5536 > URL: https://issues.jboss.org/browse/WFLY-5536 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.CR2 > Reporter: Hayk Hovsepyan > Assignee: Jeff Mesnil > Priority: Blocker > Attachments: MDB_JMS_XA.log, TEST-org.jboss.as.test.jbossts.crashrec.test.JMSMdbCrashRecoveryTestCase-jta.xml > > > Recovery manager is not able to recover MDB and shows warnings. > This causes to see the same warning log in server each time recovery is run. > This happens when server is crashed before transaction state is saved. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 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