I have updated small application to Grails 3.2.3. After some issues this is now resolved Grails 3.x update - bootRun failed
But unfortunately the application is unusable. On my high-end laptop ThinkPad 460p I cant even load home page of application. It's loading for ages and then CSS styles are not loaded at all. There is no error messages for grails run-app or IDEA Run Configuration.
I have no idea what to do now, all configuration is described here Grails 3.x update - bootRun failed
Thank you.
Chrome network profiling
Are you behind a company firewall? Are your pages trying to access remote javascript and/or css files? The process trying to access these may hang or timeout eventually.
Related
I have run into a very serious problem where I can longer deploy a war of a Grails 2.2.5 web application on Tomcat. The build (with 'grails war') proceeds without a problem, and I deploy it to Tomcat. I retsart Tomcat, and the web application simply does not run. It comes up with the deploying message, but clearly doesn't get as far as running Bootstrap.groovy, because logging from there doesn't show up in the log. No error messages are given, but the web app is simply not running.
I ran into a similar problem a few days ago on a different server which I solved by upgrading to Tomcat 7, but this one is already running Tomcat 7. I have no idea why this has started happening, unless it is something obscure to do with the recent change in Maven where only TLS 1.2 connections are allowed (a change which occurred a week or so ago).
So what could be happening? Is there some way I can log what is happening as the web app starts up, such that I might be able to see where the problem is occurring?
If it is of any relevance, it works OK when I do 'grails run-war' on my development machine.
I am trying to upgrade jruby. Went to a latest version 9.1.12.0, didn't work. Tried one version up (9.1.0.0) and same issue
The issue is it takes a very long time to boot on tomcat. Once tomcat starts the application it becomes unresponsive. Browser hangs forever and then eventually times out. Tomcat log shows that the request came, was served reply and closed (everything normal). No errors show up in tomcat log.
Tomcat is sitting behind apache, connected though AJP. I tried switching to http(s) and neither worked. Going directly to tomcat yields the same results.
I worked on solving this issue for quite some time. Not sure why it hangs and doens't throw any errors. Tried changing configurations on rails/tomcat/apache and could not find why it doens't work.
Any help tracking down this issue would be greatly appreciated
Current stack:
Rails 4.1..15
Jruby 9.0.5.0
Tomcat 6
Java 1.7.0_131
Apache 2.4.7
sounds like an enthropy depletion might be going on,
export JRUBY_OPTS=-J-Djava.security.egd=file:/dev/./urandom
or in your case :
export CATALINA_OPTS=-Djava.security.egd=file:/dev/./urandom
explanation is this' questions answer: After Upgrade To JRuby 9.1.9.0, Rails CookieStore Very Slow When Handling Encrypted Cookies
... the next jruby-openssl release should hopefully handle this better
Is anyone using the remote-control plugin with Grails 2.4.x? I'm working on upgrading an app from 2.2.4 to to 2.4.3. I've got it all working except for a few integration tests, and a bunch of functional tests. In our functional tests, I'm getting the following error:
groovyx.remote.RemoteControlException: Error sending command chain to 'http://localhost:8080/<appname>/grails-remote-control'
at groovyx.remote.transport.http.HttpTransport.send(HttpTransport.groovy:65)
at groovyx.remote.client.RemoteControl.sendCommandChain(RemoteControl.groovy:114)
at groovyx.remote.client.RemoteControl.exec(RemoteControl.groovy:73)
at groovyx.remote.client.RemoteControl.exec(RemoteControl.groovy:67)
at groovyx.remote.client.RemoteControl.call(RemoteControl.groovy:81)
at PatientTests.oneTimeSetUp(PatientTests.groovy:17)
Caused by: java.io.IOException: Server returned HTTP response code: 500 for URL: http://localhost:8080/<appname>/grails-remote-control
at groovyx.remote.transport.http.HttpTransport$_send_closure1.doCall(HttpTransport.groovy:62)
at groovyx.remote.transport.http.HttpTransport.send(HttpTransport.groovy:53)
I am using the 1.5 version of the remote-control plugin. Any ideas or insights would be much appreciated.
Thanks,
Dave
I faced this problem today with Grails 2.4.3 and remote control 1.5
I initially thought the issue was related to https://jira.grails.org/browse/GRAILS-10661
In my case, it was simply that I had a disconnected grails instance already running on port 8080 that I wasn't aware of.
Killing the errant process solved the issue for me.
Hope that helps.
Regards,
Peter
Greeting,
I'm trying to make this example work in Grails 2.1 using atmosphere plugin. When running in development environment on Tomcat it does not work, probably because Tomcat does not support web-services.
So I'm deploying it on JBoss 7.1. It does not work as well. And the following exception could be found in the log file
AtmosphereFramework exception: java.lang.IllegalStateException: The servlet or filters
that are being used by this request do not support async operation
I found the article related to async servlets support in Grails. Seems that Servlet3AsyncWebXmlProcessor should add async support to web.xml. But somebody should invoke it.
I think that atmosphere plugin is responsible for allowing async communication.
Have I missed something? Could you please help to make it work on AS7?
Ideally, I would like to figure out the way of running atmosphere applications in development environment? Is it possible?
I developed a Grails app using spring source to deploy it on cloud foundry. It seems that it has been deployed well but the url does not work. Could some one help me!
Thanks,
Reza
To access your log files using the grails plugin, use grails cf-logs.
That will surely show you how your application is behaving.
As the others have pointed out use
grails cf-logs
to see the logging results of your app.
It may also have happend that your application didn't start up properly. So try to restart it by typing:
grails cf-stop
grails cf-start
The Cloud Foundry plugin/Grails console may get stale while starting the app ("Starting app .........") but just keep hitting the deployment URL and as soon it's running you can quit and restart Grails.