Grails run-app / kill process issue

Hi there.

I usually start my Grails Server with ALT+CTRL+G run-app shortcut from within IntelliJ. The problem is that CTRL+C (which kills the process from the system´s command line) isn´t available from IntelliJ and the dead-head kill-process button seems to kill the server but not the underlying java process. That way, the old java processes keep piling up and after some server restarts and the system becomes unusable.

Thanks,
El

0
3 comments

Hello.

The most common way to start new Grails server is to create appropriate Run/Debug configuration. In such case you'll be able to debug your application. Your case seems to be very strange, cause "kill button" interrupts system process in particular, but it was not tested for described situation by reason mentioned above.
Ok, I'll look at this case.

With best regards,
Ilya

0

Thanks for answering this. I know about the Debug/Run Configs but I am so used to the run-app command and just wanted to mention that it behaves unexpectedly. I guess others may run into the same issue, especially if they are new to the IntelliJ/Grails combo.


Another thing I noticed is that code completion sometimes fails on GSP pages when tag nesting get a little deeper (let´s day some nested DIV´s). On the top level IntelliJ will automatically close the div and even move to the first attribute of the tag if I hit space after entering "<div". In deeper levels that sometimes doesn´t work.


Apart from this little things, it´s a really slick and easy to use IDE!


Thanks,

El

0


Another thing I noticed is that code completion sometimes fails on GSP pages when tag nesting get a little deeper (let´s day some nested DIV´s). On the top level IntelliJ will automatically close the div and even move to the first attribute of the tag if I hit space after entering "<div". In deep
er levels that sometimes doesn´t work.

Could you provide any example?

0

Please sign in to leave a comment.