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 < [email protected]> 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 < > [email protected]> 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
