db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepa Remesh (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-956) OutOfMemoryError: Java heap space in stress.multi
Date Fri, 10 Mar 2006 23:08:50 GMT
    [ http://issues.apache.org/jira/browse/DERBY-956?page=comments#action_12369940 ] 

Deepa Remesh commented on DERBY-956:

Thanks Andrew for verifying. I have also verified this test passes with the patch (in an environment
where it fails without the patch).

I have not figured out from where the OutOfMemoryError comes from. Here is what I found so
far. Before this patch, when stress.multi gets run as part of encryption suite, the encryption
attributes were not getting added to the database URL. This was because mtTestCase.java looks
for "database" property whereas I had changed the properties file to use "ij.database" instead.
This was a routine thing I was doing to enable tests for j2me and never imagined it had this
side-effect for the multi test till Mike tracked it down. 

So, the connect to the database fails and the output of running the sql files would be something
like this:

ERROR 08001: No suitable driver
ij version 10.2
ij> drop function PADSTRING;
IJ ERROR: Unable to establish connection

The tester threads were not doing anything in this situation because they fail to get a connection
itself. So we were not testing anything here. Now, it is more confuing how we can get an OutOfMemoryError
in such situation. As Andrew suggested, I'll open a jira issue to track what is causing the
memory error.

> OutOfMemoryError: Java heap space in stress.multi
> -------------------------------------------------
>          Key: DERBY-956
>          URL: http://issues.apache.org/jira/browse/DERBY-956
>      Project: Derby
>         Type: Bug
>   Components: Regression Test Failure
>     Versions:
>  Environment: Red Hat Enterprise Linux AS release 3 (Taroon Update 4) - Linux 2.4.21-27.ELsmp
#1 SMP Wed Dec 1 21:50:31 EST 2004 GNU/Linux, JVM: Sun Microsystems Inc. 1.5.0_03
> Solaris 10 3/05 s10_74L2a X86 - SunOS 5.10 Generic, JVM: Sun Microsystems Inc. 1.5.0_04
> Solaris 10 3/05 s10_74L2a SPARC - SunOS 5.10 Generic, JVM: Sun Microsystems Inc. 1.5.0_03
> Solaris 9 9/04 s9s_u7wos_09 SPARC - SunOS 5.9 Generic_118558-11, JVM: Sun Microsystems
Inc. 1.5.0_03
>     Reporter: Ole Solberg
>     Assignee: Deepa Remesh
>     Priority: Blocker
>  Attachments: 370061.zip, 377554.zip, derby-956-draft1.diff
> Diff: 
> *** Start: stress jdk1.5.0_03 encryption:multi 2006-02-09 23:37:11 ***
> 3a4
> > Exception in thread "Thread-1" java.lang.OutOfMemoryError: Java heap space
> 6 del
> < TEST CASE SUMMARY: normal termination
> 7 del
> < ...running last checks via final.sql
> 7 add
> > TEST CASE SUMMARY: abnormal termination due to error(s) -- see test log (./stress/stress.log)
for details 
> Test Failed.
> *** End:   stress jdk1.5.0_03 encryption:multi 2006-02-09 23:41:28 ***
> First seen in
> http://www.multinet.no/~solberg/public/Apache/TinderBox_Derby/testlog/SunOS-5.10_i86pc-i386/370061-encryption_diff.txt

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message