Nabble - OpenJPA Users

Re: overriding datasource in the persistent unit

2009-11-07T20:41:47Z

Correct, you need to create a separate instance of the EntityManagerFactory for each organization by passing in the datasource name. it means that you create the factory.createEntityManager() for each thread based on the factory.

here is where you apply the solution that Michael and Milosz were taking about.

eg:

EntityManagerFactory emf = factories.get(client);
if (emf == null)
{
Map<String, String> props = new HashMap<String, String>();
props.put("javax.persistence.jtaDataSource", "jdbc/" + client + "db");
emf = Persistence.createEntityManagerFactory("pu", props);
factories.put(client, emf);
}
EntityManager em = emf.createEntityManager();

also, you need to create the data sources programmatically if you adding new organizations while application is live. If you are interested here is an example of it.

<pre>
String dsName = String.format("%1$sDb", clientCode);
Resource res = new Resource(dsName, "javax.sql.DataSource");
res.setJndi(dsName);

Properties props = res.getProperties();
props.put("JdbcDriver", "com.microsoft.sqlserver.jdbc.SQLServerDriver");
props.put("JdbcUrl", String.format("jdbc:sqlserver://172.19.101.12;databaseName=%1$s_db", clientCode));
props.put("UserName", "sa");
props.put("Password", "whatever");
props.put("JtaManaged", "true");

try
{
Assembler component = SystemInstance.get().getComponent(Assembler.class);
component.createResource(new ConfigurationFactory().configureService(res, ResourceInfo.class));
Thread.yield();
}
catch (OpenEJBException e)
{
throw e;
}
</pre>

Hope that it helps

Daryl Stultz wrote:

On Sat, Nov 7, 2009 at 7:53 PM, rtselvan <rtselvan@gmail.com> wrote:

>
> There may be some difference in what you are doing though. I have one only
> persistence unit in the XML file and connecting to different database based
> on the user/organization. This avoids to creating a lot of persistence unit
> and as well, ability to add additional organization without having change
> the persistence unit xml file.
>

Yeah, I definitely want to be able to add and drop organizations while the
application is live, thus no changes to persistence.xml. But isn't a one to
one correspondence between persistence unit and database implied? How does
JPA know the difference between 2 entities of the same class with the same
ID but from different databases?

I'm using a DataSource to get connections from my connection pool, I can see
clearly how I can choose a connection from different databases, but I would
think JPA would get very confused if I did that.

--
Daryl Stultz
_____________________________________
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:daryl@6degrees.com

Re: overriding datasource in the persistent unit

2009-11-07T18:50:57Z

On Sat, Nov 7, 2009 at 7:53 PM, rtselvan <[hidden email]> wrote:

>
> There may be some difference in what you are doing though. I have one only
> persistence unit in the XML file and connecting to different database based
> on the user/organization. This avoids to creating a lot of persistence unit
> and as well, ability to add additional organization without having change
> the persistence unit xml file.
>

Yeah, I definitely want to be able to add and drop organizations while the
application is live, thus no changes to persistence.xml. But isn't a one to
one correspondence between persistence unit and database implied? How does
JPA know the difference between 2 entities of the same class with the same
ID but from different databases?

I'm using a DataSource to get connections from my connection pool, I can see
clearly how I can choose a connection from different databases, but I would
think JPA would get very confused if I did that.

--
Daryl Stultz
_____________________________________
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:[hidden email]

Re: overriding datasource in the persistent unit

2009-11-07T16:53:18Z

There may be some difference in what you are doing though. I have one only persistence unit in the XML file and connecting to different database based on the user/organization. This avoids to creating a lot of persistence unit and as well, ability to add additional organization without having change the persistence unit xml file.

Daryl Stultz wrote:

On Fri, Nov 6, 2009 at 8:10 PM, rtselvan <rtselvan@gmail.com> wrote:

>
> My application is a multi-tenant app, I would need to override the
> datasource
> at runtime when creating the entitymanager factory based on the client
> code/name.
>
> Does OpenJPA support that?

In a month or two I will be modifying my application to do just this sort of
thing. I assume by "multi-tenant" you mean someone will login as a user
under one of many organizations and the user will then have access to one of
many persistence units that correspond to the organizations? I have much
more to do than selecting the right persistence unit / em factory, but I'm
interested in whatever you come up with. I hadn't considered that OpenJPA
might support it, I figured I'd have to instantiate all the factories when
the app starts up, then use the URL the user accesses the app with to map to
the right factory. It actually seems fairly easy, but if OpenJPA supports
some mechanism already, all the better.

I currently use a static factory with a ThreadLocal entity manager. So I
want my business logic to continue to be able to pick the entity manager
from the current thread. This means I need to set up the ThreadLocal state
at the beginning of the event thread to be able to create an entity manager
from the right factory, presumably by mapping the URL to the factory.

Those are my thoughts thus far.

--
Daryl Stultz
_____________________________________
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:daryl@6degrees.com

Re: overriding datasource in the persistent unit

2009-11-07T20:29:59Z

It works great! It was identical to hibernate JPA implementation.

rtselvan wrote:

Thanks Guys!

Let me try that, it looks pretty simple

Michael Dick wrote:

Adding to Milosz response.

The property keys that you want are javax.persistence.jtaDataSource and
javax.persistence.nonJtaDataSource (for jta-data-source and
non-jta-data-source respectively)

For example :
Map<String, Object> props = new HashMap<String, Object>();
props.put("javax.persistence.jtaDataSource", "jdbc/override");
props.put("javax.persistence.nonJtaDataSource",
"jdbc/overrideNonJTA");
EntityManagerFactory emf =
Persistence.createEntityManagerFactory(getPersistenceUnitName(), props);

In earlier versions of OpenJPA you can use openjpa.ConnectionFactoryName for
jta-data-source and openjpa.ConnectionFactory2Name for non-jta-data-source.

Hope this helps,
-mike

On Sat, Nov 7, 2009 at 2:41 PM, Miłosz Tylenda <mtylenda@o2.pl> wrote:

> Hello!
>
> > >
> > > My application is a multi-tenant app, I would need to override the
> > > datasource
> > > at runtime when creating the entitymanager factory based on the client
> > > code/name.
> > >
> > > Does OpenJPA support that?
> >
> >
> > In a month or two I will be modifying my application to do just this sort
> of
> > thing. I assume by "multi-tenant" you mean someone will login as a user
> > under one of many organizations and the user will then have access to one
> of
> > many persistence units that correspond to the organizations? I have much
> > more to do than selecting the right persistence unit / em factory, but
> I'm
> > interested in whatever you come up with. I hadn't considered that OpenJPA
> > might support it, I figured I'd have to instantiate all the factories
> when
> > the app starts up, then use the URL the user accesses the app with to map
> to
> > the right factory. It actually seems fairly easy, but if OpenJPA supports
> > some mechanism already, all the better.
>
> Have you tried calling Persistence.createEntityManagerFactory(String, Map)?
> The second parameter should allow you to override any value you have set in
> persistence.xml, so in particular, the data source name.
>
> Regards,
> Milosz
>
>

Re: overriding datasource in the persistent unit

2009-11-07T16:55:27Z

Thanks Guys!

Let me try that, it looks pretty simple

Michael Dick wrote:

Adding to Milosz response.

The property keys that you want are javax.persistence.jtaDataSource and
javax.persistence.nonJtaDataSource (for jta-data-source and
non-jta-data-source respectively)

For example :
Map<String, Object> props = new HashMap<String, Object>();
props.put("javax.persistence.jtaDataSource", "jdbc/override");
props.put("javax.persistence.nonJtaDataSource",
"jdbc/overrideNonJTA");
EntityManagerFactory emf =
Persistence.createEntityManagerFactory(getPersistenceUnitName(), props);

In earlier versions of OpenJPA you can use openjpa.ConnectionFactoryName for
jta-data-source and openjpa.ConnectionFactory2Name for non-jta-data-source.

Hope this helps,
-mike

On Sat, Nov 7, 2009 at 2:41 PM, Miłosz Tylenda <mtylenda@o2.pl> wrote:

> Hello!
>
> > >
> > > My application is a multi-tenant app, I would need to override the
> > > datasource
> > > at runtime when creating the entitymanager factory based on the client
> > > code/name.
> > >
> > > Does OpenJPA support that?
> >
> >
> > In a month or two I will be modifying my application to do just this sort
> of
> > thing. I assume by "multi-tenant" you mean someone will login as a user
> > under one of many organizations and the user will then have access to one
> of
> > many persistence units that correspond to the organizations? I have much
> > more to do than selecting the right persistence unit / em factory, but
> I'm
> > interested in whatever you come up with. I hadn't considered that OpenJPA
> > might support it, I figured I'd have to instantiate all the factories
> when
> > the app starts up, then use the URL the user accesses the app with to map
> to
> > the right factory. It actually seems fairly easy, but if OpenJPA supports
> > some mechanism already, all the better.
>
> Have you tried calling Persistence.createEntityManagerFactory(String, Map)?
> The second parameter should allow you to override any value you have set in
> persistence.xml, so in particular, the data source name.
>
> Regards,
> Milosz
>
>

Re: overriding datasource in the persistent unit

2009-11-07T13:28:03Z

Adding to Milosz response.

The property keys that you want are javax.persistence.jtaDataSource and
javax.persistence.nonJtaDataSource (for jta-data-source and
non-jta-data-source respectively)

For example :
Map<String, Object> props = new HashMap<String, Object>();
props.put("javax.persistence.jtaDataSource", "jdbc/override");
props.put("javax.persistence.nonJtaDataSource",
"jdbc/overrideNonJTA");
EntityManagerFactory emf =
Persistence.createEntityManagerFactory(getPersistenceUnitName(), props);

