You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@openjpa.apache.org by Daniel Persson <ma...@gmail.com> on 2012/07/10 17:00:57 UTC

Thread writing.

Hi OpenJPA users.

I have a problem with one of our entities that we write in a callable
thread that could be called multiple times simultaneously.

We have an ThreadPoolExecutor that runs multiple versions of an object
implements Callable.
In some of these objects an entity is fetched and merged.

We seperate each thread using ThreadLocal so each thread has there own
entityManager and it uses it during the thread execution.
private static transient ThreadLocal<Hashtable<String, EntityManager>>
entityManagers = new ThreadLocal<Hashtable<String, EntityManager>>();

No entities is sent between threads.

The error we get frequently:

Caused by: <openjpa-2.2.1-SNAPSHOT-r422266:1352927M fatal store error>
org.apache.openjpa.persistence.EntityExistsException: Duplicate entry
'472307' for key 1 {prepstmnt 37611 INSERT INTO table(col1, col2,
col3, col4) VALUES (?, ?, ?, ?)} [code=1062, state=23000]
FailedObject: path.to.table@3725f1
        at org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4926)
        at org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4901)
        at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
        at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:78)
        at org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:143)
        at org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushInternal(PreparedStatementManagerImpl.java:99)
        at org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flush(PreparedStatementManagerImpl.java:87)
        at org.apache.openjpa.jdbc.kernel.OperationOrderUpdateManager.flushPrimaryRow(OperationOrderUpdateManager.java:203)
        at org.apache.openjpa.jdbc.kernel.OperationOrderUpdateManager.flush(OperationOrderUpdateManager.java:89)
        at org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:105)
        at org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:78)
        at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:738)
        at org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:131)
        at org.apache.openjpa.datacache.DataCacheStoreManager.flush(DataCacheStoreManager.java:661)
        at org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:131)
        ... 19 more
Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException:
Duplicate entry '472307' for key 1 {prepstmnt 37611 INSERT INTO
table(col1, col2, col3, col4) VALUES (?, ?, ?, ?)} [code=1062,
state=23000]
        at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:219)
        at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:195)
        at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$1000(LoggingConnectionDecorator.java:59)
        at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeUpdate(LoggingConnectionDecorator.java:1134)
        at org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:272)
        at org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeUpdate(JDBCStoreManager.java:1768)
        at org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.executeUpdate(PreparedStatementManagerImpl.java:267)
        at org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:118)
        ... 29 more

Our persistance configuration using an non-jta-data-source and tomcat
datasource pooling.

<property name="openjpa.ConnectionDriverName" value="com.mysql.jdbc.Driver" />
<property name="openjpa.ConnectionProperties"
value="autoReconnect=false,connectTimeout=5,socketTimeout=5" />
<property name="openjpa.jdbc.DBDictionary"
value="mysql(SupportsSubselect=true,UseClobs=true)"/>
<property name="openjpa.jdbc.UpdateManager" value="operation-order"/>
<property name="openjpa.DataCache" value="true(CacheSize=1000,
SoftReferenceSize=0, EnableStatistics=true)"/>
<property name="openjpa.QueryCache" value="true(CacheSize=200,
SoftReferenceSize=0, EvictPolicy='timestamp')"/>
<property name="openjpa.Log" value="File=/tmp/openjpa.log,
DefaultLevel=WARN, Runtime=WARN, Tool=WARN, SQL=WARN"/>
<property name="openjpa.DetachState"
value="fetch-groups(DetachedStateField=true)"/>
<property name="openjpa.FetchBatchSize" value="0"/>
<property name="openjpa.InverseManager" value="true"/>		

Any suggestions how to proceed?
My guess is that one thread writes an entity before the another thread
and the EntityManager entity state isn't updated before the next
merge.

Best regards

Daniel

RE: Thread writing.

Posted by William Brown <wi...@ericsson.com>.
 
	As the other poster suggested, I think your problem is related to multiple entity managers
	using the same primary key value. How are you generating your primary keys?

