Thanks.
I was able to get it to work, though I'm not exactly sure how.
The hazelcast lib I was using was in my Docker image so I thought there may
be some issue with my host only networking, but I dont think that was it.
It was either related to using different hazelcast versions (3.7 vs 3.9)
Jono,
Try this log4j2 item,
Ray
On Wed, 2018-02-28 at 09:44 -0800, Jono wrote:
I have done that. The log shows when I authenticate. And it shows stuff about
hazelcast's heartbeat. But it does not say anything about how the key is store
or where I can find it.
Should I see
I have done that. The log shows when I authenticate. And it shows stuff
about hazelcast's heartbeat. But it does not say anything about how the key
is store or where I can find it.
Should I see something particular?
On Wed, Feb 28, 2018 at 9:15 AM, Ray Bon wrote:
> Jono,
>
> Try
I'm using CAS 4.2 with Hazelcast, but I'm unable to verify that CAS is
writting to Hazelcast. Can you point me to how I would determine the data
that CAS is writing to the cache?
Here is the hazelcast part of my properties file:
hz.mapname=tickets
hz.cluster.logging.type=slf4j