Solace Spring Cloud processor app issues when upgrading to version 4.2.0 from 3.4.0

Can you try setting the queueNameExpression=destination,


solace:

        bindings:

          # receiveSecurities-in-0 if message is found to be an array of securities

          receiveSecurity-in-0:

            consumer:
              queueNameExpression=destination

Just FYI default value for queueNameExpression is as below.

Ref: solace-spring-cloud/solace-spring-cloud-stream-binder/solace-spring-cloud-stream-binder-core/src/main/java/com/solace/spring/cloud/stream/binder/properties/SolaceConsumerProperties.java at 9b07a576f31491c23b0e2a71d3548a20b38c1a6e · SolaceProducts/solace-spring-cloud · GitHub


	/**
	 * A SpEL expression for creating the consumer group’s queue name.
	 * Modifying this can cause naming conflicts between the queue names of consumer groups.
	 * While the default SpEL expression will consistently return a value adhering to <<Generated Queue Name Syntax>>,
	 * directly using the SpEL expression string is not supported. The default value for this config option is subject to change without notice.
	 */
	private String queueNameExpression = "'scst/' + (isAnonymous ? 'an/' : 'wk/') + (group?.trim() + '/') + 'plain/' + destination.trim().replaceAll('[*>]', '_')";