Re: [eclipselink-users] Bug 362564 - WebSphere specific randomisedorg.ec

[Tom Ware <tom.ware@xxxxxxxxxx>]

I have to admit that I am as confused about this issue as you appear to be.

The only theory I can come up with is that there is some issue with all the 
queries and that the error is different for different deployments because they 
are instantiated parsed into the EclipseLink metadata in a random order.

Since deployment is working on other application servers, this leads me to 
believe that this is somehow a packaging issue.

Is the packaging the same on all the different servers you are running on?
How is your persistence unit packaged and deployed?
Are all the classes in the same jar?
Are the classes dependent on classes from other jars?
Is there a chance that some of the dependencies are not properly loaded?
Is there anything in common between queries that do not seem to work? 
(inherited fields?)
Is there a chance that queries of the same name are defined in multiple places?

-Tom

On 01/11/2011 10:54 AM, Nathan Drew wrote:
> Hi Tom,
>
> I've retried with another example stack trace added to the ticket for
> eclipselink version 2.3.1-RC1 (2.3.1.v20111018-r10243)
>
> Kind Regards
> Nathan
>
>
> -----Original Message-----
> From: eclipselink-users-bounces@xxxxxxxxxxx
> [mailto:eclipselink-users-bounces@xxxxxxxxxxx] On Behalf Of Nathan Drew
> Sent: 01 November 2011 13:49
> To: EclipseLink User Discussions
> Subject: Re: [eclipselink-users] Bug 362564 - WebSphere specific
> randomisedorg.eclipse.persistence.exceptions.JPQLException error on
> startup
>
> Will do - just noticed in the trace that it had the old 2.2.1 library
> running, will retry and update the ticket and let you know.
>
> Kind Regards
> Nathan
>
> -----Original Message-----
> From: eclipselink-users-bounces@xxxxxxxxxxx
> [mailto:eclipselink-users-bounces@xxxxxxxxxxx] On Behalf Of Tom Ware
> Sent: 01 November 2011 13:21
> To: eclipselink-users@xxxxxxxxxxx
> Subject: Re: [eclipselink-users] Bug 362564 - WebSphere specific
> randomised org.eclipse.persistence.exceptions.JPQLException error on
> startup
>
> Can you try the latest 2.3.1 milestone (RC1)?
>
> http://www.eclipse.org/eclipselink/downloads/milestones.php
>
> -Tom
>
> On 01/11/2011 9:07 AM, Nathan Drew wrote:
> > Hi,
> >
> > Has anyone seen anything similar in WAS only? GlassFish and WebLogic
> > both seem to run without ever hitting this "random" JPQL exception on
> > startup - see
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=362564 for details.
> >
> > Many Thanks
> >
> > Nathan
> >
> >
> >
> > _______________________________________________
> > 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
>
>
> _______________________________________________
> 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