In earlier versions of OpenJPA you can use openjpa.ConnectionFactoryName for
jta-data-source and openjpa.ConnectionFactory2Name for non-jta-data-source.

Hope this helps,
-mike

On Sat, Nov 7, 2009 at 2:41 PM, Miłosz Tylenda <[hidden email]> wrote:

> Hello!
>
> > >
> > > My application is a multi-tenant app, I would need to override the
> > > datasource
> > > at runtime when creating the entitymanager factory based on the client
> > > code/name.
> > >
> > > Does OpenJPA support that?
> >
> >
> > In a month or two I will be modifying my application to do just this sort
> of
> > thing. I assume by "multi-tenant" you mean someone will login as a user
> > under one of many organizations and the user will then have access to one
> of
> > many persistence units that correspond to the organizations? I have much
> > more to do than selecting the right persistence unit / em factory, but
> I'm
> > interested in whatever you come up with. I hadn't considered that OpenJPA
> > might support it, I figured I'd have to instantiate all the factories
> when
> > the app starts up, then use the URL the user accesses the app with to map
> to
> > the right factory. It actually seems fairly easy, but if OpenJPA supports
> > some mechanism already, all the better.
>
> Have you tried calling Persistence.createEntityManagerFactory(String, Map)?
> The second parameter should allow you to override any value you have set in
> persistence.xml, so in particular, the data source name.
>
> Regards,
> Milosz
>
>

Re: overriding datasource in the persistent unit

2009-11-07T12:41:17Z

Hello!

> >
> > My application is a multi-tenant app, I would need to override the
> > datasource
> > at runtime when creating the entitymanager factory based on the client
> > code/name.
> >
> > Does OpenJPA support that?
>
>
> In a month or two I will be modifying my application to do just this sort of
> thing. I assume by "multi-tenant" you mean someone will login as a user
> under one of many organizations and the user will then have access to one of
> many persistence units that correspond to the organizations? I have much
> more to do than selecting the right persistence unit / em factory, but I'm
> interested in whatever you come up with. I hadn't considered that OpenJPA
> might support it, I figured I'd have to instantiate all the factories when
> the app starts up, then use the URL the user accesses the app with to map to
> the right factory. It actually seems fairly easy, but if OpenJPA supports
> some mechanism already, all the better.

Have you tried calling Persistence.createEntityManagerFactory(String, Map)? The second parameter should allow you to override any value you have set in persistence.xml, so in particular, the data source name.

Regards,
Milosz

Re: overriding datasource in the persistent unit

2009-11-07T11:20:48Z

On Fri, Nov 6, 2009 at 8:10 PM, rtselvan <[hidden email]> wrote:

>
> My application is a multi-tenant app, I would need to override the
> datasource
> at runtime when creating the entitymanager factory based on the client
> code/name.
>
> Does OpenJPA support that?

In a month or two I will be modifying my application to do just this sort of
thing. I assume by "multi-tenant" you mean someone will login as a user
under one of many organizations and the user will then have access to one of
many persistence units that correspond to the organizations? I have much
more to do than selecting the right persistence unit / em factory, but I'm
interested in whatever you come up with. I hadn't considered that OpenJPA
might support it, I figured I'd have to instantiate all the factories when
the app starts up, then use the URL the user accesses the app with to map to
the right factory. It actually seems fairly easy, but if OpenJPA supports
some mechanism already, all the better.

I currently use a static factory with a ThreadLocal entity manager. So I
want my business logic to continue to be able to pick the entity manager
from the current thread. This means I need to set up the ThreadLocal state
at the beginning of the event thread to be able to create an entity manager
from the right factory, presumably by mapping the URL to the factory.

Those are my thoughts thus far.

--
Daryl Stultz
_____________________________________
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:[hidden email]

overriding datasource in the persistent unit

2009-11-06T17:10:53Z

My application is a multi-tenant app, I would need to override the datasource at runtime when creating the entitymanager factory based on the client code/name. There would be only one persistent unit but at runtime different database connection to be used.

Does OpenJPA support that? Hibernate supports it and I have tested it successfully but I would like to use OpenJPA due to the light weight nature of it.

Any ideas?

Thanks
/selvan

ClassCast Exception when doing a merge on a detached object

2009-11-06T13:06:46Z

Hi,

I'm using Open jpa 1.0.1 and webshpere 6.1. I'm running into a unique problem when executing a merge on a detached obect. I have a parent class and two subclasses.

one of subclasses has a couple of one to many relationships as well.

I do a select on the parent, the actual instance could be any of the subclass. the object is then sent over to the client, the client updates the object and i then merge it back.

I then see this exception

Caused by: java.lang.Exception: java.lang.ClassCastException: parent incompatible with child at org.apache.openjpa.util.Exceptions.replaceNestedThrowables(Exceptions.java:242)
at org.apache.openjpa.persistence.PersistenceException.writeObject(PersistenceException.java:100)
at sun.reflect.GeneratedMethodAccessor475.invoke(Unknown Source)

the exception happens only when the subclass with the one-to-many relations has to be updated

can anyone tell me why this might be happening? all the classes are versioned on a timestamp

Thanks
Vinay

Re: AW: Nullable column

2009-11-06T13:29:48Z

Is your table pre-generated? Can you drop table and add this to your persistence.xml to let openjpa generate the table for you?

<property name="openjpa.jdbc.SynchronizeMappings"
value="buildSchema" />

----- Original Message ----
From: "Scherer, Annette" <[hidden email]>
To: "[hidden email]" <[hidden email]>
Sent: Fri, November 6, 2009 12:19:53 PM
Subject: AW: Nullable column

No, not an Id field

Annette Scherer
Abteilung Informatik

HUK-COBURG
Bahnhofsplatz
96444 Coburg
Telefon 09561 96-1718
Telefax 09561 96-3671
E-Mail [hidden email]
Internet www.HUK.de
=============================================================
HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter Deutschlands a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Werner Strohmayr.
Vorstand: Dr. Wolfgang Weiler (Sprecher), Wolfgang Flaßhoff, Stefan Gronbach, Klaus-Jürgen Heitmann, Dr. Christian Hofer.
=============================================================

-----Ursprüngliche Nachricht-----
Von: Fay Wang [mailto:[hidden email]]
Gesendet: Freitag, 6. November 2009 21:00
An: [hidden email]
Betreff: Re: Nullable column

Hi Annette,
Is the field materialNummer an Id field?

Regards,
Fay

----- Original Message ----
From: "Scherer, Annette" <[hidden email]>
To: "[hidden email]" <[hidden email]>
Sent: Fri, November 6, 2009 11:26:59 AM
Subject: Nullable column

Hi all,

I annotated a Column like this, hoping to succed in inserting a null value to that column
@Column(nullable=true)
private String materialNummer;

It doesn't work.
I get the exception below.
What can I do?

thank you for help
Annette

812 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 243469955> executing prepstmnt 1712481810 SELECT SEQSCHEMA AS SEQUENCE_SCHEMA, SEQNAME AS SEQUENCE_NAME FROM SYSCAT.SEQUENCES
812 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 243469955> [0 ms] spent
8656 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 2117697081> executing prepstmnt 241307234 SELECT SEQUENCE_VALUE FROM T7.OPENJPA_SEQUENCE_TABLE WHERE ID = ? FOR READ ONLY WITH RS USE AND KEEP UPDATE LOCKS [params=(int) 0]
8656 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 2117697081> [0 ms] spent
8656 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 2117697081> executing prepstmnt 677128284 UPDATE T7.OPENJPA_SEQUENCE_TABLE SET SEQUENCE_VALUE = ? WHERE ID = ? AND SEQUENCE_VALUE = ? [params=(long) 174151, (int) 0, (long) 174101]
8656 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 2117697081> [0 ms] spent
8687 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 1268140950> batching prepstmnt 294719889 INSERT INTO T7.DRUCK_MATERIAL (id, bezeichner, materialNummer) VALUES (?, ?, ?) [params=(String) 174101, (String) Toner/Tinte siehe Bemerkungsfeld, (null) null]
8687 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 1268140950> [0 ms] spent
8687 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 1268140950> batching prepstmnt 294719889 INSERT INTO T7.DRUCK_MATERIAL (id, bezeichner, materialNummer) VALUES (?, ?, ?) [params=(String) 174102, (String) Toner, cyan, (String) 20K1400]
8687 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 1268140950> [0 ms] spent
.......
Exception in thread "main" <openjpa-1.2.1-r752877:753278 fatal store error> org.apache.openjpa.persistence.RollbackException: Das Rollback der Transaktion ist abgeschlossen. Suchen Sie in den verschachtelten Ausnahmen nach Einzelheiten zu den aufgetretenen Fehlern.
at org.apache.openjpa.persistence.EntityManagerImpl.commit(EntityManagerImpl.java:523)
at de.huk.dma.persist.DataPersistorMain.main(DataPersistorMain.java:39)
Caused by: <openjpa-1.2.1-r752877:753278 fatal general error> org.apache.openjpa.persistence.PersistenceException: Das Rollback der Transaktion ist abgeschlossen. Suchen Sie in den verschachtelten Ausnahmen nach Einzelheiten zu den aufgetretenen Fehlern.
at org.apache.openjpa.kernel.BrokerImpl.newFlushException(BrokerImpl.java:2163)
at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2010)
at org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1908)
at org.apache.openjpa.kernel.BrokerImpl.beforeCompletion(BrokerImpl.java:1826)
at org.apache.openjpa.kernel.LocalManagedRuntime.commit(LocalManagedRuntime.java:81)
at org.apache.openjpa.kernel.BrokerImpl.commit(BrokerImpl.java:1350)
at org.apache.openjpa.kernel.DelegatingBroker.commit(DelegatingBroker.java:877)
at org.apache.openjpa.persistence.EntityManagerImpl.commit(EntityManagerImpl.java:512)
... 1 more
Caused by: <openjpa-1.2.1-r752877:753278 nonfatal general error> org.apache.openjpa.persistence.PersistenceException: Non-atomic batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch. Use getNextException() to retrieve the exceptions for specific batched elements.SQLCA OUTPUT[Errp=SQLDFMT1, Errd=-2146041828, 28, 0, 0, -957, 0]
Error for batch element #0: DB2 SQL error: SQLCODE: -407, SQLSTATE: 23502, SQLERRMC: TBSPACEID=2, TABLEID=269, COLNO=0
FailedObject: prepstmnt 294719889 INSERT INTO T7.DRUCK_MATERIAL (id, bezeichner, materialNummer) VALUES (?, ?, ?) [org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement]
at org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4232)
at org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4197)
at org.apache.openjpa.jdbc.sql.DB2Dictionary.newStoreException(DB2Dictionary.java:503)
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:102)
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:72)
at org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.flushBatch(BatchingPreparedStatementManagerImpl.java:195)
at org.apache.openjpa.jdbc.kernel.BatchingConstraintUpdateManager.flush(BatchingConstraintUpdateManager.java:63)
at com.ibm.ws.persistence.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:78)
at com.ibm.ws.persistence.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:60)
at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:717)
at org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130)
... 8 more
Caused by: com.ibm.db2.jcc.a.dg: Non-atomic batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch. Use getNextException() to retrieve the exceptions for specific batched elements.
at com.ibm.db2.jcc.a.f.a(f.java:328)
at com.ibm.db2.jcc.a.cp.a(cp.java:2160)
at com.ibm.db2.jcc.a.cp.executeBatch(cp.java:1991)
at com.ibm.db2.jcc.a.cp.executeBatch(cp.java:1010)
at org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeBatch(DelegatingPreparedStatement.java:244)
at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeBatch(LoggingConnectionDecorator.java:878)
at org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeBatch(DelegatingPreparedStatement.java:244)
at org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeBatch(JDBCStoreManager.java:1604)
at org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.executeBatch(BatchingPreparedStatementManagerImpl.java:325)
at org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.flushBatch(BatchingPreparedStatementManagerImpl.java:188)
... 13 more