-----Original Message-----
From: Daniel Persson [mailto:mailto.woden@gmail.com] 
Sent: Tuesday, July 10, 2012 1:20 PM
To: users@openjpa.apache.org
Subject: Re: Thread writing.

Yes, thats what I'm experience. I want the last update though. Thinking about implementing it inside transactions to isolate the writing.
On Jul 10, 2012 6:31 PM, "Rick Curtis" <cu...@gmail.com> wrote:

> Is this your scenario?
>
> T1: Find id=1, returns null
> T2: Find id=1, returns null
>
> T1: merge(id=1)
> T2: merge(id=1)
>
> T1: tran commit
> T2: tran commit, EntityExistsException
>
> If so, it sounds like you need to add some exception handling?
>
>
> On Tue, Jul 10, 2012 at 11:04 AM, Daniel Persson 
> <mailto.woden@gmail.com
> >wrote:
>
> > Correct but I'm merging entities. And if the find returns null I'll
> create
> > an new entity.
> > On Jul 10, 2012 5:11 PM, "Rick Curtis" <cu...@gmail.com> wrote:
> >
> > > > I have a problem with one of our entities that we write in a 
> > > > callable
> > > thread that could be called multiple times simultaneously.
> > > If I'm reading this correctly, you're trying to persist an Entity 
> > > with
> > the
> > > same ID multiple times simultaneously? If that is the case, this
> > exception
> > > is expected.
> > >
> > > On Tue, Jul 10, 2012 at 10:00 AM, Daniel Persson <
> mailto.woden@gmail.com
> > > >wrote:
> > >
> > > > Hi OpenJPA users.
> > > >
> > > > I have a problem with one of our entities that we write in a 
> > > > callable thread that could be called multiple times simultaneously.
> > > >
> > > > We have an ThreadPoolExecutor that runs multiple versions of an
> object
> > > > implements Callable.
> > > > In some of these objects an entity is fetched and merged.
> > > >
> > > > We seperate each thread using ThreadLocal so each thread has 
> > > > there
> own
> > > > entityManager and it uses it during the thread execution.
> > > > private static transient ThreadLocal<Hashtable<String,
> EntityManager>>
> > > > entityManagers = new ThreadLocal<Hashtable<String, 
> > > > EntityManager>>();
> > > >
> > > > No entities is sent between threads.
> > > >
> > > > The error we get frequently:
> > > >
> > > > Caused by: <openjpa-2.2.1-SNAPSHOT-r422266:1352927M fatal store
> error>
> > > > org.apache.openjpa.persistence.EntityExistsException: Duplicate 
> > > > entry '472307' for key 1 {prepstmnt 37611 INSERT INTO 
> > > > table(col1, col2, col3, col4) VALUES (?, ?, ?, ?)} [code=1062, 
> > > > state=23000]
> > > > FailedObject: path.to.table@3725f1
> > > >         at
> > > >
> org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4926
> )
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionar
> y.java:4901)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:
> 136)
> > > >         at
> > > >
> > org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.jav
> > a:78)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUp
> date(PreparedStatementManagerImpl.java:143)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushInter
> nal(PreparedStatementManagerImpl.java:99)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flush(Prep
> aredStatementManagerImpl.java:87)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.jdbc.kernel.OperationOrderUpdateManager.flushPrimar
> yRow(OperationOrderUpdateManager.java:203)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.jdbc.kernel.OperationOrderUpdateManager.flush(Opera
> tionOrderUpdateManager.java:89)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpd
> ateManager.java:105)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpd
> ateManager.java:78)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager
> .java:738)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStore
> Manager.java:131)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.datacache.DataCacheStoreManager.flush(DataCacheStor
> eManager.java:661)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStore
> Manager.java:131)
> > > >         ... 19 more
> > > > Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException:
> > > > Duplicate entry '472307' for key 1 {prepstmnt 37611 INSERT INTO 
> > > > table(col1, col2, col3, col4) VALUES (?, ?, ?, ?)} [code=1062, 
> > > > state=23000]
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingCon
> nectionDecorator.java:219)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingCon
> nectionDecorator.java:195)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$1000(Log
> gingConnectionDecorator.java:59)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnecti
> on$LoggingPreparedStatement.executeUpdate(LoggingConnectionDecorator.j
> ava:1134)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(
> DelegatingPreparedStatement.java:272)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatemen
> t.executeUpdate(JDBCStoreManager.java:1768)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.executeUpd
> ate(PreparedStatementManagerImpl.java:267)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUp
> date(PreparedStatementManagerImpl.java:118)
> > > >         ... 29 more
> > > >
> > > > Our persistance configuration using an non-jta-data-source and 
> > > > tomcat datasource pooling.
> > > >
> > > > <property name="openjpa.ConnectionDriverName"
> > > > value="com.mysql.jdbc.Driver" /> <property 
> > > > name="openjpa.ConnectionProperties"
> > > > value="autoReconnect=false,connectTimeout=5,socketTimeout=5" /> 
> > > > <property name="openjpa.jdbc.DBDictionary"
> > > > value="mysql(SupportsSubselect=true,UseClobs=true)"/>
> > > > <property name="openjpa.jdbc.UpdateManager" 
> > > > value="operation-order"/> <property name="openjpa.DataCache" 
> > > > value="true(CacheSize=1000, SoftReferenceSize=0, 
> > > > EnableStatistics=true)"/> <property name="openjpa.QueryCache" 
> > > > value="true(CacheSize=200, SoftReferenceSize=0, 
> > > > EvictPolicy='timestamp')"/> <property name="openjpa.Log" 
> > > > value="File=/tmp/openjpa.log, DefaultLevel=WARN, Runtime=WARN, 
> > > > Tool=WARN, SQL=WARN"/> <property name="openjpa.DetachState"
> > > > value="fetch-groups(DetachedStateField=true)"/>
> > > > <property name="openjpa.FetchBatchSize" value="0"/> <property 
> > > > name="openjpa.InverseManager" value="true"/>
> > > >
> > > > Any suggestions how to proceed?
> > > > My guess is that one thread writes an entity before the another
> thread
> > > > and the EntityManager entity state isn't updated before the next 
> > > > merge.
> > > >
> > > > Best regards
> > > >
> > > > Daniel
> > > >
> > >
> > >
> > >
> > > --
> > > *Rick Curtis*
> > >
> >
>
>
>
> --
> *Rick Curtis*
>

