Solace Spring Cloud processor app issues after the upgrade of the Spring libraries

@MickeyZ This is an issue with your Spring versions, not the Solace binder.



Caused by: java.lang.NoSuchMethodError: 'org.springframework.integration.support.MessageBuilder org.springframework.integration.support.MessageBuilder.removeHeader(java.lang.String)'

	at org.springframework.cloud.stream.function.FunctionConfiguration.sanitize(FunctionConfiguration.java:408)

This error originates from code in Spring Cloud Stream (SCSt), and I had to jump back to at least SCSt 4.1.0 to find a MessageBuilder.removeHeader() call on line 408 .

As per the Spring Cloud Supported Versions page , SCSt 4.1.0 corresponds to a dependency from Spring Cloud 2023.0.x , which is incompatible with both Spring Boot 3.4.x and other dependencies within Spring Cloud 2024.0.x (which is what spring-cloud-function-context:4.2.0 is a part of).

By any chance, are you already using the Spring Boot BOM ( spring-boot-dependencies ) and Spring Cloud BOM ( spring-cloud-dependencies ) in your application? If not, then I’d highly suggest that you use the them for some stability during Spring upgrades:
Spring Boot BOM:

Spring Cloud BOM:

By doing this, you won’t need to manually specify the versions of each individual Spring dependencies, and would only need to manage the versions of the two high-level BOMs.