EM 13.5 RU Patching Failed with "Deploying library ... Failed, OMS may be running, please check the log file for details" (Doc ID 2989160.1)

<PATCH_TOP_DIR>><OMS_HOME>/OMSPatcher/omspatcher apply
OMSPatcher Automation Tool
Copyright (c) 2017, Oracle Corporation.  All rights reserved.
OMSPatcher version : 13.9.5.15.0
OUI version        : 13.9.4.0.0
....
Please enter OMS weblogic admin server URL(t3s://<ADMIN_CONSOLE_HOST>:ADMIN_CONSOLE_PORT):>
Please enter OMS weblogic admin server username(<ADMINISTARTOR_SERVER_USERNAME>):>
Please enter OMS weblogic admin server password:>

Deploying Library  .....slf4japi_jar#1.7.36@1.7.36
Please monitor log file: <OMS_HOME>/cfgtoollogs/omspatcher/2023-12-19_00-44-49AM_SystemPatch_35460709_12/deploy_library_2023-12-19_00-44-49AM.log

Oracle Enterprise Manager Cloud Control 13c Release 5
Copyright (c) 1996, 2021 Oracle Corporation.  All rights reserved.
Deploying Library ... Started
Deploying library ... Failed. Check the log <INSTANCE_HOME>/em/EMGC_OMS1/sysman/log/emctl.log
Error message : Deployment of library failed. OMS may be running, please check the log file for details.
return value : 1

<Nov 9, 2023 4:02:29 PM CET> <Info> <Security> <BEA-090909> <Using the configured custom SSL Hostname Verifier implementation: weblogic.security.utils.SSLWLSHostnameVerifier$NullHostnameVerifier.>
Successfully connected to Admin Server "EMGC_ADMINSERVER" that belongs to domain "GCDomain".

Deploying application from<OMS_HOME>/sysman/thirdparty/slf4j-api.jar to targets EMGC_OMS1, (upload=false) ...
<Nov 9, 2023 4:02:32 PM CET> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, slf4japi_jar#1.7.36@1.7.36 [archive: <OMS_HOME>/sysman/thirdparty/slf4j-api.jar], to EMGC_OMS1 .>
[Deployer:149140]The task cannot be processed further until the current edit session is activated. When this occurs, task processing will continue. The user can exit the deployer tool without affecting the task.
....................................................................................................No stack trace available.
This Exception occurred at Thu Nov 09 16:07:33 CET 2023.
weblogic.management.scripting.ScriptException: Error occurred while performing deploy : The action you performed timed out after 300,000 milliseconds.
No stack trace available.
Name of Exception: main.WLSTException
Code of Exception: Error occurred while performing deploy : Target exception thrown while deploying application: Error occurred while performing deploy : The action you performed timed out after 300,000 milliseconds. : Error occurred while performing deploy : The action you performed timed out after 300,000 milliseconds.
Use dumpStack() to view the full stacktrace :
<Nov 9, 2023 4:07:33 PM CET> <Warning> <JNDI> <BEA-050001> <WLContext.close() was called in a different thread than the one in which it was created.>

2023-11-09 16:07:33,400 [main] INFO util.EmctlUtil - Exit code: 1
2023-11-09 16:07:33,400 [main] INFO util.EmctlUtil - error messages of the command : No messages

2023-11-09 16:07:33,400 [main] INFO oms.DeployLibrary - Done deploying library with wlst exit code=1
2023-11-09 16:07:33,400 [main] INFO oms.DeployLibrary - Deployment of library failed with exit code 1
2023-11-09 16:07:33,400 [main] ERROR oms.DeployLibrary - Failed to deploy library : Deployment of library failed. OMS may be running, please check the log file for details.
java.lang.Exception: Deployment of library failed. OMS may be running, please check the log file for details.
at oracle.sysman.emctl.config.oms.DeployLibrary.doDeployLibrary(DeployLibrary.java:178) ~[emCoreConsole.jar:?]
at oracle.sysman.emctl.config.oms.DeployLibrary.main(DeployLibrary.java:113) [emCoreConsole.jar:?]
2023-11-09 16:14:57,632 [main] INFO wls.OMSController - Executing emctl command : stop