[JBoss JIRA] Created: (JBMESSAGING-686) Inconsistence between DelegateSupport and States
by Clebert Suconic (JIRA)
Inconsistence between DelegateSupport and States
------------------------------------------------
Key: JBMESSAGING-686
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-686
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.2.0.Beta1
Reporter: Clebert Suconic
Assigned To: Clebert Suconic
Priority: Blocker
Fix For: 1.2.0.Beta1
I have marked this issue as blocker as we can't release without this, but the fix is simple.
All the states are currently replace delegates what is causing inconsistence on relationship between States and delegates.
HATest::testTopicSubscriber is failing because part of the delegates are from the old node, and the delegates on the states are the ones coming from the new node. This is causing issues with transactionIDs and other weird stuff when playing with transactions.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 9 months
[JBoss JIRA] Created: (JBAS-3947) JConsole throws exception on connect post JBoss4.0.3SP1
by Weston Price (JIRA)
JConsole throws exception on connect post JBoss4.0.3SP1
-------------------------------------------------------
Key: JBAS-3947
URL: http://jira.jboss.com/jira/browse/JBAS-3947
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.5.CR1, JBossAS-4.0.4.GA, JBossAS-4.0.4.CR2
Reporter: Weston Price
In JBoss 4.0.3SP1 JBoss allowed connecting via the JConsole utiltiy provided with the JDK. As of JBoss 4.0.5 this no longer works on startup and requires user action to complete effectively. I have posted a stack trace to this issue. It appears that the java.lang:type=Runtime MBean is no longer being registered at startup which causes the connection to fail when it cannot locate this MBean.
I tested this in the following configurations:
JBoss 4.0.3SP1 (successful)
JBoss 4.0.5GA (fails)
JBoss 4.2CR1 (fails)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 9 months
[JBoss JIRA] Created: (JBRULES-591) Rule stops firing when more than 2 rules are added to the same package
by Edson Tirelli (JIRA)
Rule stops firing when more than 2 rules are added to the same package
----------------------------------------------------------------------
Key: JBRULES-591
URL: http://jira.jboss.com/jira/browse/JBRULES-591
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Reteoo
Affects Versions: 3.1-m1
Reporter: Edson Tirelli
Assigned To: Edson Tirelli
Fix For: 3.1-m1
[12:37] <mic_hat> tirelli: Good DRL, just a single rule, it works as expected, very simple:
package org.acme.insurance;
rule "Pricing bracket_18"
when
Driver(age >= 25, age <= 30, priorClaims == "0")
policy: Policy(type == "COMPREHENSIVE")
then
policy.setBasePrice(120);
System.out.println("Cheapest possible");
end
[12:38] <mic_hat> tirelli: this contains that same rule, but it fails to fire:
#From row number: 18
rule "Pricing bracket_18"
when
Driver(age >= 25, age <= 30, priorClaims == "0")
policy: Policy(type == "COMPREHENSIVE")
then
policy.setBasePrice(120);
System.out.println("Cheapest possible");
end
#From row number: 19
rule "Pricing bracket_19"
when
Driver(age >= 25, age <= 30, priorClaims == "1")
policy: Policy(type == "COMPREHENSIVE")
then
policy.setBasePrice(300);
end
#From row number: 20
rule "Pricing bracket_20"
when
Driver(age >= 25, age <= 30, priorClaims == "2")
policy: Policy(type == "COMPREHENSIVE")
then
policy.setBasePrice(590);
end
[12:38] <mic_hat> otherwise all identical
[12:39] <mic_hat> it was fine in 3.0.5
[12:39] <mic_hat> but not in trunk
[12:39] <mic_hat> yep, just confirmed again, any ideas why the other rules are causing it to break?
[12:42] <mic_hat> FYI its in PricingRuleLauncher in drools-decisiontables
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 9 months