[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
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
