Another option might be to turn Pulse into a separate and standalone
(Spring Boot?) app. Perhaps that might be an acceptable compromise for
pulling it out of the locator completely.
--Jens
On Wed, May 1, 2019 at 11:26 AM Anilkumar Gingade
wrote:
> We should be supporting non-embedded mode; I
We should be supporting non-embedded mode; I believe most of the app-server
based use cases will be doing this. This also reduces the resource usage on
the geode cluster.
On Wed, May 1, 2019 at 10:44 AM Dan Smith wrote:
> Option 2 does sound like a good way to go. It does seem like if you are
Option 2 does sound like a good way to go. It does seem like if you are
making changes to fix non-embedded mode, you probably need to add an
acceptance test for that mode since there is non already, regardless of
whether you deprecate non-embedded mode.
I have no issues with deprecating either
More accurately, I think geode-core is only required when TLS is enabled on
the locator and Pulse needs to make JMX/RMI calls over TLS.
I would vote for option 2 in this scenario.
--Jens
On Tue, Apr 30, 2019 at 1:44 PM Jinmei Liao wrote:
> I believe to run pulse in non-embedded mode, you just
I believe to run pulse in non-embedded mode, you just need to install the
war in a web server and some configuration changes, you don't need
geode-core at all.
We do lack the acceptance test to run pulse in non-embedded mode though. We
have a few unit tests that touches some aspect of it.
On
Hi Geode Community!
Some colleagues and I were looking at GEODE-6683 (
https://issues.apache.org/jira/browse/GEODE-6683) and noticed that we do
not have test coverage for running Pulse in non-embedded mode. We were
wondering what our strategy is around Pulse in non-embedded mode. In order
to
