Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 2.0 final
-
Fix Version/s: 2.0.1
-
Component/s: None
-
Labels:None
Description
Start the interactive console and do a run-app. Now type exit to stop the servlet container and then edit and save one of your domain classes. You should get something like this:
| Error 2012-01-11 09:19:26,464 [Thread-9] ERROR plugins.AbstractGrailsPluginManager - Plugin [domainClass:2.0.0] could not reload changes to file [/Users/pledbrook/dev/projects/scratch/env-test/grails-app/domain/org/example/Environment.groovy]: BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext Message: BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext Line | Method ->> 129 | initializeSpringConfig in grails.spring.BeanBuilder - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | 120 | <init> in '' | 113 | <init> . . . . . . . . in '' ^ 680 | run in java.lang.Thread
Apparently the pluginManager tries to update the applicationContext, even though it's already been shut down.
Activity
- All
- Comments
- Work Log
- History
- Activity
- Git Commits
I was struggling to reproduce this, but I have a reproducible example of a similar error. Grab the 'grails2' branch of the grails-pomodoro project, start the interactive console, execute run-app}, and then {{exit once the server's up an running. I keep seeing: