-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
run-app #2
Comments
Thanks. I could reproduce the issue. I'll try to fix it later, perhaps after new-year holidays. |
Sorry for late. I've tried to fix the issue, but it's more difficult than I thought. To fix it, restructuring the whole architecture might be need. So I won't fix it for the time being. sorry. (FYI) |
I think that the forked execution will provide us a workaround. |
Ok, let's wait for 2.3. Could you check this bug when 2.3 will be released? |
Sure. I'll check this on 2.3. so I keep this issue open. We can also use a fork mode by uncommenting the followings line at BuildConfig.groovy even in 2.2.x. // uncomment (and adjust settings) to fork the JVM to isolate classpaths
grails.project.fork = [
run: [maxMemory:1024, minMemory:64, debug:false, maxPerm:256]
] I tried it, then run-app/stop-app were succeed! But fork mode of 2.2 seems a little unstable yet; A very simple application works well, but another appolication having complex dependencies couldn't run app completely. The important thing is that improx and interactive mode had kept alive after the operations! |
Hello. I'm trying to use your plugin to improve grails run-app performance by
/mnt/ntfs/job/improx/improxClient.sh run-app
but it looks like it doesn't work:
Intellij Idea console prints:
23:56:17.365 INFO [localhost].[/] Initializing Spring FrameworkServlet 'grails'
23:56:17.404 INFO http11.Http11Protocol Starting ProtocolHandler ["http-bio-8080"]
|Server running. Browse to http://localhost:8080/
but server is not alive. After run-app call Grails interactive console prints
| Enter| Goodbye
end exits from interactive mode
ps
test-app works ok
The text was updated successfully, but these errors were encountered: