RC-50208: Exception in method TimedProcessTimer.run When Running txkEBSDomainConfig.pl Script On R12.2

On Oracle Applications 12.2.3 version, IAS for Applications Technology,
when attempting to re-deploy the WLS domains using txkEBSDomainConfig.pl,
the following error occurs:
StackTrace:
java.lang.IllegalArgumentException: timeout value is negative
at java.lang.Thread.sleep(Native Method)
at java.lang.Thread.sleep(Thread.java:905)
at oracle.apps.ad.util.TimedProcess$TimedProcessTimer.run(TimedProcess.java:703)
at java.lang.Thread.run(Thread.java:781)
RC-50208: Exception in method TimedProcessTimer.run
Raised by oracle.apps.ad.util.TimedProcess$TimedProcessTimer
The Admin Server is starting up in the background..
ERROR: Unable to startup the Admin Server within the time specified in the context variable s_adminservertimeout..
ERROR: Unable to startup the Admin Server. Cannot proceed with the deployment of EBS
Creation and deployment of E-Business Suite domain completed..
The issue can be reproduced at will with the following steps:
1. Run the script txkEBSDomainConfig.pl to re-deploy the WLS domains.
2. Review the logs.
CAUSE
The issue is caused by the context parameter value s_adminservertimeout which is set incorrectly to -1.
Due to which the below error is seen:
StackTrace:
java.lang.IllegalArgumentException: timeout value is negative
at java.lang.Thread.sleep(Native Method)
at java.lang.Thread.sleep(Thread.java:905)
at oracle.apps.ad.util.TimedProcess$TimedProcessTimer.run(TimedProcess.java:703)
at java.lang.Thread.run(Thread.java:781)
RC-50208: Exception in method TimedProcessTimer.run
Raised by oracle.apps.ad.util.TimedProcess$TimedProcessTimer
This is explained in the following bug:
Bug 18485007 - FS_CLONE FAIL WITH RC-50208: EXCEPTION IN METHOD TIMEDPROCESSPROCESS.RUN
SOLUTION
Please perform the below steps:
1. Shutdown the EBS Services.
2. In both the RUN and PATCH file system context file, modify s_adminservertimeout context variable value to 4000.
From
=====
-1
To
==
4000
2. Run AutoConfig from both the RUN and PATCH file system.
Ignore the Autoconfig failures on the patch file system.
NOTE: AutoConfig should be run in full mode (Without any mode specification) , otherwise Context File will not be uploaded to database.
3. Rerun the failed script in this case it is /txkEBSDomainConfig.pl and check whether the script completes successfully.
4. Migrate the solution to appropriate environments.