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

CassandraCqlClusterFactoryBean doesn't consider maxConnections while validating coreConnection values [DATACASS-176] #307

spring-projects-issues opened this issue Oct 29, 2014 · 1 comment


Copy link

@spring-projects-issues spring-projects-issues commented Oct 29, 2014

Sumit opened DATACASS-176 and commented

The max values should be set before setting core values.
Otherwise the core values will be compared with the default max values which is 8.

The stacktrace as below

Caused by: java.lang.IllegalArgumentException: Core connections for LOCAL hosts must be less than max (100 > 8)
at com.datastax.driver.core.PoolingOptions.checkConnectionsPerHostOrder(
at com.datastax.driver.core.PoolingOptions.setCoreConnectionsPerHost(
at org.springframework.cassandra.config.PoolingOptionsFactoryBean.afterPropertiesSet(
... 19 more

Also when modifying min & max simultaneous connections

Caused by: java.lang.IllegalArgumentException: Min simultaneous requests per connection for LOCAL hosts must be less than max (110 > 100)
at com.datastax.driver.core.PoolingOptions.checkRequestsPerConnectionOrder(
at com.datastax.driver.core.PoolingOptions.setMinSimultaneousRequestsPerConnectionThreshold(
at org.springframework.cassandra.config.PoolingOptionsFactoryBean.afterPropertiesSet(
... 19 more

I have provided the pull request for the fix

Affects: 1.0.4 (Dijkstra SR4), 1.1 GA (Evans), 1.2 M1 (Fowler)

Referenced from: commits c8604af, 8a821a2, f304686, b560ce2

Backported to: 1.1.2 (Evans SR2)

Copy link

@spring-projects-issues spring-projects-issues commented Jan 27, 2015

David Webb commented

Enhanced the fix to work with all current tests, updated test class and pushed to master

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant