<?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: IoT Gateway Write Socket Error - Azure IoT Hub in Mfg Solutions &amp; Apps</title>
    <link>https://www.ptcusercommunity.com/t5/Mfg-Solutions-Apps/IoT-Gateway-Write-Socket-Error-Azure-IoT-Hub/m-p/880841#M2623</link>
    <description>&lt;P&gt;&lt;SPAN style="background: var(--ck-color-mention-background); color: var(--ck-color-mention-text);"&gt;&lt;a href="https://www.ptcusercommunity.com/t5/user/viewprofilepage/user-id/702622"&gt;@LL_10077020&lt;/a&gt;&lt;/SPAN&gt; ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please take a look at the Kepware knowledge base article in the following link. Although, the article is for an IoT Gateway Rest Client I believe the suggested resolution also applies an IoT gateway MQTT Agent disconnecting due to a full buffer:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.ptc.com/en/support/article/CS308348" target="_blank"&gt;Article - CS308348 - IOT Gateway REST client agent dropped data change events in KEPServerEX / ThingWorx Industrial Connectivity (ptc.com)&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I recommend opening a support ticket with the Kepware Technical Support team if the article isn't able to resolve your Issue. Here is a link to the my kepware page, where a ticket can be submitted:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://my.kepware.com/s/login/?ec=302&amp;amp;startURL=%2Fs%2F" target="_blank"&gt;Log In | My Kepware&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;*Chris&lt;/P&gt;</description>
    <pubDate>Tue, 13 Jun 2023 15:31:28 GMT</pubDate>
    <dc:creator>cmorehead</dc:creator>
    <dc:date>2023-06-13T15:31:28Z</dc:date>
    <item>
      <title>IoT Gateway Write Socket Error - Azure IoT Hub</title>
      <link>https://www.ptcusercommunity.com/t5/Mfg-Solutions-Apps/IoT-Gateway-Write-Socket-Error-Azure-IoT-Hub/m-p/874552#M2616</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am having a issue where the IoT Gateway, in an intermittent way, loses connection from IoT hub, then it starts a loop of errors trying to connect and being disconnected with the following messages:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Note: I hid the agent and broker link for security reason.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Date Time Level Source Event&lt;BR /&gt;5/10/2023 1:16:13 AM Warning KEPServerEX\Runtime The MQTT agent '&lt;STRONG&gt;My agent&lt;/STRONG&gt;' published events buffer is full. Dropping new data change events&lt;BR /&gt;5/10/2023 1:16:14 AM Information KEPServerEX\Runtime MQTT agent '&lt;STRONG&gt;My agent&lt;/STRONG&gt;' is connected to broker '&lt;STRONG&gt;My&lt;/STRONG&gt;&amp;nbsp;&lt;STRONG&gt;Broker Link&lt;/STRONG&gt;'&lt;BR /&gt;5/10/2023 1:16:14 AM Error KEPServerEX\Runtime MQTT agent '&lt;STRONG&gt;My agent&lt;/STRONG&gt;' disconnected - reason 'Connection reset by peer: socket write error'&lt;/P&gt;
&lt;P&gt;-------------------------------------------------------------------------------------------------------------------&lt;/P&gt;
&lt;P&gt;When I reinitialize the application, it connects again. Is there a fix or mitigation action I can set in kepware? For exemple, to restart Iot Gateway automatically&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="headerbuttontrackingcode"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="headerbuttontrackingcode"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="headerbuttontrackingcode"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 17 May 2023 15:38:58 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/Mfg-Solutions-Apps/IoT-Gateway-Write-Socket-Error-Azure-IoT-Hub/m-p/874552#M2616</guid>
      <dc:creator>LL_10077020</dc:creator>
      <dc:date>2023-05-17T15:38:58Z</dc:date>
    </item>
    <item>
      <title>Re: IoT Gateway Write Socket Error - Azure IoT Hub</title>
      <link>https://www.ptcusercommunity.com/t5/Mfg-Solutions-Apps/IoT-Gateway-Write-Socket-Error-Azure-IoT-Hub/m-p/880841#M2623</link>
      <description>&lt;P&gt;&lt;SPAN style="background: var(--ck-color-mention-background); color: var(--ck-color-mention-text);"&gt;&lt;a href="https://www.ptcusercommunity.com/t5/user/viewprofilepage/user-id/702622"&gt;@LL_10077020&lt;/a&gt;&lt;/SPAN&gt; ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please take a look at the Kepware knowledge base article in the following link. Although, the article is for an IoT Gateway Rest Client I believe the suggested resolution also applies an IoT gateway MQTT Agent disconnecting due to a full buffer:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.ptc.com/en/support/article/CS308348" target="_blank"&gt;Article - CS308348 - IOT Gateway REST client agent dropped data change events in KEPServerEX / ThingWorx Industrial Connectivity (ptc.com)&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I recommend opening a support ticket with the Kepware Technical Support team if the article isn't able to resolve your Issue. Here is a link to the my kepware page, where a ticket can be submitted:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://my.kepware.com/s/login/?ec=302&amp;amp;startURL=%2Fs%2F" target="_blank"&gt;Log In | My Kepware&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;*Chris&lt;/P&gt;</description>
      <pubDate>Tue, 13 Jun 2023 15:31:28 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/Mfg-Solutions-Apps/IoT-Gateway-Write-Socket-Error-Azure-IoT-Hub/m-p/880841#M2623</guid>
      <dc:creator>cmorehead</dc:creator>
      <dc:date>2023-06-13T15:31:28Z</dc:date>
    </item>
  </channel>
</rss>

