Last week, when I tried to deploy an ADF application to ADF managed server on WLS instance, I found below error in server logs. Of course, the application activated and worked without any other errors. But following error repeated every time when I tried deployment.
Error:
<Jun 17, 2014 9:32:01 AM CDT> <Error> <JMX> <BEA-149500> <An exception occurred while registering the MBean null.
java.lang.IllegalArgumentException: Registered more than one instance with the same objectName : com.bea:ServerRuntime=ADF_server,Name=HR,Type=ApplicationRuntime new:weblogic.j2ee.J2EEApplicationRuntimeMBeanImpl@1b017725 existing weblogic.j2ee.J2EEApplicationRuntimeMBeanImpl@1baabd61 at weblogic.management.jmx.ObjectNameManagerBase.registerObject(ObjectNameManagerBase.java:168)
at weblogic.management.mbeanservers.internal.WLSObjectNameManager.lookupObjectName(WLSObjectNameManager.java:131) at weblogic.management.jmx.modelmbean.WLSModelMBeanFactory.registerWLSModelMBean(WLSModelMBeanFactory.java:87) at weblogic.management.mbeanservers.internal.RuntimeMBeanAgent$1.registered(RuntimeMBeanAgent.java:105) at weblogic.management.provider.core.RegistrationManagerBase.invokeRegistrationHandlers(RegistrationManagerBase.java:180)
Truncated. see log file for complete stacktrace>
Solution:
After checking the Weblogic configuration, I found that the data source name is same as the deployed application name causing the problem. To fix the error, I changed the application name and deployed it. No more errors.
To avoid this error in future, use unique names across Application,Data Source & JMS Queue etc..
Error:
<Jun 17, 2014 9:32:01 AM CDT> <Error> <JMX> <BEA-149500> <An exception occurred while registering the MBean null.
java.lang.IllegalArgumentException: Registered more than one instance with the same objectName : com.bea:ServerRuntime=ADF_server,Name=HR,Type=ApplicationRuntime new:weblogic.j2ee.J2EEApplicationRuntimeMBeanImpl@1b017725 existing weblogic.j2ee.J2EEApplicationRuntimeMBeanImpl@1baabd61 at weblogic.management.jmx.ObjectNameManagerBase.registerObject(ObjectNameManagerBase.java:168)
at weblogic.management.mbeanservers.internal.WLSObjectNameManager.lookupObjectName(WLSObjectNameManager.java:131) at weblogic.management.jmx.modelmbean.WLSModelMBeanFactory.registerWLSModelMBean(WLSModelMBeanFactory.java:87) at weblogic.management.mbeanservers.internal.RuntimeMBeanAgent$1.registered(RuntimeMBeanAgent.java:105) at weblogic.management.provider.core.RegistrationManagerBase.invokeRegistrationHandlers(RegistrationManagerBase.java:180)
Truncated. see log file for complete stacktrace>
Solution:
After checking the Weblogic configuration, I found that the data source name is same as the deployed application name causing the problem. To fix the error, I changed the application name and deployed it. No more errors.
To avoid this error in future, use unique names across Application,Data Source & JMS Queue etc..
Thank you for this! :) Solved my problem!
ReplyDeleteMy Application and datasource name is different.But still getting the same error.
ReplyDeleteAny other way to resolve this issue
saving my life,thanks!
ReplyDelete