Thanks guys. Both options are working great :)
On Wed, Jul 11, 2018 at 7:21 AM, Charlie Black wrote:
> I use the technique Jens mentions... pause current thread. Works like
> champ no mater what you are debugging.
>
>
> Charlie
>
>
> On Tue, Jul 10, 2018 at 10:26 AM John Blum wrote:
>
>> Hi
I use the technique Jens mentions... pause current thread. Works like champ
no mater what you are debugging.
Charlie
On Tue, Jul 10, 2018 at 10:26 AM John Blum wrote:
> Hi Pieter - Yes, set the member-timeout Geode property when debugging,
> and then set breakpoints in whatever user-defined
Hi Pieter - Yes, set the member-timeout Geode property when debugging, and
then set breakpoints in whatever user-defined code you have deployed on the
server (e.g. *Functions*, CacheListeners/Loaders/Writers, etc) and you will
be all set. For example [1].
-j
[1]
Hi guys.
Thanks for the suggestions.
I am currently trying member-timeout and it seems to be working
Kindly
Pieter
On Tue, Jul 10, 2018 at 1:57 PM, Jens Deppe wrote:
> Hi Pieter,
>
> Make sure that you are suspending only the current thread and not all
> threads in your breakpoints.
Hi Pieter,
Make sure that you are suspending only the current thread and not all
threads in your breakpoints. Otherwise the member will not be able to
respond to heartbeats and will get kicked out of the cluster pretty quickly.
--Jens
On Tue, Jul 10, 2018 at 4:08 AM Pieter van Zyl
wrote:
>
Hi Pieter,
Looks like it could be “member-timeout”. From
https://geode.apache.org/docs/guide/10/reference/topics/gemfire_properties.html
member-timeout
Geode uses the member-timeout server configuration, specified in milliseconds,
to detect the abnormal termination of members. The
