Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot resolve reference to bean LightUserCustomDeltaDefinitionDomainClass #272

Open
lbruand opened this issue Sep 5, 2014 · 7 comments

Comments

@lbruand
Copy link
Contributor

lbruand commented Sep 5, 2014

This is a reopening of bug #199. We are using GLU version 4.7.1 and the bug is still happening from time to time.

@ypujante
Copy link
Member

ypujante commented Sep 5, 2014

Can you please provide some information? Which java version are you using? Which platform?

@lbruand
Copy link
Contributor Author

lbruand commented Sep 5, 2014

Sorry Yan, I beg your pardon for being too fast reopening that bug.
We are still unfortunate to use the IBM JVM 1.6:
/usr/lib/jvm/java-160-ibm/bin/java -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build pxa6460sr10-20111208_01(SR10))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr10-20111207_96808 (JIT enabled, AOT enabled)
J9VM - 20111207_096808
JIT - r9_20111107_21307ifx1
GC - 20110519_AA)
JCL - 20111104_02

Platform is both Linux and AIX.
We are still experiencing that problem. We will try to upgrade jdk to 1.7 and test again against GLU 5.X and see what happens.

From the previous bug, you seemed to think this was related to groovy's version ?

@ypujante
Copy link
Member

ypujante commented Sep 5, 2014

If you can upgrade to 1.7/5.X I am pretty confident it will solve the problem.

Note that you should be able to upgrade to 1.7/4.7.3: see this chart http://pongasoft.github.io/glu/docs/latest/html/release-notes-old.html#glu-4-7-0
which should also solve the problem and maybe an easier path (switch the vm...).

@lbruand
Copy link
Contributor Author

lbruand commented Sep 5, 2014

Our main problem is with upgrading to JDK 1.7. We cannot expect to do that shortly in production.
Still we can test it. I'll get back to you on monday. Thanks for being so fast responding!

@ypujante
Copy link
Member

ypujante commented Sep 7, 2014

One thing to think about is that you only need to upgrade the console host with jdk 1.7. You can still leave all your agents with 1.6...

@ylorenzati
Copy link

Well, we have made some test and we are unable to reproduce this bug with a jdk 7. I think this bug can be closed again. Now we are able to migrate to java 7. Thank you

@ypujante
Copy link
Member

ypujante commented Mar 9, 2015

Thank you for reporting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants