Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent Ringbuffer TTL defaults #9610

Closed
vbekiaris opened this issue Jan 9, 2017 · 0 comments

Comments

Projects
None yet
1 participant
@vbekiaris
Copy link
Contributor

commented Jan 9, 2017

Default ringbuffer TTL is 0 when using Java or explicit XML configuration, however when starting a Hazelcast instance without any explicit configuration (Hazelcast.newHazelcastInstance()) the default TTL is loaded from hazelcast-default.xml and is 30 seconds instead of 0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.