Soa-infra Application Fails to Start Due to Deployment Framework Issues Coherence Incomplete Policy Migration After Failed Restart of SOA Server

12-26 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite

12.8.2 Soa-infra Application Fails to Start Due to Deployment Framework Issues Coherence

Problem: The soa-infra application fails to start after changes to the Coherence configuration for deployment have been applied. The SOA server output log reports the following: Cluster communication initialization failed. If you are using multicast, Please make sure multicast is enabled on your network and that there is no interference on the address in use. Please see the documentation for more details. Solutions: 1. When using multicast instead of unicast for cluster deployments of SOA composites, a message similar to the above may appear if a multicast conflict arises when starting the soa-infra application that is, starting the managed server on which SOA runs. These messages, which occur when Oracle Coherence throws a run-time exception, also include the details of the exception itself. If such a message appears, check the multicast configuration in your network. Verify that you can ping multicast addresses. In addition, check for other clusters that may have the same multicast address but have a different cluster name in your network, as this may cause a conflict that prevents soa-infra from starting. If multicast is not enabled in your network, you can change the deployment framework to use unicast as described in Oracle Coherence Developers Guide for Oracle Coherence. 2. When entering well-known address list for unicast in server start parameters, make sure that the nodes addresses entered for the localhost and clustered servers are correct. Error messages like the following are reported in the servers output log if any of the addresses is not resolved correctly: oracle.integration.platform.blocks.deploy.CompositeDeploymentCoordinatorMessage s errorUnableToStartCoherence

12.8.3 Incomplete Policy Migration After Failed Restart of SOA Server

Problem: The SOA server fails to start through the administration console before setting Node Manager property startScriptEnabled=true. The server does not come up after the property is set either. The SOA Server output log reports the following: SEVERE: . Unable to Encrypt data Unable to Encrypt data. Check installationpost-installation steps for errors. Check for errors during SOA server startup. ORABPEL-35010 . Unable to Encrypt data. Unable to Encrypt data. Check installationpost-installation steps for errors. Check for errors during SOA server startup. . at oracle.bpel.services.common.util.EncryptionService.encryptEncryptionService.java: 56 ... Managing the Topology 12-27 Solution: Incomplete policy migration results from an unsuccessful start of the first SOA server in a cluster. To enable full migration, edit the jazn-policy element the system-jazn-data.xml file to grant permission to bpm-services.jar: grant grantee codesource urlfile:{oracle.home}soamodulesoracle.soa.workflow_11.1.1bpm-services.jar url codesource grantee permissions permission classjava.security.AllPermissionclass permission permissions grant 12.8.4 SOA, IPM, or UCM Servers Fail to Start Due to Maximum Number of Processes Available in Database Problem: A SOA, IPM, or UCM server fails to start. The domain has been extended for new types of managed server for example, UCM extended for IPM or the system has been scaled up added new servers of the same type. The SOA, IPM, or UCM server output log reports the following: Warning JDBC BEA-001129 Received exception while creating connection for pool SOADataSource-rac0: Listener refused the connection with the following error: ORA-12516, TNS:listener could not find available handler with matching protocol stack Solution: Verify the number of processes in the database and adjust accordingly. As the SYS user, issue the SHOW PARAMETER command: SQL SHOW PARAMETER processes Set the initialization parameter using the following command: SQL ALTER SYSTEM SET processes=300 SCOPE=SPFILE Restart the database.

12.8.5 Administration Server Fails to Start After a Manual Failover