GRAILS-9600: ERROR loaded.CurrentLiveVersion after changing applicationResources.groovy

[graemerocher]

Original Reporter: fjanon
Environment: Win7
Version: 2.2-RC2
Migrated From: http://jira.grails.org/browse/GRAILS-9600

Commenting out a line in ApplicationResources.groovy:

modules = {
application {
// resource url:'js/application.js'
}
}

leads to this on the console where the "grails run-app" command is run:

| Error 2012-11-21 16:11:59,601 [FileSystemWatcher: files=#338 cl=java.net.URLClassLoader@66869470] ERROR loaded.CurrentLiveVersion - Unexpected exception whilst trying to call the static initializer on ApplicationResources
| Error 2012-11-21 16:12:06,092 [FileSystemWatcher: files=#341 cl=java.net.URLClassLoader@66869470] ERROR loaded.CurrentLiveVersion - Unexpected exception whilst trying to call the static initializer on resources

[graemerocher]

ivand said:
In case it may be related, here is the list of plugins the app is using (and I've had some error messages specific to database-session appear as well): cache-1.0.1, cache-ehcache-1.0.0, database-migration-1.2, database-session-1.1.2 (with some edits of my own), hibernate-2.2.0.RC2, joda-time-1.4, mail-1.0.1, quartz-1.0-RC2, searchable-0.6.4, spring-security-core-1.2.7.3, tomcat-2.2.0.RC2, webxml-1.4.1.

[graemerocher]

graemerocher said:
Andy - could you take a look at this one?

[graemerocher]

aclement said:
The exception (NoSuchMethodError) indicates that the type 'resources' doesn't appear to be reloadable when it was expected to be. Let me see if I can recreate.

[graemerocher]

aclement said:
This turns out to be very serious. It is due to something new in grails 2.2 - the springloaded.properties file is now being used to configure additional classloader exclusions. The handling of the content of that file wasn't quite right causing it to replace the exclusions rather than augment them. This meant we were making more things reloaded than we should have done. Fixed in springloaded 1.1.1 - a fix whilst continuing to use springloaded 1.1.0 would be to remove springloaded.properties from the grails jars.

[graemerocher]

ivand said:
Upgraded app to 2.2.0.RC4, and the error messages have disappeared, but now I don't see any recompilation being triggered after I edit a service class.

[graemerocher]

brownj said:
I think RC4 uses springloaded 1.1.1. Are you using the release or a binary you got from Hudson or built yourself?

[graemerocher]

ivand said:
Jeff, after digging deeper into the issue, it turned out to be a post-upgrade misconfiguration on my part. Sorry for the unnecessary bother; all looks good now.

[graemerocher]

brownj said:
Thanks Ivan.

[graemerocher]

schlogen said:
I seem to be having the issue Ivan was describing. In grails 2.1.2 I wasn't having any real problems, however when I changed controllers (possibly other classes), I would get this error: [0] loaded.CurrentLiveVersion Unexpected exception whilst trying to call the static initializer on resources - . This didn't prevent me from doing any work so I mostly ignored it. I have since upgraded to grails 2.1.3 and I no longer get this error, however NO resources are reloading, not even css files. I have to restart the server to get things to reload. I am using IntelliJ IDEA 12. Windows 7x64 and JDK1.6_37 x64.

[graemerocher]

aclement said:
Not sure there is anything else for me to fix in springloaded for this issue? James references resource reloading which wouldn't be done by the agent, I'm not sure if he got that working after following Ivans tip.

[graemerocher]

schlogen said:
Yes, Ivan's help did get the problem fixed for me. Thanks for checking back!

[graemerocher]

aclement said:
Believed fixed - Grails 2.3.1 includes SpringLoaded 1.1.4. Please reopen if still an issue.