kodo.jdo.DataStoreException: Missing IN or OUT parameter at index:: 2 {prepstmnt 28821120 INSERT INTO BUYING.ITEMI18N (ID, SHORTTEXT, TEXT1, TEXT2, TSUPDATE, ID_ITEM, ID_LOCALE) VALUES (? , ?, ?, ?, ?, ?, ?) [params=(long) 4226013, null, null, null, (Timestamp) 2008-01-31 10:28:58.421, (long) 1932894, (long ) 1] [reused=1]} [code=17041, state=null] FailedObject: com.ottogroup.buying.sharedkernel.item.ItemI18N@5ac5f

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 666705, 1 year ago
Missing IN or OUT parameter at index:: 2 {prepstmnt 28821120 INSERT INTO BUYING.ITEMI18N (ID, SHORTTEXT, TEXT1, TEXT2, TSUPDATE, ID_ITEM, ID_LOCALE) VALUES (? , ?, ?, ?, ?, ?, ?) [params=(long) 4226013, null, null, null, (Timestamp) 2008-01-31 10:28
kodo.jdo.DataStoreException: Missing IN or OUT parameter at index:: 2 {prepstmnt 28821120 INSERT INTO BUYING.ITEMI18N (ID, SHORTTEXT, TEXT1, TEXT2, TSUPDATE, ID_ITEM, ID_LOCALE) VALUES (? , ?, ?, ?, ?, ?, ?) [params=(long) 4226013, null, null, null, (Timestamp) 2008-01-31 10:28:58.421, (long) 1932894, (long ) 1] [reused=1]} [code=17041, state=null] FailedObject: com.ottogroup.buying.sharedkernel.item.ItemI18N@5ac5f
at org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:3784)
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:97)
at kodo.jdbc.kernel.BatchingPreparedStatementManager.flushInternal(BatchingPreparedStatementManager.java:214)
at kodo.jdbc.kernel.BatchingPreparedStatementManager.flushInternal(BatchingPreparedStatementManager.java:149)
at kodo.jdbc.kernel.BatchingPreparedStatementManager.flush(BatchingPreparedStatementManager.java:72)
at kodo.jdbc.kernel.ConstraintUpdateManager.flushGraph(ConstraintUpdateManager.java:366)
at kodo.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:59)
at org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:89)
at org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:72)
at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:514)
at org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130)
at org.apache.openjpa.datacache.DataCacheStoreManager.flush(DataCacheStoreManager.java:509)
at org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130)
at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:1973)
at org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1871)
at org.apache.openjpa.kernel.BrokerImpl.beforeCompletion(BrokerImpl.java:1789)
at org.apache.openjpa.kernel.LocalManagedRuntime.commit(LocalManagedRuntime.java:80)
at kodo.kernel.KodoBroker.commit(KodoBroker.java:103)
at kodo.jdo.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:394)

Users with the same issue

You are the first who have seen this exception.

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.