<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic jvm crash with jdk 8 and AD agent ver 4.3.2.2 in Splunk AppDynamics</title>
    <link>https://community.splunk.com/t5/Splunk-AppDynamics/jvm-crash-with-jdk-8-and-AD-agent-ver-4-3-2-2/m-p/727456#M5775</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;we have noticed&amp;nbsp; jvm crashes in prod, when we look for stack trace we found AD related classes, no issues on other apps servers where AppDynamic agent is not installed, &amp;nbsp;&amp;nbsp;can some one help us&amp;nbsp;to figure out the issue?&lt;/P&gt;
&lt;P&gt;JAVA: jdk_1_8_0_112&lt;/P&gt;
&lt;P&gt;Tomcat: 7.0.56&lt;/P&gt;
&lt;P&gt;AD java agent: 4.3.2.2&lt;/P&gt;


&lt;P&gt;Stack: [0x00007f01e7f2c000,0x00007f01e802d000],&amp;nbsp; sp=0x00007f01e802b6e0,&amp;nbsp; free space=1021k&lt;BR /&gt;Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)&lt;BR /&gt;J 1049073 C2 java.util.concurrent.ConcurrentHashMap.get(Ljava/lang/Object;)Ljava/lang/Object; (162 bytes) @ 0x00007f027e1b693c [0x00007f027e1b6900+0x3c]&lt;BR /&gt;j&amp;nbsp; com.singularity.ee.agent.appagent.services.transactionmonitor.instrumentation.b.a()I+150&lt;BR /&gt;j&amp;nbsp; com.singularity.ee.agent.appagent.services.transactionmonitor.instrumentation.b.run()V+7&lt;BR /&gt;J 30308 C2 com.singularity.ee.util.javaspecific.scheduler.b.b()V (173 bytes) @ 0x00007f027b728990 [0x00007f027b7287e0+0x1b0]&lt;BR /&gt;J 17509 C2 com.singularity.ee.util.javaspecific.scheduler.b.run()V (22 bytes) @ 0x00007f02781c1c40 [0x00007f02781c1c00+0x40]&lt;BR /&gt;J 12948 C2 com.singularity.ee.util.javaspecific.scheduler.i.a(Ljava/lang/Runnable;)V (391 bytes) @ 0x00007f02793a4f98 [0x00007f02793a4da0+0x1f8]&lt;BR /&gt;J 50022 C2 com.singularity.ee.util.javaspecific.scheduler.i.run()V (67 bytes) @ 0x00007f027ba20d20 [0x00007f027ba20a40+0x2e0]&lt;BR /&gt;J 264968 C2 java.lang.Thread.run()V (17 bytes) @ 0x00007f027a1c91ac [0x00007f027a1c9160+0x4c]&lt;BR /&gt;v&amp;nbsp; ~StubRoutines::call_stub&lt;BR /&gt;V&amp;nbsp; [libjvm.so+0x690c66]&amp;nbsp; JavaCalls::call_helper(JavaValue*, methodHandle*, JavaCallArguments*, Thread*)+0x1056&lt;BR /&gt;V&amp;nbsp; [libjvm.so+0x691171]&amp;nbsp; JavaCalls::call_virtual(JavaValue*, KlassHandle, Symbol*, Symbol*, JavaCallArguments*, Thread*)+0x321&lt;BR /&gt;V&amp;nbsp; [libjvm.so+0x691617]&amp;nbsp; JavaCalls::call_virtual(JavaValue*, Handle, KlassHandle, Symbol*, Symbol*, Thread*)+0x47&lt;BR /&gt;V&amp;nbsp; [libjvm.so+0x72c990]&amp;nbsp; thread_entry(JavaThread*, Thread*)+0xa0&lt;BR /&gt;V&amp;nbsp; [libjvm.so+0xa755f3]&amp;nbsp; JavaThread::thread_main_inner()+0x103&lt;BR /&gt;V&amp;nbsp; [libjvm.so+0xa7573c]&amp;nbsp; JavaThread::run()+0x11c&lt;BR /&gt;V&amp;nbsp; [libjvm.so+0x926138]&amp;nbsp; java_start(Thread*)+0x108&lt;BR /&gt;C&amp;nbsp; [libpthread.so.0+0x7dc5]&amp;nbsp; start_thread+0xc5&lt;/P&gt;


&lt;P&gt;thanks&lt;/P&gt;
&lt;P&gt;Niranjan&lt;/P&gt;</description>
    <pubDate>Thu, 29 Jun 2017 11:31:47 GMT</pubDate>
    <dc:creator>CommunityUser</dc:creator>
    <dc:date>2017-06-29T11:31:47Z</dc:date>
    <item>
      <title>jvm crash with jdk 8 and AD agent ver 4.3.2.2</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/jvm-crash-with-jdk-8-and-AD-agent-ver-4-3-2-2/m-p/727456#M5775</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;we have noticed&amp;nbsp; jvm crashes in prod, when we look for stack trace we found AD related classes, no issues on other apps servers where AppDynamic agent is not installed, &amp;nbsp;&amp;nbsp;can some one help us&amp;nbsp;to figure out the issue?&lt;/P&gt;
&lt;P&gt;JAVA: jdk_1_8_0_112&lt;/P&gt;
&lt;P&gt;Tomcat: 7.0.56&lt;/P&gt;
&lt;P&gt;AD java agent: 4.3.2.2&lt;/P&gt;


&lt;P&gt;Stack: [0x00007f01e7f2c000,0x00007f01e802d000],&amp;nbsp; sp=0x00007f01e802b6e0,&amp;nbsp; free space=1021k&lt;BR /&gt;Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)&lt;BR /&gt;J 1049073 C2 java.util.concurrent.ConcurrentHashMap.get(Ljava/lang/Object;)Ljava/lang/Object; (162 bytes) @ 0x00007f027e1b693c [0x00007f027e1b6900+0x3c]&lt;BR /&gt;j&amp;nbsp; com.singularity.ee.agent.appagent.services.transactionmonitor.instrumentation.b.a()I+150&lt;BR /&gt;j&amp;nbsp; com.singularity.ee.agent.appagent.services.transactionmonitor.instrumentation.b.run()V+7&lt;BR /&gt;J 30308 C2 com.singularity.ee.util.javaspecific.scheduler.b.b()V (173 bytes) @ 0x00007f027b728990 [0x00007f027b7287e0+0x1b0]&lt;BR /&gt;J 17509 C2 com.singularity.ee.util.javaspecific.scheduler.b.run()V (22 bytes) @ 0x00007f02781c1c40 [0x00007f02781c1c00+0x40]&lt;BR /&gt;J 12948 C2 com.singularity.ee.util.javaspecific.scheduler.i.a(Ljava/lang/Runnable;)V (391 bytes) @ 0x00007f02793a4f98 [0x00007f02793a4da0+0x1f8]&lt;BR /&gt;J 50022 C2 com.singularity.ee.util.javaspecific.scheduler.i.run()V (67 bytes) @ 0x00007f027ba20d20 [0x00007f027ba20a40+0x2e0]&lt;BR /&gt;J 264968 C2 java.lang.Thread.run()V (17 bytes) @ 0x00007f027a1c91ac [0x00007f027a1c9160+0x4c]&lt;BR /&gt;v&amp;nbsp; ~StubRoutines::call_stub&lt;BR /&gt;V&amp;nbsp; [libjvm.so+0x690c66]&amp;nbsp; JavaCalls::call_helper(JavaValue*, methodHandle*, JavaCallArguments*, Thread*)+0x1056&lt;BR /&gt;V&amp;nbsp; [libjvm.so+0x691171]&amp;nbsp; JavaCalls::call_virtual(JavaValue*, KlassHandle, Symbol*, Symbol*, JavaCallArguments*, Thread*)+0x321&lt;BR /&gt;V&amp;nbsp; [libjvm.so+0x691617]&amp;nbsp; JavaCalls::call_virtual(JavaValue*, Handle, KlassHandle, Symbol*, Symbol*, Thread*)+0x47&lt;BR /&gt;V&amp;nbsp; [libjvm.so+0x72c990]&amp;nbsp; thread_entry(JavaThread*, Thread*)+0xa0&lt;BR /&gt;V&amp;nbsp; [libjvm.so+0xa755f3]&amp;nbsp; JavaThread::thread_main_inner()+0x103&lt;BR /&gt;V&amp;nbsp; [libjvm.so+0xa7573c]&amp;nbsp; JavaThread::run()+0x11c&lt;BR /&gt;V&amp;nbsp; [libjvm.so+0x926138]&amp;nbsp; java_start(Thread*)+0x108&lt;BR /&gt;C&amp;nbsp; [libpthread.so.0+0x7dc5]&amp;nbsp; start_thread+0xc5&lt;/P&gt;


&lt;P&gt;thanks&lt;/P&gt;
&lt;P&gt;Niranjan&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jun 2017 11:31:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/jvm-crash-with-jdk-8-and-AD-agent-ver-4-3-2-2/m-p/727456#M5775</guid>
      <dc:creator>CommunityUser</dc:creator>
      <dc:date>2017-06-29T11:31:47Z</dc:date>
    </item>
    <item>
      <title>Re: jvm crash with jdk 8 and AD agent ver 4.3.2.2</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/jvm-crash-with-jdk-8-and-AD-agent-ver-4-3-2-2/m-p/727457#M5776</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;SPAN&gt;Niranjan,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Crashes like this are very rare, so m&lt;/SPAN&gt;&lt;SPAN&gt;y recommendation is to open a Support ticket at&amp;nbsp;&lt;A href="https://help.appdynamics.com/hc/en-us/requests/new" target="_blank" rel="nofollow noopener noreferrer"&gt;https://help.appdynamics.com/hc/en-us/requests/new&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Please provide the stack trace below, and also upload the agent logs and ideally the java core dump file to the case so that the Support team can determine what went wrong.&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Brian Wheeldon&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jun 2017 18:25:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/jvm-crash-with-jdk-8-and-AD-agent-ver-4-3-2-2/m-p/727457#M5776</guid>
      <dc:creator>Brian_Wheeldon</dc:creator>
      <dc:date>2017-06-29T18:25:09Z</dc:date>
    </item>
  </channel>
</rss>

