Latest revision as of 17:01, 6 March 2016

Internal

A JVM running JGroups can be suspended from executing by sending the SIGSTOP signal into it:

kill -SIGSTOP <jvm-pid>

Execution can be later resumed by sending SIGCONT:

kill -SIGCONT <jvm-pid>

Also see SIGSTOP and SIGCONT.

Look at threads: (regular,timer,OOB).

@@ Line 7: / Line 7: @@
 =Suspend JVM Execution=
-A JVM running JGroups can be suspended from executing by sending the SIGSTOP signal into it:
+A JVM running JGroups can be suspended from executing by sending the  [[Linux Signals#SIGSTOP_.2819.29|SIGSTOP]] signal into it:
 <pre>
@@ Line 13: / Line 13: @@
 </pre>
-Execution can be later resumed with:
+Execution can be later resumed by sending [[Linux Signals#SIGCONT_.2818.29|SIGCONT]]:
 <pre>
 kill -SIGCONT <jvm-pid>
 </pre>
+Also see [[Linux Signals#SIGSTOP_.2819.29|SIGSTOP]] and [[Linux Signals#SIGCONT_.2818.29|SIGCONT]].
+=Practical Ways to Determine the Current View=
+* [[JGroups Protocol GMS#Current_Group_Membership|Group Membership based on GMS log entries]]
+* [[JGroups Protocol FD_SOCK#VIEW_CHANGE|Group Membership based on FD_SOCK VIEW_CHANGE log entries]]
+* [[WildFly CLI - Obtaining the Current JGroups View|Current view obtained with the WildFly CLI]]
+=Threads=
+<font color=red>Look at threads: (regular,timer,OOB)</font>.