You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Rajitha Rajasooriya <ra...@gmail.com> on 2017/08/29 12:44:19 UTC
Regarding the issue DERBY-6711
1. Regarding the issue DERBY-6711
<https://issues.apache.org/jira/browse/DERBY-6711>
Can I have the exact replication test for the particular issue?
Thank you!
Rajitha Rajasooriya
Re: Regarding the issue DERBY-6711
Posted by Rajitha Rajasooriya <ra...@gmail.com>.
Issue DERBY-6711,
I did exactly what's suggested by the issue owner too and added some piece
of code as a solution . :)
On Tue, Sep 5, 2017 at 11:49 AM, Rajitha Rajasooriya <
rajitharajasooriya@gmail.com> wrote:
> Hey!
> Issue DERBY-6711,
>
> I'm working on it right now. Now the Issue is fixed I think. This problem
> occurs in a method called "stopSlave()" inside a java file called
> "SlaveController.java".
> So to get rid of the issue LogToFile.stopReplicationSlaveRole() should
> either call newException() with the database name as argument and this is
> done.
> I tried again and again and then I saw in some error messages which has
> the tables names, Schema's names and also the "database name" also
> available. I've uploaded some screenshot of the error messages which
> contains the database name .
> And there's another screenshot showing that the database name has been
> called inside the particular function.
>
> On Wed, Aug 30, 2017 at 7:01 AM, Bryan Pendleton <
> bpendleton.derby@gmail.com> wrote:
>
>> Thank you for doing that testing!
>>
>> Perhaps the problem described by DERBY-6711 has already been fixed? It is
>> a slightly old issue, and perhaps it was fixed but not marked as fixed?
>>
>> Do you see any occurrences of the message in question, but with the
>> database name properly filled in, in your logs?
>>
>> bryan
>>
>>
>
>
> --
> Rajitha
>
--
Rajitha
Re: Regarding the issue DERBY-6711
Posted by Rajitha Rajasooriya <ra...@gmail.com>.
Hey!
Issue DERBY-6711,
I'm working on it right now. Now the Issue is fixed I think. This problem
occurs in a method called "stopSlave()" inside a java file called
"SlaveController.java".
So to get rid of the issue LogToFile.stopReplicationSlaveRole() should
either call newException() with the database name as argument and this is
done.
I tried again and again and then I saw in some error messages which has the
tables names, Schema's names and also the "database name" also available.
I've uploaded some screenshot of the error messages which contains the
database name .
And there's another screenshot showing that the database name has been
called inside the particular function.
On Wed, Aug 30, 2017 at 7:01 AM, Bryan Pendleton <bpendleton.derby@gmail.com
> wrote:
> Thank you for doing that testing!
>
> Perhaps the problem described by DERBY-6711 has already been fixed? It is
> a slightly old issue, and perhaps it was fixed but not marked as fixed?
>
> Do you see any occurrences of the message in question, but with the
> database name properly filled in, in your logs?
>
> bryan
>
>
--
Rajitha
Re: Regarding the issue DERBY-6711
Posted by Bryan Pendleton <bp...@gmail.com>.
Thank you for doing that testing!
Perhaps the problem described by DERBY-6711 has already been fixed? It is a
slightly old issue, and perhaps it was fixed but not marked as fixed?
Do you see any occurrences of the message in question, but with the
database name properly filled in, in your logs?
bryan
Re: Regarding the issue DERBY-6711
Posted by Rajitha Rajasooriya <ra...@gmail.com>.
Yes I almost tried everyone of them, but I didnt get the error which is
mentioned. But I had some problems with some tests. I'll try it again.
Thanks
Rajitha
On Tue, Aug 29, 2017 at 7:04 PM, Bryan Pendleton <bpendleton.derby@gmail.com
> wrote:
> Have you tried running the Derby replication tests, as described here:
> https://issues.apache.org/jira/browse/DERBY-6711?
> focusedCommentId=16100848&page=com.atlassian.jira.
> plugin.system.issuetabpanels:comment-tabpanel#comment-16100848
>
> thanks,
>
> bryan
>
>
--
Rajitha
Re: Regarding the issue DERBY-6711
Posted by Bryan Pendleton <bp...@gmail.com>.
Have you tried running the Derby replication tests, as described here:
https://issues.apache.org/jira/browse/DERBY-6711?focusedCommentId=16100848&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16100848
thanks,
bryan