RE: 1.1-alpha-2 Web application unresponsive
The scm link was not the problem. I looked at the build log and took a guess that the next project in the queue caused the hang. I deleted that project from continuum and re-added. No problems since. -Original Message- From: Jesse McConnell [mailto:[EMAIL PROTECTED] Sent: Thursday, June 28, 2007 4:43 PM To: continuum-users@maven.apache.org Subject: Re: 1.1-alpha-2 Web application unresponsive I haven't seen that exception that I remember...and if an scm link was the cause that would be even weirder...but keep us posted :) On 6/28/07, Madsen,Bryan [EMAIL PROTECTED] wrote: I'm using the default install with no modifications. This started happening more frequently over the last few days and caused the builds to hang while maxing out the CPU on the machine. This morning I deleted the contents of the ..\apps\continuum\webapp\WEB-INF\build-output-directory and 20 projects have built until the hanging/max cpu problem started again. I looked at the last project to build in the log and noticed the scm connection link in the pom is pointing to a dead link. We recently changed the url of our scm repository. I'll post again after fixing the pom and restarting continuum to see if that fixes the issue. -Original Message- From: Jesse McConnell [mailto:[EMAIL PROTECTED] Sent: Thursday, June 28, 2007 12:36 PM To: continuum-users@maven.apache.org Subject: Re: 1.1-alpha-2 Web application unresponsive your just using the supplied derby database right? looks that way from the stack trace... On 6/27/07, Madsen,Bryan [EMAIL PROTECTED] wrote: I take that back, wrong machine. It is Windows Server 2003 SE -Original Message- From: Madsen,Bryan [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 27, 2007 1:33 PM To: continuum-users@maven.apache.org Subject: RE: 1.1-alpha-2 Web application unresponsive Vista -Original Message- From: Jesse McConnell [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 27, 2007 1:08 PM To: continuum-users@maven.apache.org Subject: Re: 1.1-alpha-2 Web application unresponsive what os are you using? On 6/25/07, Madsen,Bryan [EMAIL PROTECTED] wrote: When I go to the main continuum screen I receive this exception. The only way to get the application working again is to restart the service. This is only a temporary fix as this keeps happening after an unknown amount of time. I'm guessing there is a project in the build that is causing this. Any ideas? 144655280 [Thread-6] ERROR org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor:build-project - Error executing task edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: javax.jdo.JDODataStoreException: Update request failed: UPDATE PROJECT SET OLD_STATE=?, PROJECTSTATE=? WHERE ID=? NestedThrowables: SQL Exception: An SQL data change is not permitted for a read-only connection, user or database. at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult (Futu reTask.java:299) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get (FutureTask .java:128) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut orRunnable.waitForTask(ThreadedTaskQueueExecutor.java:165) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut orRunnable.run(ThreadedTaskQueueExecutor.java:127) Caused by: javax.jdo.JDODataStoreException: Update request failed: UPDATE PROJECT SET OLD_STATE=?, PROJECTSTATE=? WHERE ID=? NestedThrowables: SQL Exception: An SQL data change is not permitted for a read-only connection, user or database. at org.jpox.store.rdbms.request.UpdateRequest.execute(UpdateRequest.java :29 8) at org.jpox.store.rdbms.table.ClassTable.update(ClassTable.java:2573) at org.jpox.store.StoreManager.update(StoreManager.java:967) at org.jpox.state.StateManagerImpl.flush(StateManagerImpl.java:4928) at org.jpox.AbstractPersistenceManager.flush( AbstractPersistenceManager.jav a:3217) at org.jpox.store.rdbms.RDBMSNonmanagedTransaction.commit (RDBMSNonmanagedTr ansaction.java:397) at org.codehaus.plexus.jdo.PlexusJdoUtils.updateObject( PlexusJdoUtils.java: 163) at org.apache.maven.continuum.store.JdoContinuumStore.updateObject (JdoConti nuumStore.java:794) at org.apache.maven.continuum.store.JdoContinuumStore.updateObject (JdoConti nuumStore.java:786) at org.apache.maven.continuum.store.JdoContinuumStore.updateProject (JdoCont inuumStore.java:966) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.startB uild(DefaultBuildController.java:289) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build( DefaultBuildController.java:95
Re: 1.1-alpha-2 Web application unresponsive
your just using the supplied derby database right? looks that way from the stack trace... On 6/27/07, Madsen,Bryan [EMAIL PROTECTED] wrote: I take that back, wrong machine. It is Windows Server 2003 SE -Original Message- From: Madsen,Bryan [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 27, 2007 1:33 PM To: continuum-users@maven.apache.org Subject: RE: 1.1-alpha-2 Web application unresponsive Vista -Original Message- From: Jesse McConnell [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 27, 2007 1:08 PM To: continuum-users@maven.apache.org Subject: Re: 1.1-alpha-2 Web application unresponsive what os are you using? On 6/25/07, Madsen,Bryan [EMAIL PROTECTED] wrote: When I go to the main continuum screen I receive this exception. The only way to get the application working again is to restart the service. This is only a temporary fix as this keeps happening after an unknown amount of time. I'm guessing there is a project in the build that is causing this. Any ideas? 144655280 [Thread-6] ERROR org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor:build-project - Error executing task edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: javax.jdo.JDODataStoreException: Update request failed: UPDATE PROJECT SET OLD_STATE=?, PROJECTSTATE=? WHERE ID=? NestedThrowables: SQL Exception: An SQL data change is not permitted for a read-only connection, user or database. at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult(Futu reTask.java:299) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get(FutureTask .java:128) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut orRunnable.waitForTask(ThreadedTaskQueueExecutor.java:165) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut orRunnable.run(ThreadedTaskQueueExecutor.java:127) Caused by: javax.jdo.JDODataStoreException: Update request failed: UPDATE PROJECT SET OLD_STATE=?, PROJECTSTATE=? WHERE ID=? NestedThrowables: SQL Exception: An SQL data change is not permitted for a read-only connection, user or database. at org.jpox.store.rdbms.request.UpdateRequest.execute(UpdateRequest.java:29 8) at org.jpox.store.rdbms.table.ClassTable.update(ClassTable.java:2573) at org.jpox.store.StoreManager.update(StoreManager.java:967) at org.jpox.state.StateManagerImpl.flush(StateManagerImpl.java:4928) at org.jpox.AbstractPersistenceManager.flush(AbstractPersistenceManager.jav a:3217) at org.jpox.store.rdbms.RDBMSNonmanagedTransaction.commit(RDBMSNonmanagedTr ansaction.java:397) at org.codehaus.plexus.jdo.PlexusJdoUtils.updateObject(PlexusJdoUtils.java: 163) at org.apache.maven.continuum.store.JdoContinuumStore.updateObject(JdoConti nuumStore.java:794) at org.apache.maven.continuum.store.JdoContinuumStore.updateObject(JdoConti nuumStore.java:786) at org.apache.maven.continuum.store.JdoContinuumStore.updateProject(JdoCont inuumStore.java:966) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.startB uild(DefaultBuildController.java:289) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build( DefaultBuildController.java:95) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.exec uteTask(BuildProjectTaskExecutor.java:50) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut orRunnable$1.run(ThreadedTaskQueueExecutor.java:116) at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter .call(Executors.java:442) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask .java:176) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker .runTask(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker .run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:595) Caused by: SQL Exception: An SQL data change is not permitted for a read-only connection, user or database. at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Un known Source) at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unkno wn Source) at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source) at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unkno wn Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeUpdate(Unknown Source
Re: 1.1-alpha-2 Web application unresponsive
I haven't seen that exception that I remember...and if an scm link was the cause that would be even weirder...but keep us posted :) On 6/28/07, Madsen,Bryan [EMAIL PROTECTED] wrote: I'm using the default install with no modifications. This started happening more frequently over the last few days and caused the builds to hang while maxing out the CPU on the machine. This morning I deleted the contents of the ..\apps\continuum\webapp\WEB-INF\build-output-directory and 20 projects have built until the hanging/max cpu problem started again. I looked at the last project to build in the log and noticed the scm connection link in the pom is pointing to a dead link. We recently changed the url of our scm repository. I'll post again after fixing the pom and restarting continuum to see if that fixes the issue. -Original Message- From: Jesse McConnell [mailto:[EMAIL PROTECTED] Sent: Thursday, June 28, 2007 12:36 PM To: continuum-users@maven.apache.org Subject: Re: 1.1-alpha-2 Web application unresponsive your just using the supplied derby database right? looks that way from the stack trace... On 6/27/07, Madsen,Bryan [EMAIL PROTECTED] wrote: I take that back, wrong machine. It is Windows Server 2003 SE -Original Message- From: Madsen,Bryan [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 27, 2007 1:33 PM To: continuum-users@maven.apache.org Subject: RE: 1.1-alpha-2 Web application unresponsive Vista -Original Message- From: Jesse McConnell [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 27, 2007 1:08 PM To: continuum-users@maven.apache.org Subject: Re: 1.1-alpha-2 Web application unresponsive what os are you using? On 6/25/07, Madsen,Bryan [EMAIL PROTECTED] wrote: When I go to the main continuum screen I receive this exception. The only way to get the application working again is to restart the service. This is only a temporary fix as this keeps happening after an unknown amount of time. I'm guessing there is a project in the build that is causing this. Any ideas? 144655280 [Thread-6] ERROR org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor:build-project - Error executing task edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: javax.jdo.JDODataStoreException: Update request failed: UPDATE PROJECT SET OLD_STATE=?, PROJECTSTATE=? WHERE ID=? NestedThrowables: SQL Exception: An SQL data change is not permitted for a read-only connection, user or database. at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult (Futu reTask.java:299) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get (FutureTask .java:128) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut orRunnable.waitForTask(ThreadedTaskQueueExecutor.java:165) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut orRunnable.run(ThreadedTaskQueueExecutor.java:127) Caused by: javax.jdo.JDODataStoreException: Update request failed: UPDATE PROJECT SET OLD_STATE=?, PROJECTSTATE=? WHERE ID=? NestedThrowables: SQL Exception: An SQL data change is not permitted for a read-only connection, user or database. at org.jpox.store.rdbms.request.UpdateRequest.execute(UpdateRequest.java :29 8) at org.jpox.store.rdbms.table.ClassTable.update(ClassTable.java:2573) at org.jpox.store.StoreManager.update(StoreManager.java:967) at org.jpox.state.StateManagerImpl.flush(StateManagerImpl.java:4928) at org.jpox.AbstractPersistenceManager.flush( AbstractPersistenceManager.jav a:3217) at org.jpox.store.rdbms.RDBMSNonmanagedTransaction.commit (RDBMSNonmanagedTr ansaction.java:397) at org.codehaus.plexus.jdo.PlexusJdoUtils.updateObject( PlexusJdoUtils.java: 163) at org.apache.maven.continuum.store.JdoContinuumStore.updateObject (JdoConti nuumStore.java:794) at org.apache.maven.continuum.store.JdoContinuumStore.updateObject (JdoConti nuumStore.java:786) at org.apache.maven.continuum.store.JdoContinuumStore.updateProject (JdoCont inuumStore.java:966) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.startB uild(DefaultBuildController.java:289) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build( DefaultBuildController.java:95) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.exec uteTask(BuildProjectTaskExecutor.java:50) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut orRunnable$1.run(ThreadedTaskQueueExecutor.java:116) at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter .call(Executors.java:442) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run (FutureTask .java:176
RE: 1.1-alpha-2 Web application unresponsive
Vista -Original Message- From: Jesse McConnell [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 27, 2007 1:08 PM To: continuum-users@maven.apache.org Subject: Re: 1.1-alpha-2 Web application unresponsive what os are you using? On 6/25/07, Madsen,Bryan [EMAIL PROTECTED] wrote: When I go to the main continuum screen I receive this exception. The only way to get the application working again is to restart the service. This is only a temporary fix as this keeps happening after an unknown amount of time. I'm guessing there is a project in the build that is causing this. Any ideas? 144655280 [Thread-6] ERROR org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor:build-project - Error executing task edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: javax.jdo.JDODataStoreException: Update request failed: UPDATE PROJECT SET OLD_STATE=?, PROJECTSTATE=? WHERE ID=? NestedThrowables: SQL Exception: An SQL data change is not permitted for a read-only connection, user or database. at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult(Futu reTask.java:299) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get(FutureTask .java:128) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut orRunnable.waitForTask(ThreadedTaskQueueExecutor.java:165) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut orRunnable.run(ThreadedTaskQueueExecutor.java:127) Caused by: javax.jdo.JDODataStoreException: Update request failed: UPDATE PROJECT SET OLD_STATE=?, PROJECTSTATE=? WHERE ID=? NestedThrowables: SQL Exception: An SQL data change is not permitted for a read-only connection, user or database. at org.jpox.store.rdbms.request.UpdateRequest.execute(UpdateRequest.java:29 8) at org.jpox.store.rdbms.table.ClassTable.update(ClassTable.java:2573) at org.jpox.store.StoreManager.update(StoreManager.java:967) at org.jpox.state.StateManagerImpl.flush(StateManagerImpl.java:4928) at org.jpox.AbstractPersistenceManager.flush(AbstractPersistenceManager.jav a:3217) at org.jpox.store.rdbms.RDBMSNonmanagedTransaction.commit(RDBMSNonmanagedTr ansaction.java:397) at org.codehaus.plexus.jdo.PlexusJdoUtils.updateObject(PlexusJdoUtils.java: 163) at org.apache.maven.continuum.store.JdoContinuumStore.updateObject(JdoConti nuumStore.java:794) at org.apache.maven.continuum.store.JdoContinuumStore.updateObject(JdoConti nuumStore.java:786) at org.apache.maven.continuum.store.JdoContinuumStore.updateProject(JdoCont inuumStore.java:966) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.startB uild(DefaultBuildController.java:289) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build( DefaultBuildController.java:95) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.exec uteTask(BuildProjectTaskExecutor.java:50) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut orRunnable$1.run(ThreadedTaskQueueExecutor.java:116) at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter .call(Executors.java:442) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask .java:176) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker .runTask(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker .run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:595) Caused by: SQL Exception: An SQL data change is not permitted for a read-only connection, user or database. at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Un known Source) at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unkno wn Source) at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source) at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unkno wn Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeUpdate(Unknown Source) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(Delega tingPreparedStatement.java:101) at org.jpox.store.rdbms.RDBMSManager.executeStatementUpdate(RDBMSManager.ja va:572) at org.jpox.store.rdbms.request.UpdateRequest.execute(UpdateRequest.java:28 4) ... 18 more Bryan -- CONFIDENTIALITY NOTICE
