Grails: Native2ascii error when I add a new property to message.properties

Question

I get a strange error when I add a new property to message.properties file in my grails application during runtime. When I restart the application via the command line, or restart STS, this error disappears. I am on version 2.0.1 and until a week ago, I was able to add new properties to message.properties file during runtime. Here is the stacktrace of the error

| Error 2012-06-18 16:54:58,702 [Thread-38] ERROR plugins.AbstractGrailsPluginManager  - Plugin [i18n:2.0.1] could not reload changes to file [/home/project/grails-app/i18n/messages.properties]: Error starting Sun's native2ascii: 
Message: Error starting Sun's native2ascii: 

Any ideas?

Answer 1

cd to jdk path

cp lib/tools.jar jre/lib/ext/tools.jar

It solves the issue.

Note: to get correct jdk path, check GGTS --> Windows --> Preferences --> Java --> Installed JREs --> JREs Home Path

Answer 2

You should be using JDK rather than JRE.

Also, if you don't need the native2ascii (which you probably don't), in BuildConfig.groovy use: grails.enable.native2ascii = false

Answer 3

Very frustrating bug.

After I executed all the steps suggested above in this thread, grails app was STILL not seeing tools.jar...

GRRR!

For anyone experiencing this problem in GGTS when pointing to the 1.7 jdk (when setting the jre) persisting afterwards, you MUST do the following:

1. Pick the correct jdk (1.7) in the "JRE Definition" panel within "Installed JRE's" in the GGTS Preferences panels.
2. Watch the jars from that jdk populate in the JRE definition window panel at the bottom "JRE System Libraries".
3. Check for tools.jar (mine DID NOT show up as recognized within the jdk lib or, after i tried 'zawmn83's post above) in /lib/ext.
4. If tools.jar does not show up as recognized in the jdk, click the "Add External JARs..." button, find it, add it.

That completely solve my problem - THANK GOD!!!!

p.s. i also had to set my JAVA_HOME to my 1.7 jdk correctly, in my .bash_profile but, that's already called out here as part of the solution.

Thanks everyone for contributing on this one - this bug has been causing me brain damage whilst tinkering with it today, and the above suggestions got me 99% of the way there!