AW: Nullable column

2009-11-06T12:19:53Z

No, not an Id field

Annette Scherer
Abteilung Informatik

HUK-COBURG
Bahnhofsplatz
96444 Coburg
Telefon 09561 96-1718
Telefax 09561 96-3671
E-Mail [hidden email]
Internet www.HUK.de
=============================================================
HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter Deutschlands a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Werner Strohmayr.
Vorstand: Dr. Wolfgang Weiler (Sprecher), Wolfgang Flaßhoff, Stefan Gronbach, Klaus-Jürgen Heitmann, Dr. Christian Hofer.
=============================================================

-----Ursprüngliche Nachricht-----
Von: Fay Wang [mailto:[hidden email]]
Gesendet: Freitag, 6. November 2009 21:00
An: [hidden email]
Betreff: Re: Nullable column

Hi Annette,
Is the field materialNummer an Id field?

Regards,
Fay

----- Original Message ----
From: "Scherer, Annette" <[hidden email]>
To: "[hidden email]" <[hidden email]>
Sent: Fri, November 6, 2009 11:26:59 AM
Subject: Nullable column

Hi all,

I annotated a Column like this, hoping to succed in inserting a null value to that column
@Column(nullable=true)
private String materialNummer;

It doesn't work.
I get the exception below.
What can I do?

thank you for help
Annette

812 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 243469955> executing prepstmnt 1712481810 SELECT SEQSCHEMA AS SEQUENCE_SCHEMA, SEQNAME AS SEQUENCE_NAME FROM SYSCAT.SEQUENCES
812 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 243469955> [0 ms] spent
8656 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 2117697081> executing prepstmnt 241307234 SELECT SEQUENCE_VALUE FROM T7.OPENJPA_SEQUENCE_TABLE WHERE ID = ? FOR READ ONLY WITH RS USE AND KEEP UPDATE LOCKS [params=(int) 0]
8656 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 2117697081> [0 ms] spent
8656 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 2117697081> executing prepstmnt 677128284 UPDATE T7.OPENJPA_SEQUENCE_TABLE SET SEQUENCE_VALUE = ? WHERE ID = ? AND SEQUENCE_VALUE = ? [params=(long) 174151, (int) 0, (long) 174101]
8656 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 2117697081> [0 ms] spent
8687 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 1268140950> batching prepstmnt 294719889 INSERT INTO T7.DRUCK_MATERIAL (id, bezeichner, materialNummer) VALUES (?, ?, ?) [params=(String) 174101, (String) Toner/Tinte siehe Bemerkungsfeld, (null) null]
8687 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 1268140950> [0 ms] spent
8687 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 1268140950> batching prepstmnt 294719889 INSERT INTO T7.DRUCK_MATERIAL (id, bezeichner, materialNummer) VALUES (?, ?, ?) [params=(String) 174102, (String) Toner, cyan, (String) 20K1400]
8687 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 1268140950> [0 ms] spent
.......
Exception in thread "main" <openjpa-1.2.1-r752877:753278 fatal store error> org.apache.openjpa.persistence.RollbackException: Das Rollback der Transaktion ist abgeschlossen. Suchen Sie in den verschachtelten Ausnahmen nach Einzelheiten zu den aufgetretenen Fehlern.
at org.apache.openjpa.persistence.EntityManagerImpl.commit(EntityManagerImpl.java:523)
at de.huk.dma.persist.DataPersistorMain.main(DataPersistorMain.java:39)
Caused by: <openjpa-1.2.1-r752877:753278 fatal general error> org.apache.openjpa.persistence.PersistenceException: Das Rollback der Transaktion ist abgeschlossen. Suchen Sie in den verschachtelten Ausnahmen nach Einzelheiten zu den aufgetretenen Fehlern.
at org.apache.openjpa.kernel.BrokerImpl.newFlushException(BrokerImpl.java:2163)
at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2010)
at org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1908)
at org.apache.openjpa.kernel.BrokerImpl.beforeCompletion(BrokerImpl.java:1826)
at org.apache.openjpa.kernel.LocalManagedRuntime.commit(LocalManagedRuntime.java:81)
at org.apache.openjpa.kernel.BrokerImpl.commit(BrokerImpl.java:1350)
at org.apache.openjpa.kernel.DelegatingBroker.commit(DelegatingBroker.java:877)
at org.apache.openjpa.persistence.EntityManagerImpl.commit(EntityManagerImpl.java:512)
... 1 more
Caused by: <openjpa-1.2.1-r752877:753278 nonfatal general error> org.apache.openjpa.persistence.PersistenceException: Non-atomic batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch. Use getNextException() to retrieve the exceptions for specific batched elements.SQLCA OUTPUT[Errp=SQLDFMT1, Errd=-2146041828, 28, 0, 0, -957, 0]
Error for batch element #0: DB2 SQL error: SQLCODE: -407, SQLSTATE: 23502, SQLERRMC: TBSPACEID=2, TABLEID=269, COLNO=0
FailedObject: prepstmnt 294719889 INSERT INTO T7.DRUCK_MATERIAL (id, bezeichner, materialNummer) VALUES (?, ?, ?) [org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement]
at org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4232)
at org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4197)
at org.apache.openjpa.jdbc.sql.DB2Dictionary.newStoreException(DB2Dictionary.java:503)
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:102)
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:72)
at org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.flushBatch(BatchingPreparedStatementManagerImpl.java:195)
at org.apache.openjpa.jdbc.kernel.BatchingConstraintUpdateManager.flush(BatchingConstraintUpdateManager.java:63)
at com.ibm.ws.persistence.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:78)
at com.ibm.ws.persistence.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:60)
at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:717)
at org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130)
... 8 more
Caused by: com.ibm.db2.jcc.a.dg: Non-atomic batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch. Use getNextException() to retrieve the exceptions for specific batched elements.
at com.ibm.db2.jcc.a.f.a(f.java:328)
at com.ibm.db2.jcc.a.cp.a(cp.java:2160)
at com.ibm.db2.jcc.a.cp.executeBatch(cp.java:1991)
at com.ibm.db2.jcc.a.cp.executeBatch(cp.java:1010)
at org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeBatch(DelegatingPreparedStatement.java:244)
at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeBatch(LoggingConnectionDecorator.java:878)
at org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeBatch(DelegatingPreparedStatement.java:244)
at org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeBatch(JDBCStoreManager.java:1604)
at org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.executeBatch(BatchingPreparedStatementManagerImpl.java:325)
at org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.flushBatch(BatchingPreparedStatementManagerImpl.java:188)
... 13 more

Re: Nullable column

2009-11-06T12:00:11Z

Hi Annette,
Is the field materialNummer an Id field?

Regards,
Fay

----- Original Message ----
From: "Scherer, Annette" <[hidden email]>
To: "[hidden email]" <[hidden email]>
Sent: Fri, November 6, 2009 11:26:59 AM
Subject: Nullable column

Hi all,

I annotated a Column like this, hoping to succed in inserting a null value to that column
@Column(nullable=true)
private String materialNummer;

It doesn't work.
I get the exception below.
What can I do?

thank you for help
Annette

