Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 790CD6B93 for ; Thu, 9 Jun 2011 13:36:25 +0000 (UTC) Received: (qmail 46221 invoked by uid 500); 9 Jun 2011 13:36:25 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 46197 invoked by uid 500); 9 Jun 2011 13:36:25 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 46190 invoked by uid 99); 9 Jun 2011 13:36:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Jun 2011 13:36:25 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Jun 2011 13:36:20 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id E764710A34B for ; Thu, 9 Jun 2011 13:35:58 +0000 (UTC) Date: Thu, 9 Jun 2011 13:35:58 +0000 (UTC) From: "Jayaprakash Kumar (JIRA)" To: derby-dev@db.apache.org Message-ID: <422487351.6830.1307626558944.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <2052864642.6596.1307620618840.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Updated] (DERBY-5266) Derby Database stored procedure is failing SYSCS_UTIL.SYSCS_BACKUP_DATABASE -urgent MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayaprakash Kumar updated DERBY-5266: ------------------------------------- Description: We are facing the problem with derby Backup Database procedure function SYSCS_UTIL.SYSCS_BACKUP_DATABASE(?) and this function failed to take the backup of the database and throws below error message. Below is the java code logic calling the procedure function. Connection conn = dataSource.getConnection(); backupdirectory = dirLocation + "/" + DateUtils.formatDate(new Date(), DATE_FORMAT); CallableStatement stmt = conn.prepareCall("CALL SYSCS_UTIL.SYSCS_BACKUP_DATABASE(?)"); stmt.setString(1, backupdirectory); stmt.execute(); stmt.close(); } catch (SQLException exp) { log.error("Error in performing backup database :" + exp.getMessage()); } Pls see the Threaddump below. Job logger created for job 20110426115633543103 Job execution started. Job program: [com.db.mbc.scheduler.jobs.DBBackupScheduleJob], Job parameters: [8501, 1942, 2011-04-26, 11:54:00, d:/db/backup/test, DBBP] Job Executer Signalling is not running... Job Executer Signalling is not running... Job Executer Signalling is not running... Job Executer Signalling is not running... Job Executer Signalling is not running... Job Executer Signalling is not running... Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message com.db.mbc.scheduler.jobs.JobExecutionException: Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message at com.db.mbc.scheduler.jobs.DBBackupScheduleJob.backUpDB(DBBackupScheduleJob.java:155) at com.db.mbc.scheduler.jobs.DBBackupScheduleJob.executeJob(DBBackupScheduleJob.java:88) at com.db.mbc.scheduler.jobs.BaseScheduleJob.execute(BaseScheduleJob.java:97) at com.db.mbc.base.job.SpringAwareJobActionListener.actionFired(SpringAwareJobActionListener.java:73) at com.topgear.executer.impl.StdJobExecutionShell.run(StdJobExecutionShell.java:207) at com.topgear.threadpool.impl.StdThreadPool.run(StdThreadPool.java:168) at java.lang.Thread.run(Thread.java:595) Job execution COMPLETED with result [true] Job logger created for job 20110426115633543103 Job execution started. Job program: [com.db.mbc.scheduler.jobs.DBBackupScheduleJob], Job parameters: [8501, 1942, 2011-04-26, 11:54:00, d:/db/backup/test, DBBP] Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message com.db.mbc.scheduler.jobs.JobExecutionException: Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message at com.db.mbc.scheduler.jobs.DBBackupScheduleJob.backUpDB(DBBackupScheduleJob.java:155) at com.db.mbc.scheduler.jobs.DBBackupScheduleJob.executeJob(DBBackupScheduleJob.java:88) at com.db.mbc.scheduler.jobs.BaseScheduleJob.execute(BaseScheduleJob.java:97) at com.db.mbc.base.job.SpringAwareJobActionListener.actionFired(SpringAwareJobActionListener.java:73) at com.topgear.executer.impl.StdJobExecutionShell.run(StdJobExecutionShell.java:207) at com.topgear.threadpool.impl.StdThreadPool.run(StdThreadPool.java:168) at java.lang.Thread.run(Thread.java:595) Job execution COMPLETED with result [true] Job logger created for job 20110426115633543103 Job execution started. Job program: [com.db.mbc.scheduler.jobs.DBBackupScheduleJob], Job parameters: [8501, 1942, 2011-04-26, 11:54:00, d:/db/backup/test, DBBP] Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message com.db.mbc.scheduler.jobs.JobExecutionException: Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message at com.db.mbc.scheduler.jobs.DBBackupScheduleJob.backUpDB(DBBackupScheduleJob.java:155) at com.db.mbc.scheduler.jobs.DBBackupScheduleJob.executeJob(DBBackupScheduleJob.java:88) at com.db.mbc.scheduler.jobs.BaseScheduleJob.execute(BaseScheduleJob.java:97) at com.db.mbc.base.job.SpringAwareJobActionListener.actionFired(SpringAwareJobActionListener.java:73) at com.topgear.executer.impl.StdJobExecutionShell.run(StdJobExecutionShell.java:207) at com.topgear.threadpool.impl.StdThreadPool.run(StdThreadPool.java:168) at java.lang.Thread.run(Thread.java:595) Job execution COMPLETED with result [true] Job logger created for job 20110426115633543103 Job execution started. Job program: [com.db.mbc.scheduler.jobs.DBBackupScheduleJob], Job parameters: [8501, 1942, 2011-04-26, 11:54:00, d:/db/backup/test, DBBP] was: onnection conn = dataSource.getConnection(); backupdirectory = dirLocation + "/" + DateUtils.formatDate(new Date(), DATE_FORMAT); CallableStatement stmt = conn.prepareCall("CALL SYSCS_UTIL.SYSCS_BACKUP_DATABASE(?)"); stmt.setString(1, backupdirectory); stmt.execute(); stmt.close(); } catch (SQLException exp) { log.error("Error in performing backup database :" + exp.getMessage()); } Pls see the Threaddump below. Job logger created for job 20110426115633543103 Job execution started. Job program: [com.db.mbc.scheduler.jobs.DBBackupScheduleJob], Job parameters: [8501, 1942, 2011-04-26, 11:54:00, d:/db/backup/test, DBBP] Job Executer Signalling is not running... Job Executer Signalling is not running... Job Executer Signalling is not running... Job Executer Signalling is not running... Job Executer Signalling is not running... Job Executer Signalling is not running... Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message com.db.mbc.scheduler.jobs.JobExecutionException: Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message at com.db.mbc.scheduler.jobs.DBBackupScheduleJob.backUpDB(DBBackupScheduleJob.java:155) at com.db.mbc.scheduler.jobs.DBBackupScheduleJob.executeJob(DBBackupScheduleJob.java:88) at com.db.mbc.scheduler.jobs.BaseScheduleJob.execute(BaseScheduleJob.java:97) at com.db.mbc.base.job.SpringAwareJobActionListener.actionFired(SpringAwareJobActionListener.java:73) at com.topgear.executer.impl.StdJobExecutionShell.run(StdJobExecutionShell.java:207) at com.topgear.threadpool.impl.StdThreadPool.run(StdThreadPool.java:168) at java.lang.Thread.run(Thread.java:595) Job execution COMPLETED with result [true] Job logger created for job 20110426115633543103 Job execution started. Job program: [com.db.mbc.scheduler.jobs.DBBackupScheduleJob], Job parameters: [8501, 1942, 2011-04-26, 11:54:00, d:/db/backup/test, DBBP] Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message com.db.mbc.scheduler.jobs.JobExecutionException: Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message at com.db.mbc.scheduler.jobs.DBBackupScheduleJob.backUpDB(DBBackupScheduleJob.java:155) at com.db.mbc.scheduler.jobs.DBBackupScheduleJob.executeJob(DBBackupScheduleJob.java:88) at com.db.mbc.scheduler.jobs.BaseScheduleJob.execute(BaseScheduleJob.java:97) at com.db.mbc.base.job.SpringAwareJobActionListener.actionFired(SpringAwareJobActionListener.java:73) at com.topgear.executer.impl.StdJobExecutionShell.run(StdJobExecutionShell.java:207) at com.topgear.threadpool.impl.StdThreadPool.run(StdThreadPool.java:168) at java.lang.Thread.run(Thread.java:595) Job execution COMPLETED with result [true] Job logger created for job 20110426115633543103 Job execution started. Job program: [com.db.mbc.scheduler.jobs.DBBackupScheduleJob], Job parameters: [8501, 1942, 2011-04-26, 11:54:00, d:/db/backup/test, DBBP] Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message com.db.mbc.scheduler.jobs.JobExecutionException: Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message at com.db.mbc.scheduler.jobs.DBBackupScheduleJob.backUpDB(DBBackupScheduleJob.java:155) at com.db.mbc.scheduler.jobs.DBBackupScheduleJob.executeJob(DBBackupScheduleJob.java:88) at com.db.mbc.scheduler.jobs.BaseScheduleJob.execute(BaseScheduleJob.java:97) at com.db.mbc.base.job.SpringAwareJobActionListener.actionFired(SpringAwareJobActionListener.java:73) at com.topgear.executer.impl.StdJobExecutionShell.run(StdJobExecutionShell.java:207) at com.topgear.threadpool.impl.StdThreadPool.run(StdThreadPool.java:168) at java.lang.Thread.run(Thread.java:595) Job execution COMPLETED with result [true] Job logger created for job 20110426115633543103 Job execution started. Job program: [com.db.mbc.scheduler.jobs.DBBackupScheduleJob], Job parameters: [8501, 1942, 2011-04-26, 11:54:00, d:/db/backup/test, DBBP] > Derby Database stored procedure is failing SYSCS_UTIL.SYSCS_BACKUP_DATABASE -urgent > ----------------------------------------------------------------------------------- > > Key: DERBY-5266 > URL: https://issues.apache.org/jira/browse/DERBY-5266 > Project: Derby > Issue Type: Bug > Components: Services > Affects Versions: 10.5.3.0 > Environment: We are using Windows 2003 server, Windows XP and Windows 7 > Reporter: Jayaprakash Kumar > Priority: Blocker > Labels: Backup, Database, Derby, issue > > We are facing the problem with derby Backup Database procedure function SYSCS_UTIL.SYSCS_BACKUP_DATABASE(?) and > this function failed to take the backup of the database and throws below error message. > Below is the java code logic calling the procedure function. > Connection conn = dataSource.getConnection(); > backupdirectory = dirLocation + "/" + DateUtils.formatDate(new Date(), DATE_FORMAT); > CallableStatement stmt = conn.prepareCall("CALL SYSCS_UTIL.SYSCS_BACKUP_DATABASE(?)"); > stmt.setString(1, backupdirectory); > stmt.execute(); > stmt.close(); > } catch (SQLException exp) { > log.error("Error in performing backup database :" + exp.getMessage()); > } > Pls see the Threaddump below. > Job logger created for job 20110426115633543103 > Job execution started. Job program: [com.db.mbc.scheduler.jobs.DBBackupScheduleJob], Job parameters: [8501, 1942, 2011-04-26, 11:54:00, d:/db/backup/test, DBBP] > Job Executer Signalling is not running... > Job Executer Signalling is not running... > Job Executer Signalling is not running... > Job Executer Signalling is not running... > Job Executer Signalling is not running... > Job Executer Signalling is not running... > Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message > Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message > com.db.mbc.scheduler.jobs.JobExecutionException: Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message > at com.db.mbc.scheduler.jobs.DBBackupScheduleJob.backUpDB(DBBackupScheduleJob.java:155) > at com.db.mbc.scheduler.jobs.DBBackupScheduleJob.executeJob(DBBackupScheduleJob.java:88) > at com.db.mbc.scheduler.jobs.BaseScheduleJob.execute(BaseScheduleJob.java:97) > at com.db.mbc.base.job.SpringAwareJobActionListener.actionFired(SpringAwareJobActionListener.java:73) > at com.topgear.executer.impl.StdJobExecutionShell.run(StdJobExecutionShell.java:207) > at com.topgear.threadpool.impl.StdThreadPool.run(StdThreadPool.java:168) > at java.lang.Thread.run(Thread.java:595) > Job execution COMPLETED with result [true] > Job logger created for job 20110426115633543103 > Job execution started. Job program: [com.db.mbc.scheduler.jobs.DBBackupScheduleJob], Job parameters: [8501, 1942, 2011-04-26, 11:54:00, d:/db/backup/test, DBBP] > Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message > Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message > com.db.mbc.scheduler.jobs.JobExecutionException: Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message > at com.db.mbc.scheduler.jobs.DBBackupScheduleJob.backUpDB(DBBackupScheduleJob.java:155) > at com.db.mbc.scheduler.jobs.DBBackupScheduleJob.executeJob(DBBackupScheduleJob.java:88) > at com.db.mbc.scheduler.jobs.BaseScheduleJob.execute(BaseScheduleJob.java:97) > at com.db.mbc.base.job.SpringAwareJobActionListener.actionFired(SpringAwareJobActionListener.java:73) > at com.topgear.executer.impl.StdJobExecutionShell.run(StdJobExecutionShell.java:207) > at com.topgear.threadpool.impl.StdThreadPool.run(StdThreadPool.java:168) > at java.lang.Thread.run(Thread.java:595) > Job execution COMPLETED with result [true] > Job logger created for job 20110426115633543103 > Job execution started. Job program: [com.db.mbc.scheduler.jobs.DBBackupScheduleJob], Job parameters: [8501, 1942, 2011-04-26, 11:54:00, d:/db/backup/test, DBBP] > Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message > Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message > com.db.mbc.scheduler.jobs.JobExecutionException: Error in performing backup database :A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message > at com.db.mbc.scheduler.jobs.DBBackupScheduleJob.backUpDB(DBBackupScheduleJob.java:155) > at com.db.mbc.scheduler.jobs.DBBackupScheduleJob.executeJob(DBBackupScheduleJob.java:88) > at com.db.mbc.scheduler.jobs.BaseScheduleJob.execute(BaseScheduleJob.java:97) > at com.db.mbc.base.job.SpringAwareJobActionListener.actionFired(SpringAwareJobActionListener.java:73) > at com.topgear.executer.impl.StdJobExecutionShell.run(StdJobExecutionShell.java:207) > at com.topgear.threadpool.impl.StdThreadPool.run(StdThreadPool.java:168) > at java.lang.Thread.run(Thread.java:595) > Job execution COMPLETED with result [true] > Job logger created for job 20110426115633543103 > Job execution started. Job program: [com.db.mbc.scheduler.jobs.DBBackupScheduleJob], Job parameters: [8501, 1942, 2011-04-26, 11:54:00, d:/db/backup/test, DBBP] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira