HazelCast starting twice about generator-jhipster HOT 9 CLOSED

I know Julien, this is due to a configuration issue with no xml
configuration. I will check this week how to fix it.
However, it works even if two Hazelcast are started but it is not what I
would like to have.

2013/12/11 Julien Dubois [email protected]

When you select HazelCast for Hibernate caching AND HTTP session
clustering, HazelCast gets started twice.
It even does a cluster between those two instances.
cc @jmirc https://github.com/jmirc

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/49
.

from generator-jhipster.

At least it proves the cluster works :-)

from generator-jhipster.

Exact. And it works even if two different database are used. I love it. And
the front-end detects when the customer log-out from another session.

2013/12/11 Julien Dubois [email protected]

At least it proves the cluster works :-)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/49#issuecomment-30371559
.

from generator-jhipster.

@jmirc another thing I'm wondering:

• Hazelcast is a bit slow to start, and having a cluster un dev mode is annoying, as your app will try to make a cluster with the other members of your team
• So maybe we should only allow it in production ?

We could have:

• No cache in development (which can also be a problem, as it's quite different from production)
• Hazelcast for JPA in production by default (do we keep ehcache? it's complicated to have too many options... so I would even remove it)
• Hazelcast for http sessions in production as an option (this is less common than the 2nd level cache)

What do you think?

from generator-jhipster.

@jdubois how did you solve the below issue? its slow to start with lot of members on LAN

"Hazelcast is a bit slow to start, and having a cluster un dev mode is annoying, as your app will try to make a cluster with the other members of your team"

from generator-jhipster.

We didn't solve this! We solve the "starting twice" issue, not the "slow to start" comment.
So maybe this shouldn't be enabled by default for dev mode.

from generator-jhipster.

As per there docs seems like we can define the IP for clusters rite, can we set this in the JH application property YML files? or do we have to create an XML config file?

from generator-jhipster.

In that case you could create your own keys in the application.yml file, indeed!

from generator-jhipster.

do I have to configure anything else or just having the keys in yml would do? couldnt find any docs on hazelcast on what keys if it needs to be on spring boot properties

from generator-jhipster.