I've reproduced your problem and am looking into it. It turns out that
it doesn't have to do with security-udp-dhalgo but with security
credentials.
On 4/15/18 11:08 PM, Thacker, Dharam wrote:
Thanks John/Bruce!
But it does not work as expected.
I tried setting (*security-udp-dhalgo=*)
Hi Dharam-
Regarding...
But the point for *spring data geode* is,
>> *How to deal with such scenario where node is no more a part of
distributed system but app is running?*
Usually one would like to take some automated corrective action on such
alerts.
Let me ask you question what do you
Thanks John/Bruce!
But it does not work as expected.
I tried setting (security-udp-dhalgo=) in properties file in both locators and
servers.
I also confirmed the same by verifying config level logs and using locator with
following command which explicitly mentions that “security-udp-dhalgo” is
Dharam-
There is nothing *Spring* can do if Apache Geode is not respecting the
setting for the Apache Geode property, "*security-udp-dhalgo*". That is
all Apache Geode.
Also, I suspect that the AuthenticationRequiredException is not bubbling
out because somewhere Geode is eating the Exception
Hello,
I recently upgraded to SDG 2.0.6 and Geode 1.5.0 but I am having
NoClassDefFoundError when starting up a client application, here is part of the
exception:
Caused by: org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'gemfireCache': FactoryBean
Hi John,
1. What type of application are you building to configure your (embedded)
peer cache? E.g. is this a Web application with an embedded peer cache
instance? Or, are you simply using Spring to configure a peer cache, Geode
server node, that is itself not an actual application?
Dennis-
SDG 2.0.6.RELEASE (SD Kay-SR6) is based [1] on Apache Geode 1.2.1. SDG
2.0.x cannot be bumped to a different minor version of Apache Geode (e.g.
1.2 -> 1.3/4/5) due to issues like you found.
SDG 2.1.0 (SD Lovelace), currently at 2.1.0.M2 (SD Lovelace-M2) is based
[2] on Apache Geode
