|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> Is it reproduced with a recent Jenkins version?
We have not yet seen it to recur since switching to the LTS-release 1.509.1 some weeks ago.
Before that, we followed the non-LTS releases relatively closely. The last versions we used before the switch to LTS was 1.497 and 1.501; one of them experienced the problem at least once.
As said in the bug description, it is very rarely-occurring bug. Even before, we sometimes had half a year of stable runtime before it struck and necessitated a reboot. But apart from that, the uptime since the last reboot does not seem to matter. The issue can strike freely even hours after a reboot.
In short: We have not seen it in the LTS-release, but we can't say for certain that the bug is gone.