Making minimal test cases is always interesting :) It appears there is some additional constraint that needs to be satisfied, so further research needs to be done to determine the exact cause of the problem.
It does seem to affect most of the forking code in maven, which should imply some kind of interaction with commons-exec or plexus-utils. Kristian 2014-10-09 9:18 GMT+02:00 Rory O'Donnell Oracle, Dublin Ireland <rory.odonn...@oracle.com>: > Hi Kristian, > > Can you log a Java Incident and I will follow up ? > > Rgds,Rory > > On 09/10/2014 07:14, Kristian Rosenvold wrote: >> >> It would appear that the ThreadPoolExecutor in UNIXProcess can keep >> the vm running for up to 12 seconds after the last process has been >> forked. Once you see the symptom it is clearly visible; maven appears >> to finish the build normally, but there is a short pause after this >> message and the return of the command prompt: >> >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] BUILD SUCCESS >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Total time: 2.155s >> [INFO] Finished at: Thu Oct 09 08:07:38 CEST 2014 >> [INFO] Final Memory: 14M/334M >> [INFO] >> ------------------------------------------------------------------------ >> <Insert pause here> >> >> >> The issue is https://jira.codehaus.org/browse/MEXEC-145 and applies to >> a truckload of maven stuff since we fork a lot of processes, the bug >> only seems to affect VM shutdown (which is also NOT very good since we >> fork a lot of VM's too :). >> >> I searched the jdk issue tracker but could not find any evidence of >> this bug, hence the cc to Rory. >> >> Kristian > > > -- > Rgds,Rory O'Donnell > Quality Engineering Manager > Oracle EMEA , Dublin, Ireland > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
