[
https://issues.apache.org/jira/browse/DERBY-5481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gray Watson updated DERBY-5481:
-------------------------------
Description:
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.
was:
I'm the lead author of ORMLite, a smallish ORM project that supports JDBC and
Android databases. I'm getting a reproducible memory fault during a derby
test. 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
https://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.
> 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: 10.8.1.2
> 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
