<?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 RuntimeLocalServer.exe never stops in Java Maps SDK Questions</title>
    <link>https://community.esri.com/t5/java-maps-sdk-questions/runtimelocalserver-exe-never-stops/m-p/682430#M2075</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;Hi Guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One observation I have made using the 10.1.1 SDK is that when you load an MPK for example the ESRI software spins up a RuntimeLocalServer instance to handle viewing that data. It will do this for each MPK you add to the map as a layer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you then remove layers the associated RuntimeLocalServer instance is never teared down until the application closes. If you then re-add&amp;nbsp; layers you added before it will seemingly reuse an existing&amp;nbsp; RuntimeLocalServer to service that MPK.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this intended behavior? For our needs we are concerned that too many instances of the RuntimeLocalServer may consume too much memory on our clients PC's&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 08 Aug 2016 18:05:52 GMT</pubDate>
    <dc:creator>MichaelKnight</dc:creator>
    <dc:date>2016-08-08T18:05:52Z</dc:date>
    <item>
      <title>RuntimeLocalServer.exe never stops</title>
      <link>https://community.esri.com/t5/java-maps-sdk-questions/runtimelocalserver-exe-never-stops/m-p/682430#M2075</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;Hi Guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One observation I have made using the 10.1.1 SDK is that when you load an MPK for example the ESRI software spins up a RuntimeLocalServer instance to handle viewing that data. It will do this for each MPK you add to the map as a layer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you then remove layers the associated RuntimeLocalServer instance is never teared down until the application closes. If you then re-add&amp;nbsp; layers you added before it will seemingly reuse an existing&amp;nbsp; RuntimeLocalServer to service that MPK.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this intended behavior? For our needs we are concerned that too many instances of the RuntimeLocalServer may consume too much memory on our clients PC's&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Aug 2016 18:05:52 GMT</pubDate>
      <guid>https://community.esri.com/t5/java-maps-sdk-questions/runtimelocalserver-exe-never-stops/m-p/682430#M2075</guid>
      <dc:creator>MichaelKnight</dc:creator>
      <dc:date>2016-08-08T18:05:52Z</dc:date>
    </item>
    <item>
      <title>Re: RuntimeLocalServer.exe never stops</title>
      <link>https://community.esri.com/t5/java-maps-sdk-questions/runtimelocalserver-exe-never-stops/m-p/682431#M2076</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Micheal,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;do you stop the service after removing the layer? Do you use&amp;nbsp;&lt;STRONG&gt;stopAsync()&amp;nbsp;&lt;/STRONG&gt;method? Can you provide the code?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Adam&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #353833; background-color: #eeeeef; font-size: 11.856px;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Oct 2016 06:58:54 GMT</pubDate>
      <guid>https://community.esri.com/t5/java-maps-sdk-questions/runtimelocalserver-exe-never-stops/m-p/682431#M2076</guid>
      <dc:creator>nita14</dc:creator>
      <dc:date>2016-10-12T06:58:54Z</dc:date>
    </item>
  </channel>
</rss>

