Bug 778097 (SOA-608)

Summary: drools: OutOfMemoryError when running org.drools.integrationtests.MultithreadTest on windows
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Jaroslaw Kijanowski <kijanowski>
Component: JBoss RulesAssignee: Mark Proctor <mark.proctor>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.2 CP02   
Target Milestone: ---   
Target Release: 4.3 GA   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-608
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-10-28 08:30:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jaroslaw Kijanowski 2008-06-24 21:06:57 UTC
Date of First Response: 2008-06-29 19:43:25
project_key: SOA

This happens only on windows:
http://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-rules-os-jdk15/label=Win2k3_x86/54/console
Still looking into it to make sure it's not a config issue

Comment 1 Jaroslaw Kijanowski 2008-06-24 21:11:42 UTC
This happens when running the drools testsuite from http://anonsvn.labs.jboss.com/labs/jbossrules/tags/DROOLS_SOA_4_2_19937_CP2 against the JBoss Rules SOA-P bits

Comment 2 Jaroslaw Kijanowski 2008-06-25 14:01:29 UTC
I've run the testsuite against its own bits, not these from SOA-P
http://hudson.qa.jboss.com/hudson/view/drools/job/drools-SOA_4_2-win/2
-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.drools.compiler.DrlParserTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.063 sec
Running org.drools.integrationtests.MultithreadTest
Exception in thread "Thread-39" Exception in thread "Thread-40" Exception in thread "Thread-11" Exception in thread "Thread-36" Exception in thread "Thread-2" java.lang.OutOfMemoryError: Java heap spacejava.lang.OutOfMemoryError: Java heap space
==>[ActivationCreated(0): rule=Auto Retract; tuple=[fid:1:1:[Person name='bobba fet']]
]
==>[ActivationCreated(3): rule=Auto Retract; tuple=[fid:2:2:[Person name='bobba fet']]
.
.
.
[BeforeActivationFired(96472): rule=Auto Retract; tuple=[fid:2:48236:[Person name='bobba fet']]
]
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 162.754 sec
[AfterActivationFired(96472): rule=Auto Retract; tuple=[fid:-1:48236:null]
]
==>[ActivationCreated(96474): rule=Auto Retract; tuple=[fid:2:48237:[Person name='bobba fet']]
.
.
.
==>[ActivationCreated(96476): rule=Auto Retract; tuple=[fid:2:48238:[Person name='bobba fet']]
]
[BeforeActivationFired(96476): rule=Auto Retract; tuple=[fid:2:48238:[Person name='bobba fet']]
Running org.drools.compiler.CompilerPerfProfileTest
]
[AfterActivationFired(96476): rule=Auto Retract; tuple=[fid:-1:48238:null]
]
.
.
.

Moreover this test throws an OOME but it's reported as passed, however this looks like an maven issue because it's reported as failed when running with ant:
http://hudson.qa.jboss.com/hudson/view/drools/job/drools-SOA_4_2-win/2/testReport/org.drools.integrationtests/MultithreadTest/

Comment 3 Len DiMaggio 2008-06-29 23:43:25 UTC
Just heard from Mark Proctor - he recalls the problem as being known and intermittent, maybe a GC issue, and is not planning action until it becomes a customer issue.

Workaround = increase XmX and XmS and it should be OK



Comment 4 Mark Little 2008-07-02 11:05:14 UTC
If that is the case then can you close this issue and create a docs issue for Josh to include it in the release notes? Thanks.