[
http://jira.codehaus.org/browse/MEXEC-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_86333
]
David Smiley commented on MEXEC-15:
-----------------------------------
1. Why do we need a time out with non-daemon threads if the behavior is
consistent with the command line? I can't see the code; you didn't check it
in, but I imagine that java on the command line would also "hang" since the
non-daemon thread decided to stick around. I wouldn't call that a hang, it's
expected behavior. BTW, AFAIK, if the java.util.Timer has no more tasks
scheduled for the future then it'll shut itself down.
2. Yes, the code I submitted should allow for that. stop() is optional. In
this case, those stubborn threads would live on as exec:java finishes and maven
goes off to do other things (if any). The VM would finally stop, aborting
those daemon threads. I don't have a testcase for this scenario; it'd be
tricky.
> 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
