[JBoss JIRA] (JBRULES-3583) Retracting an event with an explicit expiration results in memory leak
by Ladd Asper (JIRA)
Ladd Asper created JBRULES-3583:
-----------------------------------
Summary: Retracting an event with an explicit expiration results in memory leak
Key: JBRULES-3583
URL: https://issues.jboss.org/browse/JBRULES-3583
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.4.0.Final
Environment: Windows 7, Java 1.6
Reporter: Ladd Asper
Assignee: Mark Proctor
package drools.tests
import drools.tests.MyEvent
import java.util.List
declare MyEvent @role(event) @expires(14d) end // <====== leaks
//declare MyEvent @role(event) end // <====== doesn't leak
rule "UpdateAndRetractOldEvents"
salience 10000
when
$old : MyEvent( $key : key )
MyEvent( key == $key, this after $old )
then
retract( $old );
System.err.println( "retracted $old" );
end
My test case is a loop that does this:
MyEvent firstA = new MyEvent( "first", "firstA" ); // key, value
MyEvent firstB = new MyEvent( "first", "firstB" ); // key, value
...
ksession.insert( firstA );
ksession.fireAllRules();
Thread.sleep( 50 );
ksession.insert( firstB );
ksession.fireAllRules();
Memory consumption stays flat if MyEvent is declared without an expiration time. Memory consumption increases linearly if MyEvent is declared with an expiration time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (JBRULES-3527) NullPointerException when marshalling InsertObjectCmd with XStream without setting entry point
by Chang Li (JIRA)
Chang Li created JBRULES-3527:
---------------------------------
Summary: NullPointerException when marshalling InsertObjectCmd with XStream without setting entry point
Key: JBRULES-3527
URL: https://issues.jboss.org/browse/JBRULES-3527
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.4.0.Final
Environment: Windows
Reporter: Chang Li
Assignee: Mark Proctor
The following code result in NullPointerException in the last step
ArrayList<Command> commands = new ArrayList<Command>();
BatchExecutionCommand batchCmd = CommandFactory.newBatchExecution(commands, "ksession1");
MyObject myobj = new MyObject("name of object"); // just an example, not important to the bug.
Command command = CommandFactory.newInsert(myobj, "myobject");
commands.add(command);
XStream marshaller = BatchExecutionHelper.newXStreamMarshaller();
String xml = marshaller.toXML(batchCmd);
The null pointer exception is caused by the "entry point" parameter not being set on teh InesrtObjectCommand.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (JBRULES-3310) drools-camel osgi bundle
by surya aditya (Created) (JIRA)
drools-camel osgi bundle
------------------------
Key: JBRULES-3310
URL: https://issues.jboss.org/browse/JBRULES-3310
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-camel
Affects Versions: 5.3.0.Final
Environment: window, linux
Reporter: surya aditya
Assignee: Mark Proctor
Priority: Minor
Fix For: 5.3.1.Final
drools-camel is not osgi compatible i.e not an osgi bundle yet. can this be enhanced in next releases to be osgi ready? many of the apache camel components fits very well in osgi environment and drools-camel is missing this functionality. it would help if upgraded to osgi bundle like drools-core etc.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (JBRULES-3520) CamelServerApp.class missing, camel-client.xml wrong for Drools and jBPM integration camel server war on Tomcat
by Ryley Gahagan (JIRA)
Ryley Gahagan created JBRULES-3520:
--------------------------------------
Summary: CamelServerApp.class missing, camel-client.xml wrong for Drools and jBPM integration camel server war on Tomcat
Key: JBRULES-3520
URL: https://issues.jboss.org/browse/JBRULES-3520
Project: Drools
Issue Type: Release
Security Level: Public (Everyone can see)
Components: drools-camel
Affects Versions: 5.4.0.Final, 5.4.0.CR1
Environment: Tomcat 6.x
Reporter: Ryley Gahagan
Assignee: Mark Proctor
Priority: Minor
Fix For: 5.4.0.Final, 5.4.0.CR1
The CamelServerApp.class file is missing from the war. Also, the camel-client.xml has, as default:
<to uri="cxfrs://http://localhost:8080/drools-server/kservice/rest"/>
<to uri="cxfrs://http://localhost:8080/drools-server/kservice/soap"/>
Which Tomcat deploys out of the box as
<to uri="cxfrs://http://localhost:8080/drools-camel-server-5.4.0.Final/kservice/rest"/>
<to uri="cxfrs://http://localhost:8080/drools-camel-server-5.4.0.Final/kservice/soap"/>
(...5.4.0.CR1 for that dist)
Has existed for awhile, apparently.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (JBRULES-3574) Split package org.drools.rule.builder.dialect.asm in org.drools.core and org.drools.compiler causes OSGi problems
by Tillmann Seidel (JIRA)
Tillmann Seidel created JBRULES-3574:
----------------------------------------
Summary: Split package org.drools.rule.builder.dialect.asm in org.drools.core and org.drools.compiler causes OSGi problems
Key: JBRULES-3574
URL: https://issues.jboss.org/browse/JBRULES-3574
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler, drools-core
Affects Versions: 5.4.0.Final
Reporter: Tillmann Seidel
Assignee: Mark Proctor
The package {{org.drools.rule.builder.dialect.asm}} has been split between the OSGi bundles {{org.drools.core}} and {{org.drools.compiler}}. This leads to class loader problems when used in an OSGi environment:
{code}
java.lang.IllegalAccessError: tried to access method org.drools.rule.builder.dialect.asm.GeneratorHelper.createInvokerClassGenerator(Ljava/lang/String;Lorg/drools/rule/builder/dialect/asm/InvokerDataProvider;Lorg/drools/util/CompositeClassLoader;Lorg/drools/base/TypeResolver;)Lorg/drools/rule/builder/dialect/asm/ClassGenerator; from class org.drools.rule.builder.dialect.asm.InvokerGenerator
{code}
Ideally split packages should not be used at all. If they cannot be avoided, they should be declared as such in the OSGi manifest.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month