Apache OpenOffice (AOO) Bugzilla – Issue 80093
Can't add pjanik to cc of issue 80089
Last modified: 2017-05-20 10:27:49 UTC
While adding pjanik to CC of #i80089# I have received several "Error proxying data" this morning. Screenshot attached. reproducible now: Fri Jul 27 04:31:43 GMT 2007 To reproduce, go to http://www.openoffice.org/issues/show_bug.cgi?id=80089, enter pjanik into CC: box and press Enter and wait ~5 minutes.
*** Issue 80094 has been marked as a duplicate of this issue. ***
I have added me now: Fri Jul 27 04:59:54 GMT 2007 Was IZ collapsed?
Adding Stefan to CC:.
See also #i80094#. I was able to file duplicate of this issue with *empty* first description...
Created attachment 47132 [details] screenshot
IZ seems to be functional again -> P2. Let's see whether support can tell us something about the root cause...
Hi, Thank you for contacting CollabNet Customer Support. Based on the information that has been provided to us, we will initiate our research & provide you an update as soon as we have adequate information. Thanks, Harsha Support Operations.
Hi, We have analyzed and found that as there is a cronjob scheduled every Thursday 21 hrs PDT ( Friday 04 hrs GMT ) for taking database dump.During this time, whichever table that is getting backed-up will be locked. Any access by the application on a locked table throws "Error proxying data". We found from the logs, we could see that the attachment table is getting accessed by the request from pjanik at the specified time. But the table was locked. Hence the error occurred. Thanks, Harsha Support Operations.
Great - thanks for your information. i do not understand why you have assigned this issue to me? Should I implement backups using snapshot in your commercial product or what? This is clearly bug in your commercial software which prevents users to use the software during that time. You do not even produce correct and self explaining error message. I can't fix that though.
.
Pjanik and Stefan, Harsha had attempted to provide you the Root Cause of the behavior you had come across when performing IZ operations. As stated this is due to the cronjob which is scheduled every Thursday 21 hrs PDT ( Friday 04 hrs GMT ) for taking database dump. We do know in one of the previous similar issue we had stated to run the cron job during weekends to avoid running into this situation however we have noticed that we have to run these cron operation at the mentioned date/time otherwise we were unable to prepare the reports for the week . However the good news is that our engineers are very close on coming up with an alternative approach of preparing the reports instead of using the tedious approach of locking IZ component. ETA for the new approach to be carried out is 3-4 weeks until which we would have to keep running this cron job at the date/time mentioned. Resolving this issue as the Root Cause has been provided .
Happened again, exactly at the same time as described.
This happened to me again. Friday, 6am (well it is 6:50 here now!). Servlet error Error Error proxying content: error proxying data start: Please click on your browser's Back button, review your input, and try again. If you get the error again, please notify us, including the following information in your report: The date and time: 4:48:54 AM GMT Friday, October 12, 2007 The version and build number: 4.5.2.148.3 Your username: pjanik The page that caused the error: http://www.openoffice.org/issues/process_bug.cgi The referrer of the page that caused the error: http://www.openoffice.org/issues/show_bug.cgi? id=82532 Any field input you provided and the name of any button you pressed Any other relevant information So the DB is in read-only mode for approx. 48 minutes now??? I'll try to add the comment I need to that issue to see how long the DB is in read-only mode for us! Another one: Servlet error Errors Error proxying content: error proxying data Error proxying content: error proxying data start: Please click on your browser's Back button, review your input, and try again. If you get the error again, please notify us, including the following information in your report: The date and time: 4:57:27 AM GMT Friday, October 12, 2007 The version and build number: 4.5.2.148.3 Your username: pjanik The page that caused the error: http://www.openoffice.org/issues/process_bug.cgi The referrer of the page that caused the error: http://www.openoffice.org/issues/show_bug.cgi? id=80093 Any field input you provided and the name of any button you pressed Any other relevant information
OK, so 4:57:27 AM GMT Friday, October 12, 2007 was still problematic, but Fri Oct 12 04:59:19 +0000 2007 was OK -> The IZ is readonly for approx. 57 minutes 30 seconds. In this time, users can't submit their comments. CN knows that they can't submit their comments/ changes but they do not warn them before hand.
As stated in our previous post , we have come up alternative implementation of preparing the reports instead of using the tedious approach of locking IZ component. I have requested our internal team to disable the cron job from running in our production environment. Will be updating this ticket when the task has been completed
The cron job entry has been removed from the production box . Users would be not be facing this similar situation any more. Marking this issue as Resolved Fixed .