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 #199

Closed
YannRobert opened this issue Feb 1, 2013 · 10 comments
Closed

Comments

@YannRobert
Copy link

I got the following error at the glu console-server startup.

org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'org.linkedin.glu.orchestration.engine.delta.LightUserCustomDeltaDefinitionDomainClass' is defined

Full stacktrace can be found in this gist :
https://gist.github.com/4691758

https://gist.github.com/raw/4691758/efd20f27cc61c060b54337630a90022d28205ddb/gistfile1.txt

this only happens once in a while.
It is really random : tested inside a VM using the same Virtual Machine initial state, sometimes this error happens, but most of the time it does not.

Trying to connect to the console-server after that will result in a 503 HTTP response.

@ypujante
Copy link
Member

ypujante commented Feb 1, 2013

Which version of java are you using? (java -version)
On Feb 1, 2013 7:04 AM, "Yann ROBERT" notifications@github.com wrote:

I got the following error at the glu console-server startup.

org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean
named
'org.linkedin.glu.orchestration.engine.delta.LightUserCustomDeltaDefinitionDomainClass'
is defined

Full stacktrace can be found in this gist :
https://gist.github.com/4691758

this only happens once in a while.
It is really random : tested inside a VM using the same Virtual Machine
initial state, sometimes this error happens, but most of the time it does
not.

Trying to connect to the console-server after that will result in a 503
HTTP response.


Reply to this email directly or view it on GitHubhttps://github.com/linkedin/glu/issues/199.

@YannRobert
Copy link
Author

/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

@ypujante
Copy link
Member

ypujante commented Feb 1, 2013

As mentioned in the documentation only a sun/Oracle vm currently works.
This will hopefully be fixed with glu 5 coming soon.

@YannRobert
Copy link
Author

Thank you.
I switch JVM right away. Will keep you posted on the result.

@YannRobert
Copy link
Author

Hello Yan
We now run console-server using the Oracle JVM.
And still having issues, but on different ***DomainClass Spring Bean.

Did not switch to Oracle JVM for glu-agent-server nor Zookeeper yet.
Do you think it is worse trying ? Can this error on console-server be related to the JVM of glu-agent or Zookeeper ?

@YannRobert
Copy link
Author

Here is the exception using Oracle JVM

Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'org.linkedin.glu.orchestration.engine.commands.DbCommandExecutionDomainClass' is defined

@YannRobert
Copy link
Author

Also found once

Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'org.linkedin.glu.orchestration.engine.delta.UserCustomDeltaDefinitionDomainClass' is defined

@YannRobert
Copy link
Author

Using IBM JVM, the LightUserCustomDeltaDefinitionDomainClass error occured once every ~15 launch.

Using Oracle JVM, one of the UserCustomDeltaDefinitionDomainClass / DbCommandExecutionDomainClass error occured once every ~50/80 launch.

@ypujante
Copy link
Member

ypujante commented Feb 6, 2013

You start your console a lot! :)

I have not really heard about this issue with Oracle VM but I am hoping that the migration to java1.7 and more importantly the latest version of groovy (where I believe the error is occurring) will make it go away.

Or in other words I think it will be fixed with glu 5.0 coming soon.

@ypujante
Copy link
Member

ypujante commented Apr 3, 2013

This should be now fixed with glu 4.7.0. Closing this bug. If it happens again, please reopen.

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

2 participants