eclipselink-users http://dev.eclipse.org/mhonarc/lists/eclipselink-users/maillist.html eclipselink-users en-us Tue, 22 May 2012 13:40:43 GMT Tue, 22 May 2012 13:40:43 GMT http://blogs.law.harvard.edu/tech/rss MHonArc RSS 2.0 RCFile webmaster@eclipse.org (Webmaster) webmaster@eclipse.org (Webmaster) eclipselink-users http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpg http://dev.eclipse.org/mhonarc/lists/eclipselink-users/maillist.html Re: [eclipselink-users] Greetings and Questions http://dev.eclipse.org/mhonarc/lists/eclipselink-users/msg07142.html _______________________________________________ eclipselink-users mailing list eclipselink-users@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipselink-users Vaidya, Hi, in partial answer to your question for the OOME. I have seen this occur in large batch inserts of over 100k records and in non-ORM code in general when the heap is exhausted. Launch JVisualVM and check that your heap stays under 70% so the GC does not kick in continously - you will see a performance increase. The likely reason you see the OOME only when running EclipseLink in the war is because the war runs in a lower classloader than the server lib and may have a different heap size. Likely the -Xmx setting on the server is higher. Try adding -server to enable a variable heap (like the JRockit JVM) among other things and set your -Xmx to double your max heap usage. For the "not null" exception, verify that for the attributes that support it - add nullable=true for those that accept null values. Otherwise the null error is normal and expected where an attribute is not set - where it should be. Thank you /michael -----Original Message----- From: eclipselink-users-bounces@xxxxxxxxxxx [mailto:eclipselink-users-bounces@xxxxxxxxxxx] On Behalf Of Tom Ware Sent: Tuesday, May 22, 2012 9:20 AM To: eclipselink-users@xxxxxxxxxxx Subject: Re: [eclipselink-users] Greetings and Questions Hi Nathan, The number of bugs fixed between EclipseLink 1.1.1 and EclipseLink 2.3.2 is very high. Hopefully we can help you get set up to try 2.3.3 to confirm whether or not the issue you are seeing is fixed. I won't claim to be a JBoss expert, but generally, in application servers, we suggest putting EclipseLink in some kind of shared library. The following wiki page provides some details of working with EclipseLink in JBoss and it suggests putting the EclipseLink libraries in either server/default/lib or common/lib. I'll see if I can find an alternate suggestion. http://wiki.eclipse.org/EclipseLink/Examples/JPA/JBoss_Web_Tutorial Is there any additional information you can provide about the out of memory error? I know that in JBoss 5.1 they had a fairly serious bug related to byte code weaving - one that we should be able to work around if it is the issue. -Tom On 21/05/2012 1:18 PM, vaidya nathan wrote: > Hi Eclipselink users, > > We are in the process of migrating from hibernate to eclipselink in > our project and we are running into some issues. Our setup is an > application ear (APP.ear) jboss 5.1.0 GA with 2 wars - A.war and > B.war. We want to use eclipselink 1.1.1 to start with but we found an > issue with embeddables > 1. We have a class D.java which contains an embedded object E.java . > E.java extends Ebase.java and Ebase.java has some mandatory properties > prop1 and prop2. All these are declared in the persistence.xml. When > we are trying to insert D.java objects with the prop1 and prop2 > populated it is not creating insert statements for the two properties > because of which the insert fails > Caused by: com.ibm.db2.jcc.b.lm: Assignment of a NULL value to a NOT > NULL column "TBSPACEID=2, TABLEID=3346, COLNO=5" is not allowed.. > SQLCODE=-407, SQLSTATE=23502, DRIVER=3.50.152 > > So we switched from eclipselink 1.1.1 to eclipselink 2.3.2 - The first > issue that we noticed was that if the eclipselink 2.3.2 jar were to be > in the war we get an out of memory issue . We then tried to package it > in the ear with the same result (Out of memory). So we added it to the > server/default/lib and then it deployed and also we were able to > insert into the D.java table. > > So i have two questions for this group > 1. Was this a bug with embeddables that was fixed subsequently > 2. Putting it in server/default/lib though not a very good idea is > helping us proceed with development. Why are we getting the out of > memory error as soon as we include the eclipselink 2.3.2 jars in the > ear (either in the lib or the war directory). > 3. Is this all because we are using jboss 5.1.0 which is loading > hibernate in its classpath when loading and thats why #2 works . > > > Thx > Vaidya > _______________________________________________ > eclipselink-users mailing list > eclipselink-users@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/eclipselink-users _______________________________________________ eclipselink-users mailing list eclipselink-users@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipselink-users ]]> Tue, 22 May 2012 13:31:44 GMT http://dev.eclipse.org/mhonarc/lists/eclipselink-users/msg07142.html Michael.F.Obrien@xxxxxxx (Michael O'Brien) Re: [eclipselink-users] Greetings and Questions http://dev.eclipse.org/mhonarc/lists/eclipselink-users/msg07141.html Hi Nathan,
The number of bugs fixed between EclipseLink 1.1.1 and EclipseLink 2.3.2 is very high. Hopefully we can help you get set up to try 2.3.3 to confirm whether or not the issue you are seeing is fixed.

