<?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: WCF: Slow steps in Splunk AppDynamics</title>
    <link>https://community.splunk.com/t5/Splunk-AppDynamics/WCF-Slow-steps/m-p/719695#M1647</link>
    <description>&lt;P&gt;The issue could be either related to network related or the service itself is taking longer time to respond.&lt;/P&gt;

&lt;P&gt;&lt;SPAN&gt;The first step would be to identify where the bottle necks is ?&amp;nbsp;For example, use WireShark to see if the connection establishment is taking a long time.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;&lt;SPAN&gt;As&amp;nbsp;it is WCF service, you can turn on WCF trace logs on the server. &amp;nbsp;Refer -&amp;nbsp;&lt;A href="http://msdn.microsoft.com/en-us/library/ms751526.aspx" target="_blank" rel="nofollow noopener noreferrer"&gt;http://msdn.microsoft.com/en-us/library/ms751526.aspx&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;&lt;SPAN&gt;WCF traces will give you details on what is happening on service side and is there any issue happening there.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 24 Aug 2017 05:08:35 GMT</pubDate>
    <dc:creator>Kartikay_Tripat</dc:creator>
    <dc:date>2017-08-24T05:08:35Z</dc:date>
    <item>
      <title>WCF: Slow steps</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/WCF-Slow-steps/m-p/719694#M1646</link>
      <description>&lt;P&gt;&lt;STRONG&gt;WCF call is very slow because of below step:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;System.ServiceModel.Dispatcher.RequestChannelBinder:Request: Unknown (execution time: 10594 ms of 10594 ms total) WCF (10594ms): [5]&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Anyone can give some idea or thoughts around the possible reason will be appreciated!&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Aug 2017 18:10:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/WCF-Slow-steps/m-p/719694#M1646</guid>
      <dc:creator>CommunityUser</dc:creator>
      <dc:date>2017-08-23T18:10:23Z</dc:date>
    </item>
    <item>
      <title>Re: WCF: Slow steps</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/WCF-Slow-steps/m-p/719695#M1647</link>
      <description>&lt;P&gt;The issue could be either related to network related or the service itself is taking longer time to respond.&lt;/P&gt;

&lt;P&gt;&lt;SPAN&gt;The first step would be to identify where the bottle necks is ?&amp;nbsp;For example, use WireShark to see if the connection establishment is taking a long time.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;&lt;SPAN&gt;As&amp;nbsp;it is WCF service, you can turn on WCF trace logs on the server. &amp;nbsp;Refer -&amp;nbsp;&lt;A href="http://msdn.microsoft.com/en-us/library/ms751526.aspx" target="_blank" rel="nofollow noopener noreferrer"&gt;http://msdn.microsoft.com/en-us/library/ms751526.aspx&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;&lt;SPAN&gt;WCF traces will give you details on what is happening on service side and is there any issue happening there.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Aug 2017 05:08:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/WCF-Slow-steps/m-p/719695#M1647</guid>
      <dc:creator>Kartikay_Tripat</dc:creator>
      <dc:date>2017-08-24T05:08:35Z</dc:date>
    </item>
  </channel>
</rss>

