Re: continuum error after killing the application
do you have an error or something in your logs when continuum start? Emmanuel [EMAIL PROTECTED] a écrit : I had to kill the container process, that hosts the continuum webapp, now after a reboot continuum does not find the the old derby schema anymore (no admin user, no project groups nothing). Is there a file lock that I have to remove? Or a database table record that locks the schema? I?ve checked the database with sqlsquirrel, seems ok Tilman Rossmy MC-TO-CPT-POA-IMD Swisscom Mobile Waldeggstrasse 51 3097 Liebefeld BE Phone: +41795932871
RE: continuum error after killing the application
well apart from the jdo warnings (like schema sa not found which seem to appear all the time anyway) there is this fatal error: 2007-03-07 18:07:27,372 INFO [STDOUT] [FATAL ERROR] 2007-03-07 18:07:27,372 INFO [STDOUT] EnvironmentCheck Failure. == ENVIRONMENT FAILURE !! xwork.xml - Missing named result success in action account in package /security. xwork.xml - Missing named result success in action login in package /security. xwork.xml - Expected method attribute value of show but got logout instead, on action logout in package /security. xwork.xml - Missing named result input in action logout in package /security. xwork.xml - Missing named result error in action logout in package /security. xwork.xml - Missing named result success in action logout in package /security. xwork.xml - Missing named result success in action register in package /security. xwork.xml - Expected method attribute value of edit but got show instead, on action usercreate in package /security. xwork.xml - Expected method attribute value of show but got list instead, on action roles in package /security. xwork.xml - Missing named result input in action roles in package /security. xwork.xml - Missing named result error in action roles in package /security. xwork.xml - Missing named result success in action roles in package /security. xwork.xml - Expected method attribute value of show but got list instead, on action permissions in package /security. xwork.xml - Missing named result input in action permissions in package /security. xwork.xml - Missing named result error in action permissions in package /security. xwork.xml - Missing named result success in action permissions in package /security. Missing [16] xwork.xml configuration elements. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Thursday, March 08, 2007 10:02 AM To: continuum-users@maven.apache.org Subject: Re: continuum error after killing the application do you have an error or something in your logs when continuum start? Emmanuel [EMAIL PROTECTED] a écrit : I had to kill the container process, that hosts the continuum webapp, now after a reboot continuum does not find the the old derby schema anymore (no admin user, no project groups nothing). Is there a file lock that I have to remove? Or a database table record that locks the schema? I?ve checked the database with sqlsquirrel, seems ok Tilman Rossmy MC-TO-CPT-POA-IMD Swisscom Mobile Waldeggstrasse 51 3097 Liebefeld BE Phone: +41795932871
Re: continuum error after killing the application
It's a wrong fatal error, this message isn't important and not related to your db pb. [EMAIL PROTECTED] a écrit : well apart from the jdo warnings (like schema sa not found which seem to appear all the time anyway) there is this fatal error: 2007-03-07 18:07:27,372 INFO [STDOUT] [FATAL ERROR] 2007-03-07 18:07:27,372 INFO [STDOUT] EnvironmentCheck Failure. == ENVIRONMENT FAILURE !! xwork.xml - Missing named result success in action account in package /security. xwork.xml - Missing named result success in action login in package /security. xwork.xml - Expected method attribute value of show but got logout instead, on action logout in package /security. xwork.xml - Missing named result input in action logout in package /security. xwork.xml - Missing named result error in action logout in package /security. xwork.xml - Missing named result success in action logout in package /security. xwork.xml - Missing named result success in action register in package /security. xwork.xml - Expected method attribute value of edit but got show instead, on action usercreate in package /security. xwork.xml - Expected method attribute value of show but got list instead, on action roles in package /security. xwork.xml - Missing named result input in action roles in package /security. xwork.xml - Missing named result error in action roles in package /security. xwork.xml - Missing named result success in action roles in package /security. xwork.xml - Expected method attribute value of show but got list instead, on action permissions in package /security. xwork.xml - Missing named result input in action permissions in package /security. xwork.xml - Missing named result error in action permissions in package /security. xwork.xml - Missing named result success in action permissions in package /security. Missing [16] xwork.xml configuration elements. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Thursday, March 08, 2007 10:02 AM To: continuum-users@maven.apache.org Subject: Re: continuum error after killing the application do you have an error or something in your logs when continuum start? Emmanuel [EMAIL PROTECTED] a écrit : I had to kill the container process, that hosts the continuum webapp, now after a reboot continuum does not find the the old derby schema anymore (no admin user, no project groups nothing). Is there a file lock that I have to remove? Or a database table record that locks the schema? I?ve checked the database with sqlsquirrel, seems ok Tilman Rossmy MC-TO-CPT-POA-IMD Swisscom Mobile Waldeggstrasse 51 3097 Liebefeld BE Phone: +41795932871
Re: continuum error after killing the application
maybe you can use an external derby server instead of the embedded derby db so when you'll stop your container, the db will continue to work. [EMAIL PROTECTED] a écrit : well apart from the jdo warnings (like schema sa not found which seem to appear all the time anyway) there is this fatal error: 2007-03-07 18:07:27,372 INFO [STDOUT] [FATAL ERROR] 2007-03-07 18:07:27,372 INFO [STDOUT] EnvironmentCheck Failure. == ENVIRONMENT FAILURE !! xwork.xml - Missing named result success in action account in package /security. xwork.xml - Missing named result success in action login in package /security. xwork.xml - Expected method attribute value of show but got logout instead, on action logout in package /security. xwork.xml - Missing named result input in action logout in package /security. xwork.xml - Missing named result error in action logout in package /security. xwork.xml - Missing named result success in action logout in package /security. xwork.xml - Missing named result success in action register in package /security. xwork.xml - Expected method attribute value of edit but got show instead, on action usercreate in package /security. xwork.xml - Expected method attribute value of show but got list instead, on action roles in package /security. xwork.xml - Missing named result input in action roles in package /security. xwork.xml - Missing named result error in action roles in package /security. xwork.xml - Missing named result success in action roles in package /security. xwork.xml - Expected method attribute value of show but got list instead, on action permissions in package /security. xwork.xml - Missing named result input in action permissions in package /security. xwork.xml - Missing named result error in action permissions in package /security. xwork.xml - Missing named result success in action permissions in package /security. Missing [16] xwork.xml configuration elements. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Thursday, March 08, 2007 10:02 AM To: continuum-users@maven.apache.org Subject: Re: continuum error after killing the application do you have an error or something in your logs when continuum start? Emmanuel [EMAIL PROTECTED] a écrit : I had to kill the container process, that hosts the continuum webapp, now after a reboot continuum does not find the the old derby schema anymore (no admin user, no project groups nothing). Is there a file lock that I have to remove? Or a database table record that locks the schema? I?ve checked the database with sqlsquirrel, seems ok Tilman Rossmy MC-TO-CPT-POA-IMD Swisscom Mobile Waldeggstrasse 51 3097 Liebefeld BE Phone: +41795932871
RE: continuum error after killing the application
found the solution to my problem, rather trivial: Started the JBoss that hosts our Continuum from $JBOSS_HOME/bin thus the Continuum database was installed at $JBOSS_HOME/bin/database. After I had to kill the JBoss Instance I restarted it with the following script from $USER_HOME: #!/bin/sh nohup $JBOSS_HOME/bin/./run.sh 0- thus a new database was created at $USER_HOME/database Now I changed my JBoss start script to #!/bin/sh cd $JBOSS_HOME/bin nohup ./run.sh 0- and I got my old Continuum database back -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Thursday, March 08, 2007 10:28 AM To: continuum-users@maven.apache.org Subject: Re: continuum error after killing the application maybe you can use an external derby server instead of the embedded derby db so when you'll stop your container, the db will continue to work. [EMAIL PROTECTED] a écrit : well apart from the jdo warnings (like schema sa not found which seem to appear all the time anyway) there is this fatal error: 2007-03-07 18:07:27,372 INFO [STDOUT] [FATAL ERROR] 2007-03-07 18:07:27,372 INFO [STDOUT] EnvironmentCheck Failure. == ENVIRONMENT FAILURE !! xwork.xml - Missing named result success in action account in package /security. xwork.xml - Missing named result success in action login in package /security. xwork.xml - Expected method attribute value of show but got logout instead, on action logout in package /security. xwork.xml - Missing named result input in action logout in package /security. xwork.xml - Missing named result error in action logout in package /security. xwork.xml - Missing named result success in action logout in package /security. xwork.xml - Missing named result success in action register in package /security. xwork.xml - Expected method attribute value of edit but got show instead, on action usercreate in package /security. xwork.xml - Expected method attribute value of show but got list instead, on action roles in package /security. xwork.xml - Missing named result input in action roles in package /security. xwork.xml - Missing named result error in action roles in package /security. xwork.xml - Missing named result success in action roles in package /security. xwork.xml - Expected method attribute value of show but got list instead, on action permissions in package /security. xwork.xml - Missing named result input in action permissions in package /security. xwork.xml - Missing named result error in action permissions in package /security. xwork.xml - Missing named result success in action permissions in package /security. Missing [16] xwork.xml configuration elements. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Thursday, March 08, 2007 10:02 AM To: continuum-users@maven.apache.org Subject: Re: continuum error after killing the application do you have an error or something in your logs when continuum start? Emmanuel [EMAIL PROTECTED] a écrit : I had to kill the container process, that hosts the continuum webapp, now after a reboot continuum does not find the the old derby schema anymore (no admin user, no project groups nothing). Is there a file lock that I have to remove? Or a database table record that locks the schema? I?ve checked the database with sqlsquirrel, seems ok Tilman Rossmy MC-TO-CPT-POA-IMD Swisscom Mobile Waldeggstrasse 51 3097 Liebefeld BE Phone: +41795932871
