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?
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?
-
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.
Martin
Please sign in to leave a comment.
Comments 1