db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.Narayanan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3235) Implement the replication stop functionality
Date Mon, 14 Jan 2008 18:45:34 GMT

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

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

Oystein says

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

[ Show » ]
Øystein Grøvlen - 14/Jan/08 07:09 AM 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)
"

> Implement the replication stop functionality
> --------------------------------------------
>
>                 Key: DERBY-3235
>                 URL: https://issues.apache.org/jira/browse/DERBY-3235
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Replication
>    Affects Versions: 10.4.0.0
>            Reporter: V.Narayanan
>            Assignee: V.Narayanan
>         Attachments: StopImplementation_v1.diff, StopImplementation_v1.stat, StopImplementation_v1_NotForCommit.diff,
StopImplementation_v1_NotForCommit.stat, StopImplementation_v2.diff, StopImplementation_v2.stat
>
>


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


Mime
View raw message