![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Kohsuke Kawaguchi
|
|
Components:
|
core |
|
Created:
|
02/Aug/13 6:27 PM
|
|
Description:
|
"java -jar slave.jar" currently has a logic that keeps on reconnecting if a connection is dropped. This is good, but over a long run, if any memory leak happens during a connection, it'll slowly clog up the JVM.
On Unix, it is better to exec to itself to start clean in case of a connection loss. On slaves managed as a Windows service, it is better to just terminate the process and let Windows SCM launch a new one.
Slaves should do this kind of intelligent reconnection, much like how Jenkins master restarts itself.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Kohsuke Kawaguchi
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