I won't claim to be a JBoss expert, but generally, in application servers, we suggest putting EclipseLink in some kind of shared library. The following wiki page provides some details of working with EclipseLink in JBoss and it suggests putting the EclipseLink libraries in either server/default/lib or common/lib. I'll see if I can find an alternate suggestion.

http://wiki.eclipse.org/EclipseLink/Examples/JPA/JBoss_Web_Tutorial

Is there any additional information you can provide about the out of memory error? I know that in JBoss 5.1 they had a fairly serious bug related to byte code weaving - one that we should be able to work around if it is the issue.

-Tom

On 21/05/2012 1:18 PM, vaidya nathan wrote: 
Hi Eclipselink users,

We are in the process of migrating from hibernate to eclipselink in
our project and we are running into some issues. Our setup is an
application ear (APP.ear) jboss 5.1.0 GA with 2 wars - A.war and
B.war. We want to use eclipselink 1.1.1 to start with but we found an
issue with embeddables
1. We have a class D.java which contains an embedded object E.java .
E.java extends Ebase.java and Ebase.java has some mandatory properties
prop1 and prop2. All these are declared in the persistence.xml. When
we are trying to insert D.java objects with the prop1 and prop2
populated it is not creating insert statements for the two properties
because of which the insert fails
Caused by: com.ibm.db2.jcc.b.lm: Assignment of a NULL value to a NOT
NULL column "TBSPACEID=2, TABLEID=3346, COLNO=5" is not allowed..
SQLCODE=-407, SQLSTATE=23502, DRIVER=3.50.152

So we switched from eclipselink 1.1.1 to eclipselink 2.3.2 - The first
issue that we noticed was that if the eclipselink 2.3.2 jar were to be
in the war we get an out of memory issue . We then tried to package it
in the ear with the same result (Out of memory). So we added it to the
server/default/lib and then it deployed and also we were able to
insert into the D.java table.

So i have two questions for this group
1. Was this a bug with embeddables that was fixed subsequently
2. Putting it in server/default/lib though not a very good idea is
helping us proceed with development. Why are we getting the out of
memory error as soon as we include the eclipselink 2.3.2 jars in the
ear (either in the lib or the war directory).
3. Is this all because we are using jboss 5.1.0 which is loading
hibernate in its classpath when loading and thats why #2 works .


Thx
Vaidya
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users

]]> Tue, 22 May 2012 13:20:14 GMT http://dev.eclipse.org/mhonarc/lists/eclipselink-users/msg07141.html tom.ware@xxxxxxx (Tom Ware) Re: [eclipselink-users] Cannot get the JPQL & SQL String of a CriteriaQuery http://dev.eclipse.org/mhonarc/lists/eclipselink-users/msg07140.html Hi Antonio,
EclipseLink will not translate a Criteria query into JPQL for you. The getJPQLString() method will only work for queries originally written in JPQL.

The getSQLString() method relies on the query being "prepared" as indicated in the comment for that method. One you have run the query once, it will be prepared. Alternately, you should be able to call prepareCall, or prepareCalls on it to cause it to prepare.

-Tom

On 21/05/2012 9:17 AM, Antonio Goncalves wrote: 
Hi all,

