Scalability Failures Causes Total Outage Of Environment
Last updated on SEPTEMBER 08, 2016
Applies to:Oracle Transportation Management - Version 6.2.0 to 6.3.3 [Release 6.2 to 6.3]
Information in this document applies to any platform.
Scalability failures cause total outage of environment. Occasionally, our Application Server instance of Weblogic will hang for some reason. This makes the OTM login page display "No login functionality is available for the DBA domain"
It will not be possible to stop the weblogic service on either server. Only recourse available is to reboot the servers to fix the weblogic issue.
Expectation: OTM is set up with scalability configuration. When Application Server instance of Weblogic hangs, the expectation is for the failed server to remove itself from the cluster and no longer be accessible. OTM processes should change over to the available server in the cluster. This does not happen.
Because of this issue, web servers will still try to reach them but instead get an error. This causes a total outage of the environment and users become completely unable to finish their work.
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