<!-- 
RSS generated by JIRA (8.1.3#801003-sha1:6b6f07cffadda9a0d6efe24639daed8ce94dcdd6) at Sat Feb 10 05:45:42 GMT 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Rivet Logic Corporation JIRA </title>
    <link>https://issues.rivetlogic.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.1.3</version>
        <build-number>801003</build-number>
        <build-date>13-09-2019</build-date>
    </build-info>


<item>
            <title>[ACIR-3] Long running queries cause Mule to process the query multiple times </title>
                <link>https://issues.rivetlogic.com/browse/ACIR-3</link>
                <project id="10130" key="ACIR">ACIr</project>
                    <description>This issue has surfaced while working on Kaplan Catalyst.  The queries rely on a DependencyResolver (ChildAssociationDependencyResolver) to find child nodes by following parent-child associations recursively.  It is relatively time consuming for large node trees.  The default size of a Mule thread pool is 16.  When the query is long running, it will take a while before the query XML file is moved to the processed folder.  For some reason, it causes multiple threads in the QueryFolderPoller service to start handling the same query XML file.  As a result, OutOfMemoryExceptions are commonly encountered.  One of the solutions is to allow only one thread in the pool:&lt;br/&gt;
&lt;br/&gt;
&lt;br/&gt;
	&amp;lt;core:configuration&amp;gt;&lt;br/&gt;
		&amp;lt;default-threading-profile 	maxThreadsActive=&amp;quot;1&amp;quot; /&amp;gt;&lt;br/&gt;
	&amp;lt;/core:configuration&amp;gt;&lt;br/&gt;
&lt;br/&gt;
</description>
                <environment></environment>
        <key id="19191">ACIR-3</key>
            <summary>Long running queries cause Mule to process the query multiple times </summary>
                <type id="1" iconUrl="https://issues.rivetlogic.com/secure/viewavatar?size=xsmall&amp;avatarId=11083&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://issues.rivetlogic.com/images/icons/priorities/major.svg">Major</priority>
                        <status id="5" iconUrl="https://issues.rivetlogic.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="3">Duplicate</resolution>
                                        <assignee username="sokeeffe">sokeeffe</assignee>
                                    <reporter username="mverkaik">mverkaik</reporter>
                        <labels>
                    </labels>
                <created>Wed, 23 Mar 2011 12:44:46 -0400</created>
                <updated>Tue, 10 Jul 2012 12:50:49 -0400</updated>
                            <resolved>Tue, 10 Jul 2012 12:50:49 -0400</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>0</watches>
                                                                <comments>
                            <comment id="36032" author="sokeeffe" created="Tue, 10 Jul 2012 12:50:49 -0400"  >Dupe of &lt;a href=&quot;https://issues.rivetlogic.com/browse/ACIR-1&quot; title=&quot;If processing time of the file (file:endpoint) is greater than the polling frequency the file gets read more than once&quot; class=&quot;issue-link&quot; data-issue-key=&quot;ACIR-1&quot;&gt;ACIR-1&lt;/a&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                        <customfield id="customfield_11470" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_10020" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>MoSCoW</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10010"><![CDATA[Must do]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_11170" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i00j2f:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10070" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>3090</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>