Petitions to SOA only answer with a 503 HTTP error

(Doc ID 2041907.1)

Last updated on MAY 24, 2016

Applies to:

Oracle SOA Suite - Version and later
Information in this document applies to any platform.


 After restarting the environment every composite you try to check the WSDL for generates a 503 error:

[2015-06-04T17:50:10.815-05:00] [soa_server1] [TRACE] []
[oracle.integration.platform.blocks.soap] [tid: [ACTIVE].ExecuteThread: '16'
for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>]
[ecid: 9882dc0a-9802-43b6-97de-b7253123a84c-000047a0,0] [APP: soa-infra]
[SRC_CLASS: oracle.integration.platform.blocks.soap.FabricProviderServlet]
[SRC_METHOD: doGet] return 503 for request uri


If you call "isSoaServerReady"


you will get the same 503 error that we get when calling any composite wsdl

 [2015-06-09T14:02:28.441-05:00] [soa_server1] [TRACE] []
 [oracle.integration.platform.blocks.soap] [tid: [ACTIVE].ExecuteThread: '19'
 for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>]
 [ecid: 98e6a54b-cfc3-46a3-88eb-0607b110d7e3-00002be9,0] [APP: soa-infra]
 [SRC_CLASS: oracle.integration.platform.blocks.soap.FabricProviderServlet]
 [SRC_METHOD: doGet] soa_server_status_check: return 503 for request uri




Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms