Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

com.ibm.websphere.management.exception.AdminException: ADMA0094E:

2,908 views
Skip to first unread message

Rakesh Kumar

unread,
Nov 4, 2009, 2:22:39 AM11/4/09
to
Hello All,

When i am trying to publish my applications i am getting following error. If any face this problem error kindly suggest.

Log:

!STACK 0
javax.management.MBeanException: Exception thrown in RequiredModelMBean while trying to invoke operation updateApplication
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.handleAdminFault(Unknown Source)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplate(Unknown Source)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(Unknown Source)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(Unknown Source)
at $Proxy0.invoke(Unknown Source)
at com.ibm.ws.management.AdminClientImpl.invoke(Unknown Source)
at com.ibm.etools.wrd.websphere.internal.mgmt.AbstractAdminClientCommand.execute(Unknown Source)
at com.ibm.etools.wrd.websphere.internal.commands.LooseAppUpdateCommand.execute(Unknown Source)
at com.ibm.etools.wrd.websphere.internal.mgmt.SynchronousCommandWrapper.execute(Unknown Source)
at com.ibm.etools.wrd.websphere.internal.operations.AbstractServerOperation.executeCommand(Unknown Source)
at com.ibm.etools.wrd.websphere.internal.operations.ApplicationUpdateOperation.updateLocalV61Server(Unknown Source)
at com.ibm.etools.wrd.websphere.internal.operations.ApplicationUpdateOperation.execute(Unknown Source)
at com.ibm.etools.wrd.websphere.internal.operations.WASPublisherImpl.publishDelta(Unknown Source)
at com.ibm.ws.ast.st.v61.core.internal.WASServerBehaviour.publishWrdDelta(Unknown Source)
at com.ibm.ws.ast.st.v61.core.internal.WASServerBehaviour.publishModules(Unknown Source)
at com.ibm.wbit.runtime.v61.WBIServerBehaviour.publishModules(Unknown Source)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(Unknown Source)
at org.eclipse.wst.server.core.internal.Server.doPublish(Unknown Source)
at org.eclipse.wst.server.core.internal.Server.publish(Unknown Source)
at org.eclipse.wst.server.core.internal.PublishServerJob.run(Unknown Source)
at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)
Caused by: com.ibm.websphere.management.exception.AdminException: ADMA0094E: An application management operation updateApplication is not available in your WebSphere Application Server installation.
at com.ibm.ws.management.application.AppManagementImpl._updateApplication(AppManagementImpl.java:2184)
at com.ibm.ws.management.application.AppManagementImpl.updateApplication(AppManagementImpl.java:2130)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:62)
at sun.reflect.GeneratedMethodAccessor60.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:265)
at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1092)
at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:973)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:231)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:238)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:833)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:802)
at com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:1081)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:974)
at com.ibm.ws.management.connector.AdminServiceDelegator.invoke(AdminServiceDelegator.java:139)
at sun.reflect.GeneratedMethodAccessor181.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at com.ibm.ws.management.connector.soap.SOAPConnector.invoke(SOAPConnector.java:351)
at com.ibm.ws.management.connector.soap.SOAPConnector.service(SOAPConnector.java:205)
at com.ibm.ws.management.connector.soap.SOAPConnection.handleRequest(SOAPConnection.java:55)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:680)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:484)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)

Akash Bharti

unread,
Nov 4, 2009, 2:51:24 AM11/4/09
to
Instead of using publish option, can you try exporting the ear and manually deploying it from the admin console.

I know, its an irritating way to do each time, but I just want to ensure that things are good in Process Server. And problem might be with publishing from RAD/WID..

Thanks
Akash

Rakesh Kumar

unread,
Nov 4, 2009, 2:51:24 AM11/4/09
to
Hello Akash,

Thanks for early reply we are using Websphere Process Sever Version 6.1.

After modifying changes as suggested in the below link when i restart server and try to publish the problem still persists.

You can find the attachement of error exactly.

Kindly suggest.

Thanks,
Rakesh.

Akash Bharti

unread,
Nov 4, 2009, 2:27:01 AM11/4/09
to

Rakesh Kumar

unread,
Nov 4, 2009, 3:00:23 AM11/4/09
to
I have made osme xml changes, as sugggested removed version.properties file from the healthcenter.jar as it is conflicting, but the problem is not solved with that still i see the same issue

Akash Bharti

unread,
Nov 4, 2009, 2:51:24 AM11/4/09
to
btw, what modification did you make??

WorkAround :
The workaround is to remove the version.properties file from
WAS_HOME\java\jre\lib\ext\healthcenter.jar as it is conflicted
with Application Server's version.properties file.

or you are already at the required fix pack level?

Thanks
Akash

Akash Bharti

unread,
Nov 4, 2009, 3:01:44 AM11/4/09
to
Also, did you restarted the server after the change ??

Thanks
Akash

Rakesh Kumar

unread,
Nov 4, 2009, 2:58:11 AM11/4/09
to
But how can we know that ear has latest files with it when we run/deploy

Akash Bharti

unread,
Nov 4, 2009, 2:58:11 AM11/4/09
to
Check for the time stamp for files in installedApps directory.

Thanks
Akash

Rakesh Kumar

unread,
Nov 4, 2009, 4:18:58 AM11/4/09
to
Yeah i have restarted the server, even the problem is not solved.

Thanks,
Rakesh

0 new messages