Recently, I started working on a project where I'm using Spring Boot to connect to a Cassandra database. However, I'm encountering an error at startup error : "cannot resolve reference to bean 'cassandratemplate' while setting bean property 'cassandratemplate". In this post i'm going to discuess about the solution of that error.


Solution for Error: "Cannot resolve reference to bean 'cassandratemplate' while setting bean property 'cassandratemplate'"

Encountering the error "Cannot resolve reference to bean 'cassandratemplate' while setting bean property 'cassandratemplate'" indicates a configuration issue with our Spring application regarding the Cassandra template. 

Step to check that issue:

  1. First and foremost, let's ensure that Cassandra configuration is correctly set up in  Spring application context.
  2. You need to open your Spring application context configuration file (e.g., applicationContext.xml) and verify if the 'cassandratemplate' bean is defined accurately. It should resemble something like this:
    3.       <bean id="cassandratemplate" class="org.springframework.data.cassandra.core.CassandraTemplate">
          <constructor-arg ref="cassandrasession" />
      </bean>
  3. We must ensure that the bean name specified in our XML configuration matches the bean name used in our Java code where we're trying to inject the 'cassandratemplate' bean.
  4. If you're using autowiring to inject dependencies, let's double-check that the 'cassandratemplate' bean is being autowired correctly. For example:
    5.       @Autowired
      private CassandraTemplate cassandraTemplate;
  5.  Confirm that all required dependencies for the 'cassandratemplate' bean are present in our project's classpath. We should ensure that the necessary Cassandra dependencies are configured in our Maven or Gradle build file.
  6. If you're utilizing component scanning to automatically detect Spring beans, let's ensure that the package containing the 'CassandraTemplate' class is included in the component scan base package.


Check application.properties 
# Cassandra Database Configuration
spring.data.cassandra.contact-points=localhost
spring.data.cassandra.port=9042
spring.data.cassandra.keyspace=my_keyspace
spring.data.cassandra.username=my_username
spring.data.cassandra.password=my_password

After encountering the error, we successfully resolved it by implementing the following configurations alongside the settings in the application.properties file:

@Configuration
@PropertySource(value = { "classpath:application.properties" })
@EnableCassandraRepositories(basePackages = "com.walmartlabs.cia.MatchReconciler.cassandra")
public class CassandraConfig extends AbstractCassandraConfiguration {

  @Value("${spring.data.cassandra.keyspace-name}")
  private String keySpace;

  @Value("${spring.data.cassandra.contact-points}")
  private String contactPoints;

  @Value("${spring.data.cassandra.dc}")
  private String datacenter;
  @Value("${spring.data.cassandra.port}")
  private int port;
  @Value("${spring.data.cassandra.username}")
  private String username;

  @Value("${spring.data.cassandra.password}")
  private String password;
  @Value("${spring.data.cassandra.keyspace-name}")
  private String keyspaceName;

  @Override
  protected String getContactPoints() {
    return contactPoints;
  }
  @Override
  protected String getKeyspaceName() {
    return keySpace;
  }


  @Override
  protected int getPort() {
    return port;
  }

  @Override
  protected String getLocalDataCenter() {
    return datacenter;  
  }

  @Bean
  @Override
  public CqlSessionFactoryBean cassandraSession() {
    CqlSessionFactoryBean cassandraSession = super.cassandraSession();
    cassandraSession.setUsername(username);
    cassandraSession.setPassword(password);
    cassandraSession.setContactPoints(contactPoints);
    cassandraSession.setPort(port);
    cassandraSession.setLocalDatacenter(datacenter);
    cassandraSession.setKeyspaceName(keySpace);
    return cassandraSession;
  }

  @Override
  protected SessionBuilderConfigurer getSessionBuilderConfigurer() {
    return new SessionBuilderConfigurer() {

      @Override
      public CqlSessionBuilder configure(CqlSessionBuilder cqlSessionBuilder) {
        log.info("Configuring CqlSession Builder");
        return cqlSessionBuilder
                .withConfigLoader(DriverConfigLoader.programmaticBuilder()
                
                .withDuration(DefaultDriverOption.METADATA_SCHEMA_REQUEST_TIMEOUT, Duration.ofMillis(50000))
                .withDuration(DefaultDriverOption.CONNECTION_INIT_QUERY_TIMEOUT, Duration.ofMillis(50000))
                .withDuration(DefaultDriverOption.REQUEST_TIMEOUT, Duration.ofMillis(10000))
                .build());
      }
    };
  }
}

We integrated the provided configuration into our Spring application to resolve the issue. 

  • Additional Configuration: By adding a custom Cassandra configuration class, we could fine-tune our Cassandra settings beyond what's specified in the application.properties file.
  • Injection of Properties: We utilized the @Value annotation to inject property values from the application.properties file into our Java configuration class.
  • Customization of Cassandra Session: We extended AbstractCassandraConfiguration to customize the Cassandra session properties according to our requirements.
  • Timeout Configuration: Notably, we adjusted the timeout configurations to prevent timeout errors during database operations.

Read Similar Articles