My Oracle Support Banner

SOA 12c Undeployment Leads To Unreachable Default Revision (Doc ID 2404980.1)

Last updated on JUNE 04, 2018

Applies to:

Oracle SOA Suite - Version and later
Information in this document applies to any platform.


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.


####<Dec 15, 2017, 10:20:15,461 AM CET> <Warning> <RMI> <s96hr2cn07> <WLS_SOATEST1> <[ACTIVE] ExecuteThread: '40' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <f595447d-e37c-4b7c-9e8a-0864a8a4531a-00008f44> <1513329615461> <[severity-value: 16] [rid: 0:3] [partition-id: 0] [partition-name: DOMAIN] > <BEA-080003> <A RuntimeException was generated by the RMI server:;Ljava.lang.String;Ljava.rmi.MarshalledObject;[Ljava.lang.String;;) 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.. 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(
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrowMaybeMBeanException(
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(
at Method)

Caused By: oracle.fabric.common.FabricException: There was an unrecoverable error - Member(Id=1, Timestamp=2017-12-10 00:07:08.108, ...):java.lang.IllegalArgumentException; Member(Id=3, Timestamp=2017-12-10 00:23:25.872,...):java.lang.IllegalArgumentException; .  Your cluster may be in an inconsistent state.
at oracle.integration.platform.blocks.deploy.CompositeDeploymentCoordinatorMessages.throwUnrecoverableFailureOnNodes(
at oracle.integration.platform.blocks.deploy.CoherenceCompositeDeploymentCoordinatorImpl.submitRequestAndWaitForCompletion(
at oracle.integration.platform.blocks.deploy.CoherenceCompositeDeploymentCoordinatorImpl.submitRequestAndWaitForCompletion(
at oracle.integration.platform.blocks.deploy.CoherenceCompositeDeploymentCoordinatorImpl.coordinateCompositeStateChange(
at oracle.integration.platform.blocks.deploy.CoherenceCompositeDeploymentCoordinatorImpl.coordinateCompositeStateChange(
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(
at oracle.integration.platform.xapp.WLSContextCrossAppProxy$WLSCrossAppProxy.invoke(
at com.sun.proxy.$Proxy605.coordinateCompositeStateChange(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

The issue can be reproduced at will with the following steps:
1.Create a new so folder integration_repro
2.Deploy composite sca_TimeManagement_rev1.2_20171128.jar as Default into this folder
3.Requests via SOAPUI are processed with no error,
4.Deploy composite sca_TimeManagement_rev1.2_20171006.jar 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 sca_TimeManagement_rev1.2_20171006.jar
7.Requests are now processed by the new default revision with no error

8.Undeployment of the default revision9.Composite sca_TimeManagement_rev1.2_20171128.jar becomes the new default revision and is no long reachable




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.