<?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: UCX Memory Problem in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/ucx-memory-problem/m-p/3692022#M73265</link>
    <description>What version of VMS and UCX?&lt;BR /&gt;Was there any messages in operator.log?&lt;BR /&gt;</description>
    <pubDate>Fri, 16 Dec 2005 08:48:43 GMT</pubDate>
    <dc:creator>Ian Miller.</dc:creator>
    <dc:date>2005-12-16T08:48:43Z</dc:date>
    <item>
      <title>UCX Memory Problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ucx-memory-problem/m-p/3692021#M73264</link>
      <description>My VAX server transfer data to other VMS boxes using FTP service  and also talks to FEP using UCX service. These two are the only UCX service my VAX server does and remaining activities are on DECNET. All of a sudden since yesterday, at 02:03 hrs in the morning my server is losing all UCX socket connections. How to find out the reason for the problem ?</description>
      <pubDate>Thu, 15 Dec 2005 06:30:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ucx-memory-problem/m-p/3692021#M73264</guid>
      <dc:creator>Sk Noorul  Hassan</dc:creator>
      <dc:date>2005-12-15T06:30:24Z</dc:date>
    </item>
    <item>
      <title>Re: UCX Memory Problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ucx-memory-problem/m-p/3692022#M73265</link>
      <description>What version of VMS and UCX?&lt;BR /&gt;Was there any messages in operator.log?&lt;BR /&gt;</description>
      <pubDate>Fri, 16 Dec 2005 08:48:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ucx-memory-problem/m-p/3692022#M73265</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2005-12-16T08:48:43Z</dc:date>
    </item>
    <item>
      <title>Re: UCX Memory Problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ucx-memory-problem/m-p/3692023#M73266</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;$ UCX SHOW COMM and $ UCX SHOW COMM/MEM will show the amount of data structures allocated and used by UCX.&lt;BR /&gt;&lt;BR /&gt;Please check, whether the peak values of any resource have reached their maximum value.&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Fri, 16 Dec 2005 09:01:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ucx-memory-problem/m-p/3692023#M73266</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-12-16T09:01:15Z</dc:date>
    </item>
    <item>
      <title>Re: UCX Memory Problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ucx-memory-problem/m-p/3692024#M73267</link>
      <description>My VMS version is 7.1 &amp;amp; UCX version is 4.2&lt;BR /&gt;&lt;BR /&gt;Yes Volker, Large Buffers is reaching it's peak value of 200 and after that wait started increasing and finnaly wait reach to such a value that UCX stops working.</description>
      <pubDate>Fri, 16 Dec 2005 11:35:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ucx-memory-problem/m-p/3692024#M73267</guid>
      <dc:creator>Sk Noorul  Hassan</dc:creator>
      <dc:date>2005-12-16T11:35:30Z</dc:date>
    </item>
    <item>
      <title>Re: UCX Memory Problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ucx-memory-problem/m-p/3692025#M73268</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;once the Large Buffers have all been used up and you start seeing Large Buffer Waits increasing, you would need to shut down and restart UCX or even reboot your OpenVMS VAX system for recovering the resources used by UCX.&lt;BR /&gt;&lt;BR /&gt;What are the Large Buffers being used for ? UCX SHOW COMM and UCX SHOW COMM/MEM should show the usage for the Large Buffers. Does the usage increase over time (possible memory leak) ? Maybe you need to tune your UCX subsystem and provide more Large Buffers ?&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Sat, 17 Dec 2005 04:47:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ucx-memory-problem/m-p/3692025#M73268</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-12-17T04:47:35Z</dc:date>
    </item>
    <item>
      <title>Re: UCX Memory Problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ucx-memory-problem/m-p/3692026#M73269</link>
      <description>Hi Volker,&lt;BR /&gt;&lt;BR /&gt;We did server reboot to resolve the problem but it again appears in the following night at same time. so, finally we have found the cause for the problem which was external to my server. Thanks.</description>
      <pubDate>Mon, 19 Dec 2005 06:41:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ucx-memory-problem/m-p/3692026#M73269</guid>
      <dc:creator>Sk Noorul  Hassan</dc:creator>
      <dc:date>2005-12-19T06:41:25Z</dc:date>
    </item>
    <item>
      <title>Re: UCX Memory Problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ucx-memory-problem/m-p/3692027#M73270</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;thanks for the update. If you could describe the problem causing the Large Buffers to be consumed (maybe in some generic terms, if you don't want to get too specific), this may help others under similar circumstances.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Mon, 19 Dec 2005 06:46:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ucx-memory-problem/m-p/3692027#M73270</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-12-19T06:46:44Z</dc:date>
    </item>
  </channel>
</rss>