I need to get the JPQL and/or SQL String of a type safe query... but I can't
make it work. Let's take a simple example : find all the Book entities. Here is
what I can do with a simple dynamic query :

TypedQuery<Book> findAllBooksQuery = em.createQuery("SELECT b FROM Book b ORDER
BY b.id <http://b.id> DESC", Book.class);
System.out.println("JPQL " +
findAllBooksQuery.unwrap(EJBQueryImpl.class).getDatabaseQuery().getJPQLString());
System.out.println("SQL " +
findAllBooksQuery.unwrap(EJBQueryImpl.class).getDatabaseQuery().getSQLString());

As you can see, I use the unwrap(EJBQueryImpl.class) method to get the needed
string. And this works fine. But if I do the following, I get a null (for both
JPQL and SQL String) :

CriteriaBuilder cb = em.getCriteriaBuilder();
CriteriaQuery<Book> q = cb.createQuery(Book.class);
Root<Book> b = q.from(Book.class);
q.select(b).orderBy(cb.desc(b.get("id")));
TypedQuery<Book> findAllBooksCriteriaQuery = em.createQuery(q);
System.out.println("JPQL " +
findAllBooksCriteriaQuery.unwrap(EJBQueryImpl.class).getDatabaseQuery().getJPQLString());
System.out.println("SQL " +
findAllBooksCriteriaQuery.unwrap(EJBQueryImpl.class).getDatabaseQuery().getSQLString());

Any idea what this happens ? I am using the right implementation (i.e.
EJBQueryImpl) ?

Thanks
Antonio


_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users

]]> Tue, 22 May 2012 12:57:55 GMT http://dev.eclipse.org/mhonarc/lists/eclipselink-users/msg07140.html tom.ware@xxxxxxx (Tom Ware) [eclipselink-users] Greetings and Questions http://dev.eclipse.org/mhonarc/lists/eclipselink-users/msg07139.html Hi Eclipselink users, We are in the process of migrating from hibernate to eclipselink in our project and we are running into some issues. Our setup is an application ear (APP.ear) jboss 5.1.0 GA with 2 wars - A.war and B.war. We want to use eclipselink 1.... Hi Eclipselink users, We are in the process of migrating from hibernate to eclipselink in our project and we are running into some issues. Our setup is an application ear (APP.ear) jboss 5.1.0 GA with 2 wars - A.war and B.war. We want to use eclipselink 1.1.1 to start with but we found an issue with embeddables 1. We have a class D.java which contains an embedded object E.java . E.java extends Ebase.java and Ebase.java has some mandatory properties prop1 and prop2. All these are declared in the persistence.xml. When we are trying to insert D.java objects with the prop1 and prop2 populated it is not creating insert statements for the two properties because of which the insert fails Caused by: com.ibm.db2.jcc.b.lm: Assignment of a NULL value to a NOT NULL column "TBSPACEID=2, TABLEID=3346, COLNO=5" is not allowed.. SQLCODE=-407, SQLSTATE=23502, DRIVER=3.50.152 So we switched from eclipselink 1.1.1 to eclipselink 2.3.2 - The first issue that we noticed was that if the eclipselink 2.3.2 jar were to be in the war we get an out of memory issue . We then tried to package it in the ear with the same result (Out of memory). So we added it to the server/default/lib and then it deployed and also we were able to insert into the D.java table. So i have two questions for this group 1. Was this a bug with embeddables that was fixed subsequently 2. Putting it in server/default/lib though not a very good idea is helping us proceed with development. Why are we getting the out of memory error as soon as we include the eclipselink 2.3.2 jars in the ear (either in the lib or the war directory). 3. Is this all because we are using jboss 5.1.0 which is loading hibernate in its classpath when loading and thats why #2 works . Thx Vaidya ]]> Mon, 21 May 2012 17:18:43 GMT http://dev.eclipse.org/mhonarc/lists/eclipselink-users/msg07139.html vaidyaatdst@xxxxxxx (vaidya nathan) [eclipselink-users] Cannot get the JPQL & SQL String of a CriteriaQuery http://dev.eclipse.org/mhonarc/lists/eclipselink-users/msg07138.html Hi all, I need to get the&#xA0;JPQL and/or SQL String of a type safe query... but I can&#39;t make it work. Let&#39;s take a simple example : find all the Book entities. Here is what I can do with a simple dynamic query : TypedQuery&lt;Book&gt; findAllBooksQuery = em.createQ...
I need to get the JPQL and/or SQL String of a type safe query... but I can't make it work. Let's take a simple example : find all the Book entities. Here is what I can do with a simple dynamic query :

