db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5481) Unit tests fail on a derby closed iterator test with a "Invalid memory access of location"
Date Tue, 25 Oct 2011 13:44:32 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135061#comment-13135061

Bryan Pendleton commented on DERBY-5481:

Can you attach a stack trace? A derby.log? Anything that shows the Derby-related aspects
of the failure more precisely?

Assuming the problem is reproducible, a derby.log file from a run with the derby.language.logStatementText
property set to true would give us a lot more to go on.

> Unit tests fail on a derby closed iterator test with a "Invalid memory access of location"
> ------------------------------------------------------------------------------------------
>                 Key: DERBY-5481
>                 URL: https://issues.apache.org/jira/browse/DERBY-5481
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions:
>         Environment: Eclipse 3.7.0 on Mac OSX 10.7.2
>            Reporter: Gray Watson
>            Priority: Minor
> I'm the lead author of ORMLite, a smallish ORM project that supports Derby and some other
JDBC and Android databases.  I'm getting a reproducible memory fault during one of my Derby
tests.  I've just ignored the test for now in my code but I thought I'd report it.
> To check out the tree svn co http://ormlite.svn.sourceforge.net/svnroot/ormlite/ormliteTest/trunk
> You'll need maven. The DerbyEmbeddedBaseDaoImplTest is the one that fails.  Not by itself
unfortunately but running the com.j256.ormlite.dao package which is also testing some other
database types causes it to fail every time for me.  It's the testCloseInIterator() method
defined in the test base class JdbcBaseDaoImplTest.  This test closes the underlying database
connection in the middle of an iterator loop to test exception handling.
> Sorry if this is just too obscure to be useful.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message