My Oracle Support Banner

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

Last updated on JULY 31, 2019

Applies to:

Oracle API Gateway - Version 11.1.2.3.0 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, on 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 <TIMESTAMP> [<THREAD ID>] Deploying Gateway Configuration ...
ERROR <TIMESTAMP> [<THREAD ID>] Exception from: Gateway Groups Entity Store Configuration. Description: Unknown exception. Stack trace: Traceback (most recent call last):
File "<OAG HOME>/apigateway/upgrade/scripts/sysupgrade_control.py", line 328, in _Apply__apply
  result = method(importContext)
File "<OAG HOME>/apigateway/upgrade/scripts/esgroups/ESGroupsImporter.py", line 32, in deployGatewaysConfig
  deploymentAPI.deploy(gateway.getId(), archiveId)
File "<OAG HOME>/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 default management port via http.

Error messages in the Gateway instances trace file:

ERROR   <TIMESTAMP> [<THREAD ID>] [SSL_accept, XXXX]: error - SSLv2/v3 read client hello A.
ERROR   <TIMESTAMP> [<THREAD ID>] error handling connection: SSL protocol error
       error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request, source location: s23_srvr.c:418
ERROR   <TIMESTAMP> [<THREAD ID>] [SSL_accept, XXXX]: error - SSLv2/v3 read client hello A.
ERROR   <TIMESTAMP> [<THREAD ID>] 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

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
Changes
Cause
Solution
References


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