Re: Regarding the issue DERBY-6711

[Rajitha Rajasooriya]

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 <
rajitharajasoor...@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.de...@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

[Rajitha Rajasooriya]

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  wrote:

> Have you tried running the Derby replication tests, as described here:
> https://issues.apache.org/jira/browse/DERBY-6711?
> focusedCommentId=16100848=com.atlassian.jira.
> plugin.system.issuetabpanels:comment-tabpanel#comment-16100848
>
> thanks,
>
> bryan
>
>


-- 
Rajitha

Regarding the issue DERBY-6711

[Rajitha Rajasooriya]

   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

[jira] [Commented] (DERBY-6711) Missing database name in error message from LogToFile.stopReplicationSlaveRole()

[Rajitha rajasooriya (JIRA)]

[ 
https://issues.apache.org/jira/browse/DERBY-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099546#comment-16099546
 ] 

Rajitha rajasooriya commented on DERBY-6711:


Can you please provide the steps of what you've done ??

> Missing database name in error message from 
> LogToFile.stopReplicationSlaveRole()
> 
>
> Key: DERBY-6711
> URL: https://issues.apache.org/jira/browse/DERBY-6711
> Project: Derby
>  Issue Type: Bug
>  Components: Store
>Affects Versions: 10.11.1.1
>Reporter: Knut Anders Hatlen
>    Assignee: Rajitha rajasooriya
>Priority: Minor
>
> I saw this error in derby.log after running replication tests:
> {noformat}
> ERROR 08006: Database '{0}' shutdown.
>   at 
> org.apache.derby.iapi.error.StandardException.newException(StandardException.java:290)
>   at 
> org.apache.derby.iapi.error.StandardException.newException(StandardException.java:285)
>   at 
> org.apache.derby.impl.store.raw.log.LogToFile.stopReplicationSlaveRole(LogToFile.java:5253)
>   at 
> org.apache.derby.impl.store.replication.slave.SlaveController.stopSlave(SlaveController.java:266)
>   at 
> org.apache.derby.impl.store.replication.slave.SlaveController.access$500(SlaveController.java:64)
>   at 
> org.apache.derby.impl.store.replication.slave.SlaveController$SlaveLogReceiverThread.run(SlaveController.java:526)
> {noformat}
> The database name is missing from the message.
> LogToFile.stopReplicationSlaveRole() should either call newException() with 
> the database name as argument or use another message that doesn't take a 
> database name argument.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (DERBY-6711) Missing database name in error message from LogToFile.stopReplicationSlaveRole()

[Rajitha rajasooriya (JIRA)]

[ 
https://issues.apache.org/jira/browse/DERBY-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099509#comment-16099509
 ] 

Rajitha rajasooriya commented on DERBY-6711:


Can I have the source code for this? Which you got the issue when running it.

> Missing database name in error message from 
> LogToFile.stopReplicationSlaveRole()
> 
>
> Key: DERBY-6711
> URL: https://issues.apache.org/jira/browse/DERBY-6711
> Project: Derby
>  Issue Type: Bug
>  Components: Store
>Affects Versions: 10.11.1.1
>Reporter: Knut Anders Hatlen
>    Assignee: Rajitha rajasooriya
>Priority: Minor
>
> I saw this error in derby.log after running replication tests:
> {noformat}
> ERROR 08006: Database '{0}' shutdown.
>   at 
> org.apache.derby.iapi.error.StandardException.newException(StandardException.java:290)
>   at 
> org.apache.derby.iapi.error.StandardException.newException(StandardException.java:285)
>   at 
> org.apache.derby.impl.store.raw.log.LogToFile.stopReplicationSlaveRole(LogToFile.java:5253)
>   at 
> org.apache.derby.impl.store.replication.slave.SlaveController.stopSlave(SlaveController.java:266)
>   at 
> org.apache.derby.impl.store.replication.slave.SlaveController.access$500(SlaveController.java:64)
>   at 
> org.apache.derby.impl.store.replication.slave.SlaveController$SlaveLogReceiverThread.run(SlaveController.java:526)
> {noformat}
> The database name is missing from the message.
> LogToFile.stopReplicationSlaveRole() should either call newException() with 
> the database name as argument or use another message that doesn't take a 
> database name argument.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Hey there!

[Rajitha Rajasooriya]

About 6711 issue.

Can I have the piece of code where the error is occurred?

Hello!

[Rajitha Rajasooriya]

I would like to work on the following issue. DERBY-6711


Apache jira user name -rajitharajasooriya


-- 
Rajitha