<?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 CSCwn85711 - ISE: Memory leak in EPPurgeEventHandler in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cscwn85711-ise-memory-leak-in-eppurgeeventhandler/m-p/5267002#M595311</link>
    <description>&lt;P&gt;Anyone else notice this issue with patch 7 of 3.2? Just opened a TAC case because our PSN memory usage has been going up for 2 weeks straight since updating to patch 7 from patch 6. Guessing as a small workaround until more is know maybe I can reboot each node to reset the usage but not sure what the best temp fix/workaround might be.&lt;/P&gt;</description>
    <pubDate>Tue, 04 Mar 2025 02:22:48 GMT</pubDate>
    <dc:creator>Earp</dc:creator>
    <dc:date>2025-03-04T02:22:48Z</dc:date>
    <item>
      <title>CSCwn85711 - ISE: Memory leak in EPPurgeEventHandler</title>
      <link>https://community.cisco.com/t5/network-access-control/cscwn85711-ise-memory-leak-in-eppurgeeventhandler/m-p/5267002#M595311</link>
      <description>&lt;P&gt;Anyone else notice this issue with patch 7 of 3.2? Just opened a TAC case because our PSN memory usage has been going up for 2 weeks straight since updating to patch 7 from patch 6. Guessing as a small workaround until more is know maybe I can reboot each node to reset the usage but not sure what the best temp fix/workaround might be.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Mar 2025 02:22:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cscwn85711-ise-memory-leak-in-eppurgeeventhandler/m-p/5267002#M595311</guid>
      <dc:creator>Earp</dc:creator>
      <dc:date>2025-03-04T02:22:48Z</dc:date>
    </item>
  </channel>
</rss>

