I created a grails application by "grails create-app test", added logging.properties to WEB-INF/classes, created a WAR file by "grails prod war" and dropped the WAR file into /var/lib/tomcat6/webapps of my web server. As a consequence, I got the following messages in the catalina log file
Has anyone an idea what I have to do to fix this? I read that one has to add logging.properties to WEB-INF/classes, but apparently this did not help.
Check your localhost log file. Often, when the primary log doesn't have any information, it will.
Some people, when well-known sources tell them that fire will burn them, don't put their hands in the fire.
Some people, being skeptical, will put their hands in the fire, get burned, and learn not to put their hands in the fire.
And some people, believing that they know better than well-known sources, will claim it's a lie, put their hands in the fire, and continue to scream it's a lie even as their hands burn down to charred stumps.
Tim Holloway wrote:Check your localhost log file. Often, when the primary log doesn't have any information, it will.
For 6:05 the localhost log file does not contain any entries. But 4 minutes later I seem to have retried to deploy, the catalina log file for that time contains
the localhost log file contains
Is anyone able to draw any conclusions about what the problem might be (to me this seems perfectly fine)?
Check your webapp and see if it's writing any logfiles and what they say.
If that doesn't help, edit your JVM loggin file to enable debug-level logging on the org.apache.catalina resources. That way at least you'll be able to see what listeners are being processed.
Some people, when well-known sources tell them that fire will burn them, don't put their hands in the fire.
Some people, being skeptical, will put their hands in the fire, get burned, and learn not to put their hands in the fire.
And some people, believing that they know better than well-known sources, will claim it's a lie, put their hands in the fire, and continue to scream it's a lie even as their hands burn down to charred stumps.
I now found out that the error only occurs if another grails-based web application is running in tomcat. If only one of the two applications is running, everything is fine. Has anyone an idea what the problem could be in this case (I am still trying to get more logging)?
It's possible that you have a classpath issue because you placed a non-sharable jar in the Tomcat lib directory.
My experience with this kind of error is that other people have it too, so Google and see what you get.
Some people, when well-known sources tell them that fire will burn them, don't put their hands in the fire.
Some people, being skeptical, will put their hands in the fire, get burned, and learn not to put their hands in the fire.
And some people, believing that they know better than well-known sources, will claim it's a lie, put their hands in the fire, and continue to scream it's a lie even as their hands burn down to charred stumps.
We can walk to school together. And we can both read this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop