[ACIR-3] Long running queries cause Mule to process the query multiple times Created: 23/Mar/11  Updated: 10/Jul/12  Resolved: 10/Jul/12

Status: Resolved
Project: ACIr
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: mverkaik Assignee: sokeeffe
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

MoSCoW: Must do

 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:


<core:configuration>
<default-threading-profile maxThreadsActive="1" />
</core:configuration>



 Comments   
Comment by sokeeffe [ 10/Jul/12 ]
Dupe of ACIR-1
Generated at Sat Feb 10 05:45:42 GMT 2024 using Jira 8.1.3#801003-sha1:6b6f07cffadda9a0d6efe24639daed8ce94dcdd6.