Eclipse Community Forums: EclipseLink » Mbean lookup failed in Weblogic 10.3.5 eclipselink 2.1.3.v20110304-r9073

Home » Eclipse Projects » EclipseLink » Mbean lookup failed in Weblogic 10.3.5 eclipselink 2.1.3.v20110304-r9073(Erro when try init server in Mbean lookup.)

Show: Today's Messages :: Show Polls :: Message Navigator

Mbean lookup failed in Weblogic 10.3.5 eclipselink 2.1.3.v20110304-r9073 [message #853978]

Mon, 23 April 2012 14:29

Diego Silva

Messages: 4
Registered: April 2012

Junior Member

I'm using eclipselink in weblogic 10.3.5 and eclipselink 2.1.3.v20110304-r9073 embedded libraries in weblogic. When i try init server show following error:

<23/04/2012 11h23min55s BRT> <Warning> <EclipseLink> <BEA-2005000> <2012-04-23 11:23:55.701--ServerSession(1116282)--Failed to find MBean Server: javax.naming.NameNotFoundException: While trying to look up comp/env/jmx/runtime in .; remaining name 'comp/env/jmx/runtime'>
<23/04/2012 11h23min55s BRT> <Warning> <EclipseLink> <BEA-2005000> <2012-04-23 11:23:55.701--ServerSession(1116282)--Failed to find MBean Server: javax.naming.NameNotFoundException: While trying to look up comp/env/jmx/runtime in .; remaining name 'comp/env/jmx/runtime'>
<23/04/2012 11h23min55s BRT> <Warning> <EclipseLink> <BEA-2005000> <2012-04-23 11:23:55.702--ServerSession(1116282)--Failed to find MBean Server: javax.naming.NameNotFoundException: While trying to look up comp/env/jmx/runtime in .; remaining name 'comp/env/jmx/runtime'>

But if i try only lookup java:comp/env/jmx/runtime in my app that Mbean has lookup sucessful.

[Updated on: Mon, 23 April 2012 19:37]

Report message to a moderator

Re: Mbean lookup failed in Weblogic 10.3.5 eclipselink 2.1.3.v20110304-r9073 [message #855097 is a reply to message #853978]

Tue, 24 April 2012 14:16

Chris Delahunt

Messages: 1389
Registered: July 2009

Senior Member

These are warnings that can be ignored unless you plan to use the EclipseLink MBean which attempts to deploy by default. Try verifying that you are using the Weblogic_10 server platform class by specifying eclipselink.target-server (which you probably are) and turning logging on to finest using <property name="eclipselink.logging.level" value="FINEST"/> and <property name="eclipselink.logging.logger" value="DefaultLogger"/> and upload the stack trace. EclipseLink should be using the "java:comp/env/jmx/runtime" for the lookup, so the log should have the exception stack that might show more.

If possible, please try using EclipseLink 2.2 or later as there were a few code changes in this area that might be related to the issue.

Best Regards,
Chris

Report message to a moderator