|
[
Permlink
| « Hide
]
Maik Schreiber added a comment - 19/Oct/04 02:07 PM
Just to make sure: This issue is breaking automatic backups, too.
Hi,
We have partially implemented the solution you suggest. It should appear in JIRA 3.1 Thanks for the report. I'm sorry, but what exactly do you mean by saying "partially"?
Hi,
We have implemented the fix, but the code has not gone through a great deal of testing. We would like to test the fix and roll the code into JIRA 3.1. Thanks, The fix appears to work. To use this locally, download:
http://repository.atlassian.com/ofbcore/jars/ofbcore-entity-2.1.1-atlassian-06122004.jar and copy to your WEB-INF/lib/ directory (atlassian-jira/WEB-INF/lib/ in JIRA Standalone; webapp/WEB-INF/lib/ in JIRA WAR/Webapp). You must also delete the old WEB-INF/lib/ofbcore-entity-2.1.1.jar file, which this replaces. This bug is similar to
I have an XML file generated from Jira 3.2 that appears to still have this problem.
In my comment I have: ... In the XML I get: ... but nothing else]]></description> What is the XML supposed to look like? My mistake – I think that one woked right – its a different bit:
In the comment we have: WE had EX fail a event which had no reachable contacts. One we sent over was marked unreachable in the db. Alarm on 10/11/04, our log says: the XML looked like: <description><![CDATA[WE had EX fail a event which had no reachable contacts. One we sent over was marked unreachable in the db. Alarm on 10/11/04, our log says: looks like this closing ]] was missed. I appologize for the comment spam, but now I am a little confused.
The same backup file which is failing on my 3.3 enterprise system running under orion, correctly imports into my standalone 3.3 system (tomcat). So maybe this has nothing to do with this bug, even though the error message on the import pointed me here. Greg,
Orion 2.0.2 works fine with that snippet (the ']]>' has been already escaped, so I wouldn't expect it to cause problems). If you work out what is breaking it, please comment here. Cheers, Just getting back to this now (well this past weekend):
With Orion/EAR/MySQL distribution of 3.3.1 when I try to restore my backup (made by a 3.2 system) I get Parser has reached the entity expansion limit "64,000" set by the Application. I dont get this on the standalone Tomcat/MySQL installation (different machine). I tried then making a mackup from the Tomcat system and restoring that on the Orion system and still get the same error. Where is this expansion limit set, and is this something I should be changing? Or is this something with the DB driver in Orion for MySQL? Is the XML parser the same in both the Standalone and WAR/EAR distributions? Hi Greg,
I believe if you start JIRA with the option (or even bigger): You should be able ot import the file. This was found at: Cheers, re:
---------------- The fix appears to work. To use this locally, download: http://repository.atlassian.com/ofbcore/jars/ofbcore-entity-2.1.1-atlassian-06122004.jar and copy to your WEB-INF/lib/ directory (atlassian-jira/WEB-INF/lib/ in JIRA Standalone; webapp/WEB-INF/lib/ in JIRA WAR/Webapp). You must also delete the old WEB-INF/lib/ofbcore-entity-2.1.1.jar file, which this replaces. Does this mean: Derek,
> Copy that file onto our OLD jira version. Then do an export, and it wont produce the bad cdata anymore? The problem is that once 'bad' CDATA sections have been produced, its impossible to deal with them properly. Hence we need to ensure the export escapes the data properly. Thanks, |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Resolved
Major
CDATA sections in comments not escaped correctly
