DB Adapter: Interaction processing error

Exception:

Exception occured when binding was invoked.Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'DEMO_TEST' failed due to: Interaction processing error.Error while processing the execution of the APPS.ABC.DEMO API interaction.An error occurred while processing the interaction for invoking the APPS.ABC.DEMO API. Cause: java.lang.NullPointerException.Check to ensure that the XML containing parameter data matches the parameter definitions in the XSD. This exception is considered not retriable, likely due to a modelling mistake.". The invoked JCA adapter raised a resource exception.Please examine the above error message carefully to determine a resolution.

Solution:

Undeploy the composite and Redeploy it again

ORACLE initialization or shutdown in progress

Exception:

java.sql.SQLException: ORA-01033: ORACLE initialization or shutdown in progress Error Code: 1033 [Caused by: ORA-01033: ORACLE initialization or shutdown in progress ] Check to ensure that the XML containing parameter data matches the parameter definitions in the XSD.
Contact oracle support if error is not fixable.

Cause:

This is not a JCA adapter problem. Please verify the stability of target database.

No more data to read from socket

Exception:

The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.

,detail=No more data to read from socket ,code=17410}

Cause:

Occurs if application that uses DB connection from the DataSource which has been already been timed out.The application is not aware of this and still tries to use it to connect to the database.


Soultion:


Option1:
Reset the datasource

Option2:
Bounce Managed Servers

Option3:
Delete the datasource , bounce managed server and create the datasource again.

Could not instantiate InteractionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec



Exception:

Exception occured during invocation of JCA binding: "Could not instantiate InteractionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec due to: ". The invoked JCA adapter raised a resource exception.Please examine the above error message carefully to determine a resolution

Cause:

The issue was caused by known Unpublished Bug 11924578
Bug 11924578 - ADAPTERS USE OF HASHMAP CAN LEAD TO DEADLOCKS
Additional Information: Bug 11924578 exists in versions 11.1.1.3, 11.1.1.4 and 11.1.1.5


Solution:

To implement the solution:

For Non-Clustered environments, patches for the following three bugs have to be applied Bug 13360039 , Bug 12573835 and Bug 13394139
Note: Patch for Bug 11924578 is included in Patch for Bug 13360039
For Clustered environments, in addition to the above 3 patches, patch for bug 12797505 is also required

Failed to read wsdl file at: caused by:java.net.ConnectException: java.net.ConnectException: Connection refused


Solution:
Telnet to the external server to check whether the Connection to the server is established properly

Unable to undeploy Composite from SOA 11g partition



[undeployComposite] INFO: Received HTTP response from the server, response code=500


[undeployComposite] ---->response code=500, error:There was an error undeploying composite on ETH_SOA1: Cannot find revision in undeploy : ETH_INPUT_SERVICES_EMR613/ETH_EMR613_FileReceiverProcess_Composite!1.0..




Cause
Bug 13360039 - SOA11G COMPOSITE UNDEPLOYMENT FAILS WHEN THE PATCH 11924578 APPLIED.


Solution
Please follow below steps to download Patch:13360039:
1) Login to MyOracle support portal.


2) Search for patch number 13360039


3) Download the patch and follow the Readme to apply the patch in your test environment.

Could not reserve enough space for object heap Could not create the Java virtual machine

Open user_projects\domains\base_domain\bin\setSOADomainEnv.cmd file


Change From : set JAVA_OPTIONS=%JAVA_OPTIONS% set DEFAULT_MEM_ARGS=-Xms512m -Xmx1024m set PORT_MEM_ARGS=-Xms768m -Xmx1536m

To: set JAVA_OPTIONS=%JAVA_OPTIONS% set DEFAULT_MEM_ARGS=-Xms512m -Xmx768m set PORT_MEM_ARGS=-Xms768m -Xmx1536m

Save the file and then re-run startWebLogic.cmd

Oracle SOA 11g - Changing the service endpoint URL dynamically through EM console

To change the default endpoint location of the service through the EM console, please follow the below steps:

1. In EM console click on the Composite
2. Scroll down to Service and References section
3. Click on Reference link and properties tab
4. Change Endpoint Address to the desired location and click apply

The new request will be send to the new endpoint location configured through the EM console. 

The new endpoint configuration can be removed to send the request to the default endpoint location configured in the WSDL.