[jboss-jira] [JBoss JIRA] Commented: (JBRULES-1013) Two functions with Janino compiler end up with out of memory error
Edson Tirelli (JIRA)
jira-events at lists.jboss.org
Mon Jul 30 15:02:50 EDT 2007
[ http://jira.jboss.com/jira/browse/JBRULES-1013?page=comments#action_12370468 ]
Edson Tirelli commented on JBRULES-1013:
----------------------------------------
I tested command line JANINO and it works fine as well as JCI-Eclipse, so this seems to be indeed a JCI-JANINO problem. Unfortunately, applying only the suggested changes seems to not solve the problem, so I opened a bug for JCI-JANINO:
https://issues.apache.org/jira/browse/JCI-53
> Two functions with Janino compiler end up with out of memory error
> ------------------------------------------------------------------
>
> Key: JBRULES-1013
> URL: http://jira.jboss.com/jira/browse/JBRULES-1013
> Project: JBoss Rules
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: Ubuntu Feisty, JDK 1.4 or 1.5, Drools Snapshot
> Reporter: Pierre Paysant-Le Roux
> Assigned To: Edson Tirelli
> Fix For: 4.0.1
>
>
> Compiling a simple rules file containing two functions with janino causes an out of memory error.
> Rules file example :
> package test
> function boolean func1() {
> return true;
> }
> function boolean func2() {
> return true;
> }
> rule "test"
> when
> Object()
> then
> System.out.println("fired");
> end
> and the code that generate the error :
> package test;
> import java.io.IOException;
> import java.io.InputStreamReader;
> import java.util.Properties;
> import org.drools.compiler.DroolsParserException;
> import org.drools.compiler.PackageBuilder;
> import org.drools.compiler.PackageBuilderConfiguration;
> public class Test {
> public static void main (String[] args) {
> Properties properties = new Properties();
> properties.setProperty("drools.dialect.java.compiler",
> "JANINO");
> PackageBuilderConfiguration pkgBuilderCfg = new PackageBuilderConfiguration(properties);
> PackageBuilder builder = new PackageBuilder(pkgBuilderCfg);
> try {
> builder.addPackageFromDrl(getSource());
> } catch (DroolsParserException e) {
> e.printStackTrace();
> } catch (IOException e) {
> e.printStackTrace();
> }
> }
>
> private static InputStreamReader getSource() {
> return new InputStreamReader(Test.class.getResourceAsStream( "Sample.drl" ));
> }
> }
> After profiling, I identified that the problematic line is the 146 one in class JaninoJavaCompiler. It causes the loadIClass method to loop with a cycle that I don't understand. Placing a breakpoint on the line 91 of JaninoJavaCompiler class permit to observe the loop iterations.
--
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
More information about the jboss-jira
mailing list