August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBAS-3310) Remotely initiated sessions are not cleared from the JBoss Cache upon expiration

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3310?page=all ] Brian Stansberry closed JBAS-3310. ---------------------------------- Fix Version/s: JBossAS-4.0.5.CR1 Resolution: Done > Remotely initiated sessions are not cleared from the JBoss Cache upon expiration > -------------------------------------------------------------------------------- > > Key: JBAS-3310 > URL: http://jira.jboss.com/jira/browse/JBAS-3310 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service, Clustering > Affects Versions: JBossAS-4.0.4.GA > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Priority: Minor > Fix For: JBossAS-4.0.5.CR1, JBossAS-4.0.4.SP1 > > > Any http session that is in the JBoss Cache due to remote replication but which has not been accessed locally will not be cleared by the Tomcat background thread. -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBAS-3310) Remotely initiated sessions are not cleared from the JBoss Cache upon expiration

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3310?page=all ] Brian Stansberry reopened JBAS-3310: ------------------------------------ > Remotely initiated sessions are not cleared from the JBoss Cache upon expiration > -------------------------------------------------------------------------------- > > Key: JBAS-3310 > URL: http://jira.jboss.com/jira/browse/JBAS-3310 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service, Clustering > Affects Versions: JBossAS-4.0.4.GA > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Priority: Minor > Fix For: JBossAS-4.0.4.SP1 > > > Any http session that is in the JBoss Cache due to remote replication but which has not been accessed locally will not be cleared by the Tomcat background thread. -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-984) NPE when using JSTL fmt:message

by Peter Johnson (JIRA)

NPE when using JSTL fmt:message ------------------------------- Key: JBPORTAL-984 URL: http://jira.jboss.com/jira/browse/JBPORTAL-984 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.4 Final Environment: Windows XP, JBOss AS 4.0.4 GA, PostgreSQL 8.1 Reporter: Peter Johnson Fix For: 2.4 Final When using the standard tag, fmt:message, I get a null pointer excpetion in the standard tag library. The issue is that there are no headers in the HttpRequest object and when the standard tag library asks for the accept_language header, it does not expect to get a null back. There is further analysis and a proposed patch in the forum post. -- 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

19 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBRULES-394) NPE trying to add the same drl to a rulebase twice

by k s (JIRA)

NPE trying to add the same drl to a rulebase twice -------------------------------------------------- Key: JBRULES-394 URL: http://jira.jboss.com/jira/browse/JBRULES-394 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.0.3 Reporter: k s Assigned To: Mark Proctor Priority: Minor While doing some experimenting, I generated two almost identical DRLs out of almost identical decision tables. The only difference is in the ruleset/package name The DRLs are provided below. Then I tried to add the two DRLs as packages in the same rulebase. That was not really intentional, but that's another story!. Anyway, the attempt to add the second package resulted in a NPE at point where rule names are checked for equality. After playing around a bit, it seems that the root of the problem is that the rules in the two packages have the same names. ---------------------------------------------------------- Here's the relevant stack trace: ---------------------------------------------------------- java.lang.NullPointerException at org.drools.rule.Rule.equals(Rule.java:435) at org.drools.reteoo.TerminalNode.equals(TerminalNode.java:320) at java.util.ArrayList.indexOf(ArrayList.java:220) at java.util.ArrayList.contains(ArrayList.java:201) at org.drools.reteoo.TupleSource.addTupleSink(TupleSource.java:79) at org.drools.reteoo.TerminalNode.attach(TerminalNode.java:250) at org.drools.reteoo.ReteooBuilder.addRule(ReteooBuilder.java:195) at org.drools.reteoo.ReteooRuleBase.addRule(ReteooRuleBase.java:240) at org.drools.common.AbstractRuleBase.addPackage(AbstractRuleBase.java:255) ---------------------------------------------------------- Here are the first DRL: ---------------------------------------------------------- package Some_business_rules; #generated from Decision Table import org.drools.decisiontable.Cheese; import org.drools.decisiontable.Person; global java.util.List list; #From row number: 17 rule "Cheese fans_17" salience 65519 when Person(age == 42) Cheese(type=="stilton") then list.add("Old man stilton"); end #From row number: 18 rule "Cheese fans_18" salience 65518 when Person(age == 21) Cheese(type=="cheddar") then list.add("Young man cheddar"); end ---------------------------------------------------------- Here are the second DRL: ---------------------------------------------------------- Some_other_business_rules; #generated from Decision Table import org.drools.decisiontable.Cheese; import org.drools.decisiontable.Person; global java.util.List list; #From row number: 17 rule "Cheese fans_17" salience 65519 when Person(age == 42) Cheese(type=="stilton") then list.add("Old man stilton"); end #From row number: 18 rule "Cheese fans_18" salience 65518 when Person(age == 21) Cheese(type=="cheddar") then list.add("Young man cheddar"); end -- 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

19 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-393) Xml dump with illegal characters

by Javier Prieto (JIRA)

