-
Notifications
You must be signed in to change notification settings - Fork 28
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
The context startup does not take into account the setting of auto-startup
to false.
#56
Comments
Currently, when the
Instead the code should be as below:
|
@jindalshivali can you submit a pull request? |
We have a forked version of the repo which is currently being used after the fix in our application. |
Added the PR to the issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce:
Define a listener bean:
When the application server starts, the eventListenerContainer is already running (isActive=true, and isRunning=true but autoStartup=false)
This seems to be because the plugin code calls the start() method on all the listener containers during application Context start irrespective of whether or not the
autoStartup
field is set to true.It looks like the code in below file
https://github.com/gpc/jms/blob/master/src/main/groovy/grails/plugin/jms/JmsGrailsPlugin.groovy
Method
The code above starts all the containers irrespective of the autoStartup property.
The text was updated successfully, but these errors were encountered: