Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EclipseLink » Problems migrating from Toplink Essentials to EclipseLink
Problems migrating from Toplink Essentials to EclipseLink [message #387767] Fri, 08 May 2009 07:46 Go to next message
Torben Putkonen is currently offline Torben PutkonenFriend
Messages: 34
Registered: July 2009
Member
We are trying to migrate from Toplink Essentials to Eclipselink 1.1.0. We
are using Oracle AS.

Class Kikkare has OneToMany join to one table, which in turn has several
OneToMany joins. This is the error message we experience:

Begin weaver class transformer processing class
[com/juttu/homma/entities/Kikkare].
Weaver encountered an exception while trying to weave class
com/juttu/homma/entities/Kikkare. The exception was:
java.lang.ArrayIndexOutOfBoundsException: 183
java.lang.ArrayIndexOutOfBoundsException: 183
Begin weaver class transformer processing class
[com/juttu/homma/entities/Kikkare].
Weaver encountered an exception while trying to weave class
com/juttu/homma/entities/Kikkare. The exception was:
java.lang.OutOfMemoryError: Requested array size exceeds VM limit
java.lang.OutOfMemoryError: Requested array size exceeds VM limit

We disabled weaving, and then encountered the following error:

Exception [EclipseLink-7092] (Eclipse Persistence Services -
1.1.0.r3639-SNAPSHOT):
org.eclipse.persistence.exceptions.ValidationException
Exception Description: Cannot add a query whose types conflict with an
existing query. Query To Be Added: [ReadAllQuery(name="KikkareTop.findAll"
referenceClass=KikkareTop jpql="select o from KikkareTop o")] is named:
[KikkareTop.findAll] with arguments [[]].The existing conflicting query:
[ReadAllQuery(name="KikkareTop.findAll" referenceClass=KikkareTop
jpql="select o from KikkareTop o")] is named: [KikkareTop.findAll] with
arguments: [[]].

If we commented out mentioned query, the same error occured in another
entity.

Any hints where to look at?

If the source of the issues is not evident, I would be happy to post the
entity source code if requested, however it will take some time to
"generalize" them.
Re: Problems migrating from Toplink Essentials to EclipseLink [message #387778 is a reply to message #387767] Mon, 11 May 2009 13:19 Go to previous messageGo to next message
James Sutherland is currently offline James SutherlandFriend
Messages: 1939
Registered: July 2009
Location: Ottawa, Canada
Senior Member

That is odd. Could you include the full exception stack trace to both
exceptions.

The first error seems like it may be memory related, try increasing your
JVM memory to see if it affects the error.

The second error is odd, are you defining the same query twice? Perhaps
in a superclass and subclass, or in annotations and orm.xml? Is there
anything non-standard about your configuration or deployment?

---
James
http://www.nabble.com/EclipseLink---Users-f26658.html


James : Wiki : Book : Blog : Twitter
Re: Problems migrating from Toplink Essentials to EclipseLink [message #387932 is a reply to message #387778] Tue, 19 May 2009 11:21 Go to previous message
Torben Putkonen is currently offline Torben PutkonenFriend
Messages: 34
Registered: July 2009
Member
Seems that the strange query exception was caused by one query which had
incorrect syntax. We found the issue finally.

I have not yet retried the weaving. Will have to try with more memory.
Previous Topic:drop-and-create-tables for Oracle
Next Topic:ORA-01461:can bind a LONG value only for insert into a LONG column
Goto Forum:
  


Current Time: Mon Dec 22 06:25:56 GMT 2014

Powered by FUDForum. Page generated in 0.01627 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software