[오류]ggts Terminating process: Timeout: no new output for 60000 milliseconds

[오류]

Problem executing: prod war
The command 'D:\Program Files\Java\jdk1.6.0_26\bin\javaw.exe (2014. 8. 18. 오후 6:10:47)' was terminated because it didn't produce new output for some time.

See details for the output produced so far.

If you think the command simply needed more time, you can increase the time limit in the Grails preferences page.

See menu Windows >> Preferences >> Grails >> Launch
------System.out:-----------
 Welcome to Grails 1.3.7 - http://grails.org/
Licensed under Apache Standard License 2.0
Grails home is set to: D:\projects\gisDashboard\grails-1.3.7\

Base Directory: D:\projects\workspace\tmgis
Resolving dependencies...
Dependencies resolved in 1265ms.
Running script D:\projects\gisDashboard\grails-1.3.7\scripts\War.groovy
Environment set to production
  [groovyc] Compiling 1 source file to D:\projects\workspace\tmgis\target\classes
grails.config.locations = [classpath:AppConfig.groovy]
     [gspc] Compiling 1 GSP file for package [tmgis] to D:\projects\workspace\tmgis\target\classes
Building WAR file ...
     [copy] Copying 10261 files to C:\Users\07978\.grails\1.3.7\projects\tmgis\stage
------System.err:-----------
Unable to load specified config location classpath:AppConfig.groovy : class path resource [AppConfig.groovy] cannot be opened because it does not exist

Terminating process: Timeout: no new output for 60000 milliseconds

 

[해결]

Increase Grails Command Timeout in Eclipse

Every time after I had executed the ‘run-app‘ command in grails and if the application just leave it idle, I will receive an annoying error message and the process will be terminated after one minute. The timeout value has been set to 60000 ms, which is equivalent to 1 minute.

The output of the errors will look something similar to this:

Problem executing: run-app
The command '/usr/lib/jvm/java-6-openjdk/bin/java (Jun 7, 2013 11:25:27 AM)' was terminated because it didn't produce new output for some time.

See details for the output produced so far.

If you think the command simply needed more time, you can increase the time limit in the Grails preferences page.

See menu Windows >> Preferences >> Grails >> Launch
------System.out:-----------
 | Loading Grails 2.1.1
| Configuring classpath.
| Environment set to development.....
| Packaging Grails application..
| Compiling 130 source files
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
| Compiling 130 source files..
| Compiling 10 source files.....
| Running Grails application
| Server running. Browse to http://localhost:8080/CustomerApp

------System.err:-----------

Terminating process: Timeout: no new output for 60000 milliseconds

Solution:

If you are using Grails tool in Eclipse (http://grails.org/STS+Integration), you can increase the timeout value in Eclipse. The steps are as following:
1. Access to the Window > Preferences > Groovy > Grails > Grails Launch

Grails Command Timeout[ms]: 60000

The default is 60000 ms, which equivalent to 1 minute. You can convert ms to minute here: http://www.calculateme.com/Time/Milliseconds/ToMinutes.htm

Impact:

Increasing the timeout value will solve the problem of the annoying timeout message but there’s a possibility you will receive another message quite often, such as, ‘Address already in use‘. This is normal as the run-app command still running on the background. In order to solve the error, you need to check ‘Progress’ tab and stop the ‘run-app’ process. Worse comes to worse, you need to perform a ‘grep’ command for the ‘run-app’ process in Linux and kill the process. You can also try to use the grails command ‘stop-app’ but it seldom works for me.

 

[출처]

 http://www.jusuchyne.com/codingchyne/2013/06/increase-grails-command-timeout-in-eclipse/