Re: Thread writing.

Posted by Daniel Persson <ma...@gmail.com>.
Yes, thats what I'm experience. I want the last update though. Thinking
about implementing it inside transactions to isolate the writing.
On Jul 10, 2012 6:31 PM, "Rick Curtis" <cu...@gmail.com> wrote:

> Is this your scenario?
>
> T1: Find id=1, returns null
> T2: Find id=1, returns null
>
> T1: merge(id=1)
> T2: merge(id=1)
>
> T1: tran commit
> T2: tran commit, EntityExistsException
>
> If so, it sounds like you need to add some exception handling?
>
>
> On Tue, Jul 10, 2012 at 11:04 AM, Daniel Persson <mailto.woden@gmail.com
> >wrote:
>
> > Correct but I'm merging entities. And if the find returns null I'll
> create
> > an new entity.
> > On Jul 10, 2012 5:11 PM, "Rick Curtis" <cu...@gmail.com> wrote:
> >
> > > > I have a problem with one of our entities that we write in a callable
> > > thread that could be called multiple times simultaneously.
> > > If I'm reading this correctly, you're trying to persist an Entity with
> > the
> > > same ID multiple times simultaneously? If that is the case, this
> > exception
> > > is expected.
> > >
> > > On Tue, Jul 10, 2012 at 10:00 AM, Daniel Persson <
> mailto.woden@gmail.com
> > > >wrote:
> > >
> > > > Hi OpenJPA users.
> > > >
> > > > I have a problem with one of our entities that we write in a callable
> > > > thread that could be called multiple times simultaneously.
> > > >
> > > > We have an ThreadPoolExecutor that runs multiple versions of an
> object
> > > > implements Callable.
> > > > In some of these objects an entity is fetched and merged.
> > > >
> > > > We seperate each thread using ThreadLocal so each thread has there
> own
> > > > entityManager and it uses it during the thread execution.
> > > > private static transient ThreadLocal<Hashtable<String,
> EntityManager>>
> > > > entityManagers = new ThreadLocal<Hashtable<String, EntityManager>>();
> > > >
> > > > No entities is sent between threads.
> > > >
> > > > The error we get frequently:
> > > >
> > > > Caused by: <openjpa-2.2.1-SNAPSHOT-r422266:1352927M fatal store
> error>
> > > > org.apache.openjpa.persistence.EntityExistsException: Duplicate entry
> > > > '472307' for key 1 {prepstmnt 37611 INSERT INTO table(col1, col2,
> > > > col3, col4) VALUES (?, ?, ?, ?)} [code=1062, state=23000]
> > > > FailedObject: path.to.table@3725f1
> > > >         at
> > > >
> org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4926)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4901)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
> > > >         at
> > > >
> > org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:78)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:143)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushInternal(PreparedStatementManagerImpl.java:99)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flush(PreparedStatementManagerImpl.java:87)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.jdbc.kernel.OperationOrderUpdateManager.flushPrimaryRow(OperationOrderUpdateManager.java:203)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.jdbc.kernel.OperationOrderUpdateManager.flush(OperationOrderUpdateManager.java:89)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:105)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:78)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:738)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:131)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.datacache.DataCacheStoreManager.flush(DataCacheStoreManager.java:661)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:131)
> > > >         ... 19 more
> > > > Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException:
> > > > Duplicate entry '472307' for key 1 {prepstmnt 37611 INSERT INTO
> > > > table(col1, col2, col3, col4) VALUES (?, ?, ?, ?)} [code=1062,
> > > > state=23000]
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:219)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:195)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$1000(LoggingConnectionDecorator.java:59)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeUpdate(LoggingConnectionDecorator.java:1134)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:272)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeUpdate(JDBCStoreManager.java:1768)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.executeUpdate(PreparedStatementManagerImpl.java:267)
> > > >         at
> > > >
> > >
> >
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:118)
> > > >         ... 29 more
> > > >
> > > > Our persistance configuration using an non-jta-data-source and tomcat
> > > > datasource pooling.
> > > >
> > > > <property name="openjpa.ConnectionDriverName"
> > > > value="com.mysql.jdbc.Driver" />
> > > > <property name="openjpa.ConnectionProperties"
> > > > value="autoReconnect=false,connectTimeout=5,socketTimeout=5" />
> > > > <property name="openjpa.jdbc.DBDictionary"
> > > > value="mysql(SupportsSubselect=true,UseClobs=true)"/>
> > > > <property name="openjpa.jdbc.UpdateManager" value="operation-order"/>
> > > > <property name="openjpa.DataCache" value="true(CacheSize=1000,
> > > > SoftReferenceSize=0, EnableStatistics=true)"/>
> > > > <property name="openjpa.QueryCache" value="true(CacheSize=200,
> > > > SoftReferenceSize=0, EvictPolicy='timestamp')"/>
> > > > <property name="openjpa.Log" value="File=/tmp/openjpa.log,
> > > > DefaultLevel=WARN, Runtime=WARN, Tool=WARN, SQL=WARN"/>
> > > > <property name="openjpa.DetachState"
> > > > value="fetch-groups(DetachedStateField=true)"/>
> > > > <property name="openjpa.FetchBatchSize" value="0"/>
> > > > <property name="openjpa.InverseManager" value="true"/>
> > > >
> > > > Any suggestions how to proceed?
> > > > My guess is that one thread writes an entity before the another
> thread
> > > > and the EntityManager entity state isn't updated before the next
> > > > merge.
> > > >
> > > > Best regards
> > > >
> > > > Daniel
> > > >
> > >
> > >
> > >
> > > --
> > > *Rick Curtis*
> > >
> >
>
>
>
> --
> *Rick Curtis*
>