TypedQuery<Book> findAllBooksQuery = em.createQuery("SELECT b FROM Book b ORDER BY b.id DESC", Book.class);
System.out.println("JPQL " + findAllBooksQuery.unwrap(EJBQueryImpl.class).getDatabaseQuery().getJPQLString());
System.out.println("SQL  " + findAllBooksQuery.unwrap(EJBQueryImpl.class).getDatabaseQuery().getSQLString());

As you can see, I use the unwrap(EJBQueryImpl.class) method to get the needed string. And this works fine. But if I do the following, I get a null (for both JPQL and SQL String) :

CriteriaBuilder cb = em.getCriteriaBuilder();
CriteriaQuery<Book> q = cb.createQuery(Book.class);
Root<Book> b = q.from(Book.class);
q.select(b).orderBy(cb.desc(b.get("id")));
TypedQuery<Book> findAllBooksCriteriaQuery = em.createQuery(q);
System.out.println("JPQL " + findAllBooksCriteriaQuery.unwrap(EJBQueryImpl.class).getDatabaseQuery().getJPQLString());
System.out.println("SQL  " + findAllBooksCriteriaQuery.unwrap(EJBQueryImpl.class).getDatabaseQuery().getSQLString());

Any idea what this happens ? I am using the right implementation (i.e. EJBQueryImpl) ?

