Description of problem: Assuming there's no check before attempting to export to tmx, the database encounters an error when there are no items to export. Version-Release number of selected component (if applicable): Dev How reproducible: Moderate, always Steps to Reproduce: 1. New instance of Zanata server required, i.e. no projects created 2. Click Projects in menu 3. Click Export all projects to TMX 4. Click OK in "Are you sure..." dialog Actual results: | JBWEB000065: HTTP Status 500 - Error processing Request | JBWEB000309: type JBWEB000067: Status report | JBWEB000068: message Error processing Request | JBWEB000069: description JBWEB000145: The server encountered an internal error that prevented it from fulfilling this request. | JBoss Web/7.2.0.Final Expected results: Something along the lines of an error box - "No TMXs to Export!"
Appears to only affect the product if running on a h2 database which, as far as expected, in only used for development and testing. Dropping to medium priority/severity. Exporting an empty project should come with a warning of some sort, but it's a "nice to have" rather than a problematic defect. Related to 980271
Could you attach please the tail of server.log/container.log when this happens (or any other 500 error)?
This /might/ be fixed by https://github.com/zanata/zanata-server/pull/15
Verified at be36d87e795bb0b5401f8bb233de339d7927aba8
Closing VERIFIED bugs which predate Zanata 3.1.2.