Re: Thread writing.

Posted by Rick Curtis <cu...@gmail.com>.
Is this your scenario?

T1: Find id=1, returns null
T2: Find id=1, returns null

T1: merge(id=1)
T2: merge(id=1)

T1: tran commit
T2: tran commit, EntityExistsException

If so, it sounds like you need to add some exception handling?


On Tue, Jul 10, 2012 at 11:04 AM, Daniel Persson <ma...@gmail.com>wrote:

> Correct but I'm merging entities. And if the find returns null I'll create
> an new entity.
> On Jul 10, 2012 5:11 PM, "Rick Curtis" <cu...@gmail.com> wrote:
>
> > > I have a problem with one of our entities that we write in a callable
> > thread that could be called multiple times simultaneously.
> > If I'm reading this correctly, you're trying to persist an Entity with
> the
> > same ID multiple times simultaneously? If that is the case, this
> exception
> > is expected.
> >
> > On Tue, Jul 10, 2012 at 10:00 AM, Daniel Persson <mailto.woden@gmail.com
> > >wrote:
> >
> > > Hi OpenJPA users.
> > >
> > > I have a problem with one of our entities that we write in a callable
> > > thread that could be called multiple times simultaneously.
> > >
> > > We have an ThreadPoolExecutor that runs multiple versions of an object
> > > implements Callable.
> > > In some of these objects an entity is fetched and merged.
> > >
> > > We seperate each thread using ThreadLocal so each thread has there own
> > > entityManager and it uses it during the thread execution.
> > > private static transient ThreadLocal<Hashtable<String, EntityManager>>
> > > entityManagers = new ThreadLocal<Hashtable<String, EntityManager>>();
> > >
> > > No entities is sent between threads.
> > >
> > > The error we get frequently:
> > >
> > > Caused by: <openjpa-2.2.1-SNAPSHOT-r422266:1352927M fatal store error>
> > > org.apache.openjpa.persistence.EntityExistsException: Duplicate entry
> > > '472307' for key 1 {prepstmnt 37611 INSERT INTO table(col1, col2,
> > > col3, col4) VALUES (?, ?, ?, ?)} [code=1062, state=23000]
> > > FailedObject: path.to.table@3725f1
> > >         at
> > > org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4926)
> > >         at
> > >
> >
> org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4901)
> > >         at
> > >
> >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
> > >         at
> > >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:78)
> > >         at
> > >
> >
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:143)
> > >         at
> > >
> >
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushInternal(PreparedStatementManagerImpl.java:99)
> > >         at
> > >
> >
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flush(PreparedStatementManagerImpl.java:87)
> > >         at
> > >
> >
> org.apache.openjpa.jdbc.kernel.OperationOrderUpdateManager.flushPrimaryRow(OperationOrderUpdateManager.java:203)
> > >         at
> > >
> >
> org.apache.openjpa.jdbc.kernel.OperationOrderUpdateManager.flush(OperationOrderUpdateManager.java:89)
> > >         at
> > >
> >
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:105)
> > >         at
> > >
> >
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:78)
> > >         at
> > >
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:738)
> > >         at
> > >
> >
> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:131)
> > >         at
> > >
> >
> org.apache.openjpa.datacache.DataCacheStoreManager.flush(DataCacheStoreManager.java:661)
> > >         at
> > >
> >
> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:131)
> > >         ... 19 more
> > > Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException:
> > > Duplicate entry '472307' for key 1 {prepstmnt 37611 INSERT INTO
> > > table(col1, col2, col3, col4) VALUES (?, ?, ?, ?)} [code=1062,
> > > state=23000]
> > >         at
> > >
> >
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:219)
> > >         at
> > >
> >
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:195)
> > >         at
> > >
> >
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$1000(LoggingConnectionDecorator.java:59)
> > >         at
> > >
> >
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeUpdate(LoggingConnectionDecorator.java:1134)
> > >         at
> > >
> >
> org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:272)
> > >         at
> > >
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeUpdate(JDBCStoreManager.java:1768)
> > >         at
> > >
> >
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.executeUpdate(PreparedStatementManagerImpl.java:267)
> > >         at
> > >
> >
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:118)
> > >         ... 29 more
> > >
> > > Our persistance configuration using an non-jta-data-source and tomcat
> > > datasource pooling.
> > >
> > > <property name="openjpa.ConnectionDriverName"
> > > value="com.mysql.jdbc.Driver" />
> > > <property name="openjpa.ConnectionProperties"
> > > value="autoReconnect=false,connectTimeout=5,socketTimeout=5" />
> > > <property name="openjpa.jdbc.DBDictionary"
> > > value="mysql(SupportsSubselect=true,UseClobs=true)"/>
> > > <property name="openjpa.jdbc.UpdateManager" value="operation-order"/>
> > > <property name="openjpa.DataCache" value="true(CacheSize=1000,
> > > SoftReferenceSize=0, EnableStatistics=true)"/>
> > > <property name="openjpa.QueryCache" value="true(CacheSize=200,
> > > SoftReferenceSize=0, EvictPolicy='timestamp')"/>
> > > <property name="openjpa.Log" value="File=/tmp/openjpa.log,
> > > DefaultLevel=WARN, Runtime=WARN, Tool=WARN, SQL=WARN"/>
> > > <property name="openjpa.DetachState"
> > > value="fetch-groups(DetachedStateField=true)"/>
> > > <property name="openjpa.FetchBatchSize" value="0"/>
> > > <property name="openjpa.InverseManager" value="true"/>
> > >
> > > Any suggestions how to proceed?
> > > My guess is that one thread writes an entity before the another thread
> > > and the EntityManager entity state isn't updated before the next
> > > merge.
> > >
> > > Best regards
> > >
> > > Daniel
> > >
> >
> >
> >
> > --
> > *Rick Curtis*
> >
>



