|
David, is there a workaround that the client may apply? i.e. step-by-step instructions on where to set the read timeout value? So they can apply the change and monitor the effect?
Or do they have to wait till a new plugin release is available? Please advise. Thanks Ivan A new plugin release will be required. The addition itself is fairly simple, but doing a formal plugin release is a bit of a process. However, I can probably arrange for a SNAPSHOT of the plugin with the modification in it so that the client can test if it resolves the issue.
That would be wonderful David.
What is the ETA for the formal release? How can it be tested to ensure that the problem that we think is occurring will not happen again? Please advise Ib I have updated the code in SVN to set the read timeout to the same value as the connection time out. Theoretically, this means it could actually take double the timeout value to actually connect (connection timout + read timout), but usually it will just be one or the other. In either case, it's better than having an infinite timeout value.
Jonathan will have to schedule an actual release. In the meantime, I've attached a snapshot build of the calendar plugin. Please try it, test it and see if it resolves your issues. Note: All new calendars will have the timeouts set by default, but any existing calendars will probably need to be edited, set the timeout value and save. Even if the timeout is displayed as 30 seconds already when you edit an old calendar, save it anyway to ensure the timeout value is getting to the back end. We are having the same problem with 2.6.1 - our production confluence started crashing all the time and it took us a while to get a suspicion it was the calendar plugin. We've disabled it and it's been OK since.
We have an open support ticket on our crashing problem (https://support.atlassian.com/browse/CSP-18504 What's up with this? Fix coming? Our users would like their calendars back... Reading the comments above I'm not sure exactly what's up. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This will need to be resolved by adding a new property to the org.randombits.source.URLSource class to let it specify the read timeout for the URL connection.