Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=sbcglobal.net;
  h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding;
  b=jKebFpqhl1dV1HITpblfR2SVbVcukc/4d3HEBr142kToQ8Mh8a04Awwyh9Ejjoy4ZnxIIVDH/3x58XNX0bAOFdyugrKqkDDTmvJ9kRP7sTtqUsEr1ttd/4Qf6+uvt19OtFMX0vgI+xMRXU0/9W+hURckp7SUBxZTwx0ZhA5tYiQ=
  ;
Message-ID: <49DCB399.1020003@sbcglobal.net>
Date: Wed, 08 Apr 2009 07:24:25 -0700
From: Kathey Marsden <kmarsdenderby@sbcglobal.net>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: 10.4 -> 10.5 hard upgrade run
References: <49DA345B.4030009@sbcglobal.net>
 <c25576af0904061011n3c3ccd64i20e215d40a2c555@mail.gmail.com>
 <49DA39FF.7000602@sbcglobal.net> <49DA7D22.8030500@sbcglobal.net>
 <49DC619A.6080105@Sun.COM> <49DC93E4.1090705@sbcglobal.net>
 <x6zlercnw9.fsf@Sun.COM>
In-Reply-To: <x6zlercnw9.fsf@Sun.COM>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Knut Anders Hatlen wrote:
> If I read the stack trace you provided from derby.log correctly, that
> error did not happen in the replication tests, but in the upgrade tests:
>
>   
Good point.  I think I have been trying to do too many things at once 
and not looking carefully.  So, do the replication tests not use 
system/wombat at all?  If that's the case, then perhaps the failure is 
unrelated to upgrade even though I saw it twice in a row.

Below is the only thing of interest in db_slave/derby.log:

ERROR XRE43: Unexpected error when trying to stop replication slave 
mode. To stop repliation slave mode, use operation 'stopSlave' or 
'failover'.

    at 
org.apache.derby.iapi.error.StandardException.newException(Unknown Source)

    at 
org.apache.derby.impl.db.SlaveDatabase.verifyShutdownSlave(Unknown Source)

    at 
org.apache.derby.impl.jdbc.EmbedConnection.internalStopReplicationSlave(Unknown 
Source)

    at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source)

    at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown Source)

    at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)

    at org.apache.derby.jdbc.AutoloadedDriver.connect(Unknown Source)

    at org.apache.derby.impl.drda.Database.makeConnection(Unknown Source)

    at 
org.apache.derby.impl.drda.DRDAConnThread.getConnFromDatabaseName(Unknown 
Source)

    at 
org.apache.derby.impl.drda.DRDAConnThread.verifyUserIdPassword(Unknown 
Source)

    at org.apache.derby.impl.drda.DRDAConnThread.parseSECCHK(Unknown Source)

    at 
org.apache.derby.impl.drda.DRDAConnThread.parseDRDAConnection(Unknown 
Source)

    at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown 
Source)

    at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)

Cleanup action completed

2009-04-06 19:12:16.375 GMT Thread[DRDAConnThread_7,5,main] (DATABASE = 
C:\test4\db_slave\wombat), (DRDAID = {4}), Unexpected error when trying 
to stop replication slave mode. To stop repliation slave mode, use 
operation 'stopSlave' or 'failover'.

   I can't really correlate it to the failing test though. The exception 
the test reported does not seem to be in either log.  Perhaps the logs 
were overwritten by other tests or perhaps it is just one of those 
errors that doesn't get logged.

Kathey