-- 
*Rick Curtis*

Re: Thread writing.

Posted by Daniel Persson <ma...@gmail.com>.
Correct but I'm merging entities. And if the find returns null I'll create
an new entity.
On Jul 10, 2012 5:11 PM, "Rick Curtis" <cu...@gmail.com> wrote:

> > I have a problem with one of our entities that we write in a callable
> thread that could be called multiple times simultaneously.
> If I'm reading this correctly, you're trying to persist an Entity with the
> same ID multiple times simultaneously? If that is the case, this exception
> is expected.
>
> On Tue, Jul 10, 2012 at 10:00 AM, Daniel Persson <mailto.woden@gmail.com
> >wrote:
>
> > Hi OpenJPA users.
> >
> > I have a problem with one of our entities that we write in a callable
> > thread that could be called multiple times simultaneously.
> >
> > We have an ThreadPoolExecutor that runs multiple versions of an object
> > implements Callable.
> > In some of these objects an entity is fetched and merged.
> >
> > We seperate each thread using ThreadLocal so each thread has there own
> > entityManager and it uses it during the thread execution.
> > private static transient ThreadLocal<Hashtable<String, EntityManager>>
> > entityManagers = new ThreadLocal<Hashtable<String, EntityManager>>();
> >
> > No entities is sent between threads.
> >
> > The error we get frequently:
> >
> > Caused by: <openjpa-2.2.1-SNAPSHOT-r422266:1352927M fatal store error>
> > org.apache.openjpa.persistence.EntityExistsException: Duplicate entry
> > '472307' for key 1 {prepstmnt 37611 INSERT INTO table(col1, col2,
> > col3, col4) VALUES (?, ?, ?, ?)} [code=1062, state=23000]
> > FailedObject: path.to.table@3725f1
> >         at
> > org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4926)
> >         at
> >
> org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4901)
> >         at
> >
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
> >         at
> > org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:78)
> >         at
> >
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:143)
> >         at
> >
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushInternal(PreparedStatementManagerImpl.java:99)
> >         at
> >
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flush(PreparedStatementManagerImpl.java:87)
> >         at
> >
> org.apache.openjpa.jdbc.kernel.OperationOrderUpdateManager.flushPrimaryRow(OperationOrderUpdateManager.java:203)
> >         at
> >
> org.apache.openjpa.jdbc.kernel.OperationOrderUpdateManager.flush(OperationOrderUpdateManager.java:89)
> >         at
> >
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:105)
> >         at
> >
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:78)
> >         at
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:738)
> >         at
> >
> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:131)
> >         at
> >
> org.apache.openjpa.datacache.DataCacheStoreManager.flush(DataCacheStoreManager.java:661)
> >         at
> >
> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:131)
> >         ... 19 more
> > Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException:
> > Duplicate entry '472307' for key 1 {prepstmnt 37611 INSERT INTO
> > table(col1, col2, col3, col4) VALUES (?, ?, ?, ?)} [code=1062,
> > state=23000]
> >         at
> >
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:219)
> >         at
> >
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:195)
> >         at
> >
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$1000(LoggingConnectionDecorator.java:59)
> >         at
> >
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeUpdate(LoggingConnectionDecorator.java:1134)
> >         at
> >
> org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:272)
> >         at
> >
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeUpdate(JDBCStoreManager.java:1768)
> >         at
> >
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.executeUpdate(PreparedStatementManagerImpl.java:267)
> >         at
> >
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:118)
> >         ... 29 more
> >
> > Our persistance configuration using an non-jta-data-source and tomcat
> > datasource pooling.
> >
> > <property name="openjpa.ConnectionDriverName"
> > value="com.mysql.jdbc.Driver" />
> > <property name="openjpa.ConnectionProperties"
> > value="autoReconnect=false,connectTimeout=5,socketTimeout=5" />
> > <property name="openjpa.jdbc.DBDictionary"
> > value="mysql(SupportsSubselect=true,UseClobs=true)"/>
> > <property name="openjpa.jdbc.UpdateManager" value="operation-order"/>
> > <property name="openjpa.DataCache" value="true(CacheSize=1000,
> > SoftReferenceSize=0, EnableStatistics=true)"/>
> > <property name="openjpa.QueryCache" value="true(CacheSize=200,
> > SoftReferenceSize=0, EvictPolicy='timestamp')"/>
> > <property name="openjpa.Log" value="File=/tmp/openjpa.log,
> > DefaultLevel=WARN, Runtime=WARN, Tool=WARN, SQL=WARN"/>
> > <property name="openjpa.DetachState"
> > value="fetch-groups(DetachedStateField=true)"/>
> > <property name="openjpa.FetchBatchSize" value="0"/>
> > <property name="openjpa.InverseManager" value="true"/>
> >
> > Any suggestions how to proceed?
> > My guess is that one thread writes an entity before the another thread
> > and the EntityManager entity state isn't updated before the next
> > merge.
> >
> > Best regards
> >
> > Daniel
> >
>
>
>
> --
> *Rick Curtis*
>