Thanks
Antonio
]]> Mon, 21 May 2012 13:17:49 GMT http://dev.eclipse.org/mhonarc/lists/eclipselink-users/msg07138.html antonio.mailing@xxxxxxx (Antonio Goncalves) Re: [eclipselink-users] batch loading of single object reporting that query is not a single object http://dev.eclipse.org/mhonarc/lists/eclipselink-users/msg07137.html ----- http://wiki.eclipse.org/User:James.sutherland.oracle.com James Sutherland http://www.eclipse.org/eclipselink/ EclipseLink , http://www.oracle.com/technology/products/ias/toplink/ TopLink Wiki: http://wiki.eclipse.org/EclipseLink EclipseLink , http:/... James, Thank you - that JPQL worked - and I've got that "Doh!" feeling. Here is the mapping Story is @Entity @Table(name="STORY") public class Story { @Id @Column(name = "ID") private int id; @Column(name = "NAME", length = 255) private String name; @OneToMany(cascade = CascadeType.ALL, fetch = FetchType.LAZY) @JoinColumn(name = "STORY_ID", nullable = false) @OrderColumn(name = "REVISION") private List<Scenario> scenarios = new ArrayList<Scenario>(); } Scenario is @Entity @Table(name="SCENARIO") public class Scenario { @Id @Column(name = "ID") private int id; @ManyToOne @JoinColumn(name = "STORY_ID", updatable = false, nullable = false) private Story story; @Column(name = "NAME", length = 255) private String name; @ElementCollection(fetch = FetchType.LAZY) @CollectionTable(name = "SCENARIO_TAG", joinColumns = @JoinColumn(name = "SCENARIO_ID")) @OrderColumn(name="SEQUENCE") @Column(name = "TAG", length = 4000) private List<String> tags = new ArrayList<String>(); } I'll look into the QueryKey on the REVISION column. Thanks a ton!!! Brian ----- Original message ----- From: James Sutherland <jamesssss@xxxxxxxxx> To: eclipselink-users@xxxxxxxxxxx Subject: Re: [eclipselink-users] batch loading of single object reporting that query is not a single object Date: Thu, 17 May 2012 06:55:21 -0700 (PDT) You could try, select sc from Scenario sc, Story s JOIN s.scenarios sc2 WHERE s.id = :st oryId and sc = sc2 order by index(sc2) asc How is scenarios mapped, does it use a JoinTable? If it doesn't then you could probably also just add a QueryKey for the index field, or even map it in Scenario. BrianRepko wrote: > > I have 2 Entities > * Story, which has a 1-to-many ordered bidirectional > relationship with > * Scenario, which has an ElementCollection of tags (a List > element collection) > > I want to write a query that returns the Scenarios for a given > Story ID, however, I want the ability to limit the number of > results AND to batch/pre-load the Scenario tags. > > When I run the following: > em.getTransaction().begin(); > String jpql = "select sc from Story s JOIN s.scenarios sc WHERE s.id = :st > oryId order by index(sc) asc"; > TypedQuery<Scenario> query = em.createQuery(jpql, Scenario.class); > query.setParameter("storyId", 2); > query.setFirstResult(0); > query.setMaxResults(15); > query.setHint(QueryHints.BATCH, "sc.tags"); > query.setHint(QueryHints.BATCH_TYPE, "IN"); > query.setHint(QueryHints.LOAD_GROUP_ATTRIBUTE, "tags"); > List<Scenario> results = query.getResultList(); > em.getTransaction().commit(); > > I get the following error: > Exception in thread "main" java.lang.IllegalArgumentException: Query selec > t sc from Story s JOIN s.scenarios sc WHERE s.id = :storyId order by index > (sc) asc, query hint eclipselink.batch is not valid for this type of query > . > > Which is because Eclipselink thinks that this is not a single > object query. I've seen this before - it wants Scenario to be the > first referenced table in the query, but I cannot for the life of > me figure out how to write this with Scenario first in the query. > When I do, then I get messages about the index() function not > being available as that is on the ListJoin. > > Any clues? > > > ----- http://wiki.eclipse.org/User:James.sutherland.oracle.com James Sutherland http://www.eclipse.org/eclipselink/ EclipseLink , http://www.oracle.com/technology/products/ias/toplink/ TopLink Wiki: http://wiki.eclipse.org/EclipseLink EclipseLink , http://wiki.oracle.com/page/TopLink TopLink Forums: http://forums.oracle.com/forums/forum.jspa?forumID=48 TopLink , http://www.eclipse.org/forums/index.php?t=thread&frm_id=111&S=1b00bfd151289b297688823a00683aca EclipseLink Book: http://en.wikibooks.org/wiki/Java_Persistence Java Persistence Blog: http://java-persistence-performance.blogspot.com/ Java Persistence Performance -- View this message in context: http://old.nabble.com/batch-loading-of-single-object-reporting-that-query-is-not-a-single-object-tp33823753p33864331.html Sent from the EclipseLink - Users mailing list archive at Nabble.com. _______________________________________________ eclipselink-users mailing list eclipselink-users@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipselink-users ]]> Fri, 18 May 2012 15:16:15 GMT http://dev.eclipse.org/mhonarc/lists/eclipselink-users/msg07137.html brian.repko@xxxxxxx (Brian Repko) Re: [eclipselink-users] lifecycle and validation annotations don't work in embeded classes http://dev.eclipse.org/mhonarc/lists/eclipselink-users/msg07136.html ----- http://wiki.eclipse.org/User:James.sutherland.oracle.com James Sutherland http://www.eclipse.org/eclipselink/ EclipseLink , http://www.oracle.com/technology/products/ias/toplink/ TopLink Wiki: http://wiki.eclipse.org/EclipseLink EclipseLink , http:/... The JPA spec does not define event for Embeddables. EclipseLink does support events on Embeddables if you use a DescriptorEventListener set by a DescriptorCustomizer. Please log a bug on EclipseLink to have the event annotations supported by EclipseLink. For the validation annotations, that is not part of JPA, but another spec/product. It should also be possible though I think, but it depends on your validation provider. marekpribyl wrote: > > hello there, > I have troubles to make JPA/validation annotations work in embeded class. > Assume following simple example: > > @Entity > class Parent { > @NotNull > private String name; > > @Embeded @Valid > private Child child; > > @PrePersist > public void parentMethod() {...} > > ...getters/setters... > } > > @Embedable > class Child extends AbstractChild { > @NotNull > private String name; > > @PrePersist > public void childMethod() {...} > > ...getters/setters... > } > > @MappedSuperclass > abstract class AbstractChild { > ... > > @PrePersist > public void abstractChildMethod() {...} > } > > > when I run it as a JUnit test neither JPA lifecycle nor validation > annotations defined in the embeded class work. on other hand these in the > parent class work correctly. > > My setup is: > - Eclipselink 2.3.2 > - apache bval-jsr303 0.4 + geronimo-validation_1.0_spec > - Spring 3.1.1 > > thanks in advance for any help > marek > ----- http://wiki.eclipse.org/User:James.sutherland.oracle.com James Sutherland http://www.eclipse.org/eclipselink/ EclipseLink , http://www.oracle.com/technology/products/ias/toplink/ TopLink Wiki: http://wiki.eclipse.org/EclipseLink EclipseLink , http://wiki.oracle.com/page/TopLink TopLink Forums: http://forums.oracle.com/forums/forum.jspa?forumID=48 TopLink , http://www.eclipse.org/forums/index.php?t=thread&frm_id=111&S=1b00bfd151289b297688823a00683aca EclipseLink Book: http://en.wikibooks.org/wiki/Java_Persistence Java Persistence Blog: http://java-persistence-performance.blogspot.com/ Java Persistence Performance -- View this message in context: http://old.nabble.com/lifecycle-and-validation-annotations-don%27t-work-in-embeded-classes-tp33862645p33864534.html Sent from the EclipseLink - Users mailing list archive at Nabble.com. ]]> Thu, 17 May 2012 14:14:55 GMT http://dev.eclipse.org/mhonarc/lists/eclipselink-users/msg07136.html jamesssss@xxxxxxx (James Sutherland) Re: [eclipselink-users] batch loading of single object reporting that query is not a single object http://dev.eclipse.org/mhonarc/lists/eclipselink-users/msg07135.html ----- http://wiki.eclipse.org/User:James.sutherland.oracle.com James Sutherland http://www.eclipse.org/eclipselink/ EclipseLink , http://www.oracle.com/technology/products/ias/toplink/ TopLink Wiki: http://wiki.eclipse.org/EclipseLink EclipseLink , http:/... You could try, select sc from Scenario sc, Story s JOIN s.scenarios sc2 WHERE s.id = :st oryId and sc = sc2 order by index(sc2) asc How is scenarios mapped, does it use a JoinTable? If it doesn't then you could probably also just add a QueryKey for the index field, or even map it in Scenario. BrianRepko wrote: > > I have 2 Entities > * Story, which has a 1-to-many ordered bidirectional > relationship with > * Scenario, which has an ElementCollection of tags (a List > element collection) > > I want to write a query that returns the Scenarios for a given > Story ID, however, I want the ability to limit the number of > results AND to batch/pre-load the Scenario tags. > > When I run the following: > em.getTransaction().begin(); > String jpql = "select sc from Story s JOIN s.scenarios sc WHERE s.id = :st > oryId order by index(sc) asc"; > TypedQuery<Scenario> query = em.createQuery(jpql, Scenario.class); > query.setParameter("storyId", 2); > query.setFirstResult(0); > query.setMaxResults(15); > query.setHint(QueryHints.BATCH, "sc.tags"); > query.setHint(QueryHints.BATCH_TYPE, "IN"); > query.setHint(QueryHints.LOAD_GROUP_ATTRIBUTE, "tags"); > List<Scenario> results = query.getResultList(); > em.getTransaction().commit(); > > I get the following error: > Exception in thread "main" java.lang.IllegalArgumentException: Query selec > t sc from Story s JOIN s.scenarios sc WHERE s.id = :storyId order by index > (sc) asc, query hint eclipselink.batch is not valid for this type of query > . > > Which is because Eclipselink thinks that this is not a single > object query. I've seen this before - it wants Scenario to be the > first referenced table in the query, but I cannot for the life of > me figure out how to write this with Scenario first in the query. > When I do, then I get messages about the index() function not > being available as that is on the ListJoin. > > Any clues? > > > ----- http://wiki.eclipse.org/User:James.sutherland.oracle.com James Sutherland http://www.eclipse.org/eclipselink/ EclipseLink , http://www.oracle.com/technology/products/ias/toplink/ TopLink Wiki: http://wiki.eclipse.org/EclipseLink EclipseLink , http://wiki.oracle.com/page/TopLink TopLink Forums: http://forums.oracle.com/forums/forum.jspa?forumID=48 TopLink , http://www.eclipse.org/forums/index.php?t=thread&frm_id=111&S=1b00bfd151289b297688823a00683aca EclipseLink Book: http://en.wikibooks.org/wiki/Java_Persistence Java Persistence Blog: http://java-persistence-performance.blogspot.com/ Java Persistence Performance -- View this message in context: http://old.nabble.com/batch-loading-of-single-object-reporting-that-query-is-not-a-single-object-tp33823753p33864331.html Sent from the EclipseLink - Users mailing list archive at Nabble.com. ]]> Thu, 17 May 2012 13:55:21 GMT http://dev.eclipse.org/mhonarc/lists/eclipselink-users/msg07135.html jamesssss@xxxxxxx (James Sutherland) Re: [eclipselink-users] jms cache coordination http://dev.eclipse.org/mhonarc/lists/eclipselink-users/msg07134.html -- REINHARD GIRSTENBREI | Senior Principal Technical Support Engineer Phone: +49 89 1430 2318 | Fax: +49 89 1430 2318 | Mobile: +49 177 594 1318 | VOIP: +49 89 1430 2318 Oracle Oracle Customer Services ORACLE Deutschland B.V. &amp; Co. KG | Riesstr. 25 | 8099... Hi Yannick,
EclipseLink prints cache coordination events if you have configured log level FINEST in your persistence.xml:
<property name="eclipselink.logging.level" value="FINEST" />

