Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 40700 invoked from network); 14 Jan 2008 15:03:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Jan 2008 15:03:59 -0000 Received: (qmail 74997 invoked by uid 500); 14 Jan 2008 15:03:48 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 74967 invoked by uid 500); 14 Jan 2008 15:03:48 -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 74957 invoked by uid 99); 14 Jan 2008 15:03:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jan 2008 07:03:47 -0800 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jan 2008 15:03:42 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 5070F714268 for ; Mon, 14 Jan 2008 07:03:34 -0800 (PST) Message-ID: <10919523.1200323014326.JavaMail.jira@brutus> Date: Mon, 14 Jan 2008 07:03:34 -0800 (PST) From: =?utf-8?Q?=C3=98ystein_Gr=C3=B8vlen_=28JIRA=29?= To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-3318) Missing clean-up after failed startMaster In-Reply-To: <14853177.1200323014149.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-3318?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] =C3=98ystein Gr=C3=B8vlen updated DERBY-3318: ----------------------------------- Description:=20 It seems like some clean-up is missing if startMaster fails. This happened when I tried to connect to a non-existing slave: > > java org.apache.derby.tools.ij ij version 10.4 ij> connect 'jdbc:derby:test;create=3Dtrue'; ij> connect 'jdbc:derby:test;startMaster=3Dtrue;slaveHost=3Dlocalhost'; ERROR XRE04: Could not establish a connection to the peer of the replicated= database 'null'. ij> quit; Exception in thread "main" java.lang.NullPointerException at org.apache.derby.impl.services.replication.master.MasterControll= er.flushedTo(MasterController.java:278) at org.apache.derby.impl.store.raw.log.LogToFile.flush(LogToFile.ja= va:3953) at org.apache.derby.impl.store.raw.log.LogToFile.flush(LogToFile.ja= va:1762) at org.apache.derby.impl.store.raw.log.LogToFile.checkpointWithTran= (LogToFile.java:1653) at org.apache.derby.impl.store.raw.log.LogToFile.checkpoint(LogToFi= le.java:1469) at org.apache.derby.impl.store.raw.RawStore.stop(RawStore.java:363) at org.apache.derby.impl.services.monitor.TopService.stop(TopServic= e.java:405) at org.apache.derby.impl.services.monitor.TopService.shutdown(TopSe= rvice.java:349) at org.apache.derby.impl.services.monitor.BaseMonitor.shutdown(Base= Monitor.java:235) at org.apache.derby.impl.services.monitor.BaseMonitor.shutdown(Base= Monitor.java:201) at org.apache.derby.jdbc.InternalDriver.connect(InternalDriver.java= :205) at org.apache.derby.jdbc.AutoloadedDriver.connect(AutoloadedDr= iver.java:119) at java.sql.DriverManager.getConnection(DriverManager.java:582) at java.sql.DriverManager.getConnection(DriverManager.java:207) at org.apache.derby.impl.tools.ij.utilMain.cleanupGo(utilMain.java:= 416) at org.apache.derby.impl.tools.ij.utilMain.go(utilMain.java:249) at org.apache.derby.impl.tools.ij.Main.go(Main.java:215) at org.apache.derby.impl.tools.ij.Main.mainCore(Main.java:181) at org.apache.derby.impl.tools.ij.Main.main(Main.java:73) at org.apache.derby.tools.ij.main(ij.java:59) was: It seems like some clean-up is missing if startMaster fails. This happened when I tried to connect to a non-existing slave: (Please, tell me if I should rather report such bugs in new JIRAs) > > java org.apache.derby.tools.ij ij version 10.4 ij> connect 'jdbc:derby:test;create=3Dtrue'; ij> connect 'jdbc:derby:test;startMaster=3Dtrue;slaveHost=3Dlocalhost'; ERROR XRE04: Could not establish a connection to the peer of the replicated= database 'null'. ij> quit; Exception in thread "main" java.lang.NullPointerException at org.apache.derby.impl.services.replication.master.MasterControll= er.flushedTo(MasterController.java:278) at org.apache.derby.impl.store.raw.log.LogToFile.flush(LogToFile.ja= va:3953) at org.apache.derby.impl.store.raw.log.LogToFile.flush(LogToFile.ja= va:1762) at org.apache.derby.impl.store.raw.log.LogToFile.checkpointWithTran= (LogToFile.java:1653) at org.apache.derby.impl.store.raw.log.LogToFile.checkpoint(LogToFi= le.java:1469) at org.apache.derby.impl.store.raw.RawStore.stop(RawStore.java:363) at org.apache.derby.impl.services.monitor.TopService.stop(TopServic= e.java:405) at org.apache.derby.impl.services.monitor.TopService.shutdown(TopSe= rvice.java:349) at org.apache.derby.impl.services.monitor.BaseMonitor.shutdown(Base= Monitor.java:235) at org.apache.derby.impl.services.monitor.BaseMonitor.shutdown(Base= Monitor.java:201) at org.apache.derby.jdbc.InternalDriver.connect(InternalDriver.java= :205) at org.apache.derby.jdbc.AutoloadedDriver.connect(AutoloadedDr= iver.java:119) at java.sql.DriverManager.getConnection(DriverManager.java:582) at java.sql.DriverManager.getConnection(DriverManager.java:207) at org.apache.derby.impl.tools.ij.utilMain.cleanupGo(utilMain.java:= 416) at org.apache.derby.impl.tools.ij.utilMain.go(utilMain.java:249) at org.apache.derby.impl.tools.ij.Main.go(Main.java:215) at org.apache.derby.impl.tools.ij.Main.mainCore(Main.java:181) at org.apache.derby.impl.tools.ij.Main.main(Main.java:73) at org.apache.derby.tools.ij.main(ij.java:59) > Missing clean-up after failed startMaster > ----------------------------------------- > > Key: DERBY-3318 > URL: https://issues.apache.org/jira/browse/DERBY-3318 > Project: Derby > Issue Type: Bug > Components: Replication > Affects Versions: 10.4.0.0 > Environment: Trunk on Solaris > Reporter: =C3=98ystein Gr=C3=B8vlen > > It seems like some clean-up is missing if startMaster fails. This > happened when I tried to connect to a non-existing slave: > > > java org.apache.derby.tools.ij > ij version 10.4 > ij> connect 'jdbc:derby:test;create=3Dtrue'; > ij> connect 'jdbc:derby:test;startMaster=3Dtrue;slaveHost=3Dlocalhost'; > ERROR XRE04: Could not establish a connection to the peer of the replicat= ed database 'null'. > ij> quit; > Exception in thread "main" java.lang.NullPointerException > at org.apache.derby.impl.services.replication.master.MasterContro= ller.flushedTo(MasterController.java:278) > at org.apache.derby.impl.store.raw.log.LogToFile.flush(LogToFile.= java:3953) > at org.apache.derby.impl.store.raw.log.LogToFile.flush(LogToFile.= java:1762) > at org.apache.derby.impl.store.raw.log.LogToFile.checkpointWithTr= an(LogToFile.java:1653) > at org.apache.derby.impl.store.raw.log.LogToFile.checkpoint(LogTo= File.java:1469) > at org.apache.derby.impl.store.raw.RawStore.stop(RawStore.java:36= 3) > at org.apache.derby.impl.services.monitor.TopService.stop(TopServ= ice.java:405) > at org.apache.derby.impl.services.monitor.TopService.shutdown(Top= Service.java:349) > at org.apache.derby.impl.services.monitor.BaseMonitor.shutdown(Ba= seMonitor.java:235) > at org.apache.derby.impl.services.monitor.BaseMonitor.shutdown(Ba= seMonitor.java:201) > at org.apache.derby.jdbc.InternalDriver.connect(InternalDriver.ja= va:205) at org.apache.derby.jdbc.AutoloadedDriver.connect(Autoloaded= Driver.java:119) > at java.sql.DriverManager.getConnection(DriverManager.java:582) > at java.sql.DriverManager.getConnection(DriverManager.java:207) > at org.apache.derby.impl.tools.ij.utilMain.cleanupGo(utilMain.jav= a:416) > at org.apache.derby.impl.tools.ij.utilMain.go(utilMain.java:249) > at org.apache.derby.impl.tools.ij.Main.go(Main.java:215) > at org.apache.derby.impl.tools.ij.Main.mainCore(Main.java:181) > at org.apache.derby.impl.tools.ij.Main.main(Main.java:73) > at org.apache.derby.tools.ij.main(ij.java:59) --=20 This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.