<?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: 500 - Internal error in Share dashlets in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/500-internal-error-in-share-dashlets/m-p/245012#M198142</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;It sounds like this bug: &lt;/SPAN&gt;&lt;A href="https://issues.alfresco.com/jira/browse/ETHREEOH-4089" rel="nofollow noopener noreferrer"&gt;https://issues.alfresco.com/jira/browse/ETHREEOH-4089&lt;/A&gt;&lt;SPAN&gt; where the error was spotted in a 2-node cluster. That could be a red herring however, as obviously there's been a write error at some point… the proposed fix was to make the reader more tolerant to XML errors. I'm not sure why the file's XML came to be unreadable however.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It probably makes sense to raise a new JIRA against Community, referencing the ETHREEOH one - make sure to add your exception trace.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Mike&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 12 Feb 2010 09:23:58 GMT</pubDate>
    <dc:creator>mikeh</dc:creator>
    <dc:date>2010-02-12T09:23:58Z</dc:date>
    <item>
      <title>500 - Internal error in Share dashlets</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/500-internal-error-in-share-dashlets/m-p/245011#M198141</link>
      <description>I'm getting error text in Share dashlets, usually in My Dashboard but sometimes in Site Dashboards. On other occasions dashlets appear to be missing entirely and site lists also appear empty.The problem is most repeatable if I wander round some sites and then leave the browser for 5 minutes or so be</description>
      <pubDate>Fri, 12 Feb 2010 01:19:43 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/500-internal-error-in-share-dashlets/m-p/245011#M198141</guid>
      <dc:creator>kilucas</dc:creator>
      <dc:date>2010-02-12T01:19:43Z</dc:date>
    </item>
    <item>
      <title>Re: 500 - Internal error in Share dashlets</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/500-internal-error-in-share-dashlets/m-p/245012#M198142</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;It sounds like this bug: &lt;/SPAN&gt;&lt;A href="https://issues.alfresco.com/jira/browse/ETHREEOH-4089" rel="nofollow noopener noreferrer"&gt;https://issues.alfresco.com/jira/browse/ETHREEOH-4089&lt;/A&gt;&lt;SPAN&gt; where the error was spotted in a 2-node cluster. That could be a red herring however, as obviously there's been a write error at some point… the proposed fix was to make the reader more tolerant to XML errors. I'm not sure why the file's XML came to be unreadable however.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It probably makes sense to raise a new JIRA against Community, referencing the ETHREEOH one - make sure to add your exception trace.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Mike&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Feb 2010 09:23:58 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/500-internal-error-in-share-dashlets/m-p/245012#M198142</guid>
      <dc:creator>mikeh</dc:creator>
      <dc:date>2010-02-12T09:23:58Z</dc:date>
    </item>
    <item>
      <title>Re: 500 - Internal error in Share dashlets</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/500-internal-error-in-share-dashlets/m-p/245013#M198143</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Mike&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks for your help here. And I will indeed find out how to raise the JIRA as you suggest. Can I just check one idea though. You mention the possibility of a write error. This reminds me that I'm getting errors in the tomcat DOS window saying that Alfresco failed to rename alfresco.log from time to time. I know this is very different from the aspects of Alfresco that we're suspecting as the cause of my dashlet errors but each implies a write error.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So, albeit a bit simplistic, are there any permissions I should check for example? I've checked there are njo diskspace problems.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Lastly, if this really is the bug you mentioned do I take it that there are no workrounds I can use? And do I just monitor the link you sent me until I see someone say that there's a new version with a fix? I'm conscious that I can't really use Share in the meantime since the dashlets are fairly fundamental to the uses I'd intended. So obviously it's great to know what my options are.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Many thanks once again.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Kevin&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Feb 2010 09:46:24 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/500-internal-error-in-share-dashlets/m-p/245013#M198143</guid>
      <dc:creator>kilucas</dc:creator>
      <dc:date>2010-02-12T09:46:24Z</dc:date>
    </item>
  </channel>
</rss>

