Closed tylervz closed 4 years ago
Did pull-request to your sample project with different configuration setup.
But main issue with newer Spring's is that it uses for different configuration setup different bean names for JmsConnectionFactory, there is not always only 'jmsConnectionFactory'.
With SpringBoot default configuration the bean name is actually 'cachingJmsConnectionFactory'
To turn caching off use configuration spring.jms.cache.enabled=false
, then there will be bean with name 'jmsConnectionFactory'.
When you use pooling spring.activemq.pool.enabled=true
, then there will be bean with name 'pooledJmsConnectionFactory'.
To overcome those different namings, then you can use spring bean alias'es in resources.groovy.
springConfig.addAlias('jmsConnectionFactory', 'pooledJmsConnectionFactory')
or
springConfig.addAlias('jmsConnectionFactory', 'cachingJmsConnectionFactory')
OR you override jms plugin default configuration and use not jmsConnectionFactory naming: https://github.com/gpc/jms/blob/2.0.x/src/main/groovy/grails/plugin/jms/bean/DefaultJmsBeans.groovy
Thanks! I got it working now.
We cannot upgrade to Grails 4.0.1 because this plugin is throwing an exception.
Right now the
dependencies
section in our build.gradle has the following:And we get this error when trying to run the application:
I created a repo that demonstrates this. Use the
jms
branch. https://github.com/tylervz/grails4jms/tree/jms