openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pinaki Poddar (JIRA)" <>
Subject [jira] Commented: (OPENJPA-1001) java.lang.IndexOutOfBoundsException when executing attached test case
Date Fri, 03 Apr 2009 20:33:13 GMT


Pinaki Poddar commented on OPENJPA-1001:

> The results look identical to what I get when running on trunk which has Pinaki's version
of SQL caching. 
Does that imply the test passed with 'Pinaki's version of SQL caching'?

The test passed on trunk for me.

*If* this test is failing with previous SQLCaching (not pinaki's version of  SQL caching which
is better be referred as Prepared Query caching -- because that more accurately reflects what
it is) that brings up again the long-standing issue with QuerySQLCache. 

Though Prepared Query Cache has no resemblance to  QuerySQLCache in terms of its design and
its solution approach -- I still agreed to retain the same moniker to configure it because
I saw it as a replacement for a potentially risky (and costly) mistake that has entered our
released service stream. 

I am aware of the concerns/risks of backporting a rather large change such as Prepared Query
Cache  in a released service stream. But If Prepared Query Cache were not written by me, I
would have voiced my opinion more strongly to backport it as a replacement for existing QuerySQLCache.
The risk of regression with PQC changes are minimal both because of its design as well as
it has been operation/tested in one way or other in different scenarios. 

Effectively, In my view (which can be accused of bias in this case), the cost of retaining
existing QuerySQLCache in the service stream outweighs the risks of injecting PQC in the stream

> java.lang.IndexOutOfBoundsException when executing attached test case
> ---------------------------------------------------------------------
>                 Key: OPENJPA-1001
>                 URL:
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 1.2.1
>         Environment: Can reproduce on Max OS X and Linux
>            Reporter: Richard Rak
>         Attachments:,,,
> I am hitting the following exception when executing the given test case:
> Caused by: java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
> 	at java.util.ArrayList.RangeCheck(
> 	at java.util.ArrayList.get(
> 	at org.apache.openjpa.jdbc.sql.SQLBuffer.setParameters(
> 	at org.apache.openjpa.jdbc.sql.SQLBuffer.prepareStatement(
> 	at org.apache.openjpa.jdbc.sql.SQLBuffer.prepareStatement(
> 	at org.apache.openjpa.jdbc.sql.SelectImpl.prepareStatement(
> 	at org.apache.openjpa.jdbc.sql.SelectImpl.execute(
> 	at org.apache.openjpa.jdbc.sql.SelectImpl.execute(
> 	at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.getInitializeStateResult(
> 	at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.initializeState(
> 	at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.initialize(
> 	at org.apache.openjpa.kernel.DelegatingStoreManager.initialize(
> 	at org.apache.openjpa.kernel.ROPStoreManager.initialize(
> 	at org.apache.openjpa.kernel.BrokerImpl.initialize(
> 	at org.apache.openjpa.kernel.BrokerImpl.find(
> 	... 53 more
> <openjpa-1.2.1-rexported nonfatal general error> org.apache.openjpa.persistence.PersistenceException:
Index: 1, Size: 1
> 	at org.apache.openjpa.kernel.BrokerImpl.find(
> 	at org.apache.openjpa.kernel.BrokerImpl.find(
> 	at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.find(
> 	at org.apache.openjpa.jdbc.meta.strats.RelationFieldStrategy.load(
> 	at org.apache.openjpa.jdbc.meta.FieldMapping.load(
> 	at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.load(
> 	at org.apache.openjpa.kernel.DelegatingStoreManager.load(
> 	at org.apache.openjpa.kernel.ROPStoreManager.load(
> 	at org.apache.openjpa.kernel.StateManagerImpl.loadFields(
> 	at org.apache.openjpa.kernel.StateManagerImpl.loadField(
> 	at org.apache.openjpa.kernel.StateManagerImpl.fetchObjectField(
> 	at org.apache.openjpa.jdbc.meta.strats.RelationFieldStrategy.delete(
> 	at org.apache.openjpa.jdbc.meta.FieldMapping.delete(
> 	at org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.delete(
> 	at org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.delete(
> 	at org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.populateRowManager(
> 	at org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(
> 	at org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(
> 	at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(
> 	at org.apache.openjpa.kernel.DelegatingStoreManager.flush(
> 	at org.apache.openjpa.kernel.BrokerImpl.flush(
> 	at org.apache.openjpa.kernel.BrokerImpl.flushSafe(
> 	at org.apache.openjpa.kernel.BrokerImpl.flush(
> 	at org.apache.openjpa.kernel.QueryImpl.isInMemory(
> 	at org.apache.openjpa.kernel.QueryImpl.execute(
> 	at org.apache.openjpa.kernel.QueryImpl.deleteAll(
> 	at org.apache.openjpa.kernel.QueryImpl.deleteAll(
> 	at org.apache.openjpa.kernel.DelegatingQuery.deleteAll(
> 	at org.apache.openjpa.persistence.QueryImpl.executeUpdate(
> 	at org.apache.openjpa.persistence.test.PersistenceTestCase.clear(
> 	at org.apache.openjpa.persistence.test.PersistenceTestCase.clear(
> 	at org.apache.openjpa.persistence.test.SingleEMFTestCase.tearDown(
> 	at junit.framework.TestCase.runBare(
> ...

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message