As a seasoned C++ developer I should’ve been aware of this which makes it a little bit embarrassing. But, since this issue has cost me several hours of searching through the Internet over the course of two or three days, I thought it might be worth sharing. Maybe somebody else is trying to be too smart or just doesn’t know better.
Grails always has something new to offer, not only features but also random bugs (unfortunately). Out of the blue I couldn’t even let Grails show its own version (grails –version) let alone perform any other action. This is all I got for each and every command I tried to execute.
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with message transform method call failed at ../../../src/share/instrument/JPLISAgent.c line: 844 Exception: java.lang.StackOverflowError thrown from the UncaughtExceptionHandler in thread "main"
The following runtimes were used:
- Windows 7 64bit
- Java 7 Update 71 64bit
- Grails 2.4.4
Of course I removed all temporary files and folders, the “target” folder of the project and the “.grails”, “.groovy”, “.m2” and “.ivy” folders in the user directory. Nothing helped. Some say it has to do with forking processes, but playing with those settings didn’t change a thing. After all, the error happens way earlier.
Then I came across a post that mentioned to create the “.inputrc” file (on a Linux system) because through debugging it was found that Grails tries to access this files. Well, I’m not using Linux, but since I was already in the “helplessly desperate” phase I wanted to give it a shot. Surprisingly, this file already existed.
Solution: I deleted “.inputrc” from the user folder et voilà, Grails worked again.
Recently I have updated our Grails 2.3 based web application to Grails 2.4. Although the 2.3 release was working fine, one doesn’t want to fall too far behind. I know out of experience that this can happen very fast. If you wait too long, then at some point the migration to a newer version is almost like starting from scratch, instead of just updating a few lines of code to accommodate for deprecated APIs. The biggest problem I encountered going to version 2.4 was a behavioral change regarding the validation.
Read More »
I “saved” this setting by syncing and then I was done.
Since I first got my iMac I always wondered why the machine would suddenly just wake up from Sleep in the middle of the night. I didn’t touch it since at night I prefer to sleep (or else I must be sleepwalking). I initially found a way to fix this but it came up again with the update to Mountain Lion (which just reset the preference).
Go the System Preferences and hit Energy Saver. There you’ll uncheck Wake for Wi-Fi network access (in German: Ruhezustand bei Netzwerkzugriff beenden). I figured that must be the reason because at night my router automatically turns off wireless and just before I get home from work it turns it back on. For me it did the trick.
Here are two images, one from my machine (in German) and one found on Google for an english machine.