<?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: Recycle a Socket in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/recycle-a-socket/m-p/5094349#M540955</link>
    <description>Thanks, I was able to accomplish what I needed by temporarily lowering the keepalive to ensure any ports atht needed clearing/recycling happened.  thanks</description>
    <pubDate>Fri, 29 Feb 2008 19:29:35 GMT</pubDate>
    <dc:creator>Simpson</dc:creator>
    <dc:date>2008-02-29T19:29:35Z</dc:date>
    <item>
      <title>Recycle a Socket</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/recycle-a-socket/m-p/5094347#M540953</link>
      <description>Is there anyway to restart/recycle a single socket connection?   i know it will eventually time out but i have been asked to provide a solution to a socket that is stuck without a reboot.&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Mon, 25 Feb 2008 16:57:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/recycle-a-socket/m-p/5094347#M540953</guid>
      <dc:creator>Simpson</dc:creator>
      <dc:date>2008-02-25T16:57:20Z</dc:date>
    </item>
    <item>
      <title>Re: Recycle a Socket</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/recycle-a-socket/m-p/5094348#M540954</link>
      <description>Hi &lt;BR /&gt;What is the state of your socket?&lt;BR /&gt;&lt;BR /&gt;check with netstat -an or ndd -get /dev/tcp tcp_status&lt;BR /&gt;&lt;BR /&gt;else you have a ndd tcp_discon_by_addr&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Else we have a lot of different timeouts.&lt;BR /&gt;the most usefull is usually keepalive. you configure SO_KEEPALIVE on your socket, then it will send a probe to the peer. In case of no response after the usual timeout( tcp_ip_abort_interval ndd param) your connection is reset.&lt;BR /&gt;By default keepalive interval is 2hours, which is very long, you can lower it with ndd parameter tcp_keepalive_interval.&lt;BR /&gt;&lt;BR /&gt;You must then configure tcp_keepalive_interval and tcp_ip_abort_interval to values which matches with your requirements.&lt;BR /&gt;&lt;BR /&gt;If you lower tcp_ip_abort_interval, you need also to be sure tcp_notify_interval stay tcp_ip_abort_interval.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 25 Feb 2008 17:11:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/recycle-a-socket/m-p/5094348#M540954</guid>
      <dc:creator>Laurent Menase</dc:creator>
      <dc:date>2008-02-25T17:11:37Z</dc:date>
    </item>
    <item>
      <title>Re: Recycle a Socket</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/recycle-a-socket/m-p/5094349#M540955</link>
      <description>Thanks, I was able to accomplish what I needed by temporarily lowering the keepalive to ensure any ports atht needed clearing/recycling happened.  thanks</description>
      <pubDate>Fri, 29 Feb 2008 19:29:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/recycle-a-socket/m-p/5094349#M540955</guid>
      <dc:creator>Simpson</dc:creator>
      <dc:date>2008-02-29T19:29:35Z</dc:date>
    </item>
  </channel>
</rss>

