November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-5552) Synchronized deployment repositories across the cluster

by Brian Stansberry (JIRA)

Synchronized deployment repositories across the cluster ------------------------------------------------------- Key: JBAS-5552 URL: http://jira.jboss.com/jira/browse/JBAS-5552 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering, ProfileService Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR2 Basic ability to keep deployment repository content in sync across a cluster. -- 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

15 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1855) Serialization of working memories for rulebases with Accumulates are failing

by Edson Tirelli (JIRA)

Serialization of working memories for rulebases with Accumulates are failing ---------------------------------------------------------------------------- Key: JBRULES-1855 URL: https://jira.jboss.org/jira/browse/JBRULES-1855 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.0.0.M2 Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.0.0.M3 Serialization of working memories with rules like this are failing: rule "Test sum" salience 80 dialect "java" when $sum : Number( doubleValue >= 10 ) from accumulate( Person( $likes : likes ) and Cheese( type == $likes, $price : price ), sum( $price ) ); then results.add( $sum ); end -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-1792) Start node triggers

by Kris Verlaenen (JIRA)

Start node triggers ------------------- Key: JBRULES-1792 URL: https://jira.jboss.org/jira/browse/JBRULES-1792 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core (flow) Reporter: Kris Verlaenen Assignee: Kris Verlaenen Fix For: 5.0.0.M3 Start nodes can be automatically triggered, e.g. when rules are activated or when an event is signalled. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-3834) i18n of jmx-console

by Ryusuke Kajiyama (JIRA)

i18n of jmx-console ------------------- Key: JBAS-3834 URL: http://jira.jboss.com/jira/browse/JBAS-3834 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.0.4.GA Environment: Any operating system with multiple language such as MS932 (Japanese) Reporter: Ryusuke Kajiyama We found that there are difference in screen-displayed multibyte characters on using Internet Explorer and Firefox. When using MS932, with IE, characters are returned same as posted, however with Firefox, characters are url-escaped like %xx. Our guess is that html of jmx-console does not have charset and there are no functions to handle encoding request parameter. It could be fixed if there were some filter action something like distinguish character set of posted data, and add <meta> tag into html or set Content-Type. -- 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

15 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1815) DoPropfind servlet ignores property attributes due to bad refactoring

by Cezary Dendek (JIRA)

DoPropfind servlet ignores property attributes due to bad refactoring --------------------------------------------------------------------- Key: JBRULES-1815 URL: https://jira.jboss.org/jira/browse/JBRULES-1815 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-guvnor Affects Versions: 5.0.0.M2, 5.0.0.M3, FUTURE Reporter: Cezary Dendek Assignee: Mark Proctor Method execute(HttpServletRequest req, HttpServletResponse resp) calls method getPropertyNodeAndType() expecting it to change values of parameters (which is incorrect): int propertyFindType = FIND_ALL_PROP; Node propNode = null; getPropertyNodeAndType(propNode, propertyFindType, req); // propNode is here expected to be set as well as propertyFindType. This is not correct, this is very not correct. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBRULES-1738) Support XAResource transactions and generic save points

by Mark Proctor (JIRA)

Support XAResource transactions and generic save points ------------------------------------------------------- Key: JBRULES-1738 URL: https://jira.jboss.org/jira/browse/JBRULES-1738 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assignee: Mark Proctor Fix For: 5.0.0.M2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1759) Exception when compiling a rule with "dialect mvel"

by Ming Jin (JIRA)

Exception when compiling a rule with "dialect mvel" --------------------------------------------------- Key: JBRULES-1759 URL: https://jira.jboss.org/jira/browse/JBRULES-1759 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 5.0.0.M1 Reporter: Ming Jin Assignee: Mark Proctor Attachments: testdrools.zip The following expression would compile without any problem with "dialect java": new String[][]{{"2008-04-01", "2008-04-10"}} But would generate a compiler error - "Unable to build expression...." with "dialect mvel". Will upload an sample code to demonstrate this bug. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-1876) Deadlock when RuleAgent thread refreshes rules while another thread creates a statefulSession

by Shahad Ahmed (JIRA)

Deadlock when RuleAgent thread refreshes rules while another thread creates a statefulSession --------------------------------------------------------------------------------------------- Key: JBRULES-1876 URL: https://jira.jboss.org/jira/browse/JBRULES-1876 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 4.0.7 Environment: Windows XP SP3 Sun JRE 1.5.0_14 Reporter: Shahad Ahmed Assignee: Mark Proctor I believe I have discovered a deadlock that can occur in drools 4.0.7 if the RuleAgent refreshes its associated RuleBase whilst a new stateful session is being created on the RuleBase by another thread. The thread dump below shows the deadlock where the two thread "Timer-15" and "DataSource(com.acme.Source)-2" are deadlocked. Thread "Timer-15" is the timer thread created by the RuleAgent rule refresh mechanism to check if the rules files have changed, and to refresh the rules when a change is found. If it finds changes to the rules then it obtains a lock (<0x189a8d88> (a java.util.HashMap)) and proceeds to removes the old version of the changed package from the RuleBase. To do this it needs to obtain another lock (<0x189a2ba0> (a org.drools.reteoo.ReteooRuleBase)) before it can call removeRule. However, in another thread "DataSource(com.acme.Source)-2" a new stateful session is being created on the same RuleBase. This has already obtained the lock (<0x189a8d88> (a java.util.HashMap)) that the Timer thread is waiting for, and is itself waiting for the another lock <0x189a2ba0> (a org.drools.reteoo.ReteooRuleBase) that the Timer thread has already locked, hence the deadlock. In my own application I coded around this by eventually not using the RuleAgent in-built refresh mechanism, but instead periodically calling refreshRuleBase() on the RuleAgent in the SAME thread used to create the Stateful session, thus avoiding any deadlock. "Timer-15" daemon prio=6 tid=0x02f4b0e8 nid=0x1864 waiting for monitor entry [0x038cf000..0x038cfa68] at org.drools.reteoo.ReteooRuleBase.removeRule(ReteooRuleBase.java:270) - waiting to lock <0x189a2ba0> (a org.drools.reteoo.ReteooRuleBase) at org.drools.common.AbstractRuleBase.removeRule(AbstractRuleBase.java:656) at org.drools.common.AbstractRuleBase.removePackage(AbstractRuleBase.java:570) - locked <0x189a8d88> (a java.util.HashMap) at org.drools.agent.PackageProvider.removePackage(PackageProvider.java:45) at org.drools.agent.PackageProvider.applyChanges(PackageProvider.java:63) at org.drools.agent.RuleAgent.refreshRuleBase(RuleAgent.java:320) at org.drools.agent.RuleAgent$2.run(RuleAgent.java:438) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source) "DataSource(com.acme.Source)-2" daemon prio=4 tid=0x03027610 nid=0xfac waiting for monitor entry [0x0378f000..0x0378fb68] at org.drools.reteoo.ReteooRuleBase.newStatefulSession(ReteooRuleBase.java:225) - waiting to lock <0x189a8d88> (a java.util.HashMap) - locked <0x189a2ba0> (a org.drools.reteoo.ReteooRuleBase) at org.drools.common.AbstractRuleBase.newStatefulSession(AbstractRuleBase.java:284) at com.acme.RunRules.flush(RunRules.java:3337) at com.acme.ControlThread.run(ControlThread.java:465) at java.lang.Thread.run(Unknown Source) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

4
6
0 / 0

[JBoss JIRA] Created: (JBRULES-1629) Different versions of JAR files in Drools distributives and Drools Maven repository.

by Yuriy Drozhdzhal' (JIRA)

Different versions of JAR files in Drools distributives and Drools Maven repository. ------------------------------------------------------------------------------------ Key: JBRULES-1629 URL: http://jira.jboss.com/jira/browse/JBRULES-1629 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.7, 4.0.6, 4.0.5, 4.0.4 Environment: Windows XP SP2, JDK 1.5.0_15, Apache Tomcat 6.0.16, BRMS 4.0.7 Reporter: Yuriy Drozhdzhal' Assigned To: Mark Proctor There are different versions of drools-core-xxx.jar in Drools binaries and Drools Maven repository. -- 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

15 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1701) add unique directive for drl

by zhou yanming (JIRA)

add unique directive for drl ---------------------------- Key: JBRULES-1701 URL: https://jira.jboss.org/jira/browse/JBRULES-1701 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder Reporter: zhou yanming Assignee: Mark Proctor when Number(A:value); Number(B:value); Number(C:value); Number(D:value); unique(A,B,C,D); equals to when Number(A:value); Number(B:value); Number(C:value); eval(A!=B and A!=C and A!=D and B!=C and B!=D and C!=D ); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2008