If you are looking for an example for EclipseLink Cache Coordination on Glassfish 3.1.2 and you have access to
"My Oracle Support" then take a look at:
Doc Id: 1395570.1 - How To Configure Cache Coordination With JMS on Glassfish
there is also one for RMI:
Doc Id 1396971.1 - How To Configure Cache Coordination With RMI on Glassfish

Please take a look at
GLASSFISH-18476 Deployment Fails If EclipseLink Cache Coordination Is Configured
which reports a problem with Glassfish 3.1.2

Regards,
Reinhard
    
   
       
    

On 5/14/2012 6:00 PM, eclipselink-users-request@xxxxxxxxxxx wrote: 
Send eclipselink-users mailing list submissions to
	eclipselink-users@xxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
	https://dev.eclipse.org/mailman/listinfo/eclipselink-users
or, via email, send a message with subject or body 'help' to
	eclipselink-users-request@xxxxxxxxxxx

You can reach the person managing the list at
	eclipselink-users-owner@xxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of eclipselink-users digest..."


Today's Topics:

   1. jms cache coordination (Yannick Majoros)
   2. EclipseLink - HermesParser.buildException when	compiling JPQL
      Query (Markus Tiede)
   3. Re: EclipseLink - HermesParser.buildException when compiling
      JPQL Query (Tom Ware)
   4. Re: EclipseLink - HermesParser.buildException when compiling
      JPQL Query (Markus Tiede)
   5. Re: EclipseLink - HermesParser.buildException when compiling
      JPQL Query (Tom Ware)


