Apache OpenOffice (AOO) Bugzilla – Issue 105135
Creating a HG-based CWS via command spits error
Last modified: 2013-01-29 21:45:23 UTC
When I just tried to create a new mercurial based cws via the cws command, it spits out an error message, but somehow succeeds in creating a new cws. Here is the command run and its output: --- $ cws create --hg -m m59 DEV300 calcphonetic Warning: web service unavailable. Trying backup server. ERROR: Connection to EIS database failed. at /media/disk/ooo/hg-pilot/koheirowlimitperf/solenv/bin/modules/Cws.pm line 1839 ***** Successfully ***** registered child workspace 'calcphonetic' for master workspace 'DEV300' (milestone 'm59'). Child workspace Id: 8705. --- It creates a new entry in the EIS, but the SCM type is set to CVS, not HG as I expected.
Btw, when I omit the milestone, it doesn't even create an entry in the EIS. According to the help output of the cws command, you are supposed to get the latest published milestone if you don't specify the milestone.
I forgot to mention that, I have used the cws tool that comes with m59.
@kohei: did you update solenv/bin/modulesCws.pm also to m59 level? I made a few API changes there and the problem with the milestone and the left out setting of the HG flag could be caused by a mismatch.
@hr: I assume so, since I rebased the entire cws to m59. Here is my hg log output on solenv/bin/modules/Cws.pm: $ hg log solenv/bin/modules/Cws.pm changeset: 262998:fdf76db01ccd user: releng date: Thu Aug 27 15:47:51 2009 +0000 summary: CWS-TOOLING: integrate CWS hr65 changeset: 262531:d853316ba75f user: vg date: Tue Mar 17 00:00:46 2009 +0000 summary: CWS-TOOLING: integrate CWS hr60_DEV300 changeset: 262026:6e75d9dd4600 user: kz date: Thu Nov 06 16:01:03 2008 +0000 summary: CWS-TOOLING: integrate CWS rt34 ...
@kohei: Having everything on hr65 level rules out an incompatibility between cws.pl and Cws.pm. Looks like you were victim of yet another temporary webservice outtage. I've have to look why the script didn't completely bail out after the first difficulty. This fallback thing needs to be removed as well, it's no longer really applicable. I would assume that if you create another CWS everything would be fine. Which URL do you use in your $HOME/.cwsrc? 'cc Bernd.
Here is the server line in my .cwsrc: CWS_DB_SERVER_1=https://eis.services.openoffice.org/soap/servlet/rpcrouter But the command *did* create a new entry in the EIS database. So, I'm a bit skeptical it was the server...
All the SOAP requests are independent. It might very well be that the query for the latest milestones fails, the next query (for example the registration) works. The script should bail out if one request fails, but if it does after registration but before marking the CWS as HG based it would leave an incompletely initialized CWS. I would like some rollback possibility here :-) Or one API call to do all the writing requests in one go.
BTW cws creation still fails even right now. $ cws create --hg -m m59 DEV300 calctabcolor Warning: web service unavailable. Trying backup server. ERROR: Connection to EIS database failed. at /media/disk/ooo/calcphonetic/solenv/bin/modules/Cws.pm line 1839 ***** Successfully ***** registered child workspace 'calctabcolor' for master workspace 'DEV300' (milestone 'm59'). Child workspace Id: 8706.
Some of the EIS servers were down, broken UPS. I'll have a look at it tomorrow when the situation settles.
@kohei: I was able to reproduce it now. It's probable the EIS service. I'll contact Bernd.
@hr: thank you, and I'm glad to see you have been able to reproduce this.
bei->kohei: I have made a fix in EIS in the cws create method but I am not sure if that was the one needed in your case . Can you please try again to create a childworkspace?
@bei: yup, it worked. I just created (and deleted) koheitestcws01. It was correctly registered as an HG-based CWS.
Re-opening. I just had the same problem again just now, with the creation of koheicopyborder cws.
@bei: reassign
bei->kohei: can not reproduce an error. If it was excatly the same error as described at first occurance than I would suppose it was just a temporary outage of the eis service. If you got another error message for the last occurrence than "web service unavailable" please describe the error message. Errors like the SOAP method is throwning an exception because for example an argument is not being accepted or if there is a null pointer access or if the SOAP service is not correctly deployed should result in a different error message than "web service unavailable."
@bei: The error output was exactly the same (except for the cws name) as in desc1.
occured for annother user to reopening
Which was me. Cc-ing myself.
Played a bit with it. First suspected a 64bit problem, but then tried it on a x86_64 fc11 install, and it works there. Current theory: specific version of client libs don't play nice with server (we might need to compare things on packet level for further info). These are the versions of the relevant libs: fc11 ---- perl-Crypt-SSLeay-0.57-11.fc11.x86_64 perl-Net-SSLeay-1.35-4.fc11.x86_64 perl-SOAP-Lite-0.710.08-2.fc11.noarch perl-5.10.0-73.fc11.x86_64 opensuse 11.0 ------------- perl-Crypt-SSLeay-0.57-14.1 perl-Net_SSLeay-1.32-20.1 perl-SOAP-Lite-0.71.01-13.1 perl-5.10.0-37.6 (fc11: works. opensuse 11.0: doesn't work)