Domain might be locked by some other WLS user process

Validating configuration on node: [hostname].
    Log: /apps2/oracle/product/fs_ne/EBSapps/log/adop/24/20180404_200441/prepare/validate/hostname
        [WARNING]: There could be issues while validating the ports used for E-Business Suite instance against ports used in /etc/services. Refer the log file for more details.
        [WARNING]: Either some of the required entries in /etc/hosts file might be missing (e.g. localhost or hostname) OR the file /etc/hosts could not be read.
        [ERROR]: Domain might be locked by some other WLS user process
    [UNEXPECTED]Error occurred running "perl /apps2/oracle/product/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPValidations.pl  -contextfile=/apps2/oracle/product/fs2/inst/apps/DEV_hostname/appl/admin/DEV_suthakar.xml -patchctxfile=/apps2/oracle/product/fs1/inst/apps/DEV_suthakar/appl/admin/DEV_suthakar.xml -phase=prepare -logloc=/apps2/oracle/product/fs_ne/EBSapps/log/adop/24/20180404_200441/prepare/validate/suthakar -promptmsg=hide"
    [UNEXPECTED]Error 1 occurred while Executing txkADOPValidation script on hostname

If the EBS Weblogic domain is in EDIT mode, it can cause adop to fail.
Someone with administrator privileges on WLS Admin Console may have locked the Weblogic domain for making changes, and has not released the checkout.
This leaves the domain in edit mode, resulting in the issue

To resolve the issue test the following steps in a development instance and then migrate accordingly:
1. Start the admin server on the run file system (if not started already).
2. Login in to WLS Admin Console (http(s)://hostname.domain:/console)
3. Click on the "Activate Changes" or the "Release Configuration" button (depending on the version) in the "Change Center" region on the top left corner.
4. Logout of the WLS console.
5. Rerun the adop phase=prepare command and confirm adop completes successfully.

doc reference : Doc ID 2042785.1