BEA-149231 Unable to set the activation state to true for the application 'soa-infra'.SOA-Infra fails to start if a composite fails on startup of SOA server 11.1.1.7.6 / 11.1.1.7.7

BEA-149231 Unable to set the activation state to true for the application 'soa-infra'.SOA-Infra fails to start if a composite fails on startup of SOA server 11.1.1.7.6 / 11.1.1.7.7

SOA-Infra fails to start if a composite fails on startup of the SOA server 11.1.1.7.6 / 11.1.1.7.7

Error messages as below can be seen in the stdout 

Deployer BEA-149231 Unable to set the activation state to true for the application 'soa-infra'. weblogic.application.ModuleException: [HTTP:101216]Servlet: failed to preload on startup in Web application: "/soa-infra". oracle.fabric.common.FabricException: Error in getting XML input stream: oramds:/deployed-composites/test1/composite.xml: oracle.mds.exception.MDSException: MDS-00054: The file to be loaded oramds:/deployed-composites/test1/composite.xml does not exist.

1) For SOA 11.1.1.7.6


Patch 16574779: SOA-INFRA SHOULD START UP INSPITE OF ERRORS ENCOUNTERED IN SOA APPS


Pre-requisite Patches ( Mandatory)
-----------------------------------------------

19953598 SOA Bundle Patch 11.1.1.7.6


2) For SOA 11.1.1.7.7

Patch 16574779: SOA-INFRA SHOULD START UP INSPITE OF ERRORS ENCOUNTERED IN SOA APPS
 

Pre-requisite Patches ( Mandatory)
-----------------------------------------------


20423535 SOA Bundle Patch 11.1.1.7.7

Applying Patch 16574779: SOA-INFRA SHOULD START UP INSPITE OF ERRORS ENCOUNTERED IN SOA APPS on SOA 11.1.1.7.7

Applying Patch 16574779: SOA-INFRA SHOULD START UP INSPITE OF ERRORS ENCOUNTERED IN SOA APPS on SOA 11.1.1.7.7

If soa-infra fails to start on SOA 11.1.1.7.7 start due to failure in starting a composite, you will see errors in stdout as in this post. 

If the errors are similar then you should consider applying Patch 16574779.


Pre-requisite Patches
-----------------------------

20423535 SOA Bundle Patch 11.1.1.7.7


Pre-Installation Instructions:
------------------------------

- Ensure Patch 20423535 SOA Bundle Patch 11.1.1.7.7 already applied. 

- Review and download the latest version of OPatch 11.1.x via Bug 6880880

- Ensure access to valid OUI Inventory by running opatch lsinventory

- Validate the executables in system PATH like 'which opatch', 'which unzip'


Installation Instructions
---------------------------

1. Unzip the patch zip file into the PATCH_TOP.

   $ unzip -d PATCH_TOP p16574779_111177_Generic.zip

2. $ cd PATCH_TOP/16574779/oui

3. Stop MT services and run opatch apply (Conflict checks & cold backup recommended before applying patch)

4. If patch is successful, restart the services and verify the patch by running opatch lsinventory | grep 16574779


5. If patch fails for some reason, roll back the patch by running opatch rollback -id 16574779 and restart the services. 

Related posts:

BEA-149231 Unable to set the activation state to true for the application 'soa-infra'.SOA-Infra fails to start if a composite fails on startup of SOA server 11.1.1.7.6 / 11.1.1.7.7

Applying Patch 16574779: SOA-INFRA SHOULD START UP INSPITE OF ERRORS ENCOUNTERED IN SOA APPS on SOA 11.1.1.7.6

Applying Patch 16574779: SOA-INFRA SHOULD START UP INSPITE OF ERRORS ENCOUNTERED IN SOA APPS on SOA 11.1.1.7.6


If soa-infra fails to start on SOA 11.1.1.7.7 start due to failure in starting a composite, you will see errors in stdout as in this post. 

If the errors are similar then you should consider applying Patch 16574779

Pre-requisite Patches
-----------------------------

19953598 SOA Bundle Patch 11.1.1.7.6


Pre-Installation Instructions:
-----------------------------

- Ensure Patch 19953598 SOA Bundle Patch 11.1.1.7.6 already applied

- Review and download the latest version of OPatch 11.1.x via Bug 6880880

- Ensure access to valid OUI Inventory by running opatch lsinventory

- Validate the executables in system PATH like 'which opatch', 'which unzip'


Installation Instructions
---------------------------

1. Unzip the patch zip file into the PATCH_TOP.

   $ unzip -d PATCH_TOP p16574779_111176_Generic.zip

2. $ cd PATCH_TOP/16574779/oui

3. Stop MT services and run opatch apply (Conflict checks & cold backup recommended before applying patch)

4. If patch is successful, restart the services and verify the patch by running opatch lsinventory | grep 16574779


5. If patch fails for some reason, roll back the patch by running opatch rollback -id 16574779 and restart the services. 

Related posts:

BEA-149231 Unable to set the activation state to true for the application 'soa-infra'.SOA-Infra fails to start if a composite fails on startup of SOA server 11.1.1.7.6 / 11.1.1.7.7

Recovering failed instances / messages in SOA 11g using Enterprise Manager

Recovering failed instances / messages in SOA 11g using Enterprise Manager

Want to recover failed instances in SOA? Below are the high level steps to recover.

- Login to SOA EM console http://virtualhost.example.com/em

- On the left side tree navigation, go to Farm_soa_domain > SOA > soa-infra (WLS_SOA1)

- Right click on soa-infra (WLS_SOA1) and then select Service Engines > BPEL

- In the BPEL Service Home page, you will see tabs - Dashboard, Statistics, Instances, Faults, Deployed components, Recovery.

- Click on Recovery tab

- Select the following from the drop downs.
Type:  Invoke , Duration: Select appropriate duration you need to check, Message State: All

- Select the relevant conversation ID and click on 'Recover' tab. Repeat this for all the conversation IDs that need to be recovered.

Please note you can recover or cancel selected messages marked as Recoverable. If messages are marked as Exhausted you can select them and click Reset to return them to the auto-recovery queue, click Mark Cancelled so that recovery is never attempted on them, or click Recover to attempt to recover them immediately.