From derby-dev-return-96451-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Wed Jun 13 13:43:43 2012 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 4F331C452 for ; Wed, 13 Jun 2012 13:43:43 +0000 (UTC) Received: (qmail 67205 invoked by uid 500); 13 Jun 2012 13:43:43 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 67174 invoked by uid 500); 13 Jun 2012 13:43:43 -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 67166 invoked by uid 99); 13 Jun 2012 13:43:43 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jun 2012 13:43:43 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id CC4F51404B4 for ; Wed, 13 Jun 2012 13:43:42 +0000 (UTC) Date: Wed, 13 Jun 2012 13:43:42 +0000 (UTC) From: "Dag H. Wanvik (JIRA)" To: derby-dev@db.apache.org Message-ID: <1812769182.12582.1339595022838.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Comment Edited] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-4269?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1329= 3939#comment-13293939 ]=20 Dag H. Wanvik edited comment on DERBY-4269 at 6/13/12 1:41 PM: --------------------------------------------------------------- Attaching a patch which skips the cleaning action iff we are booting a slav= e. It makes the test work. I don't believe it will cause any problem, but w= e'll see when the regression come in. An alternative way to fix this would be some kind of extra synchronization = to hold back the recovery thread till the boot thread has returned control = to the client. =20 was (Author: dagw): Attaching a patch which skips the cleaning action iff we are booting a = slave. It makes the test work. I don't believe it will cause any problem, b= ut we'll see when the regression come in. An alternative way to fix this would be sonme kind of extra synchronization= to hold back the recovery thread till the boot thread has returned control= to the client. =20 > Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit= _OK > -------------------------------------------------------------------------= --- > > Key: DERBY-4269 > URL: https://issues.apache.org/jira/browse/DERBY-4269 > Project: Derby > Issue Type: Bug > Components: Replication > Affects Versions: 10.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, 10= .6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2 > Environment: OS: > Microsoft=C2=A9 Windows VistaT Ultimate - 6.0.6001 Service Pack 1 - Windo= wsNT 0 6 > JVM: > Sun Microsystems Inc.=20 > java version "1.4.2_16" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_16-b05) > Java HotSpot(TM) Client VM (build 1.4.2_16-b05 mixed mode 32-bit) > Reporter: Ole Solberg > Assignee: Dag H. Wanvik > Labels: derby_triage10_5_2 > Attachments: 4269-client-jstack.txt, 4269-master.txt, 4269-slave-= jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff, DERBY-4269.sta= t, DERBY-4269b.diff, db_master-derby.log, db_slave-derby.log.gz, derby-4269= -typo.diff > > > Failover did not succeed. > 2) testReplication_Local_3_p6_autocommit_OK(org.apache.derbyTesting.funct= ionTests.tests.replicationTests.ReplicationRun_Local_3_p6)junit.framework.A= ssertionFailedError: Failover did not succeed. > =09at org.apache.derbyTesting.functionTests.tests.replicationTests.Replic= ationRun.connectPing(ReplicationRun.java:270) > =09at org.apache.derbyTesting.functionTests.tests.replicationTests.Replic= ationRun_Local_3_p6.derby_3896(ReplicationRun_Local_3_p6.java:200) > =09at org.apache.derbyTesting.functionTests.tests.replicationTests.Replic= ationRun_Local_3_p6.testReplication_Local_3_p6_autocommit_OK(ReplicationRun= _Local_3_p6.java:86) > =09at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > =09at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImp= l.java:39) > =09at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcc= essorImpl.java:25) > =09at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.jav= a:106) > =09at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) > =09at junit.extensions.TestSetup$1.protect(TestSetup.java:21) > =09at junit.extensions.TestSetup.run(TestSetup.java:25) > See http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/testlog/vist= a-64/782274-suitesAll_diff.txt -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp= a For more information on JIRA, see: http://www.atlassian.com/software/jira