Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
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.)
Mbean lookup failed in Weblogic 10.3.5 eclipselink 2.1.3.v20110304-r9073 [message #853978] Mon, 23 April 2012 14:29 Go to next message
Diego Silva is currently offline 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 Go to previous messageGo to next message
Chris Delahunt is currently offline Chris Delahunt
Messages: 1023
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
Re: Mbean lookup failed in Weblogic 10.3.5 eclipselink 2.1.3.v20110304-r9073 [message #856474 is a reply to message #855097] Wed, 25 April 2012 17:45 Go to previous message
Diego Silva is currently offline Diego Silva
Messages: 4
Registered: April 2012
Junior Member
Don't have stackTrace, only this warnning ...
What is the function of the MBean?
As it is not necessary, I would remove this warning?
Previous Topic:Const Mapping
Next Topic:jpa primary key violation when persisting many-to-many columns
Goto Forum:
  


Current Time: Mon Sep 22 14:19:25 GMT 2014

Powered by FUDForum. Page generated in 0.02156 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software