Continuum
  1. Continuum
  2. CONTINUUM-1355

No admin user found after Tomcat shutdown (Tomcat doesn't shutdown properly)

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 1.1-beta-1
    • Fix Version/s: 1.1-beta-4
    • Component/s: None
    • Labels:
      None
    • Environment:
      Linux, Tomcat 5.5.17
    • Complexity:
      Intermediate
    • Number of attachments :
      1

      Description

      Hi,

      using the latest snapshot (from yesterday) running on Tomcat 5.5.17. After the Tomcat kill and running again, Continuum starts with "Create Admin User" page saying "No admin user found" in the log.

      This has been experienced even with the older versions (1.1 snapshots).

        Issue Links

          Activity

          Hide
          Jesse McConnell added a comment -

          this sounds like the user database is not getting linked up correctly with tomcat or something..

          what database are you using, the derby one or are you setting up jndi goop in tomcat?

          Show
          Jesse McConnell added a comment - this sounds like the user database is not getting linked up correctly with tomcat or something.. what database are you using, the derby one or are you setting up jndi goop in tomcat?
          Hide
          Pavel Halas added a comment -

          Tomcat context definition file.

          Show
          Pavel Halas added a comment - Tomcat context definition file.
          Hide
          Pavel Halas added a comment -

          You can take a look at the config file – Derby is used as a data source.

          I admit it might be purely Tomcat or Derby issue – this happens when Tomcat needs to be killed (kill -9) and the database hence is not parked properly – that's my guess. So the question might be "Why tomcat needs to be killed?" or "Why Derby is not able to recover after shut down?"...

          I'm waiting for anyone else dealing with the same to provide some additional remarks.

          Thanks.

          Show
          Pavel Halas added a comment - You can take a look at the config file – Derby is used as a data source. I admit it might be purely Tomcat or Derby issue – this happens when Tomcat needs to be killed (kill -9) and the database hence is not parked properly – that's my guess. So the question might be "Why tomcat needs to be killed?" or "Why Derby is not able to recover after shut down?"... I'm waiting for anyone else dealing with the same to provide some additional remarks. Thanks.
          Hide
          Olivier Lamy added a comment -

          Which tomcat version do you use ?
          IMHO The shutdown doesn't work properly with tomcat due to the ehcache shutdowHook which failed witn an NPE.
          Looks related to http://issues.apache.org/bugzilla/show_bug.cgi?id=40212.
          A solution is to upgrade ehcache to version 1.3 which has a shutdowhook off by default. (testing with tomcat 6.0.14 and works fine)
          Can you try with manual replace of ehcache jar in continuum webapp ?
          Thanks

          Show
          Olivier Lamy added a comment - Which tomcat version do you use ? IMHO The shutdown doesn't work properly with tomcat due to the ehcache shutdowHook which failed witn an NPE. Looks related to http://issues.apache.org/bugzilla/show_bug.cgi?id=40212 . A solution is to upgrade ehcache to version 1.3 which has a shutdowhook off by default. (testing with tomcat 6.0.14 and works fine) Can you try with manual replace of ehcache jar in continuum webapp ? Thanks
          Hide
          Olivier Lamy added a comment -

          upgrade ehcache version to 1.3.0 in rev 578388.

          Show
          Olivier Lamy added a comment - upgrade ehcache version to 1.3.0 in rev 578388.

            People

            • Assignee:
              Olivier Lamy
              Reporter:
              Pavel Halas
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: