<?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 HTTP calls missing from Application Flow Map after JDK Upgrade in Splunk AppDynamics</title>
    <link>https://community.splunk.com/t5/Splunk-AppDynamics/HTTP-calls-missing-from-Application-Flow-Map-after-JDK-Upgrade/m-p/719511#M1557</link>
    <description>&lt;P&gt;We have one application (App A) which calls another app (App B) via HTTP(s) API. Both apps have AppD Machine and App agents&amp;nbsp;installed. After performing an upgrade on App A from Java 1.8 to OpenJDK11, we are no longer seeing the interaction between App A &amp;amp; B on the Application Flow Map.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any idea why an HTTP API call would no longer show up on our Application Flow Map after a JDK upgrade? We know&amp;nbsp;&lt;EM&gt;for certain&amp;nbsp;&lt;/EM&gt;the call is still being made, otherwise there'd be a much larger fire to put out.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;App A is custom Java app running on OpenJDK11&lt;UL&gt;&lt;LI&gt;This is what has changed&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;App B is a COTS Java app running on Java 1.8&lt;/LI&gt;&lt;LI&gt;App A connects to App B via HTTP(s) API call&lt;/LI&gt;&lt;LI&gt;Both App A and App B have machine agents installed and running&lt;UL&gt;&lt;LI&gt;Both are running on Java 1.8&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
    <pubDate>Tue, 10 Dec 2019 13:19:38 GMT</pubDate>
    <dc:creator>CommunityUser</dc:creator>
    <dc:date>2019-12-10T13:19:38Z</dc:date>
    <item>
      <title>HTTP calls missing from Application Flow Map after JDK Upgrade</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/HTTP-calls-missing-from-Application-Flow-Map-after-JDK-Upgrade/m-p/719511#M1557</link>
      <description>&lt;P&gt;We have one application (App A) which calls another app (App B) via HTTP(s) API. Both apps have AppD Machine and App agents&amp;nbsp;installed. After performing an upgrade on App A from Java 1.8 to OpenJDK11, we are no longer seeing the interaction between App A &amp;amp; B on the Application Flow Map.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any idea why an HTTP API call would no longer show up on our Application Flow Map after a JDK upgrade? We know&amp;nbsp;&lt;EM&gt;for certain&amp;nbsp;&lt;/EM&gt;the call is still being made, otherwise there'd be a much larger fire to put out.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;App A is custom Java app running on OpenJDK11&lt;UL&gt;&lt;LI&gt;This is what has changed&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;App B is a COTS Java app running on Java 1.8&lt;/LI&gt;&lt;LI&gt;App A connects to App B via HTTP(s) API call&lt;/LI&gt;&lt;LI&gt;Both App A and App B have machine agents installed and running&lt;UL&gt;&lt;LI&gt;Both are running on Java 1.8&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Tue, 10 Dec 2019 13:19:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/HTTP-calls-missing-from-Application-Flow-Map-after-JDK-Upgrade/m-p/719511#M1557</guid>
      <dc:creator>CommunityUser</dc:creator>
      <dc:date>2019-12-10T13:19:38Z</dc:date>
    </item>
    <item>
      <title>Re: HTTP calls missing from Application Flow Map after JDK Upgrade</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/HTTP-calls-missing-from-Application-Flow-Map-after-JDK-Upgrade/m-p/719512#M1558</link>
      <description>&lt;P&gt;What version is your agents and controller? AppD supports OpenJDK11 but I think it has to be version 4.5.6 and on.&lt;/P&gt;</description>
      <pubDate>Thu, 12 Dec 2019 21:03:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/HTTP-calls-missing-from-Application-Flow-Map-after-JDK-Upgrade/m-p/719512#M1558</guid>
      <dc:creator>millerep</dc:creator>
      <dc:date>2019-12-12T21:03:31Z</dc:date>
    </item>
  </channel>
</rss>

