maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Halas (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-1355) No admin user found after Tomcat shutdown
Date Wed, 01 Aug 2007 07:21:13 GMT


Pavel Halas commented on CONTINUUM-1355:

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

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


> No admin user found after Tomcat shutdown
> -----------------------------------------
>                 Key: CONTINUUM-1355
>                 URL:
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.1-beta-1
>         Environment: Linux, Tomcat 5.5.17
>            Reporter: Pavel Halas
>            Priority: Critical
>         Attachments: continuum.xml
> 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).

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message