March 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1944) Adding crontab type functionality for repetitive rules.

by Griz frf (JIRA)

Adding crontab type functionality for repetitive rules. ------------------------------------------------------- Key: JBRULES-1944 URL: https://jira.jboss.org/jira/browse/JBRULES-1944 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-api Affects Versions: FUTURE Reporter: Griz frf Assignee: Mark Proctor A convinient helper function to schedule rule executions in a similar manner to the cron utility would be useful. My specific use case is for a long running session to periodically write out data to a persistence store (db, file, etc) The current code for this is as follows : rule "DBpoll" duration(30s) when $d:String(toString=="Run") then System.out.println("30seconds elapsed"); Database.dosomething(); modify($d){}; end -------------------------------- session.insert(new String("Run")); --------------------------------- While this method does work, it requires the external dummy object trigger. In dynamically generated rules and rules pulled in from libraries, etc (not under the current developers control) it is difficult to ensure that a suibtable trigger is available. Therefore a cron like function would solve this issue. I envision the EVERY keyword and possibly a COUNT or for loop style format rule "DBpoll" EVERY(30s, 100) <-- means every 30 seconds for 100 iterations. or EVERY(30s, 10m) <-- every 30 seconds for 10 mins then System.out.println("30seconds elapsed"); Database.dosomething(); 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

16 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2431) Typo on Drools Fusion website

by Bruce Mitchener (JIRA)

Typo on Drools Fusion website ----------------------------- Key: JBRULES-2431 URL: https://jira.jboss.org/jira/browse/JBRULES-2431 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Bruce Mitchener Assignee: Mark Proctor http://www.jboss.org/drools/drools-fusion.html In the TOC, the 2nd entry reads: What is Event Processin (or Complex Event Processing, CEP)? But should read: What is Event Processing (or Complex Event Processing, CEP)? Just a small typo... -- 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

16 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1804) Logical insertion lingers after the rule that inserted it no longer supports it (with testcase patch)

by Geoffrey De Smet (JIRA)

Logical insertion lingers after the rule that inserted it no longer supports it (with testcase patch) ----------------------------------------------------------------------------------------------------- Key: JBRULES-1804 URL: https://jira.jboss.org/jira/browse/JBRULES-1804 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert) Affects Versions: 5.0.0.M2 Reporter: Geoffrey De Smet Assignee: Edson Tirelli Priority: Critical Fix For: 5.0.0.M3 This one got me headscratching for a while, untill I realized what the problem is. Tim reported on the mailing list he ran into it to. I've commmited a testcase in subversion, in TruthMaintenanceTest, called disabled_testLogicalInsertionsModifySameRuleGivesDifferentLogicalInsertion Remove the "disabled_" to enable it and try it out. Here's what happens in the testcase: 3 sensors with tempature 100, 200 and 200 are inserted. There's a rule which logically inserts all encountered tempatures, so 100 and 200. Then the first sensor modifies to a tempature of 150. As it turns out, the encoutered tempatures should be 150 and 200 now, but instead it's 100, 150 and 200. Even though there is no sensor that has a tempature of 100. -- 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

16 years, 3 months

4
17
0 / 0

[JBoss JIRA] Created: (SECURITY-490) JBossAuthorizationManager-<JBossAuthorizationContext.authorize call has an unnecessary lock

by Anil Saldhana (JIRA)

JBossAuthorizationManager-<JBossAuthorizationContext.authorize call has an unnecessary lock ------------------------------------------------------------------------------------------- Key: SECURITY-490 URL: https://jira.jboss.org/jira/browse/SECURITY-490 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: PicketBox_v3_0_beta4, JBossSecurity_2.0.4.SP3 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: JBossSecurity_2.0.4.SP4, PicketBox_v3_0_beta5 Thanks to Marcus Moyses for detecting this. -- 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

16 years, 3 months

1
7
0 / 0

[JBoss JIRA] Created: (JGRP-1180) OutOfMemoryError

by Peter Kormos (JIRA)

OutOfMemoryError ---------------- Key: JGRP-1180 URL: https://jira.jboss.org/jira/browse/JGRP-1180 Project: JGroups Issue Type: Bug Affects Versions: 2.8 Environment: 2.8.0.GA Reporter: Peter Kormos Assignee: Bela Ban Hi Guys, I wrote a simple program. public testbed() throws Exception { JChannel channel = new JChannel(); channel.connect("channelName"); for (int i = 0; i < 100000000; i++) { Message msg = new Message( null, null, "Test"); channel.send(msg); // Thread.sleep(10); if (i % 1000 == 0) System.out.print("."); } } When I run it with java -Xmx8m -XX:+HeapDumpOnOutOfMemoryError -cp .;jgroups-all.jar testbed not always, but quite often it dies with OutOfMemoryError When I look at the heap dump with jhat, for "Instance Counts" it tells me 22036 instances of class org.jgroups.Message 22036 instances of class org.jgroups.protocols.pbcast.NakAckHeader 22036 instances of class org.jgroups.util.Headers 21316 instances of class org.jgroups.Event 21314 instances of class org.jgroups.util.Queue$Element 304 instances of class org.jgroups.util.UUID Why are there so many message objects stuck in memory? java org.jgroups.Version prints Version: 2.8.0.GA CVS: $Id: Version.java,v 1.81 2009/12/01 10:31:13 belaban Exp $ I'm using Windows Xp with 1.6 JDK -- 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

16 years, 3 months

2
7
0 / 0

[JBoss JIRA] Created: (JBAS-4383) Allow a different JSF implementation to be packaged in the WAR

by Stan Silvert (JIRA)

Allow a different JSF implementation to be packaged in the WAR -------------------------------------------------------------- Key: JBAS-4383 URL: http://jira.jboss.com/jira/browse/JBAS-4383 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JavaServerFaces Affects Versions: JBossAS-4.2.0.CR2, JBossAS-5.0.0.Beta2 Reporter: Stan Silvert Assigned To: Stan Silvert Fix For: JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta3, JBossAS-5.0.0.GA Prior to JEE5, most developers would bundle a JSF implementation such as MyFaces with the WAR. With AS 4.2 and 5.0, you should instead rely on the JSF implementation that ships with the container. However, for these legacy applications that rely on a particular implementation, we can disable the built-in JSF implementation as long as you stick with the default classloader settings. To disable the built-in JSF, you will add this to your web.xml: <context-param> <param-name>org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL</param-name> <param-value>true</param-value> </context-param> -- 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

16 years, 3 months

4
9
0 / 0

[JBoss JIRA] Created: (JBAOP-784) NullPointerException in Dispatcher when doing toString

by Carlo de Wolf (JIRA)

NullPointerException in Dispatcher when doing toString ------------------------------------------------------ Key: JBAOP-784 URL: https://jira.jboss.org/jira/browse/JBAOP-784 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.1.9.Alpha1 Reporter: Carlo de Wolf java.lang.NullPointerException at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:117) at org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invoke(IsLocalProxyFactoryInterceptor.java:97) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62) at $Proxy123.toString(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

16 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAOP-771) Avoid transformation of classes that are already loaded but are not woven

by Flavia Rainone (JIRA)

Avoid transformation of classes that are already loaded but are not woven ------------------------------------------------------------------------- Key: JBAOP-771 URL: https://jira.jboss.org/jira/browse/JBAOP-771 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.1.9.Alpha1 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: 2.1.9.GA This could bring some optimization, by avoiding useless work. -- 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

16 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (GPD-302) Generate Form Dialog is NOT auto-populated with controller variables or named transitions

by Nobody Cares (JIRA)

Generate Form Dialog is NOT auto-populated with controller variables or named transitions ----------------------------------------------------------------------------------------- Key: GPD-302 URL: https://jira.jboss.org/jira/browse/GPD-302 Project: JBoss jBPM GPD Issue Type: Bug Affects Versions: jBPM jPDL Designer 3.1.6 Environment: Eclipse 3.1.4 w/ packaged jBPM GPD (assuming 3.1.6) Reporter: Nobody Cares Assignee: Koen Aers Priority: Minor The launched dialog of a task's "Generate Form..." button is NOT automatically populated with the task's defined controller variables nor with buttons that correspond to the task's named transitions. This issue significantly hinders the usefulness of the GPD. -- 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

16 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAOP-776) jboss-50-install-jboss.xml does not install jboss-aop-deployers.jar

by Flavia Rainone (JIRA)

jboss-50-install-jboss.xml does not install jboss-aop-deployers.jar ------------------------------------------------------------------- Key: JBAOP-776 URL: https://jira.jboss.org/jira/browse/JBAOP-776 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.1.9.Alpha1 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: 2.1.9.GA The jboss-aop-deployers.jar should be copied into the as lib directory during installation. -- 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

16 years, 3 months

1
3
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 March 2010