It looks like the error is more to di with a problem reading the XML file, rather than how the Jira is configured. So could you attach a copy of the XML file? This way we can see exactly what the problem is.

It may also be useful to make sure that the file has valid XML, so can you try running the Linux xml validation tool (xmllint)?

For example, the command below should check if the xml file is valid.

xmllint <file name>

Thanks,
Brian

I had the same problem. JIRA is working perfectly under Jetty, but importing data fails. I tried some different combinations of Java versions and Jetty versions, but with the same result; importing the backup fails at some point. To get around the problem I configured a JIRA standalone to use the same database and did the inport from there. Starting JIRA in Jetty afterwards worked perfectly. Currently I run JIRA as well as Confluence under:

• Debian GNU/Linux Sarge
• Jetty 5.1.10
  • Started with Java Service Wrapper 3.2.0
  • PostgreSQL 8.1 JDBC driver added under JETTY_HOME/ext
  • log4j added under JETTY_HOME/ext
  • All XML-related JARs moved from JETTY_HOME/ext to JETTY_HOME/lib
• JDK 5.0 update 5
• PostgreSQL 7.4.7

Thanks for the information.

If its only importing that is failing there may be a problem with transactions, but its difficult to tell without the logs. So to help us find the cause of the problem, could you attach a copy of your logs as well as your jetty config files?

Thanks,
Brian

This could well be the issue, but as I said earlier I cannot be certain unless I can see the error you recieved when importing. So a copy of the logs would be extremely useful in finding out the cause of the problem.

Thanks,
Brian

I just did that in my local machine and got the errors logged in the attached file. Results differ when Jetty is run under a 1.4.2 version JVM and 1.5. I remember seeing that complaint about the license, but it is possible that I had other issues too.

Again, I don't have the original logs anymore as I played with several systems simultaneously to figure out the best way of running both Confluence and JIRA in the same Jetty instance. Most of the problems were related to Commons-logging and Log4J and as usual, the XML-parsers and tools. The problem with the import was a smaller thing really, especially as you somewhere in the install/upgrade manual recommend upgrading by using the stand-alone version, test the backup there, then point it to the external database and test the backup again... and first after that point the other app-server installation at the new database.

All in all, both JIRA and Confluence work rather well in the same Jetty instance.

• Debian GNU/Linux 3.1 (Sarge)
• Postgres 7.4.7
• JVM 1.4.2_10 and 1.5.0_06
• Jetty 5.1.10
  • Started with Java Service Wrapper 3.2.0
  • PostgreSQL 8.1 JDBC driver added under JETTY_HOME/ext
  • log4j added under JETTY_HOME/ext
  • All XML-related JARs moved from JETTY_HOME/ext to JETTY_HOME/lib
    • xercesImpl.jar, xml-apis.jar and xmlParserAPIs.jar

The problem does look to be due to the inline-jdbc issue we have seen earlier.

Thanks,
Brian

Thanks,
Brian

Yeah, the error is rather different. Anyhow, thanks for testing. Let's see if the problem I have goes away in a future version of JIRA. At least for me/us it's not such a big problem as the import can be done through JIRA-standalone. Perhaps another solution would be to use a datasource from JETTY. I didn't try that as it would have taken more time than just configuring the standalone version for our PosrgreSQL database.

Cheers,

//
Johan