Re: Re: Eclipselink2 "weaving" does not take place on JOnAS 5.3.0 M4
"Hans J. Prueller" <[email protected]> Thu, 08 Sep 2011 16:34:23 +0200
| Newsgroups | gmane.comp.java.objectweb.jonas |
|---|---|
| Organization | LBS logics GmbH |
| Message-ID | <1315492464.2049.8.camel@kodos> |
--=-KpsaAA8RCOocPfqdLsrY
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Florent,
thank you for your message.
I am not sure if it is related to the eclipselink issue you mentioned,
because the issue is called " ... requires better error message ..."
which I am
interpreting that the error message should be better if weaving did not
take place.
Anyway under JOnAS 5.2 it worked fine with JPA persistence provider
"eclipselink2"
but it only worked from JOnAS-5.2.0-Milestones up to 5.2.0-RC --- the
problem already appeared with 5.2.0-RELEASE version
Earlier as I reported this problem for 5.2.0 release version, you
suggested:
>> Also, for a test, could you replace the EasyBeans core bundle 5.2.0
and replace it with the bundle of 5.2.0-M5 :
>>JONAS_ROOT/repositories/maven2-internal/org/ow2/easybeans/osgi/easybeans-modules-core/
I did that and sent the result via mailinglist:
>> Hi Florent,
>>
>> meanwhile I had time to perform the test you suggested - I replaced
the EasyBeans core bundle of 5.2.0 (release)
>> with the EasyBeans core bundle of my working 5.2.0 M5 installation.
>>
>>Now deployment of the application (EAR) works perfectly, also
persistence with EclipseLink2 works without problems again.
>>
>> Seems that some change in EasyBeans core between 5.2.0 M5 and 5.2.0
release broke "weaving" ?
So the error also happened on 5.2 without changing the EclipseLink
Version - changing the EasyBeans core fixed the issue, so somehow
it has to be related to EasyBeans core which inhibits EclipseLink JPA
from weaving ?????
(you should find all this mails on the list regarding that).
For 5.2, we "worked around" this problem by sticking to 5.2.0-RC and
not using the release version of 5.2.0 :-)
But now it is required for us to upgrade to 5.3 (because we need JSF2)
and we must stick to EclipseLink2
(we have used hibernate earlier but were forced to switch JPA provider
to eclipselink because Hibernate caused severe system hangs
and crashes under heavy load ....)
So it is really a BLOCKER for us if eclipselink2 JPA persistence
provider does not work in 5.3 !!!
Could you please give it a look once again ?
Hans
Am Donnerstag, den 08.09.2011, 16:20 +0200 schrieb Florent BENOIT:
> Hans,
>
> Maybe it's linked to the following
> issue :https://bugs.eclipse.org/bugs/show_bug.cgi?id=323403 (as you
> said on missing wawing classes)
> We should upgrade EclipseLink 2 version in JOnAS
> In 5.2.0-M5, what was the property set for JPA persistence provider ?
> eclipselink or eclipselink2 ?
>
> You may try to weave your classes offline, so that the runtime weawing
> won't occur :
> org.eclipse.persistence.tools.weaving.jpa.StaticWeave needs to be used
> As you're using if I remember well, here is a link :
> http://wiki.eclipse.org/EclipseLink/UserGuide/JPA/Advanced_JPA_Development/Performance/Weaving/Static_Weaving/Static_Weaving
>
>
> Also you may try with another provider like hibernate3.5
>
> Regards,
>
> Florent
>
>
> On 09/08/2011 07:52 AM, Hans J. Prueller wrote:
>
> > Hi JOnAS Team!
> >
> > I just downloaded and configured the new JOnAS 5.3 M4 Milestone,
> > and tried to deploy our EAR application.
> >
> > Basically it works, but there seems to be a Problem with contained
> > EclipseLink (2.1.3) - seems that weaving does not take place!
> >
> > The identical EAR archive which works on 5.2.0-M5/RC produces the
> > following error on 5.3.0 M4:
> >
> >
> > [EL Info]: 2011-09-08
> > 07:45:23.633--ServerSession(2018501004)--EclipseLink, version:
> > Eclipse Persistence Services - 2.1.3.v20110304-r9073
> > [EL Info]: 2011-09-08
> > 07:45:23.661--ServerSession(2018501004)--Server: EasyBeans
> > [EL Severe]: 2011-09-08
> > 07:45:24.343--ServerSession(2018501004)--Local Exception Stack:
> > Exception [EclipseLink-0] (Eclipse Persistence Services -
> > 2.1.3.v20110304-r9073):
> > org.eclipse.persistence.exceptions.IntegrityException
> > Descriptor Exceptions:
> > ---------------------------------------------------------
> >
> > Exception [EclipseLink-60] (Eclipse Persistence Services -
> > 2.1.3.v20110304-r9073):
> > org.eclipse.persistence.exceptions.DescriptorException
> > Exception Description: The method [_persistence_set_businessTrip_vh]
> > or [_persistence_get_businessTrip_vh] is not defined in the object
> > [com.lbslogics.ims.model.Event].
> > Internal Exception: java.lang.NoSuchMethodException:
> > com.lbslogics.ims.model.Event._persistence_get_businessTrip_vh()
> > Mapping:
> > org.eclipse.persistence.mappings.ManyToOneMapping[businessTrip]
> > Descriptor: RelationalDescriptor(com.lbslogics.ims.model.Event -->
> > [DatabaseTable(EventBean_)])
> >
> > Exception [EclipseLink-60] (Eclipse Persistence Services -
> > 2.1.3.v20110304-r9073):
> > org.eclipse.persistence.exceptions.DescriptorException
> > Exception Description: The method
> > [_persistence_set_businessTripDay_vh] or
> > [_persistence_get_businessTripDay_vh] is not defined in the object
> > [com.lbslogics.ims.model.Event].
> > Internal Exception: java.lang.NoSuchMethodException:
> > com.lbslogics.ims.model.Event._persistence_get_businessTripDay_vh()
> > Mapping:
> > org.eclipse.persistence.mappings.ManyToOneMapping[businessTripDay]
> > Descriptor: RelationalDescriptor(com.lbslogics.ims.model.Event -->
> > [DatabaseTable(EventBean_)])
> >
> > Runtime Exceptions:
> > ---------------------------------------------------------
> >
> > java.lang.NullPointerException
> >
> > at
> > org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.initializeDescriptors(DatabaseSessionImpl.java:471)
> > at
> > org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.initializeDescriptors(DatabaseSessionImpl.java:406)
> > at
> > org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.postConnectDatasource(DatabaseSessionImpl.java:666)
> > at
> > org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:615)
> > at
> > org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:228)
> > at
> > org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:389)
> > at
> > org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.getServerSession(EntityManagerFactoryImpl.java:164)
> > at
> > org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:221)
> > at
> > org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:209)
> > at
> > org.ow2.easybeans.persistence.TxEntityManagerHandler.buildNewTxEntityManager(TxEntityManagerHandler.java:124)
> > at
> > org.ow2.easybeans.persistence.TxEntityManagerHandler.getCurrent(TxEntityManagerHandler.java:112)
> > at
> > org.ow2.easybeans.persistence.TxEntityManager.getCurrentEntityManager(TxEntityManager.java:74)
> > at
> > org.ow2.easybeans.persistence.TxEntityManager.createNamedQuery(TxEntityManager.java:246)
> > at
> > org.ow2.easybeans.persistence.ContainerManagedEntityManager.createNamedQuery(ContainerManagedEntityManager.java:244)
> > at
> > com.lbslogics.ims.system.objects.IMSSetting.loadFromStore(IMSSetting.java:430)
> >
> >
> >
> > Seems very clear to me that the error occurs because the JPA
> > entities are not "enhanced"/weaved by EclipseLink -- what do you
> > think ?
> >
> > regards,
> > HANS
> >
>
>
--=-KpsaAA8RCOocPfqdLsrY
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY TEXT="#000000" BGCOLOR="#ffffff">
Florent,<BR>
<BR>
thank you for your message.<BR>
<BR>
I am not sure if it is related to the eclipselink issue you mentioned, because the issue is called " ... requires better error message ..." which I am<BR>
interpreting that the error message should be better if weaving did not take place.<BR>
<BR>
Anyway under JOnAS 5.2 it worked fine with JPA persistence provider "eclipselink2"<BR>
<BR>
but it only worked from JOnAS-5.2.0-Milestones up to 5.2.0-RC --- the problem already appeared with 5.2.0-RELEASE version<BR>
<BR>
Earlier as I reported this problem for 5.2.0 release version, you suggested:<BR>
<BR>
>> Also, for a test, could you replace the EasyBeans core bundle 5.2.0 and replace it with the bundle of 5.2.0-M5 :<BR>
>>JONAS_ROOT/repositories/maven2-internal/org/ow2/easybeans/osgi/easybeans-modules-core/<BR>
<BR>
<BR>
I did that and sent the result via mailinglist:<BR>
<BR>
>> Hi Florent,<BR>
>> <BR>
>> meanwhile I had time to perform the test you suggested - I replaced the EasyBeans core bundle of 5.2.0 (release) <BR>
>> with the EasyBeans core bundle of my working 5.2.0 M5 installation.<BR>
>><BR>
>>Now deployment of the application (EAR) works perfectly, also persistence with <B><FONT COLOR="#a020f0">EclipseLink</FONT></B>2 works without problems again.<BR>
>><BR>
>> Seems that some change in EasyBeans core between 5.2.0 M5 and 5.2.0 release broke "weaving" ?<BR>
<BR>
So the error also happened on 5.2 without changing the EclipseLink Version - changing the EasyBeans core fixed the issue, so somehow<BR>
it has to be related to EasyBeans core which inhibits EclipseLink JPA from weaving ?????<BR>
<BR>
(you should find all this mails on the list regarding that).<BR>
<BR>
For 5.2, we "worked around" this problem by sticking to 5.2.0-RC and not using the release version of 5.2.0 :-)<BR>
<BR>
But now it is required for us to upgrade to 5.3 (because we need JSF2) and we must stick to EclipseLink2 <BR>
<BR>
(we have used hibernate earlier but were forced to switch JPA provider to eclipselink because Hibernate caused severe system hangs<BR>
and crashes under heavy load ....)<BR>
<BR>
So it is really a BLOCKER for us if eclipselink2 JPA persistence provider does not work in 5.3 !!! <BR>
<BR>
<BR>
Could you please give it a look once again ?<BR>
<BR>
<BR>
Hans<BR>
<BR>
<BR>
<BR>
Am Donnerstag, den 08.09.2011, 16:20 +0200 schrieb Florent BENOIT:<BR>
<BLOCKQUOTE TYPE=CITE>
Hans,<BR>
<BR>
Maybe it's linked to the following issue :<A HREF="https://bugs.eclipse.org/bugs/show_bug.cgi?id=323403">https://bugs.eclipse.org/bugs/show_bug.cgi?id=323403</A> (as you said on missing wawing classes)<BR>
We should upgrade EclipseLink 2 version in JOnAS<BR>
In 5.2.0-M5, what was the property set for JPA persistence provider ? eclipselink or eclipselink2 ?<BR>
<BR>
You may try to weave your classes offline, so that the runtime weawing won't occur :<BR>
org.eclipse.persistence.tools.weaving.jpa.StaticWeave needs to be used<BR>
As you're using if I remember well, here is a link : <A HREF="http://wiki.eclipse.org/EclipseLink/UserGuide/JPA/Advanced_JPA_Development/Performance/Weaving/Static_Weaving/Static_Weaving">http://wiki.eclipse.org/EclipseLink/UserGuide/JPA/Advanced_JPA_Development/Performance/Weaving/Static_Weaving/Static_Weaving</A><BR>
<BR>
<BR>
Also you may try with another provider like hibernate3.5<BR>
<BR>
Regards,<BR>
<BR>
Florent<BR>
<BR>
<BR>
On 09/08/2011 07:52 AM, Hans J. Prueller wrote: <BR>
<BLOCKQUOTE TYPE=CITE>
Hi JOnAS Team!<BR>
<BR>
I just downloaded and configured the new JOnAS 5.3 M4 Milestone, and tried to deploy our EAR application.<BR>
<BR>
Basically it works, but there seems to be a Problem with contained EclipseLink (2.1.3) -<U> seems that weaving does not take place!</U><BR>
<BR>
The identical EAR archive which works on 5.2.0-M5/RC produces the following error on 5.3.0 M4:<BR>
<BR>
<BR>
[EL Info]: 2011-09-08 07:45:23.633--ServerSession(2018501004)--<B>EclipseLink, version: Eclipse Persistence Services - 2.1.3.v20110304-r9073</B><BR>
[EL Info]: 2011-09-08 07:45:23.661--ServerSession(2018501004)--Server: EasyBeans<BR>
[EL Severe]: 2011-09-08 07:45:24.343--ServerSession(2018501004)--Local Exception Stack: <BR>
Exception [EclipseLink-0] (Eclipse Persistence Services - 2.1.3.v20110304-r9073): org.eclipse.persistence.exceptions.IntegrityException<BR>
Descriptor Exceptions: <BR>
---------------------------------------------------------<BR>
<BR>
<B>Exception [EclipseLink-60] (Eclipse Persistence Services - 2.1.3.v20110304-r9073): org.eclipse.persistence.exceptions.DescriptorException</B><BR>
<B>Exception Description: The method [_persistence_set_businessTrip_vh] or [_persistence_get_businessTrip_vh] is not defined in the object [com.lbslogics.ims.model.Event].</B><BR>
<B>Internal Exception: java.lang.NoSuchMethodException: com.lbslogics.ims.model.Event._persistence_get_businessTrip_vh()</B><BR>
<B>Mapping: org.eclipse.persistence.mappings.ManyToOneMapping[businessTrip]</B><BR>
<B>Descriptor: RelationalDescriptor(com.lbslogics.ims.model.Event --> [DatabaseTable(EventBean_)])</B><BR>
<BR>
Exception [EclipseLink-60] (Eclipse Persistence Services - 2.1.3.v20110304-r9073): org.eclipse.persistence.exceptions.DescriptorException<BR>
Exception Description: The method [_persistence_set_businessTripDay_vh] or [_persistence_get_businessTripDay_vh] is not defined in the object [com.lbslogics.ims.model.Event].<BR>
Internal Exception: java.lang.NoSuchMethodException: com.lbslogics.ims.model.Event._persistence_get_businessTripDay_vh()<BR>
Mapping: org.eclipse.persistence.mappings.ManyToOneMapping[businessTripDay]<BR>
Descriptor: RelationalDescriptor(com.lbslogics.ims.model.Event --> [DatabaseTable(EventBean_)])<BR>
<BR>
Runtime Exceptions: <BR>
---------------------------------------------------------<BR>
<BR>
java.lang.NullPointerException<BR>
<BR>
at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.initializeDescriptors(DatabaseSessionImpl.java:471)<BR>
at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.initializeDescriptors(DatabaseSessionImpl.java:406)<BR>
at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.postConnectDatasource(DatabaseSessionImpl.java:666)<BR>
at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:615)<BR>
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:228)<BR>
at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:389)<BR>
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.getServerSession(EntityManagerFactoryImpl.java:164)<BR>
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:221)<BR>
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:209)<BR>
at org.ow2.easybeans.persistence.TxEntityManagerHandler.buildNewTxEntityManager(TxEntityManagerHandler.java:124)<BR>
at org.ow2.easybeans.persistence.TxEntityManagerHandler.getCurrent(TxEntityManagerHandler.java:112)<BR>
at org.ow2.easybeans.persistence.TxEntityManager.getCurrentEntityManager(TxEntityManager.java:74)<BR>
at org.ow2.easybeans.persistence.TxEntityManager.createNamedQuery(TxEntityManager.java:246)<BR>
at org.ow2.easybeans.persistence.ContainerManagedEntityManager.createNamedQuery(ContainerManagedEntityManager.java:244)<BR>
at com.lbslogics.ims.system.objects.IMSSetting.loadFromStore(IMSSetting.java:430)<BR>
<BR>
<BR>
<BR>
Seems very clear to me that the error occurs because the JPA entities are not "enhanced"/weaved by EclipseLink -- what do you think ?<BR>
<BR>
regards,<BR>
HANS<BR>
<BR>
</BLOCKQUOTE>
<BR>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>
--=-KpsaAA8RCOocPfqdLsrY--