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

Øystein Grøvlen commented on DERBY-3189:
----------------------------------------

I tried a connnection with stopMaster=true in ij and it seemed to work well.  
However, when I tried to exit ij, nothing happened.  A QUIT signal to the java 
process, showed that the  LogShipper thread is still around:

Full thread dump Java HotSpot(TM) Server VM (1.6.0_01-b06 mixed mode):

"DestroyJavaVM" prio=10 tid=0x08070c00 nid=0x2 waiting on condition 
[0x00000000..0xfe56bbb0]
   java.lang.Thread.State: RUNNABLE

"Thread-1" prio=10 tid=0x08412400 nid=0x10 in Object.wait() 
[0xb64cd000..0xb64cd970]
   java.lang.Thread.State: TIMED_WAITING (on object monitor)
       at java.lang.Object.wait(Native Method)
 - waiting on <0xf408f0e0> (a 
org.apache.derby.impl.services.replication.master.AsynchronousLogShipper)
  at 
org.apache.derby.impl.services.replication.master.AsynchronousLogShipper.run(AsynchronousLogShipper.java:133)
        - locked <0xf408f0e0> (a 
org.apache.derby.impl.services.replication.master.AsynchronousLogShipper)



> Replication: Add connection url command options for starting and stopping 
> master
> --------------------------------------------------------------------------------
>
>                 Key: DERBY-3189
>                 URL: https://issues.apache.org/jira/browse/DERBY-3189
>             Project: Derby
>          Issue Type: Sub-task
>          Components: JDBC
>    Affects Versions: 10.4.0.0
>            Reporter: Jørgen Løland
>            Assignee: V.Narayanan
>         Attachments: derby-3189-1a.diff, derby-3189-1a.stat, 
> StopMaster_impl_3189_v1.diff, StopMaster_impl_3189_v1.stat, 
> StopMaster_impl_3189_v2.diff, StopMaster_impl_3189_v2.diff, 
> StopMaster_impl_3189_v2.stat, StopMaster_impl_3189_v2.stat
>
>
> Add commands to start and stop the replication master using properties or 
> connection url. Example:
> 'jdbc:derby:<host><masterdb>;startMaster=true';
> 'jdbc:derby:<host><masterdb>;stopMaster=true';
> Connection url options that must be recognized:
> startMaster=true
> stopMaster=true
> slaveHost=<host> (required)
> slavePort=<port> (optional, defaults to 8001)
> See functional specification on Derby-2872 for further details.

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