Re: Thread writing.

Posted by Rick Curtis <cu...@gmail.com>.
> I have a problem with one of our entities that we write in a callable
thread that could be called multiple times simultaneously.
If I'm reading this correctly, you're trying to persist an Entity with the
same ID multiple times simultaneously? If that is the case, this exception
is expected.

On Tue, Jul 10, 2012 at 10:00 AM, Daniel Persson <ma...@gmail.com>wrote:

> Hi OpenJPA users.
>
> I have a problem with one of our entities that we write in a callable
> thread that could be called multiple times simultaneously.
>
> We have an ThreadPoolExecutor that runs multiple versions of an object
> implements Callable.
> In some of these objects an entity is fetched and merged.
>
> We seperate each thread using ThreadLocal so each thread has there own
> entityManager and it uses it during the thread execution.
> private static transient ThreadLocal<Hashtable<String, EntityManager>>
> entityManagers = new ThreadLocal<Hashtable<String, EntityManager>>();
>
> No entities is sent between threads.
>
> The error we get frequently:
>
> Caused by: <openjpa-2.2.1-SNAPSHOT-r422266:1352927M fatal store error>
> org.apache.openjpa.persistence.EntityExistsException: Duplicate entry
> '472307' for key 1 {prepstmnt 37611 INSERT INTO table(col1, col2,
> col3, col4) VALUES (?, ?, ?, ?)} [code=1062, state=23000]
> FailedObject: path.to.table@3725f1
>         at
> org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4926)
>         at
> org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4901)
>         at
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
>         at
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:78)
>         at
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:143)
>         at
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushInternal(PreparedStatementManagerImpl.java:99)
>         at
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flush(PreparedStatementManagerImpl.java:87)
>         at
> org.apache.openjpa.jdbc.kernel.OperationOrderUpdateManager.flushPrimaryRow(OperationOrderUpdateManager.java:203)
>         at
> org.apache.openjpa.jdbc.kernel.OperationOrderUpdateManager.flush(OperationOrderUpdateManager.java:89)
>         at
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:105)
>         at
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:78)
>         at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:738)
>         at
> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:131)
>         at
> org.apache.openjpa.datacache.DataCacheStoreManager.flush(DataCacheStoreManager.java:661)
>         at
> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:131)
>         ... 19 more
> Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException:
> Duplicate entry '472307' for key 1 {prepstmnt 37611 INSERT INTO
> table(col1, col2, col3, col4) VALUES (?, ?, ?, ?)} [code=1062,
> state=23000]
>         at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:219)
>         at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:195)
>         at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$1000(LoggingConnectionDecorator.java:59)
>         at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeUpdate(LoggingConnectionDecorator.java:1134)
>         at
> org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:272)
>         at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeUpdate(JDBCStoreManager.java:1768)
>         at
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.executeUpdate(PreparedStatementManagerImpl.java:267)
>         at
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:118)
>         ... 29 more
>
> Our persistance configuration using an non-jta-data-source and tomcat
> datasource pooling.
>
> <property name="openjpa.ConnectionDriverName"
> value="com.mysql.jdbc.Driver" />
> <property name="openjpa.ConnectionProperties"
> value="autoReconnect=false,connectTimeout=5,socketTimeout=5" />
> <property name="openjpa.jdbc.DBDictionary"
> value="mysql(SupportsSubselect=true,UseClobs=true)"/>
> <property name="openjpa.jdbc.UpdateManager" value="operation-order"/>
> <property name="openjpa.DataCache" value="true(CacheSize=1000,
> SoftReferenceSize=0, EnableStatistics=true)"/>
> <property name="openjpa.QueryCache" value="true(CacheSize=200,
> SoftReferenceSize=0, EvictPolicy='timestamp')"/>
> <property name="openjpa.Log" value="File=/tmp/openjpa.log,
> DefaultLevel=WARN, Runtime=WARN, Tool=WARN, SQL=WARN"/>
> <property name="openjpa.DetachState"
> value="fetch-groups(DetachedStateField=true)"/>
> <property name="openjpa.FetchBatchSize" value="0"/>
> <property name="openjpa.InverseManager" value="true"/>
>
> Any suggestions how to proceed?
> My guess is that one thread writes an entity before the another thread
> and the EntityManager entity state isn't updated before the next
> merge.
>
> Best regards
>
> Daniel
>



-- 
*Rick Curtis*