RuntimeErrorException on weblogic 6.0

[sujit smore]

I am getting this Exception when I try to deploy the application on Weblogic 6.0
*****************
javax.management.RuntimeErrorException: Error thrown by the invoke in the invoke method of the Dynamic MBean
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1559)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:409)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:287)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:866)
at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:853)
at weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:838)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:566)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:548)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:285)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:439)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:180)
at $Proxy50.addTarget(Unknown Source)
at weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationManager.java:486)
at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:557)
at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:504)
at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:428)
at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:380)
at weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:152)
at weblogic.management.mbeans.custom.ApplicationManager.startAdminManager(ApplicationManager.java:205)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:120)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:562)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:548)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:285)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:439)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:180)
at $Proxy3.start(Unknown Source)
at weblogic.management.Admin.startApplicationManager(Admin.java:1037)
at weblogic.management.Admin.finish(Admin.java:493)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
<Jan 24, 2003 12:51:25 PM EST> <Notice> <WebLogicServer> <WebLogic Server started>
<Jan 24, 2003 12:51:25 PM EST> <Notice> <WebLogicServer> <ListenThread listening on port 7001>
<Jan 24, 2003 12:51:25 PM EST> <Notice> <WebLogicServer> <SSLListenThread listening on port 7002>
<Jan 24, 2003 12:51:25 PM EST> <Info> <NT Performance Pack> <NATIVE: NTSocketMuxer was built on Nov 17 2000 17:38:02
****************
Please email me at [email protected] if anyone has a solution/fix to it.
Thanks,
Sujit

[Chris Mathews]

This is a problem with WLS 6.0, there have been cases where it will fail in deployment without giving any indication why.
Here are my recommendations:
1) Put all utility classes used by your Application on the CLASSPATH, I have seen this error in a case where the EJB could not find a class. Ultimately this is not where you may want the classes but it will help in diagnosing the problem.
2) Failing 1, start ripping out parts of your application one by one to try and isolate the problem.
3) Open a Support Case with BEA.
4) Upgrade to WLS 6.1 (of course I realize this may not be an option).
Sorry, I can't help more but it is not one of those errors that typically has a cut and dry solution.
[ January 24, 2003: Message edited by: Chris Mathews ]