ADOP Cutover Hangs When Multiple MWA Dispatchers Are Configured - ERROR: MSCA Dispatcher Port <port number> is not free
(Doc ID 2806048.1)
Last updated on JUNE 15, 2022
Applies to:
Oracle Mobile Application Server - Version 12.2.8 and laterInformation in this document applies to any platform.
Symptoms
On : 12.2.8 version, Patch Application Issues
ADOP cutover hangs when multiple MWA Dispatchers are defined in mwa.cfg and CONTEXT_FILE.
When we specify multiple MWA dispatcher ports in CONTEXT_FILE variable s_mwaDispatcherPort
cutover hangs with the message below even though netstat shows nothing attached to either port.
Multiple dispatcher ports are defined correctly as follows in the mwa.cfg file as seen in this example (where <hostname> is the hostname of your dispatcher server):
After mwa.cfg is refreshed during patch installation, the mwa.cfg now shows the following which is incorrect:
The following error is seen in the ADOP logs when ADOP cutover is running and the cutover appears to hang:
Inside verifyPorts()...
================================
ERROR: MSCA Dispatcher Port 10300,10303 is not free
ERROR: Some of the ports which are common across RUN and PATCH fs are not yet free.
Waiting for 1 minute before rechecking.
Changes
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 |