From: Himani K. <him...@gm...> - 2013-02-12 10:06:05
|
Hi All, I have a scenario where the tomcat stop doesn't allow the tomcat engine to stop as some process in my app had created threads which are not released on stopping the tomcat and thus we have to kill the tomcat instance PID's. But after killing the tomcat the cobertura reports doesn't seem to flush the data and the reports show 0% coverage. Is there any other way for flushing the cobertura coverage result other than code hacks? |
From: Steven C. <sch...@gm...> - 2013-02-12 11:34:44
|
On 02/12/2013 04:05 AM, Himani Khanna wrote: > Hi All, > > I have a scenario where the tomcat stop doesn't allow the tomcat > engine to stop as some process in my app had created threads which are > not released on stopping the tomcat and thus we have to kill the > tomcat instance PID's. But after killing the tomcat the cobertura > reports doesn't seem to flush the data and the reports show 0% coverage. > > Is there any other way for flushing the cobertura coverage result > other than code hacks? > > > > ------------------------------------------------------------------------------ > Free Next-Gen Firewall Hardware Offer > Buy your Sophos next-gen firewall before the end March 2013 > and get the hardware for free! Learn more. > http://p.sf.net/sfu/sophos-d2d-feb > > > _______________________________________________ > Cobertura-devel mailing list > Cob...@li... > https://lists.sourceforge.net/lists/listinfo/cobertura-devel Cobertura flushes it's data when the java shutdown hooks are executed. However there is a way to execute a flush without extra code. Since you're using tomcat you can deploy the coberturaFlush.war file as part of your container and invoke a flush by going to http://<URL>:<PORT>/FlushCobertufa/flushCobertura to flush the data. |