Custom Search SOABYTE here

Thursday, April 18, 2013

Managed servers starting in ADMIN mode Plan.xml propagation across cluster not happening


<Apr 13, 2013 1:09:55 AM KST> <Error> <Cluster> <BEA-000140> <Failed to deserialize statedump from server -XXXXXXXXXXXXXXS:xxxxxx01:[8002,8002,-1,-1,-1,-1,-1]:xxxxxx01:8001,xxxxxx01:8002,xxxxxx02:8001,xxxxxx02:8002:AABC_domain:xxxx_server2 with java.lang.ClassNotFoundException: oracle.bpm.bpmn.engine.instancemanagement.ejb.IInternalInstanceManagementServiceRemote.
java.lang.ClassNotFoundException: oracle.bpm.bpmn.engine.instancemanagement.ejb.IInternalInstanceManagementServiceRemote
        at weblogic.application.internal.AppClassLoaderManagerImpl.loadApplicationClass(


java.lang.IllegalArgumentException: Cannot convert value of type [$Proxy223
to required type
[] for
property 'verificationService': no matching editors or conversion strategy found
Message icon - Warning Errors were encountered while performing this operation.
The SOA Infrastructure status is also displayed as failed.

Happens if changes were made to SOA connectors or soa-infra EJBs <deployed in nostage mode>.

Workaround was pushing of Plan.xml manually. The same is suggested in metalink note

"Deployment plan creation failed - configuration not changed." when Changing the Configuration of SOA-INFRA EJB's. [ID 1440105.1].

WebLogic Server: Deployment Plan Is Not Replicating Across Cluster [ID 1296510.1].

Applications are only deployed to managed servers if they use "stage" mode for deployment.
However,if  the applications were deployed using "no-stage" mode, so the deployment plan did not replicate the application to the managed servers. This is expected behavior.

1.> Change the deployment mode from "no-stage" to "stage" and the deployment plan will replicate the application to the managed servers as expected.
2.> Shared Location solution
3.> Manually pushing of Plan.xml to targets.

Also check for oramds.jar under oracle_common/modules/oracle.mds_11.1.1
This error is not specific to FacadeFinderBean; it also applies to any EJB that is part of the SOA Infrastructure application.

To resolve this error, you must manually modify the transaction timeout setting in your deployment archive.

To update the transaction timeout setting:

Open the fabric-ejb.jar file in your deployment archive.

Increase the transaction timeout value in the META-INF/weblogic-ejb-jar.xml file to a larger value.

Rejar the file.


Post a Comment

Blogger Profile