Zero Downtime Patching Rolling Restart Feature Failed to Work After Admin Port is Enabled
Last updated on JUNE 26, 2017
Applies to:Oracle WebLogic Server - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
When domain-wide administrator port is enabled, using Zero Downtime Patching workflow to execute rolling restart can cause a freeze of process.
- Via console: <Domain> --> Settings --> ZDT Control --> Clusters --> Patch --> Rolling Restart
- Via WLST command line: rollingRestart('cluster name')
After the process starts, all admin activities are moved to administration port and incoming admin requests on other ports are rejected. In Zero Downtime Patching Rolling Restart, the process attempt to test the regular port instead of the admin port for the admin URL in the step of resume the shutdown server.
As a result , only the first server in the cluster member list gets restarted, the second server in the member list remains shutdown state and the rolling restart process can not be proceed further since the second server.
Following the procedure for rolling restart as documented in:
Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help 12c (12.2.1)
Perform a Rolling Restart of Servers
ZDT Patching; A Simple Case – Rolling Restart
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms