ERROR: The following required ports are in use: 6801 : WLS OAEA Application Port

Anil pinged me today when his adop phase=fs_clone failed with this error message:

-----------------------------
ERROR: The following required ports are in use:
-----------------------------
6801 : WLS OAEA Application Port
Corrective Action: Free the listed ports and retry the adop operation.

Completed execution : ADOPValidations.java

====================================
Inside _validateETCHosts()...
====================================

This is a bug mentioned in the appendix of article: 

Integrating Oracle E-Business Suite Release 12.2 with Oracle Access Manager 11gR2 (11.1.2) using Oracle E-Business Suite AccessGate (Doc ID 1576425.1)

Bug 19817016

The following errors are encountered when running fs_clone after completing AccessGate and OAM integration and after completing a patch cycle:

Checking  WLS OAEA Application Port on aolesc11:  Port Value = 6801
RC-50204: Error: - WLS OAEA Application Port in use: Port Value = 6801

-----------------------------
ERROR: The following required ports are in use:
-----------------------------
6801 : WLS OAEA Application Port
Corrective Action: Free the listed ports and retry the adop operation.

Workaround:
Stop the oaea managed server on the run file system before performing the fs_clone operation, immediately after the accessgate deployment.

Solution:
This issue will be addressed through Bug 19817016.

If you read the bug:

Bug 19817016 : RUNNING ADOP FS_CLONE FAILS DUE TO PORT CONFLICT BETWEEN RUN AND PATCH EDITION	To Bottom

Bug Attributes

---

Type	B - Defect	Fixed in Product Version
Severity	2 - Severe Loss of Service	Product Version	12.2.4
Status	11 - Code/Hardware Bug (Response/Resolution)	Platform	226 - Linux x86-64
Created	14-Oct-2014	Platform Version	ORACLE LINUX 5
Updated	02-Dec-2014	Base Bug	N/A
Database Version	11.2.0.3	Affects Platforms	Generic
Product Source	Oracle	Knowledge, Patches and Bugs related to this bug

Related Products

---

Line	Oracle E-Business Suite	Family	Applications Technology
Area	Technology Components	Product	1745 - Oracle Applications Technology Stack

Hdr: 19817016 11.2.0.3 FSOP 12.2.4 PRODID-1745 PORTID-226
Abstract: RUNNING ADOP FS_CLONE FAILS DUE TO PORT CONFLICT BETWEEN RUN AND PATCH EDITION
 
*** 10/14/14 11:58 am ***
Service Request (SR) Number:
----------------------------
 
 
Problem Statement:
------------------
Running fs_clone after completing EBS and OAM integration and after 
completing a patch cycle results in fs_clone failing with the following 
errors:
 
Checking  WLS OAEA Application Port on aolesc11:  Port Value = 6801
RC-50204: Error: - WLS OAEA Application Port in use: Port Value = 6801
 
-----------------------------
ERROR: The following required ports are in use:
-----------------------------
6801 : WLS OAEA Application Port
Corrective Action: Free the listed ports and retry the adop operation.
 
Detailed Results of Problem Analysis:
-------------------------------------
The problem is due to the newly added managed server port being the same for 
both the run and patch edition.  Going back to the sequence of steps and 
tracking the port assignment, it showed the following:
 
- deploy accessgate on patch
Creates managed server - oaea_server1:6801
This is the default port and doing this to the patch edition...
 
fs2 - run -> 6801 port
fs1 - patch -> 6801 port
 
- complete OAM registration
- close patching cycle
- cutover
- after cutover, SSO is working
 
fs1 - run -> 6801 port
fs2 - patch -> 6801 port
 
- fs_clone -> fails due to both run(fs1) and patch(fs2) referencing the same 
port 6801
 
Configuration and Version Details:
----------------------------------
OAM - 11.1.2.2.0
WG - 11.1.2.2.0
EAG - 1.2.3
WT - 11.1.1.6.0
 
EBS 12.2.4 w/ AD/TXK delta 5
 
Steps To Reproduce:
-------------------
As part of the EBS integration w/ OAM, we add a managed server for use as the 
EBS AccessGate (EAG) to the existing WLS in EBS.  There is an option to do 
this to both run edition, as well as the patch edition during an active patch 
cycle.  In this case the latter was done.  Here is a summary of the steps 
used:
 
1. Start patch cycle
2. Integrated OID and EBS
3. Cutover
4. Confirmed OID provisioning is working
5. Start patch cycle
6. Apply pre-req EBS patches for OAM
7. Proceed w/ OAM integration on patch file system
8. Cutover
9. Confirmed SSO/OAM is working
10. Run fs_clone -> this is where the issue appears
 
 
Additional Information:
-----------------------
The workaround here is to stop the oaea_server1 managed server operating in 
the run edition on port 6801, and then re-running fs_clone.  Once this is 
done, fs_clone completes and the patch edition now operates on port 6802 for 
the same managed server.
 
For A Severity 1 Bug: Justification and 24x7 Contact Details:
-------------------------------------------------------------
 
 
*** 10/14/14 01:19 pm ***
*** 10/16/14 07:05 am ***
*** 10/16/14 07:05 am ***
*** 10/17/14 01:47 am ***
*** 10/17/14 01:49 am *** 
*** 10/17/14 01:57 am ***
*** 10/17/14 08:47 am ***
*** 10/23/14 12:16 am ***
*** 10/23/14 12:17 am ***
*** 10/26/14 10:07 pm ***
*** 10/27/14 10:06 pm ***
*** 10/27/14 10:09 pm ***
*** 10/30/14 10:40 pm ***
*** 10/30/14 10:49 pm ***
*** 10/30/14 10:49 pm ***
*** 11/05/14 04:30 pm *** 
*** 11/05/14 04:30 pm ***
*** 11/06/14 10:59 am *** 
*** 11/17/14 09:20 pm ***
*** 12/02/14 12:36 am ***
*** 12/02/14 07:26 pm ***

Till a patch is made available, you need to shutdown the oaea managed server and restart fs_clone. So much for keeping all services online and the promise of no outage during fs_clone.