java.lang.illegalargumentexception weblogic

While trying to deploy an application using the install button on weblogic admin console we were getting below error

####<Oct 11, 2013 12:18:03 AM MYT> <Error> <Console> <my_prodsrv003>  <AdminServer> <ACTIVE ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic>
<1383063483962> <BEA-240003> <Console encountered the following error java.lang.IllegalArgumentException:
weblogic.management.mbeanservers.edit.internal.ActivationTaskMBeanImpl is not an interface
at java.lang.reflect.Proxy.getProxyClass(Proxy.java:362)
at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:581)
at weblogic.management.jmx.MBeanServerInvocationHandler.newProxyInstance(MBeanServerInvocationHandler.java:264)
at weblogic.management.jmx.MBeanServerInvocationHandler.newProxyInstance(MBeanServerInvocationHandler.java:636)
at weblogic.management.jmx.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:418)
at $Proxy98.activate(Unknown Source)

Error Seen on Console:

configuration.SecurityConfigurationMBeanImpl

According to oracle description on BEA-240003 :

Error: Console encountered the following error msg

Description: The console has output an error message to the server log.

Cause : The Console has encountered an error, but the console may continue to run.

Action : Review the error message text to determine the appropriate action.

The easiest workaround is to clean bounce all the managed servers and admin server after clearing the tmp and cache folder. This usually solves the stray class loading issue.

If still you are seeing error like below, when trying to deploy an application from admin console, WLST or deployer utility.:

Caused by: java.lang.NoSuchMethodException: weblogic.management.configuration.SecurityConfigurationMBeanImpl.isExcludedDomainNamesSet()

at java.lang.Class.getMethod(Class.java:1585)

at com.bea.staxb.buildtime.internal.bts.MethodName.getMethodOn(MethodName.java:171)

at com.bea.staxb.runtime.internal.util.ReflectionUtils.getMethodOnClass(ReflectionUtils.java:169)

at com.bea.staxb.runtime.internal.util.ReflectionUtils.getIssetterMethod(ReflectionUtils.java:141)

at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.isSet(RuntimeBindingType.java:572)

at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType.predefineNamespaces(ByNameRuntimeBindingType.java:113)

at com.bea.staxb.runtime.internal.PushMarshalResult.writeContents(PushMarshalResult.java:189)

at com.bea.staxb.runtime.internal.PushMarshalResult.marshalType(PushMarshalResult.java:148)

at com.bea.staxb.runtime.internal.PushMarshalResult.visitProp(PushMarshalResult.java:613)

at com.bea.staxb.runtime.internal.PushMarshalResult.visit(PushMarshalResult.java:385)

at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType.accept(ByNameRuntimeBindingType.java:89)

at com.bea.staxb.runtime.internal.PushMarshalResult.writeContents(PushMarshalResult.java:190)

at com.bea.staxb.runtime.internal.PushMarshalResult.marshalTopType(PushMarshalResult.java:91)

at com.bea.staxb.runtime.internal.MarshallerImpl.marshalBindingType(MarshallerImpl.java:290)

at com.bea.staxb.runtime.internal.MarshallerImpl.marshal(MarshallerImpl.java:140)

at com.bea.staxb.runtime.internal.MarshallerImpl.marshal(MarshallerImpl.java:184)

at weblogic.descriptor.EditableDescriptorManager.writeDescriptorBeanAsXML(EditableDescriptorManager.java:148)

at weblogic.descriptor.DescriptorManager.writeDescriptorAsXML(DescriptorManager.java:361)

at weblogic.management.provider.internal.DescriptorHelper.saveDescriptorTree(DescriptorHelper.java:68)

at weblogic.management.provider.internal.DescriptorHelper.saveDescriptorTree(DescriptorHelper.java:35)

at weblogic.management.provider.internal.EditAccessImpl.saveChanges(EditAccessImpl.java:658)

The issue might be because of weblogic.jar is corrupted. The method “weblogic.management.configuration.SecurityConfigurationMBeanImpl.isExcludedDomainNamesSet” will be missing from weblogic.jar or the jar itself is corrupted.

Easy way out of this issue is to get the weblogic.jar file which comes with installer and replace the corrupted weblogic.jar file and bounce the domain.

In case of any ©Copyright or missing credits issue please check CopyRights page for faster resolutions.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.