SOA 12c Undeployment Leads To Unreachable Default Revision
(Doc ID 2404980.1)
Last updated on MAY 15, 2023
Applies to:
Oracle SOA Suite - Version 12.2.1.2.0 and laterInformation in this document applies to any platform.
Symptoms
Customer has deployed 2 revisons of a composite utilising REST bindings with the latest set to default revision.
After undeploying the default revision the cluster seams to be in inconsitent state and the revision now marked as default revision is not reachable any more.
ERROR
-----------------------
javax.management.RuntimeMBeanException: javax.management.RuntimeMBeanException: There was an unrecoverable error - Member(Id=1, Timestamp=2017-12-10 00:07:08.108, ...):java.lang.IllegalArgumentException; . Your cluster may be in an inconsistent state..
javax.management.RuntimeMBeanException: javax.management.RuntimeMBeanException: There was an unrecoverable error - Member(Id=1, Timestamp=2017-12-10 00:07:08.108, ...):java.lang.IllegalArgumentException; . Your cluster may be in an inconsistent state.
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrow(DefaultMBeanServerInterceptor.java:839)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrowMaybeMBeanException(DefaultMBeanServerInterceptor.java:852)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:821)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$21.run(WLSMBeanServerInterceptorBase.java:589)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:587)
at weblogic.management.mbeanservers.internal.JMXContextInterceptor.invoke(JMXContextInterceptor.java:249)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$21.run(WLSMBeanServerInterceptorBase.java:589)
......
Caused By: oracle.fabric.common.FabricException: There was an unrecoverable error - Member(Id=1, Timestamp=YYYY-MM-DD HH MI SS.SSSS, ...):java.lang.IllegalArgumentException; Member(Id=3, Timestamp=YYYY-MM-DD HH MI SS.SSSS,...):java.lang.IllegalArgumentException; . Your cluster may be in an inconsistent state.
at oracle.integration.platform.blocks.deploy.CompositeDeploymentCoordinatorMessages.throwUnrecoverableFailureOnNodes(CompositeDeploymentCoordinatorMessages.java:167)
at oracle.integration.platform.blocks.deploy.CoherenceCompositeDeploymentCoordinatorImpl.submitRequestAndWaitForCompletion(CoherenceCompositeDeploymentCoordinatorImpl.java:997)
at oracle.integration.platform.blocks.deploy.CoherenceCompositeDeploymentCoordinatorImpl.submitRequestAndWaitForCompletion(CoherenceCompositeDeploymentCoordinatorImpl.java:966)
at oracle.integration.platform.blocks.deploy.CoherenceCompositeDeploymentCoordinatorImpl.coordinateCompositeStateChange(CoherenceCompositeDeploymentCoordinatorImpl.java:536)
at oracle.integration.platform.blocks.deploy.CoherenceCompositeDeploymentCoordinatorImpl.coordinateCompositeStateChange(CoherenceCompositeDeploymentCoordinatorImpl.java:484)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at oracle.integration.platform.xapp.WLSContextCrossAppProxy$WLSCrossAppProxy.invoke(WLSContextCrossAppProxy.java:53)
at com.sun.proxy.$Proxy605.coordinateCompositeStateChange(Unknown Source)
at oracle.fabric.management.deployedcomposites.mbean.CompositeLifecycle.setCompositeState(CompositeLifecycle.java:574)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
......
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.Create a new so folder
2.Deploy composite as Default into this folder
3.Requests via SOAPUI are processed with no error,
4.Deploy composite as none-Default revision into the same folder
5.Requests via SOAPUI are processed with no error from the in step 2 deployed default revision
6.Set default revision to the composite
7.Requests are now processed by the new default revision with no error
8.Undeployment of the default revision becomes the new default revision and is no long reachable
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |