<?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 Re: Attempting to start a debug remote session---Connection Refused in ArcGIS GeoEvent Server Questions</title>
    <link>https://community.esri.com/t5/arcgis-geoevent-server-questions/attempting-to-start-a-debug-remote-session/m-p/491614#M2150</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Brian,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;On the machine where your GeoEvent Processor is setup go to the folder '[GeoEvent Home]\sdk'. Inside you will find a file 'GeoEvent Processor Developer Guide.pdf' Please read 'Appendix C: Logging and Debugging' section of this document. This will explain what is needed to run GeoEvent Processor in 'DEBUG' mode as well as how do you attach a remote debugger to it.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Please let us know if you require further assistance.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Vlad.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 01 Apr 2014 22:27:42 GMT</pubDate>
    <dc:creator>VladislavPlechnoy</dc:creator>
    <dc:date>2014-04-01T22:27:42Z</dc:date>
    <item>
      <title>Attempting to start a debug remote session---Connection Refused</title>
      <link>https://community.esri.com/t5/arcgis-geoevent-server-questions/attempting-to-start-a-debug-remote-session/m-p/491613#M2149</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Was wondering if I have to have a local AGES running in order to debug??&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Also how does the debug session know the values if it has not been connected to an adapter-- is this something that would get set in the defaults??&amp;nbsp; or does it pair to the known domain of the transport and set the source to the debug session?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;P.S. been trying to get some more documentation on AGES --- seems pretty difficult to find and I feel like I am programming and configuring in the dark &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Mar 2014 19:55:08 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-geoevent-server-questions/attempting-to-start-a-debug-remote-session/m-p/491613#M2149</guid>
      <dc:creator>BrianLocke</dc:creator>
      <dc:date>2014-03-31T19:55:08Z</dc:date>
    </item>
    <item>
      <title>Re: Attempting to start a debug remote session---Connection Refused</title>
      <link>https://community.esri.com/t5/arcgis-geoevent-server-questions/attempting-to-start-a-debug-remote-session/m-p/491614#M2150</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Brian,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;On the machine where your GeoEvent Processor is setup go to the folder '[GeoEvent Home]\sdk'. Inside you will find a file 'GeoEvent Processor Developer Guide.pdf' Please read 'Appendix C: Logging and Debugging' section of this document. This will explain what is needed to run GeoEvent Processor in 'DEBUG' mode as well as how do you attach a remote debugger to it.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Please let us know if you require further assistance.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Vlad.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Apr 2014 22:27:42 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-geoevent-server-questions/attempting-to-start-a-debug-remote-session/m-p/491614#M2150</guid>
      <dc:creator>VladislavPlechnoy</dc:creator>
      <dc:date>2014-04-01T22:27:42Z</dc:date>
    </item>
  </channel>
</rss>

