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

ThreadPoolName is not respecting the input listener name #197

Open
murillocg opened this issue Mar 3, 2023 · 1 comment
Open

ThreadPoolName is not respecting the input listener name #197

murillocg opened this issue Mar 3, 2023 · 1 comment
Labels
question Further information is requested

Comments

@murillocg
Copy link

The class where we have the listener (StreamListener) has the following thread pool naming standard:
pool-11-thread-43

In the Spring Cloud Streams with Rabbit Binder, the thread pool prefix follows the channel name as follows:
gov-connector.v1.send-to-gov-{thread_number}

@Mrc0113
Copy link
Contributor

Mrc0113 commented Mar 3, 2023

Hi @murillocg,

@StreamListener is actually deprecated in the Spring Cloud Stream framework. Can you try to use Spring Cloud Function and see if that meets your needs? You would use a Consumer function if just consuming and a Function function if you also have outbound messages. See the Spring Cloud Stream reference guide for more info.

Deprecation notice: https://docs.spring.io/spring-cloud-stream/docs/current/reference/html/spring-cloud-stream.html#spring-cloud-stream-preface-notable-deprecations

*Note that I am moving this over to solace-spring-cloud since that is where our Spring Cloud Stream binder resides.

@Mrc0113 Mrc0113 transferred this issue from SolaceProducts/solace-spring-boot Mar 3, 2023
@Nephery Nephery added the question Further information is requested label May 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants