RESOLVED: The issue was with 2 wrong DNS on Health check nodes. in AEM
6.5.5 this has been addressed added timeout configuration on this.
Does anyone know about this configuration usage and its importance? OSGI
I have this java 8 version. Will this support for AEM 6.5 ? java version
"1.8.0_161"Java(TM) SE Runtime Environment (build 1.8.0_161-b12)Java
HotSpot(TM) 64-Bit Server VM (build 25.161-b12, mixed mode)
@surabhikatiyarTried recreating multiple times and observed the same
issue, also observed service will come up after 2 or 3 Hrs and again
hangs in case if we restart. Too weird During startup, I Can see this
com.adobe.cq.deserfw.impl.DeserializationFirewallImpl Unable to load
Attach API. Unable to dynamically load deserialization protection agent.
This usually happens when running a JRE (instead of a JDK) or a JVM that
doesn't provide the Attach API. Please review ...
we are trying to upgrade from 6.3 to 6.5, We have taken fresh AEM 6.5
and deploying code and content from AEM 6.3 instance. After content
migration, all AEM service hangs and stays in the startup in progress
and most of the bundle shows resolved statushappening only on the
publisher mode of the instance No significant error logs observed