Issue: Weblogic apps are failed/admin state after applying weblogic patches and after restart twice came to up and running mode.
If your weblogic applications are entering an admin state or failing after applying patches and then returning to normal after a couple of restarts, it suggests that there might be some race conditions or issues related to the patching process. Here are a few possibilities:
Service Dependencies: The weblogic applications might have dependencies on other services or components that are being updated. In some cases, these dependencies might not be ready when the weblogic applications start after a patch. Subsequent restarts allow the system more time to ensure that all necessary components are in the correct state.
Configuration Changes: The patching process might include changes to configurations that require a couple of restarts to take effect. This could be related to the application server settings, database connections, or other configurations.
Delayed Startup Processes: Some processes or services that the weblogic applications depend on may take longer to start after the patches are applied. Restarting the applications multiple times gives these processes additional time to initialize.
Race Conditions: There might be race conditions or timing issues that cause the applications to fail during the initial restarts but are resolved with subsequent restarts.
To troubleshoot and address the issue:
Logs and Error Messages: Check the logs and error messages generated during the startup process to identify any specific issues or error codes. This information can provide insights into what might be going wrong during the initial restart attempts.
Dependencies: Review the dependencies of your weblogic applications, including database connections, network services, and other external dependencies. Ensure that these dependencies are fully started and operational before starting the weblogic applications.
Configuration Changes: Examine the patch documentation and release notes to identify any configuration changes that might require special attention. Make sure that all necessary configurations are in place.
Startup Order: If your weblogic applications have dependencies on other services, ensure that the startup order is configured correctly. You might need to adjust the startup scripts or configurations to accommodate any changes introduced by the patches.
Patch Reapplication: If the issue persists, consider reapplying the patches and carefully following the recommended procedures. Ensure that the patching process is completed successfully without interruptions.
Consult Vendor Documentation: Check the documentation provided by Oracle for WebLogic Server and any documentation related to the specific patches applied. It’s possible that there are known issues or recommended procedures for dealing with such situations.
