Apache OpenOffice (AOO) Bugzilla – Issue 30722
XML export failed for Issue 30699
Last modified: 2007-02-23 09:06:46 UTC
XML export failed for Issue 30699 with URL http://www.openoffice.org/issues/xml.cgi?id=30699 Script writes invalid XML-code. A simple view with a Mozilla shows following error: "XML Parsing Error: no element found Location: http://www.openoffice.org/issues/xml.cgi?id=30699 Line Number 4, Column 1:" also some other browsers. Please fix the problem asap., thx. Frank
added some CCs
For me the easiest way to produce the faulty output is wget -S -O- 'http://www.openoffice.org/issues/xml.cgi?id=30699'
I've opened an internal issue to get this looked at. I have been able to reproduce this with the issue mentioned but no others. Given that, can someone explain or justify why this is a p2 issue?
We are going to produce some more of these issues containing XML stacktrace data automatically. For the moment I set the priority to P3 - but there might be the need to raise it again.
The engineers are still working on this one and have gained some insight into it.
This seems to be specific to the perl code on solaris. More research is being conducted.
PB-DEF: Engineering doing additional debugging to find out the root-cause.
Correcting whiteboard. Adding keyword.
It seems that issue 35751 points to 2 more cases with the same problem. Raising prio to P2.
If issue 35751 is the same as this, justifying the increased priority, it should be closed as a duplicate. Otherwise the priority should be decreased.
*** Issue 35751 has been marked as a duplicate of this issue. ***
I closed issue 35751 as a duplicate as requested and added a dependency to check it as soon as this is fixed.
XML export failed for issues: http://www.openoffice.org/issues/xml.cgi?id=14349 (reported by MBA today) http://www.openoffice.org/issues/xml.cgi?id=35131 http://www.openoffice.org/issues/xml.cgi?id=33205 FYI, Frank
New failure for http://www.openoffice.org/issues/xml.cgi?id=14349 Frank
Engineering obtained the Openoffice data. Cannot reproduce with this specific data and platform(OS). Requested engineer to update. Should have a feedback by early next week.
Correction to previous update: Read "without this specific data" instead of "with this specific data"
Can you please provide us with a simple description of the business impact of this problem - trying to prioritize this against your other issues
XML export is the main interface for many developers to review issues. The business impact is that an increasing number of issues containing XML crash data can't be handled via the XML export.
We have another example: issue 30722
That was this issue. I meant issue 34048
New failure with issue 40162
cc'ed myself
new failure with issue 40837
The core issue is considered for fix in Amazon (CEE 3.5.1). Once that fix exists, we may be able to fix individual issues without deleting them, as a stop gap until Openoffice gets to Amazon. But, until that fix exists, all we can offer is removal of the offending issues.
My understanding was that you are going to search the database and automatically change to comments with "angle bracket question mark" xml to something exportable. From there we should should file TASKs for further issues with problematic content. I never heard about removing issues.
Stefan, Engineering is currently looking into this issue. Looks like a possible solaris/perl issue. Will update once I have some more information. For now, ignore the comments regarding "removal of issues".
Hi all, what about using a 'standard' xml-writer? What about using java as an OS-independent language? Do you need assistance? I'm not sure about your problems, but I think this issue and some other ones are very old. These longer discussions about the importance of these issue could be avoided by using a simple xml-writer. I don't want to blame you but I'm very annoyed about this, cause it seems to be solvable in a reasonable time. Sorry to say this, Frank Here is a list of issues with a xml-failure in your export beside 30699: 10825,11398,11644,12131,12573,12658,13487,1349,14367,14625,1516,15598,1567,15714,15716,17193,17196,17377,17585,17684,17843,18132,18273,1884,19389,19711,19787,19823,19831,20399,20807,20808,21060,21391,22487,22834,22836,2286,23117,23408,2344,23448,23502,23654,23962,25044,25314,25546,25865,25968,26468,26849,2813,3289,3589,3796,4053,4086,4348,4735,5031,5063,5122,5306,5525,6190,660,6772,7183,721,7216,7437,7438,7574,7623,7813,7974,8444,9846 Note: The list is not complete, only a set of un-exportable issues
Hi all, one more for an attachment problem in your xml-export: Issue 45829 Any news about fixing this issue?!? Kind regards, Frank
another issue id 39961 with export problems. Have you any news for us about this bug?!?
And another one 52711 Any news about the defect?!? Do you need assistance, may I can help?!? Regards, Frank
So far we couldn't reproduce this issue in dev environment and the problem is specific to the PERL library used in production box(verified). CN engineering will defer the fix to the later release which is due soon.
Could you please confirm that this issue is resolved in Danube running on our production environment perl libraries.
A small clarification to this. The plan is to fix this after OpenOffice upgrades to Danube-S. There is no CEE code-fix for this as such. After the upgrade with the site on the new PERL libraries if this problem still appears to be unresolved, engineering will fix it on the site itself. Hence marking this as one of the POST-UPGRADE TASK.
Could this issue be verified on the staging site?
If the problem can be reproduced, absolutely.
Can't xml-export issue 53773
Can't export issue 70788 see: http://www.openoffice.org/issues/xml.cgi?id=70788 Please answer this question: Which version is RESOLVED/LATER it is not CEE Danube which is currently running. Next release is named 'Snake', isn't it? - So I'll REOPEN this issue. FIXED but FAILED in my eyes. I also can't xml-export the very old issue http://www.openoffice.org/issues/xml.cgi?id=30699 Note this issue is over 2 years old and important for us. If you need assistance let me/us know!!!! Cheers, Frank
Frank : Have been doing some investigation on this issue and given below are my findings . 1) Normal Export of issues does work. 2) Export of issues containing intricate code information in the comment's section of the IZ does seem to have some problem with Exporting . 3) I tried pasting the entire issue comment's of both 30699 and 70788 to test issues in the stage.openoffice.org and tried exporting the issues and surprise...surprise the Export does Fail . 4) Now tried the same in the latest Build of CEE Snake-T in Linux Platform and was not able to Export the issues . I am going to put forth by findings to the Engineering and would request them to work on this issue with due diligence .
Pinged the engineers for an update .
Positive progress has been done in the investigation of this issue . However we are still in the process of identifying the actual root cause for this recurring problem. Please note we have also conveyed appropriately to the engineers the pain that the users seem to be facing in not able to fully utilize export functionality
We have a fix for this and are attempting to get it into the next patch for the site which should be available in the next few weeks.
Verified that after the application of the patch 10 that we are able to perform xml-export of the following issues. http://www.openoffice.org/issues/xml.cgi?id=14349 http://www.openoffice.org/issues/xml.cgi?id=35131 http://www.openoffice.org/issues/xml.cgi?id=33205 http://www.openoffice.org/issues/xml.cgi?id=70788 http://www.openoffice.org/issues/xml.cgi?id=30699 Closing this issue as fixed .
support - case creation .
Please verify and close this issue .
Verified, thank you. Frank
closing issue