|
||||||||
|
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.
Does anyone have any advice on how to reproduce this problem in 1.480.1? In large environments with a lot of real traffic, 1.480.1 appears to be experiencing this issue and becomes essentially unusable. However, in a smaller environment with much less traffic, I cannot get this defect to appear.
What I'm trying to do is prove that a) this is the issue we are seeing and not something else, and b) that it is indeed gone in 1.480.3. I've tried Apache Benchmark with 20+ concurrency, and I've tried simulating traffic with 20+ tabs open with auto-refresh on...
This upgrade is a little more risky since the whole 're-keying' process will take effect, so I want to make sure we won't have to rollback... again...![]()
Any advice would be greatly apprciated!