[ 
https://issues.apache.org/jira/browse/DERBY-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578688#action_12578688
 ] 

V.Narayanan commented on DERBY-3447:
------------------------------------

Thank you for the inputs Oystein.

I have been single stepping this issue and will briefly try to describe my 
progress so far.

I tried calling the stopMaster() method from RawStore#stop() to check if this 
will help me
in determining if this would help result in a proper master shutdown. It did 
not.

I resorted to good old single stepping with my buddy Netbeans

I placed breakpoints in the following places

1) ij#quit() line no 342
2) TopService#shutdown() line no 327 (I did this after I did one round of 
single stepping with 3) below)
3) MasterController#stopMaster() line no 262

I basically started ij with the following command

java -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=9009 
org.apache.derby.tools.ij

and connected to it through netbeans

I basically observed the following when authentication is enabled

1) MasterController#stopMaster() is never called (called when authentication is 
not enabled)
2) TopService#shutdown() is never called with authentication enabled ( I tried 
this twice and observed the
   same this. Shouldn't the modules that are currently loaded be shutdown when 
authentication is enabled too?
   I am not sure how replication code can influence this.)

I need to basically take it from here. I decided to report because I thought 
maybe people
could guide me as to why TopService#shutdown() is not called with 
authentication enabled and as to whether
this is something they know of?

TopService#shutdown() is however called when I do a connect 
'jdbc:derby:;shutdown=true;user=oystein;password=pass';

> Shutdown on a database without stopping replication hangs
> ---------------------------------------------------------
>
>                 Key: DERBY-3447
>                 URL: https://issues.apache.org/jira/browse/DERBY-3447
>             Project: Derby
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 10.4.0.0
>            Reporter: V.Narayanan
>            Assignee: V.Narayanan
>         Attachments: Derby3447_v1.diff, Derby3447_v1.stat, Derby3447_v2.diff, 
> Derby3447_v2.stat
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to