The 14.1.2 EAP versions bring some very welcome fixes and changes for Groovy / Grails development but the new forked debugging support seems to have some issues still.
I am upgrading a Grails application to 2.5.0 and it seems that the non-forked execution is a no-go at the moment so forked debugging is coming just at the right time for me - and I have re-enabled the forked startup in my run configuration.
However the debugger doesn't always attach itself.
In the console log I see:
Listening for transport dt_socket at address: 65414
And in the debugger:
- Connecting to the target VM, address: '127.0.0.1:65414', transport: 'socket'
However, in many cases, no connection is made. I have no idea yet, why sometimes it works and sometimes it doesn't.
Switching JDK versions doesn't make a difference, restarting the IDE doesn't help either.
I'm using MacOS 10.10.3, IntelliJ is running on the provided custom-built 1.8.0-40 JDK runtime version.
An option to switch to shared-memory for the debugger is unfortunately not available, otherwise I would have tried that.
Any ideas, any extra information which I can provide to help figuring out this issue?
Is it something stupid which I'm doing wrong?
Is anyone else seeing this?