Xml dump with illegal characters -------------------------------- Key: JBRULES-393 URL: http://jira.jboss.com/jira/browse/JBRULES-393 Project: JBoss Rules Issue Type: Patch Security Level: Public (Everyone can see) Components: xml Affects Versions: 3.0.3 Environment: Eclipse 3.2 with Drools IDE plug-in 3.0.3 Reporter: Javier Prieto Assigned To: Mark Proctor Java operators contain illegal xml characters like '<', '>' and '&'. I've modified the XmlDumper.java to replace these illegal characters with their escaped equivalent (<, >, &amp), in order to fix the dump of blocks which contain java code. These are eval (java expressions), function body (java code) and rhs (java code). So, i've added 'replaceIllegalChars' method and i've modified 'visitFunctionDescr', 'visitEvalDescr' and 'processRules'. -- 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

19 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-421) Unnecessary Intern on String Literal in PackageBuilder

by Geoffrey Wiseman (JIRA)

Unnecessary Intern on String Literal in PackageBuilder ------------------------------------------------------ Key: JBRULES-421 URL: http://jira.jboss.com/jira/browse/JBRULES-421 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: All Affects Versions: 3.0.4 Reporter: Geoffrey Wiseman Assigned To: Mark Proctor Priority: Trivial Found this: if ( !"1.4".intern().equals( configuration.getJavaLanguageLevel() ) ) throw new RuntimeDroolsException( "Incompatible Java language level with selected compiler" ); Not sure why intern() is called on the string literal; literals are intern'd by default, and, besides, the code is using .equals(), so intern() is unnecessary. -- 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

19 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-383) some typos in the documentation

by KickMeToAndy (JIRA)

some typos in the documentation ------------------------------- Key: JBRULES-383 URL: http://jira.jboss.com/jira/browse/JBRULES-383 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 3.0.3 Environment: documentation that is currently online. Reporter: KickMeToAndy Assigned To: Mark Proctor Priority: Minor Hello all, i have just been evaluation jboss rules and encountered the following documentation typos : > > public Class Module { > > private String name; > > private String studentName; > > private int score; class has to be written with lowercase letter > > Example 3.9. Literal Cosntraints with Collections > > Example 3.10. Literal Cosntraints with Collections misspelled constraints > > 3.5.4.1.3. Literal Constraints > > ....can use hasing to improve.... misspelled hashing > > chapter following the figure 1.17 WorkingMemory > > ....it should eventually me garbage collected anyway.... be garbage collected ? > > 1.6.4.2. Assertion > > ....however, no rules are executedl you call "fireAllRules()" after.... are executed ? -- 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

19 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-390) Documentation for adding packages says its for removing packages

by gregorypierce (JIRA)

Documentation for adding packages says its for removing packages ---------------------------------------------------------------- Key: JBRULES-390 URL: http://jira.jboss.com/jira/browse/JBRULES-390 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 3.0.3 Reporter: gregorypierce Assigned To: Mark Proctor http://labs.jboss.com/file-access/default/members/jbossrules/freezone/doc... ruleBase.addPackage( "org.com.sample" ); // remove a package, and all its parts, by it's namespace This should be changed to ruleBase.addPackage( "org.com.sample" ); // add a package, and all its parts, by it's namespace -- 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

19 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-3500) Ensure ClusterPartition and ClusterTreeCache use the same JChannel

by Brian Stansberry (JIRA)

Ensure ClusterPartition and ClusterTreeCache use the same JChannel ------------------------------------------------------------------ Key: JBAS-3500 URL: http://jira.jboss.com/jira/browse/JBAS-3500 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Critical Fix For: JBossAS-5.0.0.Beta Services like DRM and DS that are made available through ClusterPartition/HAPartition use an independent JBC instance (ClusterTreeCache) to manage state. It is therefore imperative that the JBC instance and the ClusterPartition use the same underlying JChannel and that the JBC instance be running before the ClusterPartition starts. Logically this would imply that the ClusterPartition must depend on the JBC service and that it either 1) gets its multiplexer config from the JBC service or 2) confirms that it has the same config as the JBC service. This also means the ability to configure the JBC instance and the ClusterPartition to use independent JChannels must be removed. -- 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

19 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-3531) ClusterPartition and related services must share the same multiplexed JChannel

by Brian Stansberry (JIRA)

ClusterPartition and related services must share the same multiplexed JChannel ------------------------------------------------------------------------------ Key: JBAS-3531 URL: http://jira.jboss.com/jira/browse/JBAS-3531 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta ClusterPartition/HAPartition expose DistributedReplicantManager and DistributedState as part of their API. These 2 services use the "ClusterTreeCache" JBC instance to manage state. To allow consistent use of HAPartition and DRM/DS, they must be talking to the same underlying JChannel. To ensure this: 1) ClusterTreeCache will be injected into ClusterPartition. 2) ClusterPartiton will check that ClusterTreeCache is using the multiplexer. It will obtain it's multiplexer reference and stack name from ClusterTreeCache. 3) ClusterPartition will no longer support creation of a JChannel from a jgroups protocol stack config element. -- 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

19 years, 11 months

1
1
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 August 2006