[JBoss JIRA] (WFLY-4414) Non Standard SESSIONID not clustered
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-4414?page=com.atlassian.jira.plugin.... ]
Paul Ferraro updated WFLY-4414:
-------------------------------
Issue Type: Bug (was: Feature Request)
> Non Standard SESSIONID not clustered
> ------------------------------------
>
> Key: WFLY-4414
> URL: https://issues.jboss.org/browse/WFLY-4414
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Reporter: Robert Smith
> Assignee: Paul Ferraro
>
> We are using Wildfly 8.1.0-Final in domain mode with mod-cluster.
> We use a non-standard session id in a web application as follows:
> ...
> <distributable />
> <session-config>
> <cookie-config>
> <name>VSOPSESSIONID</name>
> </cookie-config>
> </session-config>
> ...
> During testing of this we had our sticky set to JSESSIONID which caused requests to be forwarded to our 2 nodes alternatively.
> In our 1st request we do:
> request.getSession().setAttribute(KEY, value)
> In our 2nd request we do:
> request.getSession.getAttribute(KEY)
> The second request always returns null.
> When we remove the custom session id, the session data is avaliable.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (WFCORE-1111) Expose runtime methods in JMX for resources in domain servers
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1111?page=com.atlassian.jira.plugi... ]
Brian Stansberry reassigned WFCORE-1111:
----------------------------------------
Assignee: Jeff Mesnil (was: Kabir Khan)
> Expose runtime methods in JMX for resources in domain servers
> -------------------------------------------------------------
>
> Key: WFCORE-1111
> URL: https://issues.jboss.org/browse/WFCORE-1111
> Project: WildFly Core
> Issue Type: Feature Request
> Components: JMX
> Affects Versions: 2.0.0.Final
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Fix For: 3.0.0.Alpha1
>
>
> The JMX subsystem only exposes MBean operations for READ_ONLY management operations on domain servers.
> It should also be possible to expose RUNTIME_ONLY management operations as they only deal with the runtime and do not alter the management model.
> WFLY-5418 is an example of such operations.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (WFCORE-1111) Expose runtime methods in JMX for resources in domain servers
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1111?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1111:
-------------------------------------
Fix Version/s: 3.0.0.Alpha1
> Expose runtime methods in JMX for resources in domain servers
> -------------------------------------------------------------
>
> Key: WFCORE-1111
> URL: https://issues.jboss.org/browse/WFCORE-1111
> Project: WildFly Core
> Issue Type: Feature Request
> Components: JMX
> Affects Versions: 2.0.0.Final
> Reporter: Jeff Mesnil
> Assignee: Kabir Khan
> Fix For: 3.0.0.Alpha1
>
>
> The JMX subsystem only exposes MBean operations for READ_ONLY management operations on domain servers.
> It should also be possible to expose RUNTIME_ONLY management operations as they only deal with the runtime and do not alter the management model.
> WFLY-5418 is an example of such operations.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[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:
------------------------------------------------
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
> 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, 8 months
[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:
------------------------------------------------
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
> 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