812 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 243469955> executing prepstmnt 1712481810 SELECT SEQSCHEMA AS SEQUENCE_SCHEMA, SEQNAME AS SEQUENCE_NAME FROM SYSCAT.SEQUENCES
812 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 243469955> [0 ms] spent
8656 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 2117697081> executing prepstmnt 241307234 SELECT SEQUENCE_VALUE FROM T7.OPENJPA_SEQUENCE_TABLE WHERE ID = ? FOR READ ONLY WITH RS USE AND KEEP UPDATE LOCKS [params=(int) 0]
8656 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 2117697081> [0 ms] spent
8656 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 2117697081> executing prepstmnt 677128284 UPDATE T7.OPENJPA_SEQUENCE_TABLE SET SEQUENCE_VALUE = ? WHERE ID = ? AND SEQUENCE_VALUE = ? [params=(long) 174151, (int) 0, (long) 174101]
8656 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 2117697081> [0 ms] spent
8687 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 1268140950> batching prepstmnt 294719889 INSERT INTO T7.DRUCK_MATERIAL (id, bezeichner, materialNummer) VALUES (?, ?, ?) [params=(String) 174101, (String) Toner/Tinte siehe Bemerkungsfeld, (null) null]
8687 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 1268140950> [0 ms] spent
8687 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 1268140950> batching prepstmnt 294719889 INSERT INTO T7.DRUCK_MATERIAL (id, bezeichner, materialNummer) VALUES (?, ?, ?) [params=(String) 174102, (String) Toner, cyan, (String) 20K1400]
8687 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 1268140950> [0 ms] spent
.......
Exception in thread "main" <openjpa-1.2.1-r752877:753278 fatal store error> org.apache.openjpa.persistence.RollbackException: Das Rollback der Transaktion ist abgeschlossen. Suchen Sie in den verschachtelten Ausnahmen nach Einzelheiten zu den aufgetretenen Fehlern.
at org.apache.openjpa.persistence.EntityManagerImpl.commit(EntityManagerImpl.java:523)
at de.huk.dma.persist.DataPersistorMain.main(DataPersistorMain.java:39)
Caused by: <openjpa-1.2.1-r752877:753278 fatal general error> org.apache.openjpa.persistence.PersistenceException: Das Rollback der Transaktion ist abgeschlossen. Suchen Sie in den verschachtelten Ausnahmen nach Einzelheiten zu den aufgetretenen Fehlern.
at org.apache.openjpa.kernel.BrokerImpl.newFlushException(BrokerImpl.java:2163)
at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2010)
at org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1908)
at org.apache.openjpa.kernel.BrokerImpl.beforeCompletion(BrokerImpl.java:1826)
at org.apache.openjpa.kernel.LocalManagedRuntime.commit(LocalManagedRuntime.java:81)
at org.apache.openjpa.kernel.BrokerImpl.commit(BrokerImpl.java:1350)
at org.apache.openjpa.kernel.DelegatingBroker.commit(DelegatingBroker.java:877)
at org.apache.openjpa.persistence.EntityManagerImpl.commit(EntityManagerImpl.java:512)
... 1 more
Caused by: <openjpa-1.2.1-r752877:753278 nonfatal general error> org.apache.openjpa.persistence.PersistenceException: Non-atomic batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch. Use getNextException() to retrieve the exceptions for specific batched elements.SQLCA OUTPUT[Errp=SQLDFMT1, Errd=-2146041828, 28, 0, 0, -957, 0]
Error for batch element #0: DB2 SQL error: SQLCODE: -407, SQLSTATE: 23502, SQLERRMC: TBSPACEID=2, TABLEID=269, COLNO=0
FailedObject: prepstmnt 294719889 INSERT INTO T7.DRUCK_MATERIAL (id, bezeichner, materialNummer) VALUES (?, ?, ?) [org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement]
at org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4232)
at org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4197)
at org.apache.openjpa.jdbc.sql.DB2Dictionary.newStoreException(DB2Dictionary.java:503)
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:102)
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:72)
at org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.flushBatch(BatchingPreparedStatementManagerImpl.java:195)
at org.apache.openjpa.jdbc.kernel.BatchingConstraintUpdateManager.flush(BatchingConstraintUpdateManager.java:63)
at com.ibm.ws.persistence.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:78)
at com.ibm.ws.persistence.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:60)
at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:717)
at org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130)
... 8 more
Caused by: com.ibm.db2.jcc.a.dg: Non-atomic batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch. Use getNextException() to retrieve the exceptions for specific batched elements.
at com.ibm.db2.jcc.a.f.a(f.java:328)
at com.ibm.db2.jcc.a.cp.a(cp.java:2160)
at com.ibm.db2.jcc.a.cp.executeBatch(cp.java:1991)
at com.ibm.db2.jcc.a.cp.executeBatch(cp.java:1010)
at org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeBatch(DelegatingPreparedStatement.java:244)
at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeBatch(LoggingConnectionDecorator.java:878)
at org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeBatch(DelegatingPreparedStatement.java:244)
at org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeBatch(JDBCStoreManager.java:1604)
at org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.executeBatch(BatchingPreparedStatementManagerImpl.java:325)
at org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.flushBatch(BatchingPreparedStatementManagerImpl.java:188)
... 13 more

Nullable column

2009-11-06T11:26:59Z

Hi all,

I annotated a Column like this, hoping to succed in inserting a null value to that column
@Column(nullable=true)
private String materialNummer;

It doesn't work.
I get the exception below.
What can I do?

thank you for help
Annette

812 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 243469955> executing prepstmnt 1712481810 SELECT SEQSCHEMA AS SEQUENCE_SCHEMA, SEQNAME AS SEQUENCE_NAME FROM SYSCAT.SEQUENCES
812 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 243469955> [0 ms] spent
8656 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 2117697081> executing prepstmnt 241307234 SELECT SEQUENCE_VALUE FROM T7.OPENJPA_SEQUENCE_TABLE WHERE ID = ? FOR READ ONLY WITH RS USE AND KEEP UPDATE LOCKS [params=(int) 0]
8656 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 2117697081> [0 ms] spent
8656 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 2117697081> executing prepstmnt 677128284 UPDATE T7.OPENJPA_SEQUENCE_TABLE SET SEQUENCE_VALUE = ? WHERE ID = ? AND SEQUENCE_VALUE = ? [params=(long) 174151, (int) 0, (long) 174101]
8656 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 2117697081> [0 ms] spent
8687 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 1268140950> batching prepstmnt 294719889 INSERT INTO T7.DRUCK_MATERIAL (id, bezeichner, materialNummer) VALUES (?, ?, ?) [params=(String) 174101, (String) Toner/Tinte siehe Bemerkungsfeld, (null) null]
8687 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 1268140950> [0 ms] spent
8687 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 1268140950> batching prepstmnt 294719889 INSERT INTO T7.DRUCK_MATERIAL (id, bezeichner, materialNummer) VALUES (?, ?, ?) [params=(String) 174102, (String) Toner, cyan, (String) 20K1400]
8687 DruckerMaterialAnforderung_DB TRACE [main] openjpa.jdbc.SQL - <t 109577864, conn 1268140950> [0 ms] spent
.......
Exception in thread "main" <openjpa-1.2.1-r752877:753278 fatal store error> org.apache.openjpa.persistence.RollbackException: Das Rollback der Transaktion ist abgeschlossen. Suchen Sie in den verschachtelten Ausnahmen nach Einzelheiten zu den aufgetretenen Fehlern.
at org.apache.openjpa.persistence.EntityManagerImpl.commit(EntityManagerImpl.java:523)
at de.huk.dma.persist.DataPersistorMain.main(DataPersistorMain.java:39)
Caused by: <openjpa-1.2.1-r752877:753278 fatal general error> org.apache.openjpa.persistence.PersistenceException: Das Rollback der Transaktion ist abgeschlossen. Suchen Sie in den verschachtelten Ausnahmen nach Einzelheiten zu den aufgetretenen Fehlern.
at org.apache.openjpa.kernel.BrokerImpl.newFlushException(BrokerImpl.java:2163)
at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2010)
at org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1908)
at org.apache.openjpa.kernel.BrokerImpl.beforeCompletion(BrokerImpl.java:1826)
at org.apache.openjpa.kernel.LocalManagedRuntime.commit(LocalManagedRuntime.java:81)
at org.apache.openjpa.kernel.BrokerImpl.commit(BrokerImpl.java:1350)
at org.apache.openjpa.kernel.DelegatingBroker.commit(DelegatingBroker.java:877)
at org.apache.openjpa.persistence.EntityManagerImpl.commit(EntityManagerImpl.java:512)
... 1 more
Caused by: <openjpa-1.2.1-r752877:753278 nonfatal general error> org.apache.openjpa.persistence.PersistenceException: Non-atomic batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch. Use getNextException() to retrieve the exceptions for specific batched elements.SQLCA OUTPUT[Errp=SQLDFMT1, Errd=-2146041828, 28, 0, 0, -957, 0]
Error for batch element #0: DB2 SQL error: SQLCODE: -407, SQLSTATE: 23502, SQLERRMC: TBSPACEID=2, TABLEID=269, COLNO=0
FailedObject: prepstmnt 294719889 INSERT INTO T7.DRUCK_MATERIAL (id, bezeichner, materialNummer) VALUES (?, ?, ?) [org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement]
at org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4232)
at org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4197)
at org.apache.openjpa.jdbc.sql.DB2Dictionary.newStoreException(DB2Dictionary.java:503)
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:102)
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:72)
at org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.flushBatch(BatchingPreparedStatementManagerImpl.java:195)
at org.apache.openjpa.jdbc.kernel.BatchingConstraintUpdateManager.flush(BatchingConstraintUpdateManager.java:63)
at com.ibm.ws.persistence.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:78)
at com.ibm.ws.persistence.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:60)
at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:717)
at org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130)
... 8 more
Caused by: com.ibm.db2.jcc.a.dg: Non-atomic batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch. Use getNextException() to retrieve the exceptions for specific batched elements.
at com.ibm.db2.jcc.a.f.a(f.java:328)
at com.ibm.db2.jcc.a.cp.a(cp.java:2160)
at com.ibm.db2.jcc.a.cp.executeBatch(cp.java:1991)
at com.ibm.db2.jcc.a.cp.executeBatch(cp.java:1010)
at org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeBatch(DelegatingPreparedStatement.java:244)
at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeBatch(LoggingConnectionDecorator.java:878)
at org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeBatch(DelegatingPreparedStatement.java:244)
at org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeBatch(JDBCStoreManager.java:1604)
at org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.executeBatch(BatchingPreparedStatementManagerImpl.java:325)
at org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.flushBatch(BatchingPreparedStatementManagerImpl.java:188)
... 13 more