----------------------------------------------------------------------

Message: 1
Date: Sun, 13 May 2012 21:32:11 +0200
From: Yannick Majoros <yannick.majoros@xxxxxxxxx>
To: EclipseLink User Discussions <eclipselink-users@xxxxxxxxxxx>
Subject: [eclipselink-users] jms cache coordination
Message-ID: <4FB00C3B.2000806@xxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hello,

Is there a way to monitor jms cache coordination? I couldn't find 
documentation about setting log levels to see jms messages being sent / 
received, either from Eclipselink or from Glassfish 3.1.2 (EL is used 
from the ejb container).

Thanks for your help,

Yannick Majoros


------------------------------

Message: 2
Date: Mon, 14 May 2012 16:20:03 +0200
From: Markus Tiede <Markus.Tiede@xxxxxxxxx>
To: EclipseLink User Discussions <eclipselink-users@xxxxxxxxxxx>
Subject: [eclipselink-users] EclipseLink - HermesParser.buildException
	when	compiling JPQL Query
Message-ID: <4FB11493.8010807@xxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hello,

we, the Jubula team, are currently experiencing problems working with 
EclipseLink 2.4.0 in our standalone version of "Eclipse for Testers" 
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=379221).

We get a JPQL exception thrown by the HermesParser when trying to 
compile one of our JPQL queries (in 2.3.2 this works without any problems):

