Application Deployed To SOA Server Fail At Startup When The SOA Servers Are Restarted
(Doc ID 2495494.1)
Last updated on JULY 10, 2020
Applies to:Oracle SOA Suite - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Three application deployed to the SOA servers fail at startup when the SOA servers are restarted
These applications use Web Service proxies that fail to start when the SOA servers are restarted. After the SOA servers are started the three applications are in prepared or failed state. The three applications can then be started successfully, but only after the SOA servers are in RUNNING status.
Each of the failed applications will have a "connection refused" error associated with them, despite it being valid for SOA on that host.
After SOA servers are running you can ping the host/port and they are valid, however not during the SOA server startup.
The workaround is to manually start these three applications in the WLS Console after the SOA servers are in RUNNING.
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