JIRA Migration from Version 5.1 to Version 6 Issue

Other Questions Jira
1

Need help with JIRA version migration

I’m working on migrating my JIRA installation from version 5.1 to version 6 on my testing environment. The setup is running on a Windows 64-bit system.

Here’s what I did:

  1. Downloaded JIRA version 6 (the standalone package named “atlassian-jira-6.0-m08-standalone”)
  2. Attempted to launch the application using the command line
  3. Executed the startup command: bin> start-jira.bat /fg

The problem:
When I try to start the service, I get this error message:

java.lang.AbstractMethodError: org.apache.catalina.connector.CoyoteAdapter.getDomain()Ljava/lang/String;

This seems to be related to some compatibility issue but I’m not sure how to resolve it. Has anyone encountered this type of error during a JIRA upgrade process? What steps should I take to fix this problem and complete the migration successfully?

2

This AbstractMethodError usually happens when there’s a Tomcat version mismatch during JIRA upgrades. You’re running the m08 milestone build, which could be causing problems since milestone releases aren’t always stable. I’d grab the stable JIRA 6.0 release instead. Before you reinstall, make sure you’re running a compatible Java version - Oracle JDK 1.6 or 1.7 works best. Also check that any custom plugins or tweaks from your JIRA 5.1 setup won’t break with version 6. Your best bet is doing a clean install with proper database migration.

3

Had the same issue upgrading from JIRA 5.x to 6.0. AbstractMethodError typically means you’ve got conflicting JAR files or leftover libraries from your old install messing with the new one. I’d completely wipe any 5.1 remnants from your system and clear temp files before trying the migration again. Also double-check that JAVA_HOME points to a JDK version that’s compatible with JIRA 6. When this happened to me, old servlet-api.jar files were still lurking in the classpath and causing the exact same error.

4

totally agree, tht error is common when the tomcat version is mismatched. make sure to use the right tomcat for jira 6, otherwise, just reinstall it fresh. it can save a lot of headache.