SOA Production Interface Failed To Start After Server Restart with Error Unsupported protocol: https (Doc ID 2867382.1)

Last updated on SEPTEMBER 24, 2023

Applies to:

Symptoms

SOA Production interface failed to start after server restart

After soa_server restart one of the SOA composites failed to start and threw an error.

ERROR
-----------------------

[2022-04-27T10:21:13.681-04:00] [soa_server1] [ERROR] [SOA-20020] [oracle.integration.platform] [tid: DaemonWorkThread: '1' of WorkManager: 'wm/SOAWorkManager'] [userId: ] [ecid: XXXXXXXXXXXXXXXXXXX] [APP: soa-infra] [partition-name: DOMAIN] [tenant-name: GLOBAL] Deployment of composite "XXXXXXXXXXXXXXXXXXX" failed: Error occurred during deployment of component: XXXXXXXXXXXXXXXXXXX to service engine: implementation.bpel, for composite: XXXXXXXXXXXXXXXXXXX: ORABPEL-05215[[
The process domain is encountering the following errors while loading the process "XXXXXXXXXXXXXXXXXXX" (composite "XXXXXXXXXXXXXXXXXXX/XXXXXXXXXXXXXXXXXXX!1.0*soa_XXXXXXXXXXXXXXXXXXX"): Unsupported protocol: https'.

[2022-04-27T10:21:16.450-04:00] [soa_server1] [ERROR] [SOA-20020] [oracle.integration.platform] [tid: DaemonWorkThread: '1' of WorkManager: 'wm/SOAWorkManager'] [userId: ] [ecid: XXXXXXXXXXXXXXXXXXX] [APP: soa-infra] [partition-name: DOMAIN] [tenant-name: GLOBAL] Deployment of composite "XXXXXXXXXXXXXXXXXXX" failed: Failed to concatanate the following 2 urls: home= "null" and relative="SCA-INF/classes".: no protocol: SCA-INF/classes.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.