![]() It is clear from OS and application perspective with above logs and PS output user does initiate two PIDs with same agent config parameters (-javaagent and -Dappdynamics) args with 10 seconds period gap and hence and agent shows "JVM startup time" discrepancy as same node name used for two different PIDs initiated by OS which is "Invalid config" as per doc specs. If you see later JVM has additional args:Ĭonclusion: The agent getting same node id because we are using manual node as per recent logs shared still.2022 01:05:50,251 INFO ConfigurationChannel - Registration information received Node ID Component ID Application ID 2022 01:05:50,251 INFO ConfigurationChannel - Auto agent registration attempted: Application Name Component Name Node Name 2022 01:05:45,827 INFO AgentKernel - JVM Args : -Xmx2g | -Xms2g | -XX:+UseParallelGC | -XX:NewRatio=8 | -XX:+HeapDumpOnOutOfMemoryError | -javaagent:/opt/appdynamics/appagent/java/javaagent.jar | =/app/pingdirectory/racdirectory/logs/ | =PingDirectory | .certificate.validation=true | -add-opens=java.base/java.io=ALL-UNNAMED | -add-opens=java.base/java.lang=ALL-UNNAMED | -add-opens=java.base/=ALL-UNNAMED | -add-opens=java.base/=ALL-UNNAMED | -add-opens=java.base/curity=ALL-UNNAMED | -add-opens=java.base/java.text=ALL-UNNAMED | -add-opens=java.base/java.util=ALL-UNNAMED | -add-opens=java.base/=ALL-UNNAMED | -add-opens=sktop/=ALL-UNNAMED | -Xlog:gc*:file=/app/pingdirectory/racdirectory/current/logs/jvm/gc.log:time,uptime,level,tags:filecount=3,filesize=100m | .scriptName=export-ldif | 2022 01:05:45,845 INFO AgentKernel - JVM Runtime Name: Agent init] 28 Apr. ![]() Second JVM PID with just 10 seconds gap:.2022 01:05:39,642 INFO ConfigurationChannel - Registration information received Node ID Component ID Application ID 2022 01:05:39,642 INFO ConfigurationChannel - Auto agent registration attempted: Application Name Component Name Node Name 2022 01:05:35,045 INFO AgentKernel - JVM Args : -Xmx256m | -Xms128m | -javaagent:/opt/appdynamics/appagent/java/javaagent.jar | =/app/pingdirectory/racdirectory/logs/ | =PingDirectory | .certificate.validation=true | -add-opens=java.base/java.io=ALL-UNNAMED | -add-opens=java.base/java.lang=ALL-UNNAMED | -add-opens=java.base/=ALL-UNNAMED | -add-opens=java.base/=ALL-UNNAMED | -add-opens=java.base/curity=ALL-UNNAMED | -add-opens=java.base/java.text=ALL-UNNAMED | -add-opens=java.base/java.util=ALL-UNNAMED | -add-opens=java.base/=ALL-UNNAMED | -add-opens=sktop/=ALL-UNNAMED | .scriptName=export-ldif | 2022 01:05:35,054 INFO AgentKernel - JVM Runtime Name: Agent init] 28 Apr. First JVM PID with below JVM startup args stated at 28 Apr 01:05:35 seconds at host " ."ĪD Agent init] 28 Apr.Next steps: I have offered web call in tickets/316533 see if you can join we can discuss over your concerns, Also, I will leave it to others to also comment in the community to comment on my analysis. If you see in same host " dld201013230254" at 1:05 AM two app JVM PID started which is using same = value and you can see the evidence of difference in application runtime args difference, this args are from app not javaagent. I have "NOT" shared theory but shared evidence it is the customer starting second JVM PID here. Hi see a disconnect, have you checked the support update on the root cause of the April 29 update ticket? I manage support in India and I confirm from supoort ticket#316533? Why have not the user come back in ticket? The root cause with evidence is already shown but i am listing here as you are reaching in community, I suggest you reach any application dev team, You can see there are two JVM PID (javaagent is a thread (premain program) part of app JVM PID and it will not create JVM PID).
0 Comments
Leave a Reply. |