Why the SAP Java Server instances remain in an hanging/starting state during SCS/CI failover?

Issue

• SAP Java instance remains in a hanging/starting state while we test a takover scenario startup.
• If we simply stop and start the resource group on different servers while the outsider Application server remains active, it ends up starting normally and the foreign server simply reconnects its SAP instances to the Central Instance, keeping its work normally.
• If we simulate a crash scenario, leading the cluster to a takeover scenario, although IP, VG, LV, Filesystems and even SAP are started correctly and the cluster SAPinstance script gets a GREEN response, the SAP Java instance remains in a "starting" state. This is an internal SAP issue. Regular checks for SAPInstance return a "0" = OK status.
• In the takeover scenario, while the clustered Java instance is in the hanging "starting" state, if we stop the foreign application server instance, that same Java instance gets started almost instantly.