Field taskScheduler in gateway.confserv.conf.WebSocketConfig required a single bean, but 2 were found:

To resolve the issue of having multiple beans for the `taskScheduler` field in `gateway.confserv.conf.WebSocketConfig`, you can try the following steps:

1. Specify a qualifier for each `taskScheduler` bean in your configuration. This will help identify which bean should be injected into the `WebSocketConfig` class. For example, you can use `@Qualifier("bean1")` and `@Qualifier("bean2")`.

2. Update the `WebSocketConfig` class to use the appropriate qualifier for the `taskScheduler` field. This ensures that the correct bean is injected.

Example:

@Configuration
public class WebSocketConfig {

    @Autowired
    @Qualifier("bean1")
    private TaskScheduler taskScheduler;

    // Rest of the configuration
}

3. Make sure that you have defined the beans with the corresponding qualifiers in your configuration class or XML file.

Example:

@Configuration
public class AppConfig {

    @Bean
    @Qualifier("bean1")
    public TaskScheduler taskSchedulerBean1() {
        // Bean definition
    }

    @Bean
    @Qualifier("bean2")
    public TaskScheduler taskSchedulerBean2() {
        // Bean definition
    }

    // Rest of the configuration
}

By qualifying the beans and specifying the appropriate qualifier in the `WebSocketConfig` class, you can ensure that only one bean is injected into the `taskScheduler` field.