Upon SAP Server Restart, SAP Adapter Couldn't Reestablish the Connection Automatically.
(Doc ID 577503.1)
Last updated on SEPTEMBER 11, 2008
Applies to:
Oracle(R) BPEL Process Manager - Version: 10.1.3.1 to 10.1.3.3This problem can occur on any platform.
Symptoms
SAP Adapter couldn't establish the connection automatically when the SAP server was restarted. You
have to restart the Application Server in order to establish the connection from SAP Adapter back to
the SAP server.
Error stack, you will notice:
<Oracle Home>\opmn\logs\default_group~home~default_group~1.log
<2007-11-03 23:40:27,034> <ERROR> <default.collaxa.cube.ws>
<AdapterFramework::Outbound>
file:/D:/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_Inbound214FromNistevo_1.4_0484c5
5e48158c7bd44828537f7fc651.tmp/Z_RFC_NIS_TO_R3_invoke.wsdl [
Z_RFC_NIS_TO_R3PortType::Z_RFC_NIS_TO_R3(input_Z_RFC_NIS_TO_R3,output_Z_RFC_NIS_TO_R3) ] - Could
not invoke operation 'Z_RFC_NIS_TO_R3' against the 'iWay JCA adapter' due to:
javax.resource.spi.EISSystemException: Connect to message server failed
Connect_PM MSHOST=cpcr3p.clorox.com, R3NAME=R3P, GROUP=EDI_RFC_GROUP Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms
Cause
Solution
References