# Run away process

**URL:** <https://forum.cloverdx.com/t/run-away-process/713>\
**Category:** CloverDX Platform\
**Created:** [May 26, 2010, 12:00am UTC](https://forum.cloverdx.com/t/run-away-process/713 "2010-05-26T00:00:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ntmoyer](https://avatars.discourse-cdn.com/v4/letter/n/ad7895/32.png) [@ntmoyer](https://forum.cloverdx.com/u/ntmoyer)\
**Post date:** [May 26, 2010, 12:00am UTC](https://forum.cloverdx.com/t/run-away-process/713/1 "2010-05-26T00:00:00Z")

</div>

we are using cloverETL server 2.9.2 hosted on a windows server 2008 64 bit in a 64 bit version of tomcat 6.0

we need to run about 80 graphs in series and are using the graph listener feature. Everything works fine when we are running a small test set, a few 1000 records, but have not been able to run everything on a full set, a few million records. during the run a graph will “hang” and just keep running and never finish. if i kill the graph the tomcat process on the server acts like it is still going and takes about 13% of the cpu. the next time a graph hangs and is killed it takes another 13%. to recover this i have to restart tomcat. is there a better way?

---

<div class="post-metadata">

**Author:** ![mvarecha](https://avatars.discourse-cdn.com/v4/letter/m/5daacb/32.png) [@mvarecha](https://forum.cloverdx.com/u/mvarecha)\
**Post date:** [July 12, 2010, 11:15am UTC](https://forum.cloverdx.com/t/run-away-process/713/2 "2010-07-12T11:15:21Z")

</div>

This issue has been solved using our customer support system.  
Instant solution is to replace FastSorts with ExtSorts.  
You can follow the FastSort issue status in our bug tracking system [http://bug.cloveretl.org/view.php?id=4343](http://bug.cloveretl.org/view.php?id=4343).

Martin