The basic mapping 'compName.hbmGuid' cannot be used in conjunction with 
the = operator. (Exception Description: Problem compiling [select assoc 
from ObjectMappingAssoziationPO as assoc, CompIdentifierPO as compId, 
ComponentNamePO as compName join assoc.logicalNames as logicalName where 
logicalName = compName.hbmGuid and logicalName = :compNameGuid and 
assoc.technicalName = compId and compName.hbmParentProjectId = 
:parentProjectId]).

Does anyone else face such problems and know how to resolve them? Is 
this a newly introduced feature / bug fix which requires adjustments of 
JPQL queries in general?

With best regards,
MarkusT

--
Oracle
REINHARD GIRSTENBREI | Senior Principal Technical Support Engineer
Phone: +49 89 1430 2318 | Fax: +49 89 1430 2318 | Mobile: +49 177 594 1318 | VOIP: +49 89 1430 2318
Oracle Oracle Customer Services

ORACLE Deutschland B.V. & Co. KG | Riesstr. 25 | 80992 Munich

ORACLE Deutschland B.V. & Co. KG
Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603
Geschäftsführer: Jürgen Kunz

Komplementärin: ORACLE Deutschland Verwaltung B.V.
Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Alexander van der Ven, Astrid Kepper, Val Maher
Green Oracle Oracle is committed to developing practices and products that help protect the environment

GIF image

GIF image

]]> Mon, 14 May 2012 20:25:45 GMT http://dev.eclipse.org/mhonarc/lists/eclipselink-users/msg07134.html reinhard.girstenbrei@xxxxxxx (REINHARD GIRSTENBREI) Re: [eclipselink-users] EclipseLink - HermesParser.buildException when compiling JPQL Query http://dev.eclipse.org/mhonarc/lists/eclipselink-users/msg07133.html _______________________________________________ eclipselink-users mailing list eclipselink-users@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipselink-users _______________________________________________ eclipselink-users mailing list eclipseli... Please file a ticket.
Our goal for Juno is to ship the new parser with as few regressions from the old parser as possible. We have not evaluated this issue yet, so I cannot make any promises, but fixing these bugs is a high priority for us.

On 14/05/2012 10:50 AM, Markus Tiede wrote: 
Thanks for the quick response - shall I file a separate ticket for this or will
you do that?

Do you recommend using the old parser or are you planning to fix this for Juno?

Best regards,
MarkusT

On 14.05.2012 16:39, Tom Ware wrote: 
We have just changed our JPA parser. We will look into this issue soon.

In you need to, you can enable the old parser with this persistence unit
property:

eclipselink.jpql.parser=org.eclipse.persistence.queries.ANTLRQueryBuilder

On 14/05/2012 10:20 AM, Markus Tiede wrote: 
Hello,

we, the Jubula team, are currently experiencing problems working with
EclipseLink 2.4.0 in our standalone version of "Eclipse for Testers"
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=379221).

We get a JPQL exception thrown by the HermesParser when trying to compile one of
our JPQL queries (in 2.3.2 this works without any problems):

The basic mapping 'compName.hbmGuid' cannot be used in conjunction with the =
operator. (Exception Description: Problem compiling [select assoc from
ObjectMappingAssoziationPO as assoc, CompIdentifierPO as compId, ComponentNamePO
as compName join assoc.logicalNames as logicalName where logicalName =
compName.hbmGuid and logicalName = :compNameGuid and assoc.technicalName =
compId and compName.hbmParentProjectId = :parentProjectId]).

Does anyone else face such problems and know how to resolve them? Is this a
newly introduced feature / bug fix which requires adjustments of JPQL queries in
general?

With best regards,
MarkusT

_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users



_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users

]]> Mon, 14 May 2012 14:55:51 GMT http://dev.eclipse.org/mhonarc/lists/eclipselink-users/msg07133.html tom.ware@xxxxxxx (Tom Ware)