What steps will reproduce the problem?
1. Configure a ManagedDefaultMessageListenerContainer in Spring with no thread
pool set.
2. Start app
What is the expected output? What do you see instead?
Expect to see threads named as per message listener container bean name.
Instead threads get the default thread name.
What version of the product are you using? On what operating system?
xebia-management-extras 1.2.1
Please provide any additional information below.
Fix is simple. Either:
1. Call super.setBeanName() to set bean name
2. Override getBeanName() from super class.
Original issue reported on code.google.com by mike.hor...@gmail.com on 20 Nov 2012 at 3:00
Original issue reported on code.google.com by
mike.hor...@gmail.com
on 20 Nov 2012 at 3:00