HTTP Status: 500 During Upgrade From 11.1.2.1.0 To 11.1.2.3.0 (Doc ID 1986311.1)

Last updated on AUGUST 18, 2016

Applies to:

Oracle API Gateway - Version 11.1.2 and later
Information in this document applies to any platform.

Symptoms

Oracle API Gateway (OAG) 11.1.2.3.0

During upgrade from 11.1.2.1.0 to 11.1.2.3.0, when "sysupgrade apply" is run,
in the step after Node Manager and Gateway instances have been created in the upgraded configuration,
the Node Manager cannot deploy the upgraded configuration to the newly created
Gateway instances.

Error messages from sysupgrade apply:

Doing work prior to starting Gateways ...
Starting Gateways ...
[...]
Doing work post Gateway start ...
Doing work prior to deploying Gateway Configuration ...
Deploying Gateway Configuration ...
Errors from: Gateway Groups Entity Store Configuration. Please see log for details:
Unknown exception
Deploying Gateway Configuration ... failed



Error messages in sysapply.trc:

REPORT 16/Feb/2015:12:14:23.131 [0001] Deploying Gateway Configuration ...
ERROR 16/Feb/2015:12:14:45.929 [0001] Exception from: Gateway Groups Entity Store Configuration. Description: Unknown exception. Stack trace: Traceback (most recent call last):
File "/u1/app/oracle/product/OAG11.1.2.3/apigateway/upgrade/scripts/sysupgrade_control.py", line 328, in _Apply__apply
  result = method(importContext)
File "/u1/app/oracle/product/OAG11.1.2.3/apigateway/upgrade/scripts/esgroups/ESGroupsImporter.py", line 32, in deployGatewaysConfig
  deploymentAPI.deploy(gateway.getId(), archiveId)
File "/u1/app/oracle/product/OAG11.1.2.3/apigateway/system/lib/jython/nmdeployment.py", line 149, in deploy
  return self.deploymentClient.deploy(serviceID, archiveID)
NodeManagerAPIException: com.vordel.api.nm.NodeManagerAPIException: Node Manager error: error occurred on call from Node Manager on 'localhost' to http://localhost:8085' for URL '/api/configuration' and 'PUT'
.
HTTP status: 500.
Error code: 102.

Note that the Node Manager tries to access the Gateway instance on the management port via http.

Error messages in the Gateway instances trace file:

ERROR   20/Feb/2015:09:42:55.494 [0022] [SSL_accept, 2210]: error - SSLv2/v3 read client hello A.
ERROR   20/Feb/2015:09:42:55.534 [0022] error handling connection: SSL protocol error
       error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request, source location: s23_srvr.c:418
ERROR   20/Feb/2015:09:45:13.921 [0021] [SSL_accept, 2210]: error - SSLv2/v3 read client hello A.
ERROR   20/Feb/2015:09:45:13.922 [0021] error handling connection: SSL protocol error
       error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request, source location: s23_srvr.c:418
[... many of these ...]

 The SSL messages indicate that a https request had been required, but an http request had been received.

Changes

In OAG 11.1.2.1.0 and OAG 11.1.2.2.0, it was possible to configure the Gateway management port for http only.
In OAG 11.1.2.3.0, the Gateway management port is always https. The upgrade mechanism is unable to handle this scenario.

Cause

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