<?xml version="1.0" ?>
<!--
  RSS generated by Inquira Information Manager
-->
<rss version="2.0">
<channel>
<title><![CDATA[Hexagon Safety &amp; Infrastructure - Post to topic An exception occurred in component  DBReader  of type  DBReader   "Queue limit reached."]]></title>
<link>http://support.hexagonsafetyinfrastructure.com/infocenter/index?page=home</link>
<description>Post to topic An exception occurred in component  DBReader  of type  DBReader   "Queue limit reached."</description>
<language>en</language>
<copyright>Copyright © 2002, 2012, Oracle and/or its affiliates. All rights reserved.</copyright>
<generator>Oracle Knowledge Information Manager</generator>
<docs>http://blogs.law.harvard.edu/tech/rss</docs>
 

 
<item>
        <title><![CDATA[An exception occurred in component  DBReader  of type  DBReader   "Queue limit reached."]]></title>
        <link><![CDATA[http://support.hexagonsafetyinfrastructure.com/infocenter/index?page=forums&topic=50720254022f7a33d015976bac0e8006e91&actp=RSS]]></link>
        <description><![CDATA[<p>Has anyone seen this message before written to an EdgeFrontier systems error log?</p>

<p>This occurred recently in more than one system, at different times. When it does happen, it generally spits out thousands of these errors. I&#39;ve looked through various logs and can&#39;t find a direct reason as to why this happens. This is happening after months and hundreds of thousands of successful messages have been read/received/written through these systems, so please understand that it is not a &#39;in-development&#39; system that I am referring to. These errors are occurring long after a system has been stable for months with zero errors.</p>

<p>I am hoping one of you have seen this before and know what it was that &#39;caused&#39; the error to occur.</p>

<p>&#39;Reloading&#39; the system causes the errors to stop, if that helps.</p>

<p>&nbsp;</p>

<p>Thanks in advance,</p>

<p>Brien Foss</p>

<p>&nbsp;</p>
]]></description>
        <pubDate>2017-01-27 20:18:08 Etc/GMT</pubDate>
        <guid isPermaLink="true"><![CDATA[http://support.hexagonsafetyinfrastructure.com/infocenter/index?page=forums&topic=50720254022f7a33d015976bac0e8006e91&actp=RSS]]></guid>
</item><item>
        <title><![CDATA[RE: An exception occurred in component  DBReader  of type  DBReader   "Queue limit reached."]]></title>
        <link><![CDATA[http://support.hexagonsafetyinfrastructure.com/infocenter/index?page=forums&topic=50720254022f7a33d015976bac0e8006e91&actp=RSS#5072036073e2ff2015ef254b173007e32]]></link>
        <description><![CDATA[<p>Still observing this error every couple of months.</p>

<p>Happening more frequently to a particular system which uses DB Writers as its main function/purpose.</p>

<p>&nbsp;</p>

<p>Here is the most recent error that happened before the thousands of &#39;queue limit reached&#39; errors started showing up. I think of this error as the possible &#39;trigger&#39; for the complete meltdown. Re-loading the system with issues resolves the problem every time.</p>

<p>Possible trigger:</p>

<p>An exception occurred in component SQLUnitCustomWriter of type DBWriter -&gt; <strong>Source array was not long enough. Check srcIndex and length, and the array s lower bounds.&quot;</strong></p>

<p>&nbsp;</p>
]]></description>
        <pubDate>2017-10-12 20:20:04 Etc/GMT</pubDate>
        <guid isPermaLink="true"><![CDATA[http://support.hexagonsafetyinfrastructure.com/infocenter/index?page=forums&topic=50720254022f7a33d015976bac0e8006e91&actp=RSS#5072036073e2ff2015ef254b173007e32]]></guid>
</item>
</channel>
</rss>
