Jira fails to start after initializing modules - Prevents tomcat from starting fully.

XMLWordPrintable

    • Type: Support Request
    • Resolution: Handled by Support
    • Priority: High
    • None
    • Affects Version/s: 4.0.2
    • Environment:

      We recently had a crash due to the permagen being too low, even though it was set to 256.

      Shut down the service and unlocked the JIRA home directory. Now, when I try to restart tomcat it won't get past the following last two entries

      2010-03-10 21:26:54,223 main INFO     [atlassian.plugin.loaders.ScanningPluginLoader] No plugins found to be deployed
      2010-03-10 21:26:54,228 main INFO     [atlassian.plugin.manager.DefaultPluginManager] Plugin system started in 0:00:13.680
      

      Now if I shot down and change tomcats port from 80 to 8080, it starts up fine.

      If I delete my database, I can then start on 80 with a fresh install, then the restore of the backup works fine, but if I shut down tomcat, again, it won't start.

      I can provide my backup file but I would prefer to not make it public.

              Assignee:
              Patrick Gisbey
              Reporter:
              Brett Ryan
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: