<?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: VRMS log4j workaround broke the UI in vSphere Replication Discussions</title>
    <link>https://communities.vmware.com/t5/vSphere-Replication-Discussions/VRMS-log4j-workaround-broke-the-UI/m-p/2883122#M3523</link>
    <description>&lt;P&gt;I guess I should be more specific. The Site Recovery UI is now broken with a 404-Not Found error.&lt;/P&gt;&lt;P&gt;&lt;A href="https://communities.vmware.com/" target="_blank"&gt;https://&amp;lt;sitemanager&amp;gt;/dr&lt;/A&gt;&amp;nbsp;returns a HTTP - 404 - Site not Found&lt;/P&gt;&lt;P&gt;Just wondering id anyone else implemented the workaround.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 13 Dec 2021 17:47:26 GMT</pubDate>
    <dc:creator>sbd27</dc:creator>
    <dc:date>2021-12-13T17:47:26Z</dc:date>
    <item>
      <title>VRMS log4j workaround broke the UI</title>
      <link>https://communities.vmware.com/t5/vSphere-Replication-Discussions/VRMS-log4j-workaround-broke-the-UI/m-p/2883113#M3522</link>
      <description>&lt;P&gt;After implementing the workaround to mitigate the log4j issue my VRMS replication manager interface is now broke with a 404 error:&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/87098" target="_blank" rel="noopener"&gt;https://kb.vmware.com/s/article/87098&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone else seeing this?&lt;/P&gt;&lt;P&gt;Running 8.4&lt;/P&gt;</description>
      <pubDate>Mon, 13 Dec 2021 17:14:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Replication-Discussions/VRMS-log4j-workaround-broke-the-UI/m-p/2883113#M3522</guid>
      <dc:creator>sbd27</dc:creator>
      <dc:date>2021-12-13T17:14:35Z</dc:date>
    </item>
    <item>
      <title>Re: VRMS log4j workaround broke the UI</title>
      <link>https://communities.vmware.com/t5/vSphere-Replication-Discussions/VRMS-log4j-workaround-broke-the-UI/m-p/2883122#M3523</link>
      <description>&lt;P&gt;I guess I should be more specific. The Site Recovery UI is now broken with a 404-Not Found error.&lt;/P&gt;&lt;P&gt;&lt;A href="https://communities.vmware.com/" target="_blank"&gt;https://&amp;lt;sitemanager&amp;gt;/dr&lt;/A&gt;&amp;nbsp;returns a HTTP - 404 - Site not Found&lt;/P&gt;&lt;P&gt;Just wondering id anyone else implemented the workaround.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Dec 2021 17:47:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Replication-Discussions/VRMS-log4j-workaround-broke-the-UI/m-p/2883122#M3523</guid>
      <dc:creator>sbd27</dc:creator>
      <dc:date>2021-12-13T17:47:26Z</dc:date>
    </item>
    <item>
      <title>Re: VRMS log4j workaround broke the UI</title>
      <link>https://communities.vmware.com/t5/vSphere-Replication-Discussions/VRMS-log4j-workaround-broke-the-UI/m-p/2883135#M3524</link>
      <description>&lt;P&gt;So I updated to 8.4.0.3 and the UI came back, however, I assume the log4j issue is back. Oh well, I guess I'll wait for a patch and cross my fingers.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Dec 2021 18:32:28 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Replication-Discussions/VRMS-log4j-workaround-broke-the-UI/m-p/2883135#M3524</guid>
      <dc:creator>sbd27</dc:creator>
      <dc:date>2021-12-13T18:32:28Z</dc:date>
    </item>
    <item>
      <title>Re: VRMS log4j workaround broke the UI</title>
      <link>https://communities.vmware.com/t5/vSphere-Replication-Discussions/VRMS-log4j-workaround-broke-the-UI/m-p/2883147#M3525</link>
      <description>&lt;P&gt;It was causing some issues for me as well.&amp;nbsp; I rolled back to my snapshot and it cleared up.&amp;nbsp; Going to wait for a revision.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Dec 2021 19:27:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Replication-Discussions/VRMS-log4j-workaround-broke-the-UI/m-p/2883147#M3525</guid>
      <dc:creator>BrianCoA</dc:creator>
      <dc:date>2021-12-13T19:27:22Z</dc:date>
    </item>
    <item>
      <title>Re: VRMS log4j workaround broke the UI</title>
      <link>https://communities.vmware.com/t5/vSphere-Replication-Discussions/VRMS-log4j-workaround-broke-the-UI/m-p/2883233#M3526</link>
      <description>&lt;P&gt;I can confirm the same issue happened for me.&lt;/P&gt;&lt;P&gt;Edit: Using the new KB &lt;A href="https://kb.vmware.com/s/article/87125" target="_blank"&gt;https://kb.vmware.com/s/article/87125&lt;/A&gt; worked for me now.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Dec 2021 07:44:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Replication-Discussions/VRMS-log4j-workaround-broke-the-UI/m-p/2883233#M3526</guid>
      <dc:creator>Sam38</dc:creator>
      <dc:date>2021-12-14T07:44:36Z</dc:date>
    </item>
  </channel>
</rss>

