|
[jira] Commented: (MEXEC-15) exec:java plugin never shuts down: msg#00351java.maven-plugins.mojo.devel
[ http://jira.codehaus.org/browse/MEXEC-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_86330 ] Jerome Lacoste commented on MEXEC-15: ------------------------------------- David, 2 notes: 1- I am testing the patch against my test cases and I still get a hang. One of my new test cases add a non daemon Timer to the MainWIthThreads.main() (test project 7). In the case the Timer is not daemon, the code path that takes: void joinNonDaemonThreads() will still hang. It looks like we still need a time out even with non daemon threads. 2- And as I said before, I personnaly would prefer an implementation that allows to use a time out and ignore the threads that have been interrupted but didn't properly quit. Did you intend the implementation to work like that, e.g. if one uses a non zero time out and do not choose to use stop() ? > exec:java plugin never shuts down > --------------------------------- > > Key: MEXEC-15 > URL: http://jira.codehaus.org/browse/MEXEC-15 > Project: Mojo Exec Plugin > Issue Type: Bug > Affects Versions: 1.1 > Reporter: Ryan Sonnek > Priority: Critical > Attachments: dsmiley-MEXEC-15.patch > > > I've debugged that my main method has finished running, but the exec:java > plugin never exits. Here's the last output I see before it hangs > indeffinately. > T10 2007-01-15 10:34:59.959 > com.digitalriver.logging.BatchPersistentRecordHandler <FINE> Persisting 1 > LogRecords > [DEBUG] interrupting thread > Thread[Thread-1,1,com.digitalriver.schedule.JobRunner] > [DEBUG] joining on thread > Thread[Thread-1,1,com.digitalriver.schedule.JobRunner] > My plugin configuration is pretty simple: > <!-- support exec:java to run application --> > <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>exec-maven-plugin</artifactId> > <configuration> > <systemProperties> > <systemProperty> > <key>com.digitalriver.system.configName</key> > <value>client</value> > </systemProperty> > <systemProperty> > <key>com.digitalriver.system.home</key> > <value>${runtimeRoot}</value> > </systemProperty> > </systemProperties> > <mainClass>com.digitalriver.schedule.JobRunner</mainClass> > <keepAlive>false</keepAlive> > </configuration> > </plugin> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
|
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | [jira] Commented: (MEXEC-17) system dependencies are not put on exec:java classpath, Jerome Lacoste (JIRA) |
|---|---|
| Next by Date: | [jira] Commented: (MEXEC-17) system dependencies are not put on exec:java classpath, Ryan Sonnek (JIRA) |
| Previous by Thread: | [jira] Commented: (MEXEC-15) exec:java plugin never shuts down, Jerome Lacoste (JIRA) |
| Next by Thread: | [jira] Commented: (MEXEC-15) exec:java plugin never shuts down, David Smiley (JIRA) |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |