RE: 1.1-beta-3 Commiter build failure notifier Continuum-605
I understand now. I never went to that screen since I declare my notifiers in the pom. It is working for me now. Thank you. Is there a way to enable this for the entire box instead of on a per project group basis? That would cut down on my admin time. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 31, 2007 2:20 PM To: continuum-users@maven.apache.org Subject: Re: 1.1-beta-3 Commiter build failure notifier Continuum-605 I mean the notifier configuration (where you set the TO mail address) in the Continuum interface. Emmanuel Madsen,Bryan a écrit : > Where do I find that configuration? This is my current config and it is > working for notifiers. > > This is my config in .\installdir\conf\plexus.xml > > > org.codehaus.plexus.naming.Naming > > org.codehaus.plexus.naming.DefaultNaming > dataSources > > > > > mail/Session > javax.mail.Session > > > mail.smtp.host > mail.company.net > > > mail.smtp.port > 25 > > ... > > This is the config in the > .\installdir\apps\continuum\webapp\WEB-INF\classes\META-INF\plexus\application.xml > > > org.codehaus.plexus.notification.notifier.Notifier > mail > > org.apache.maven.continuum.notification.mail.MailContinuumNotifier > > > org.codehaus.plexus.velocity.VelocityComponent > > > org.apache.maven.continuum.store.ContinuumStore > jdo > > > org.codehaus.plexus.mailsender.MailSender > > > > org.apache.maven.continuum.configuration.ConfigurationService > > > org.apache.maven.continuum.Continuum > > > > [EMAIL PROTECTED] > Continuum 1.1-Beta-3 > EEE d MMM HH:mm:ss Z > true > true > > > > > > > -Original Message- > From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 31, 2007 12:48 PM > To: continuum-users@maven.apache.org > Subject: Re: 1.1-beta-3 Commiter build failure notifier Continuum-605 > > Do you have configured you mail notifier to send to committers too? > > Emmanuel > > Madsen,Bryan a écrit : >> I had the committer update the pom to match the SCM sign-on and they still >> did not receive an email. >> >> -Original Message- >> From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, October 31, 2007 10:59 AM >> To: continuum-users@maven.apache.org >> Subject: Re: 1.1-beta-3 Commiter build failure notifier Continuum-605 >> >> yes, it must match exactly. SP012456 != sp012456 >> >> Madsen,Bryan a écrit : >>> Does the id in the pom have to exactly match the id of the committer? I >>> would hope this is equivalent: SP012456 vs sp012456 >>> >>> >From build email: >>> >>> >>> SCM Changes: >>> >>> Changed: SP012456 @ Tue 30 Oct 2007 13:26:00 -0500 >>> >>> >>> In the pom: >>> >>> >>> sp012456 >>> the address >>> >>> >>> -Original Message- >>> From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] >>> Sent: Wednesday, October 31, 2007 10:42 AM >>> To: continuum-users@maven.apache.org >>> Subject: Re: 1.1-beta-3 Commiter build failure notifier Continuum-605 >>> >>> Do they have their id defined in pom set to their committer id? >>> Do you have changes authors in build results? >>> >>> Emmanuel >>> >>> Madsen,Bryan a écrit : >>>> Is this feature enabled on a clean install? What are the steps to >>>> configure it? I can't find any documentation in the Administrator guides >>>> for this. >>>> >>>> Currently our committers are not receiving a failure email and they are >>>> a developer in the pom. The declared notifiers are receiving emails >>>> however. >>>> >>>> Bryan >>>> >>>> >>>> >>>> >>>> -- >>>> CONFIDENTIALITY NOTICE This message and any included attachments are from >>>> Cerner Corporation and are intended only for the addressee. The >>>> information contained in this message is confidential and may constitute >>>> inside or non-public information under international, federal, or state >>>> securities laws. Unauthorized forwarding, printing, copying, distribution, >>>> or use of such information is strictly prohibited and may be unlawful. If >>>> you are not the addressee, please promptly delete this message and notify >>>> the sender of the delivery error by e-mail or you may call Cerner's >>>> corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. >>> >> >> > > >
RE: 1.1-beta-3 Commiter build failure notifier Continuum-605
I'm not configuring the notifiers in the Continuum interface. They are all pulled in from the pom. The committer in this scenario is not a notifier in the pom. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 31, 2007 2:20 PM To: continuum-users@maven.apache.org Subject: Re: 1.1-beta-3 Commiter build failure notifier Continuum-605 I mean the notifier configuration (where you set the TO mail address) in the Continuum interface. Emmanuel Madsen,Bryan a écrit : > Where do I find that configuration? This is my current config and it is > working for notifiers. > > This is my config in .\installdir\conf\plexus.xml > > > org.codehaus.plexus.naming.Naming > > org.codehaus.plexus.naming.DefaultNaming > dataSources > > > > > mail/Session > javax.mail.Session > > > mail.smtp.host > mail.company.net > > > mail.smtp.port > 25 > > ... > > This is the config in the > .\installdir\apps\continuum\webapp\WEB-INF\classes\META-INF\plexus\application.xml > > > org.codehaus.plexus.notification.notifier.Notifier > mail > > org.apache.maven.continuum.notification.mail.MailContinuumNotifier > > > org.codehaus.plexus.velocity.VelocityComponent > > > org.apache.maven.continuum.store.ContinuumStore > jdo > > > org.codehaus.plexus.mailsender.MailSender > > > > org.apache.maven.continuum.configuration.ConfigurationService > > > org.apache.maven.continuum.Continuum > > > > [EMAIL PROTECTED] > Continuum 1.1-Beta-3 > EEE d MMM HH:mm:ss Z > true > true > > > > > > > -Original Message- > From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 31, 2007 12:48 PM > To: continuum-users@maven.apache.org > Subject: Re: 1.1-beta-3 Commiter build failure notifier Continuum-605 > > Do you have configured you mail notifier to send to committers too? > > Emmanuel > > Madsen,Bryan a écrit : >> I had the committer update the pom to match the SCM sign-on and they still >> did not receive an email. >> >> -Original Message- >> From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, October 31, 2007 10:59 AM >> To: continuum-users@maven.apache.org >> Subject: Re: 1.1-beta-3 Commiter build failure notifier Continuum-605 >> >> yes, it must match exactly. SP012456 != sp012456 >> >> Madsen,Bryan a écrit : >>> Does the id in the pom have to exactly match the id of the committer? I >>> would hope this is equivalent: SP012456 vs sp012456 >>> >>> >From build email: >>> >>> >>> SCM Changes: >>> >>> Changed: SP012456 @ Tue 30 Oct 2007 13:26:00 -0500 >>> >>> >>> In the pom: >>> >>> >>> sp012456 >>> the address >>> >>> >>> -Original Message- >>> From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] >>> Sent: Wednesday, October 31, 2007 10:42 AM >>> To: continuum-users@maven.apache.org >>> Subject: Re: 1.1-beta-3 Commiter build failure notifier Continuum-605 >>> >>> Do they have their id defined in pom set to their committer id? >>> Do you have changes authors in build results? >>> >>> Emmanuel >>> >>> Madsen,Bryan a écrit : >>>> Is this feature enabled on a clean install? What are the steps to >>>> configure it? I can't find any documentation in the Administrator guides >>>> for this. >>>> >>>> Currently our committers are not receiving a failure email and they are >>>> a developer in the pom. The declared notifiers are receiving emails >>>> however. >>>> >>>> Bryan >>>> >>>> >>>> >>>> >>>> -- >>>> CONFIDENTIALITY NOTICE This message and any included attachments are from >>>> Cerner Corporation and are intended only for the addressee. The >>>> information contained in this message is confidential and may constitute >>>> inside or non-public information under international, federal, or state >>>> securities laws. Unauthorized forwarding, printing, copying, distribution, >>>> or use of such information is strictly prohibited and may be unlawful. If >>>> you are not the addressee, please promptly delete this message and notify >>>> the sender of the delivery error by e-mail or you may call Cerner's >>>> corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. >>> >> >> > > >
RE: 1.1-beta-3 Commiter build failure notifier Continuum-605
Does the id in the pom have to exactly match the id of the committer? I would hope this is equivalent: SP012456 vs sp012456 >From build email: SCM Changes: Changed: SP012456 @ Tue 30 Oct 2007 13:26:00 -0500 In the pom: sp012456 the address -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 31, 2007 10:42 AM To: continuum-users@maven.apache.org Subject: Re: 1.1-beta-3 Commiter build failure notifier Continuum-605 Do they have their id defined in pom set to their committer id? Do you have changes authors in build results? Emmanuel Madsen,Bryan a écrit : > Is this feature enabled on a clean install? What are the steps to > configure it? I can't find any documentation in the Administrator guides > for this. > > Currently our committers are not receiving a failure email and they are > a developer in the pom. The declared notifiers are receiving emails > however. > > Bryan > > > > > -- > CONFIDENTIALITY NOTICE This message and any included attachments are from > Cerner Corporation and are intended only for the addressee. The information > contained in this message is confidential and may constitute inside or > non-public information under international, federal, or state securities > laws. Unauthorized forwarding, printing, copying, distribution, or use of > such information is strictly prohibited and may be unlawful. If you are not > the addressee, please promptly delete this message and notify the sender of > the delivery error by e-mail or you may call Cerner's corporate offices in > Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
1.1-beta-3 Commiter build failure notifier Continuum-605
Is this feature enabled on a clean install? What are the steps to configure it? I can't find any documentation in the Administrator guides for this. Currently our committers are not receiving a failure email and they are a developer in the pom. The declared notifiers are receiving emails however. Bryan -- CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
RE: [Announce] Continuum 1.1-beta-1 is released
I realized I posted to the wrong list. See below. After playing around with this it looks like the save and cancel button are operating opposite of what they should on the Profiles page. I am able to save installations on a Profile if I save using the cancel button. -Original Message- From: Madsen,Bryan Sent: Friday, July 27, 2007 8:58 AM To: 'Maven Users List' Subject: RE: [Announce] Continuum 1.1-beta-1 is released In the Build Profiles page I added an installation to my profile and saved it. When the screen refreshed the installation did not attach to the profile. No errors, nothing in the continuum.log. Any ideas why this would happen? Bryan -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 25, 2007 9:04 AM To: continuum-users@maven.apache.org Cc: [EMAIL PROTECTED]; Maven Users List Subject: [Announce] Continuum 1.1-beta-1 is released Hi, The maven/Continuum team is pleased to announce the first beta of Continuum 1.1 Highlights are: * Continuum profiles to define JDK/maven/ANT to use in a build definition * many bug fixes and ui improvements. You can grab the latest release from: http://maven.apache.org/continuum/download.html Next up we are going to have another beta release in a month, or ideally before to have a final release in 1.5 month Anyway, below is the jira release notes for this release. Release Notes - Continuum - Version 1.1-alpha-2 Bug * [CONTINUUM-530] - HTML encode the build output * [CONTINUUM-691] - Build Numbers are obscured by the queuing/building icon * [CONTINUUM-706] - XML-RPC Server does not support addition of BuildDefinitions * [CONTINUUM-709] - Runtime error during recording in datanase * [CONTINUUM-723] - strange trouble on solaris * [CONTINUUM-817] - The generated output in the Working Copy page displays the wrong content * [CONTINUUM-821] - The Project.getBuildResults() method returns an empty list * [CONTINUUM-963] - Derby Database initialization error on Webapp restarts on Jetty * [CONTINUUM-1094] - Continuum does not build with Sun JDK 6 * [CONTINUUM-1119] - Creating a Group with an existing id errors * [CONTINUUM-1191] - editProject: NoSuchMethodException: * [CONTINUUM-1194] - Project is stuck in the "Build in Progress" state if the associated exception has more than 8192 chars * [CONTINUUM-1226] - Second build definitions on a project is never triggered with CVS * [CONTINUUM-1228] - OgnlException while setting property 'projectGroupId' on redirect * [CONTINUUM-1235] - Continuum 1.1-SNAPSHOT fails to check out projects from CVS when kicking off the build * [CONTINUUM-1241] - Schedule fails to start due to derby database column being too small * [CONTINUUM-1244] - project group name is not validated when left blank in Edit Project Group page, resulting to an error * [CONTINUUM-1308] - error moving projects to a new group * [CONTINUUM-1314] - NPE in DefaultContinuum.java - isInBuildingQueue * [CONTINUUM-1316] - Hitting 'Add' button repetitively in adding an Ant, Shell and Schedule using empty string only accumulates validation prompts in IE browser * [CONTINUUM-1320] - DefaultBuildController.makeAndStoreBuildResult cannot save build result due to maximum size of COMMAND_LINE * [CONTINUUM-1337] - NPE during profile creation * [CONTINUUM-1338] - field name in class org.apache.maven.continuum.model.scm is too small * [CONTINUUM-1339] - Deleting a project group does not delete related build output directories * [CONTINUUM-1340] - After adding a ant project to the default project group (default project group is not displayed) * [CONTINUUM-1341] - Adding a Maven 2 POM from secure SVN on a non-standard port does not work Improvement * [CONTINUUM-774] - Better support for multiprojects * [CONTINUUM-1002] - build email cleanup * [CONTINUUM-1113] - Continuum doesn't work with MySQL * [CONTINUUM-1184] - Ability to pre-configure the Jetty port in conf/plexus.xml * [CONTINUUM-1350] - Documentation on Build profiles New Feature * [CONTINUUM-44] - multiple profiles * [CONTINUUM-614] - Enable auto-refresh for the build results page * [CONTINUUM-761] - Ability to delete results * [CONTINUUM-991] - Add meta refresh header to summary pages * [CONTINUUM-1178] - In Add New Maven 2 Project woudl like opportunity not to load modules * [CONTINUUM-1222] - usage of an alternative maven2-executable * [CONTINUUM-1291] - In a special configuration the report mail can contains false java version used for the build Task * [CONTINUUM-977] - Create web UI tests for "Add m1 & m2 projects" pages Test * [CONTINUUM-978] - add web ui tests for all pages related to schedules * [CONTINUUM-1223] - Ability to choose JVM (export JAVA_HOME) for different projects Wi
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 > > >
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.executeUpda