Re: left join fetch with long text fields

2009-11-05T08:59:46Z

On Thu, Nov 5, 2009 at 11:52 AM, Daryl Stultz <[hidden email]> wrote:

> slow. Is there some way to annotate this field so it is always retrieved in
> the main query? Do I need to put a real limit on it? What would that be?
>
> Setting
length = 1000000000
seems to do the trick (leaving database column as varchar(0)). A billion
characters ought to be enough for my purposes (if JPA does any checking),
but I still wonder if there's a better way.

--
Daryl Stultz
_____________________________________
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:[hidden email]

left join fetch with long text fields

2009-11-05T08:52:15Z

Hello,

I have entity B with field "myLongText" defined like so:

@Column(name = "mylongtext", length = -1)
private String myLongText;

In PostgreSQL the column is a varchar(0).

When I retrieve a list of B entities, I get myLongText as expected, selected
in one query. Suppose I have entity A with bCol, a collection of B. If I
select like so:

select distinct o from A as o
left join fetch o.bCol

the value of myLongText is retrieved with an individual query PER B
instance! Naturally this is pretty slow. Is there some way to annotate this
field so it is always retrieved in the main query? Do I need to put a real
limit on it? What would that be?

I think somebody explored this problem recently but I can't remember any key
words from the discussion to search on.

Thanks.

--
Daryl Stultz
_____________________________________
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:[hidden email]

MappingTool ignores FK constraints during DELETE

2009-11-04T23:26:01Z

Hi Folks,

I run MappingTool with "-schemaAction deleteTableContents", and it looks like OpenJPA issues DELETE statements in alphabetical order of entities. In my application, a DELETE for the parent table is issued before the DELETE for the dependent table can be issued. Both tables are populated, and the parent table DELETE fails because of the default ON DELETE NO ACTION constraint.

Is there a way to tell MappingTool to order its deletes taking into account the RI dependency chain ?

(I could set the MappingDefaults property's ForeignKeyDeleteAction option to 'cascade', so OpenJPA will alter tables for ON DELETE CASCADE, but I am hoping MappingTool can be made to work).

Thanks,
Dinkar

Re: Eager fetch leads to out of bounds error

2009-11-07T13:59:00Z

On Thu, Nov 5, 2009 at 1:27 PM, Daryl Stultz <[hidden email]> wrote:

> On Thu, Nov 5, 2009 at 1:48 PM, Michael Dick <[hidden email]
> >wrote:
>
> > On Thu, Nov 5, 2009 at 12:17 PM, Daryl Stultz <[hidden email]>
> wrote:
> >
> >
> > I think I misunderstood your point (I thought the FETCH was implied).
> >
>
> I think I asked a new question, not necessarily based on your previous
> input, so I don't think you misunderstood anything, I just changed the line
> of questioning on you. :-)
>
> >
> > Adding in the fetch clause:
> >
> > A JOIN FETCH differs from a JOIN in two ways :
> > * You will get one reference to the entity on the left side of the JOIN
> > for every related entity on the right side of the JOIN.
> >
>
> This I misunderstood long ago before our discussion - I didn't
> misunderstand
> what you were saying about it. I don't think. Anyway.
>
>
> > * The relationship on the right side of the JOIN will be eagerly loaded.
> >
>
> This is what I'm having trouble with. If a JOIN would return the children,
> isn't it implied that they are eagerly loaded? What exactly does eagerly
> loaded mean in this case? Picture this:
>
> select a, bCol.b from A as a
> join a.bCol as bCol
>
> compared to this:
>
> select a from A as a
> join fetch a.bCol
>
> They both return all the child B entities (same number of "rows") but the
> second puts the B's into the appropriate a.bCol collection. In both cases,
> B's are being loaded. Is it the bCol collection you are referring to as
> being eagerly loaded? Sorry if I'm putting too fine a point on this, just
> trying to cement it all in my brain.
>
>

In the join fetch case the eager loading is a side effect of the query, the
entities on the right hand side are not part of the query results.

Another difference is that with a join fetch you can't set an identification
variable for the entities on the right hand side.
For example :
"select a from A join fetch a.bCol b" would throw an exception.

Having multiple references to the same entity from the left side of the
query is a side effect of this loading as far as I can tell.

I can't claim to be an expert here, I'm learning as I go. A lot of how we
handle joins seems a bit odd to me. Sorry if this isn't terribly
enlightening. The best reference I can give you is section 4.4.5 of the JPA
1.0 specification. Mike Keith's Pro EJB3 book is also a good place to look.

-mike

--
> Daryl Stultz
> _____________________________________
> 6 Degrees Software and Consulting, Inc.
> http://www.6degrees.com
> mailto:[hidden email]
>

Re: Eager fetch leads to out of bounds error

2009-11-05T11:27:23Z

On Thu, Nov 5, 2009 at 1:48 PM, Michael Dick <[hidden email]>wrote:

> On Thu, Nov 5, 2009 at 12:17 PM, Daryl Stultz <[hidden email]> wrote:
>
>
> I think I misunderstood your point (I thought the FETCH was implied).
>

I think I asked a new question, not necessarily based on your previous
input, so I don't think you misunderstood anything, I just changed the line
of questioning on you. :-)

>
> Adding in the fetch clause:
>
> A JOIN FETCH differs from a JOIN in two ways :
> * You will get one reference to the entity on the left side of the JOIN
> for every related entity on the right side of the JOIN.
>

This I misunderstood long ago before our discussion - I didn't misunderstand
what you were saying about it. I don't think. Anyway.

> * The relationship on the right side of the JOIN will be eagerly loaded.
>

This is what I'm having trouble with. If a JOIN would return the children,
isn't it implied that they are eagerly loaded? What exactly does eagerly
loaded mean in this case? Picture this:

select a, bCol.b from A as a
join a.bCol as bCol

compared to this:

select a from A as a
join fetch a.bCol

They both return all the child B entities (same number of "rows") but the
second puts the B's into the appropriate a.bCol collection. In both cases,
B's are being loaded. Is it the bCol collection you are referring to as
being eagerly loaded? Sorry if I'm putting too fine a point on this, just
trying to cement it all in my brain.

--
Daryl Stultz
_____________________________________
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:[hidden email]

Re: Eager fetch leads to out of bounds error

2009-11-05T10:48:40Z

On Thu, Nov 5, 2009 at 12:17 PM, Daryl Stultz <[hidden email]> wrote:

> On Thu, Nov 5, 2009 at 12:52 PM, Michael Dick <[hidden email]
> >wrote:
>
> > Can you give the 1.2.x patch attached to OPENJPA-894 a try? There are
> some
> > limitations with the approach I took (ie if Large Result Sets are used),
> > but
> > it'd be nice to know whether it works for you.
> >
>
> I'm pretty strapped for time, but I'll try to squeeze it in.
>
> LEFT JOINS should behave the same way..
>
>
> I was originally under the impression that JOIN FETCH was somehow different
> from a JOIN from an SQL/DB perspective, perhaps because of the bug. If the
> duplicates were returned, exactly how is JOIN different than JOIN FETCH?
> The
> latter returns the parent duplicated for each child along with each child
> AND populates each parent with the set of children? What is the difference
> between
>
> select o from A as o
> join o.bCol as bCol
>
> and
>
> select o from A as o
> join fetch o.bCol
>
> assuming duplicate bug is fixed?
>

I think I misunderstood your point (I thought the FETCH was implied).

A LEFT JOIN FETCH and a JOIN FETCH differ in that the LEFT JOIN FETCH is
more inclusive (ie you don't have to have a relation to the right side).

The same applies to a LEFT JOIN and a JOIN (no fetch).

Adding in the fetch clause:

A JOIN FETCH differs from a JOIN in two ways :
* You will get one reference to the entity on the left side of the JOIN
for every related entity on the right side of the JOIN.
* The relationship on the right side of the JOIN will be eagerly loaded.

LEFT JOIN FETCH and LEFT JOIN follow the same rules (but again the LEFT part
makes the results more inclusive).

Sorry for the confusion, I thought you were asking about the difference
between a JOIN FETCH and a LEFT JOIN FETCH. Not between a JOIN and a JOIN
FETCH.

> > In OpenJPA 1.2.1 if you want the duplicate references in your result list
> > then you're mostly out of luck.
>
>
> Fortunately I don't. But I don't want them to show up later because I
> forgot
> the "DISTINCT" keyword...
>

> > One ugly way to get them is to run the query
> > twice (the second time we operate in memory and return the correct
> > results).
> > If you don't want duplicate references then I _think_ it works out of the
> > box (until you run the query in memory . . .).
> >
>
> Meaning without the DISTINCT keyword? I should not get the duplicates now
> or
> in the future (after bugs fixed) if I include DISTINCT, right (assuming
> simple "select distinct o from A as o left join fetch o.bCol")?
>
>

Correct. Distinct should prevent duplicates now and in the future.

> --
> Daryl Stultz
> _____________________________________
> 6 Degrees Software and Consulting, Inc.
> http://www.6degrees.com
> mailto:[hidden email]
>

Re: Eager fetch leads to out of bounds error

2009-11-05T10:17:27Z

On Thu, Nov 5, 2009 at 12:52 PM, Michael Dick <[hidden email]>wrote:

> Can you give the 1.2.x patch attached to OPENJPA-894 a try? There are some
> limitations with the approach I took (ie if Large Result Sets are used),
> but
> it'd be nice to know whether it works for you.
>

I'm pretty strapped for time, but I'll try to squeeze it in.

LEFT JOINS should behave the same way..

I was originally under the impression that JOIN FETCH was somehow different
from a JOIN from an SQL/DB perspective, perhaps because of the bug. If the
duplicates were returned, exactly how is JOIN different than JOIN FETCH? The
latter returns the parent duplicated for each child along with each child
AND populates each parent with the set of children? What is the difference
between

select o from A as o
join o.bCol as bCol

and

select o from A as o
join fetch o.bCol

assuming duplicate bug is fixed?

> In OpenJPA 1.2.1 if you want the duplicate references in your result list
> then you're mostly out of luck.

Fortunately I don't. But I don't want them to show up later because I forgot
the "DISTINCT" keyword...

> One ugly way to get them is to run the query
> twice (the second time we operate in memory and return the correct
> results).
> If you don't want duplicate references then I _think_ it works out of the
> box (until you run the query in memory . . .).
>

Meaning without the DISTINCT keyword? I should not get the duplicates now or
in the future (after bugs fixed) if I include DISTINCT, right (assuming
simple "select distinct o from A as o left join fetch o.bCol")?

--
Daryl Stultz
_____________________________________
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:[hidden email]

Re: Eager fetch leads to out of bounds error

2009-11-05T09:52:24Z

On Thu, Nov 5, 2009 at 10:26 AM, Daryl Stultz <[hidden email]> wrote:

> On Thu, Nov 5, 2009 at 11:10 AM, Michael Dick <[hidden email]
> >wrote:
>
> > A JOIN FETCH will eagerly load the collection for you, but should return
> > one reference to the entity for each element in the collection. I'm
> > working on fixing this under OPENJPA-894 (proceeding slowly though).
>
>
> Yes, I discovered this bug a month or so ago which led me to change my
> approach for using fetch joins to modifying the fetch plan on the query.
> Now
> I've run into this other problem.
>

I was afraid of that. I haven't kept up with the mailing lists as well as
I'd like to. In any event you are hitting a bug in FetchPlans.. Just thought
I'd throw out the vendor agnostic solution in case you hadn't seen it.

Can you give the 1.2.x patch attached to OPENJPA-894 a try? There are some
limitations with the approach I took (ie if Large Result Sets are used), but
it'd be nice to know whether it works for you.

>
>
> > When it's all working you could use a query like this :
> > Query q = em.createQuery("SELECT DISTINCT o from A as o JOIN FETCH
> > o.bCol");
> >
> >
> So this doesn't work now? (Or is it simply that DISTINCT is not required on
> first pass due to the bug?)
>

The latter. DISTINCT is not required due to the bug.

> Should LEFT JOIN FETCH work the same way?
>

LEFT JOINS should behave the same way.. The only difference is that it will
return entities from the LEFT side which do not 'match' any entities on the
RIGHT side..

ie
SELECT m from Manager m LEFT JOIN FETCH m.employees
includes Managers with no employee.

SELECT m from Manager m JOIN FETCH m.employees
only returns Managers which have a an employee in the employees collection..

> I've experienced 894 directly but I don't fully understand 1365. If I have
> OpenJPA 1.2.1, what are my options?
>
>
OPENJPA-1365 is a change in the way we handle distinct results. Previously
we just added in the DISTINCT keyword to the SQL statement and relied on
that to return the correct results. This doesn't work if DISTINCT is applied
to multiple tables.

The best example is buried in a longish email I wrote to the dev mailing
list :
http://n2.nabble.com/How-should-we-handle-the-JPQL-DISTINCT-keyword-td3908400.html#a3908400

In OpenJPA 1.2.1 if you want the duplicate references in your result list
then you're mostly out of luck. One ugly way to get them is to run the query
twice (the second time we operate in memory and return the correct results).
If you don't want duplicate references then I _think_ it works out of the
box (until you run the query in memory . . .).

-mike

> Thanks.
>
> --
> Daryl Stultz
> _____________________________________
> 6 Degrees Software and Consulting, Inc.
> http://www.6degrees.com
> mailto:[hidden email]
>

Re: Eager fetch leads to out of bounds error

2009-11-05T08:26:30Z

On Thu, Nov 5, 2009 at 11:10 AM, Michael Dick <[hidden email]>wrote:

> A JOIN FETCH will eagerly load the collection for you, but should return
> one reference to the entity for each element in the collection. I'm
> working on fixing this under OPENJPA-894 (proceeding slowly though).

Yes, I discovered this bug a month or so ago which led me to change my
approach for using fetch joins to modifying the fetch plan on the query. Now
I've run into this other problem.

> When it's all working you could use a query like this :
> Query q = em.createQuery("SELECT DISTINCT o from A as o JOIN FETCH
> o.bCol");
>
>
So this doesn't work now? (Or is it simply that DISTINCT is not required on
first pass due to the bug?)
Should LEFT JOIN FETCH work the same way?

I've experienced 894 directly but I don't fully understand 1365. If I have
OpenJPA 1.2.1, what are my options?

Thanks.

--
Daryl Stultz
_____________________________________
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:[hidden email]

Re: Eager fetch leads to out of bounds error

2009-11-05T08:10:11Z

Hi Daryl,

A JOIN FETCH will eagerly load the collection for you, but should return one
reference to the entity for each element in the collection. I'm working on
fixing this under OPENJPA-894 (proceeding slowly though).

Adding a distinct clause will filter out these duplicates (but there are
issues there as well : OPENJPA-1365).

When it's all working you could use a query like this :
Query q = em.createQuery("SELECT DISTINCT o from A as o JOIN FETCH o.bCol");

If your goal is to selectively eagerly load a collection I believe this is
the vendor agnostic syntax you want..

Hope this helps,

-mike

On Wed, Nov 4, 2009 at 7:48 PM, Daryl Stultz <[hidden email]> wrote:

> On Wed, Nov 4, 2009 at 4:07 PM, Daryl Stultz <[hidden email]> wrote:
>
> > Hello,
> >
> > I'm wondering if anyone has seen something like this:
> >
> > <openjpa-1.2.1-r752877:753278 nonfatal general error>
> > org.apache.openjpa.persistence.PersistenceException: 5
> >
>
> I've run into this on 2 occasions with different fields in one entity. I
> can
> get around it in both cases by changing a fetch from EAGER to LAZY. So I
> have the entity A which has a collection of B which is set to LAZY. B has a
> field C that is set to EAGER. I retrieve like this:
>
> query = em.createQuery("select o from A as o");
> ((QueryImpl) query).getFetchPlan().addField(A.class, "bCol"); // bCol is
> collection of B
>
> The field B.c is defined like so
>
> @ManyToOne(fetch = FetchType.EAGER, optional = false)
> @JoinColumn(name = "cid", nullable = false)
> @ForeignKey
> private C c;
>
> This has also happened on another field of B that is nullable/optional.
>
> Right now the only way for me to feel the system is secure is to change
> everything to LAZY and put fetchPlan addFields all over. Please tell me I
> don't have to do that!
>
> Thanks.
>
> --
> Daryl Stultz
> _____________________________________
> 6 Degrees Software and Consulting, Inc.
> http://www.6degrees.com
> mailto:[hidden email]
>

Re: Eager fetch leads to out of bounds error

2009-11-04T17:48:57Z

On Wed, Nov 4, 2009 at 4:07 PM, Daryl Stultz <[hidden email]> wrote:

> Hello,
>
> I'm wondering if anyone has seen something like this:
>
> <openjpa-1.2.1-r752877:753278 nonfatal general error>
> org.apache.openjpa.persistence.PersistenceException: 5
>

I've run into this on 2 occasions with different fields in one entity. I can
get around it in both cases by changing a fetch from EAGER to LAZY. So I
have the entity A which has a collection of B which is set to LAZY. B has a
field C that is set to EAGER. I retrieve like this:

query = em.createQuery("select o from A as o");
((QueryImpl) query).getFetchPlan().addField(A.class, "bCol"); // bCol is
collection of B

The field B.c is defined like so

@ManyToOne(fetch = FetchType.EAGER, optional = false)
@JoinColumn(name = "cid", nullable = false)
@ForeignKey
private C c;

This has also happened on another field of B that is nullable/optional.

Right now the only way for me to feel the system is secure is to change
everything to LAZY and put fetchPlan addFields all over. Please tell me I
don't have to do that!

Thanks.

--
Daryl Stultz
_____________________________________
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:[hidden email]

Eager fetch leads to out of bounds error

2009-11-04T13:07:05Z

Hello,

I'm wondering if anyone has seen something like this:

<openjpa-1.2.1-r752877:753278 nonfatal general error>
org.apache.openjpa.persistence.PersistenceException: 5
at org.apache.openjpa.kernel.BrokerImpl.find(BrokerImpl.java:875)
at org.apache.openjpa.kernel.BrokerImpl.find(BrokerImpl.java:774)
at
org.apache.openjpa.jdbc.kernel.JDBCStoreManager.load(JDBCStoreManager.java:982)
at org.apache.openjpa.jdbc.sql.AbstractResult.load(AbstractResult.java:278)
at
org.apache.openjpa.jdbc.sql.SelectImpl$SelectResult.load(SelectImpl.java:2400)
at
org.apache.openjpa.jdbc.meta.strats.RelationFieldStrategy.loadEagerJoin(RelationFieldStrategy.java:541)
at
org.apache.openjpa.jdbc.meta.FieldMapping.loadEagerJoin(FieldMapping.java:807)
...snip
Caused by: java.lang.ArrayIndexOutOfBoundsException: 5
at
org.apache.openjpa.meta.ClassMetaData.getExtraFieldDataIndex(ClassMetaData.java:859)
at
org.apache.openjpa.jdbc.kernel.JDBCStoreManager.initializeState(JDBCStoreManager.java:358)
at
org.apache.openjpa.jdbc.kernel.JDBCStoreManager.initialize(JDBCStoreManager.java:278)
at
org.apache.openjpa.kernel.DelegatingStoreManager.initialize(DelegatingStoreManager.java:111)
at
org.apache.openjpa.kernel.ROPStoreManager.initialize(ROPStoreManager.java:57)
at org.apache.openjpa.kernel.BrokerImpl.initialize(BrokerImpl.java:894)
at org.apache.openjpa.kernel.BrokerImpl.find(BrokerImpl.java:852)
... 78 more

I'm running a query thathas a particular field added to the fetch group for
the query, something like this:

((QueryImpl) query).getFetchPlan().addField(A.class, "funkyField");

There error doesn't happen with all data sets and it doesn't happen with
other fields on the same query/class. Anyone have any clue? What is the
significance of the "5"? Can I use that as the index of field names into a
class or something?

Is there a better way to prefetch fields? (In this case a collection). Is
there a JPA (i.e. non-OpenJPA-specific) way to prefetch collections? Perhaps
I just have a major misunderstanding of fetching again.

Thanks.

--
Daryl Stultz
_____________________________________
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:[hidden email]

Rollback - Transaction issue

2009-11-03T02:06:43Z

Hey,
Is there any way to "replay" transaction?
I mean, sometimes I get RollbackException and rollback the transaction. Can I then "clone" the transaction and try again, or once rollback is called, transaction is lost?
I really need the changes, and really don't want to trace every change for rerunning later...

thanks,
udi

Re: Query not getting evicted from QueryCache

2009-11-03T20:23:24Z

Catalina,

1. This is how I enabled DataCache and QueryCache:
<property name="openjpa.QueryCache" value="true"/>
<property name="openjpa.DataCache" value="true"/>
2. The same application that updates RelationshipInfo also issues the
query.
3. This is how the Query is created:

Query query = entityManager.createQuery(queryStmt);

Here is the stacktrace:

org.apache.openjpa.kernel.QueryImpl.<init>(org.apache.openjpa.kernel.Broker,
java.lang.String, org.apache.openjpa.kernel.StoreQuery) line: 132
org.apache.openjpa.kernel.FinalizingBrokerImpl(org.apache.openjpa.kernel.BrokerImpl).newQueryImpl(java.lang.String,
org.apache.openjpa.kernel.StoreQuery) line: 3519
org.apache.openjpa.kernel.FinalizingBrokerImpl(org.apache.openjpa.kernel.BrokerImpl).newQuery(java.lang.String,
java.lang.Object) line: 3496
org.apache.openjpa.kernel.DelegatingBroker.newQuery(java.lang.String,
java.lang.Object) line: 1225
org.apache.openjpa.persistence.EntityManagerImpl.createQuery(java.lang.String,
java.lang.String) line: 870
org.apache.openjpa.persistence.EntityManagerImpl.createQuery(java.lang.String)
line: 865
org.apache.openjpa.persistence.EntityManagerImpl.createQuery(java.lang.String)
line: 1

queryStmt =
"SELECT distinct
OPERATINGSYSTEM1.OID,OPERATINGSYSTEM1.Guid,OPERATINGSYSTEM1.ObjectType,OPERATINGSYSTEM1.Name,REMOTESERVICEACCESSPOINT1.OID,REMOTESERVICEACCESSPOINT1.Guid,REMOTESERVICEACCESSPOINT1.ObjectType,REMOTESERVICEACCESSPOINT1.Name
FROM OperatingSystem
OPERATINGSYSTEM1,System_accessedVia_RemoteServiceAccessPoint
SYSTEM_ACCESSEDVIA_REMOTESERVICEACCESSPOINT1,RemoteServiceAccessPoint
REMOTESERVICEACCESSPOINT1,RelationshipInfo RELATIONSHIPINFO1 WHERE
OPERATINGSYSTEM1.OID = SYSTEM_ACCESSEDVIA_REMOTESERVICEACCESSPOINT1.sourceId
AND REMOTESERVICEACCESSPOINT1.OID =
SYSTEM_ACCESSEDVIA_REMOTESERVICEACCESSPOINT1.targetId AND
(OPERATINGSYSTEM1.Guid = ?1) AND (OPERATINGSYSTEM1.OID = ?2) AND
((OPERATINGSYSTEM1.BuildNumber = ?3)) AND (REMOTESERVICEACCESSPOINT1.Guid =
?4) AND (REMOTESERVICEACCESSPOINT1.OID = ?5) AND
((REMOTESERVICEACCESSPOINT1.Port = ?6)) AND RELATIONSHIPINFO1.changedDate >
?7 and RELATIONSHIPINFO1.sourceOID=OPERATINGSYSTEM1.OID and
RELATIONSHIPINFO1.relationshipType = ?8 and
RELATIONSHIPINFO1.targetOID=REMOTESERVICEACCESSPOINT1.OID"

Then parameters are set on the Query after it is created.

Thanks,

Jeff

On Mon, Nov 2, 2009 at 2:01 PM, catalina wei <[hidden email]> wrote:

> Jeff,
> Could you provide more info :
> 1. in persistence.xml, show us how you enable DataCache and QueryCache.
> 2. the updates to RelationshipInfo, is that done by the same application
> that issued the query ? or some other application ?
> 3. Could you show the code fragment that issues em.createQuery ?
>
> Thanks.
> Catalina
>
> On Mon, Nov 2, 2009 at 10:15 AM, Jeff Awe <[hidden email]> wrote:
>
> > I'm running on OpenJPA 1.2.1
> >
> > The following query is added to the QueryCache:
> >
> > Query: org.apache.openjpa.kernel.QueryImpl@3afe3afe;
> > candidate class: class com.ibm.usmi.datamodel.system.OperatingSystem;
> > query: SELECT distinct
> >
> >
> OPERATINGSYSTEM1.OID,OPERATINGSYSTEM1.Guid,OPERATINGSYSTEM1.ObjectType,OPERATINGSYSTEM1.Name,REMOTESERVICEACCESSPOINT1.OID,REMOTESERVICEACCESSPOINT1.Guid,REMOTESERVICEACCESSPOINT1.ObjectType,REMOTESERVICEACCESSPOINT1.Name
> > FROM OperatingSystem
> > OPERATINGSYSTEM1,System_accessedVia_RemoteServiceAccessPoint
> > SYSTEM_ACCESSEDVIA_REMOTESERVICEACCESSPOINT1,RemoteServiceAccessPoint
> > REMOTESERVICEACCESSPOINT1,RelationshipInfo RELATIONSHIPINFO1 WHERE
> > OPERATINGSYSTEM1.OID =
> > SYSTEM_ACCESSEDVIA_REMOTESERVICEACCESSPOINT1.sourceId
> > AND REMOTESERVICEACCESSPOINT1.OID =
> > SYSTEM_ACCESSEDVIA_REMOTESERVICEACCESSPOINT1.targetId AND
> > (OPERATINGSYSTEM1.Guid = ?1) AND (OPERATINGSYSTEM1.OID = ?2) AND
> > ((OPERATINGSYSTEM1.BuildNumber = ?3)) AND (REMOTESERVICEACCESSPOINT1.Guid
> =
> > ?4) AND (REMOTESERVICEACCESSPOINT1.OID = ?5) AND
> > ((REMOTESERVICEACCESSPOINT1.Port = ?6)) AND RELATIONSHIPINFO1.changedDate
> >
> > ?7 and RELATIONSHIPINFO1.sourceOID=OPERATINGSYSTEM1.OID and
> > RELATIONSHIPINFO1.relationshipType = ?8 and
> > RELATIONSHIPINFO1.targetOID=REMOTESERVICEACCESSPOINT1.OID
> >
> > Later on, a record in RelationshipInfo is changed, which changes what
> > should
> > be returned from this query. I'd expect this to cause the cached query
> to
> > get evicted from the QueryCache, but it is not. If I get the
> > QueryResultCache, and evictAll RelationshipInfo.class, it still doesn't
> get
> > removed. This seems to be because the AccessPath only contains
> > OperatingSystem. I'd expect this to contain all entities that this query
> > deals with:
> > {OperatingSystem,
> > System_accessedVia_RemoteServiceAccessPoint, RemoteServiceAccessPoint,
> > RelationshipInfo}
> > But the AccessPath only seems to contain the entity of what is returned
> > from
> > the query.
> >
> > What do I need to do so this query gets evicted like I'd expect.
> >
> > Thanks - Jeff
> >
>

Re: Query not getting evicted from QueryCache

2009-11-02T12:01:49Z

Jeff,
Could you provide more info :
1. in persistence.xml, show us how you enable DataCache and QueryCache.
2. the updates to RelationshipInfo, is that done by the same application
that issued the query ? or some other application ?
3. Could you show the code fragment that issues em.createQuery ?

Thanks.
Catalina

On Mon, Nov 2, 2009 at 10:15 AM, Jeff Awe <[hidden email]> wrote:

> I'm running on OpenJPA 1.2.1
>
> The following query is added to the QueryCache:
>
> Query: org.apache.openjpa.kernel.QueryImpl@3afe3afe;
> candidate class: class com.ibm.usmi.datamodel.system.OperatingSystem;
> query: SELECT distinct
>
> OPERATINGSYSTEM1.OID,OPERATINGSYSTEM1.Guid,OPERATINGSYSTEM1.ObjectType,OPERATINGSYSTEM1.Name,REMOTESERVICEACCESSPOINT1.OID,REMOTESERVICEACCESSPOINT1.Guid,REMOTESERVICEACCESSPOINT1.ObjectType,REMOTESERVICEACCESSPOINT1.Name
> FROM OperatingSystem
> OPERATINGSYSTEM1,System_accessedVia_RemoteServiceAccessPoint
> SYSTEM_ACCESSEDVIA_REMOTESERVICEACCESSPOINT1,RemoteServiceAccessPoint
> REMOTESERVICEACCESSPOINT1,RelationshipInfo RELATIONSHIPINFO1 WHERE
> OPERATINGSYSTEM1.OID =
> SYSTEM_ACCESSEDVIA_REMOTESERVICEACCESSPOINT1.sourceId
> AND REMOTESERVICEACCESSPOINT1.OID =
> SYSTEM_ACCESSEDVIA_REMOTESERVICEACCESSPOINT1.targetId AND
> (OPERATINGSYSTEM1.Guid = ?1) AND (OPERATINGSYSTEM1.OID = ?2) AND
> ((OPERATINGSYSTEM1.BuildNumber = ?3)) AND (REMOTESERVICEACCESSPOINT1.Guid =
> ?4) AND (REMOTESERVICEACCESSPOINT1.OID = ?5) AND
> ((REMOTESERVICEACCESSPOINT1.Port = ?6)) AND RELATIONSHIPINFO1.changedDate >
> ?7 and RELATIONSHIPINFO1.sourceOID=OPERATINGSYSTEM1.OID and
> RELATIONSHIPINFO1.relationshipType = ?8 and
> RELATIONSHIPINFO1.targetOID=REMOTESERVICEACCESSPOINT1.OID
>
> Later on, a record in RelationshipInfo is changed, which changes what
> should
> be returned from this query. I'd expect this to cause the cached query to
> get evicted from the QueryCache, but it is not. If I get the
> QueryResultCache, and evictAll RelationshipInfo.class, it still doesn't get
> removed. This seems to be because the AccessPath only contains
> OperatingSystem. I'd expect this to contain all entities that this query
> deals with:
> {OperatingSystem,
> System_accessedVia_RemoteServiceAccessPoint, RemoteServiceAccessPoint,
> RelationshipInfo}
> But the AccessPath only seems to contain the entity of what is returned
> from
> the query.
>
> What do I need to do so this query gets evicted like I'd expect.
>
> Thanks - Jeff
>

Query not getting evicted from QueryCache

2009-11-02T10:15:04Z

I'm running on OpenJPA 1.2.1

The following query is added to the QueryCache:

Query: org.apache.openjpa.kernel.QueryImpl@3afe3afe;
candidate class: class com.ibm.usmi.datamodel.system.OperatingSystem;
query: SELECT distinct
OPERATINGSYSTEM1.OID,OPERATINGSYSTEM1.Guid,OPERATINGSYSTEM1.ObjectType,OPERATINGSYSTEM1.Name,REMOTESERVICEACCESSPOINT1.OID,REMOTESERVICEACCESSPOINT1.Guid,REMOTESERVICEACCESSPOINT1.ObjectType,REMOTESERVICEACCESSPOINT1.Name
FROM OperatingSystem
OPERATINGSYSTEM1,System_accessedVia_RemoteServiceAccessPoint
SYSTEM_ACCESSEDVIA_REMOTESERVICEACCESSPOINT1,RemoteServiceAccessPoint
REMOTESERVICEACCESSPOINT1,RelationshipInfo RELATIONSHIPINFO1 WHERE
OPERATINGSYSTEM1.OID = SYSTEM_ACCESSEDVIA_REMOTESERVICEACCESSPOINT1.sourceId
AND REMOTESERVICEACCESSPOINT1.OID =
SYSTEM_ACCESSEDVIA_REMOTESERVICEACCESSPOINT1.targetId AND
(OPERATINGSYSTEM1.Guid = ?1) AND (OPERATINGSYSTEM1.OID = ?2) AND
((OPERATINGSYSTEM1.BuildNumber = ?3)) AND (REMOTESERVICEACCESSPOINT1.Guid =
?4) AND (REMOTESERVICEACCESSPOINT1.OID = ?5) AND
((REMOTESERVICEACCESSPOINT1.Port = ?6)) AND RELATIONSHIPINFO1.changedDate >
?7 and RELATIONSHIPINFO1.sourceOID=OPERATINGSYSTEM1.OID and
RELATIONSHIPINFO1.relationshipType = ?8 and
RELATIONSHIPINFO1.targetOID=REMOTESERVICEACCESSPOINT1.OID

Later on, a record in RelationshipInfo is changed, which changes what should
be returned from this query. I'd expect this to cause the cached query to
get evicted from the QueryCache, but it is not. If I get the
QueryResultCache, and evictAll RelationshipInfo.class, it still doesn't get
removed. This seems to be because the AccessPath only contains
OperatingSystem. I'd expect this to contain all entities that this query
deals with:
{OperatingSystem,
System_accessedVia_RemoteServiceAccessPoint, RemoteServiceAccessPoint,
RelationshipInfo}
But the AccessPath only seems to contain the entity of what is returned from
the query.

What do I need to do so this query gets evicted like I'd expect.

Thanks - Jeff

OptimisticLockException problem

2009-11-02T01:27:16Z

Hey,
My application have few EntityManagers.
Each EM, works on a different Thread.
I configured openjpa.Optimistic to false and openjpa.Multithreaded to true. (Though Im not sure its related)
I get the following exception (sorry for not pasting the full stack... I just can't):

org.apache.openjpa.persistence.OptimisticLockException: an optimistic lock violation was detected when flushing objects instance "bla.A-110" to the data store. This indicates that the object was cocurrently modified in another transaction.
failed object:
bla.A-bla.A-110
at or.apache...BatchingPreparedStatementManagerImpl.checkUpdateCount(284)
...
...

How can I get this concurrent modification if any EM uses different thread and connection?

I'm using OpenJPA 1.2.0, btw...

Thanks,
Udi

Re: Maven dependencies in 1.3.0-SNAPSHOT

2009-11-02T13:10:19Z

I'll have to take a look at it. I my have broken something when
switching the aggregate JAR assemblies (openjpa.jar and openjpa-all.jar)
over to use the shade plugin, instead of manual Ant steps...

-Donald

Laird Nelson wrote:

> Perhaps it's just me, but I noticed that all of a sudden dependencies like
> commons-lang and serp are not being pulled down when I depend on
> <artifactId>openjpa</artifactId> (I cleaned my local repository of OpenJPA
> artifacts, and after rebuilding, my build fails, saying that it cannot find
> classes that would be present if commons-lang and serp were pulled down).
> Was a change made? I noticed that in the openjpa POM they are listed as
> <scope>provided</scope>, which indicates they should be present, yes?
>
> Best,
> Laird
>

Maven dependencies in 1.3.0-SNAPSHOT

2009-10-31T12:37:55Z

Perhaps it's just me, but I noticed that all of a sudden dependencies like
commons-lang and serp are not being pulled down when I depend on
<artifactId>openjpa</artifactId> (I cleaned my local repository of OpenJPA
artifacts, and after rebuilding, my build fails, saying that it cannot find
classes that would be present if commons-lang and serp were pulled down).
Was a change made? I noticed that in the openjpa POM they are listed as
<scope>provided</scope>, which indicates they should be present, yes?

Best,
Laird

Re: Select NEW Issues

2009-10-30T19:19:07Z

Hi,
JPQL implementation of OpenJPA 1.3 (or before) had this limitation: if you specify a NEW in select projection then rest of the projection clauses are silently ignore.
This is in agreement with your observation.
The good news is, the latest version of OpenJPA does not have any such restriction.

Pinaki

dharga wrote:

So I'm pretty new to using OpenJPA so this might be a simple fix...

I'm doing the following query.

select new com.bcbst.odstats.ejb.beans.RangeStats(count(a), avg(a.loadTime))
FROM ODUsage a
WHERE
a.accessDate BETWEEN :startDate AND :endDate and
a.loadTime is not NULL

I've noticed the following. If I remove the AVG aggregation function (and change the RangeStats constructor accordingly) it works fine in all cases.

The whole function is here.
http://aluink.pastebin.com/m49bbacb8

The RangeStats class is here
http://aluink.pastebin.com/m54beb0d

When I try to loop and do several queries I get this error. http://aluink.pastebin.com/m164f3d96

I've also noticed that if do the query just once with static :startDate and :endDate parameter values it works fine. If I run a loop over a date range which includes the static date previously used, it fails.

The end goal is to reproduce the following transact-sql query and have the values in somekind of bean. I really don't like the idea of doing multiple queries, but have yet to find a better solution. I'm open to idea.

SELECT count(*), avg(loadTime), month(accessDate)
FROM Table
WHERE
accessDate BETWEEN :startDate AND :endDate
GROUP BY month(accessDate)

TIA!

Pinaki

Select NEW Issues

2009-10-30T12:54:49Z

So I'm pretty new to using OpenJPA so this might be a simple fix...

I'm doing the following query.

select new com.bcbst.odstats.ejb.beans.RangeStats(count(a), avg(a.loadTime))
FROM ODUsage a
WHERE
a.accessDate BETWEEN :startDate AND :endDate and
a.loadTime is not NULL

I've noticed the following. If I remove the AVG aggregation function (and change the RangeStats constructor accordingly) it works fine in all cases.

The whole function is here.
http://aluink.pastebin.com/m49bbacb8

The RangeStats class is here
http://aluink.pastebin.com/m54beb0d

When I try to loop and do several queries I get this error. http://aluink.pastebin.com/m164f3d96

I've also noticed that if do the query just once with static :startDate and :endDate parameter values it works fine. If I run a loop over a date range which includes the static date previously used, it fails.

The end goal is to reproduce the following transact-sql query and have the values in somekind of bean. I really don't like the idea of doing multiple queries, but have yet to find a better solution. I'm open to idea.

SELECT count(*), avg(loadTime), month(accessDate)
FROM Table
WHERE
accessDate BETWEEN :startDate AND :endDate
GROUP BY month(accessDate)

TIA!