|
||||||||||||
|
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/d/optout.
I'm relaying one of our sysadmins:
===
Yes, we are running an older version of openfire.
The info and debug logs contained nothing from the time period.
Warning only contained the following:
2014.11.25 11:55:29 Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.
2014.11.25 11:55:29 Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.
But it isn't repeated for the other times when this happened so it seems unrelated.
Error has an incredible amount of errors that it repeats at an insane rate, so much so that I don't have the data available from the original time period any more. However, recreating the event (same symptoms, ~6 min disconnect) seems to show nothing relevant (attached file), but appears to be related to when we stripped out many our LDAP groups. There is the mention of one non-existent user in a group, but this is not the user we are concerned with.
Would increasing verbosity perhaps give something more useful?