Context Unavailable Error

I'm getting a "context unavailable" alert in the Cloud Foundry deployment tab. The app seems to working just fine. Is this something I should try to address?

I've included the relevant tomcat log. I'm curious if the error on "log4j:ERROR LogMananger.repositorySelector was null likely due to error in class reloading, using NOPLoggerRepository." is the root cause of the alert.

BTW, I'm deploying a Grails 1.2.1 app via CloudFoundry. I didn't have these issues before when deploying a Grails 1.1.1 app.

Java HotSpot(TM) Client VM warning: Can't detect initial thread stack location - find_vma failed
Feb 21, 2010 7:33:47 PM com.springsource.tcserver.security.PropertyDecoder <init>
INFO: tcServer property decoder has been initialized.
Feb 21, 2010 7:33:48 PM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Listener} Setting property 'deadlockCheckInterval' to '60' did not find a matching property.
Feb 21, 2010 7:33:48 PM com.springsource.tcserver.serviceability.Serviceab ilityLifecycleListener configureAspect
WARNING: This tc Server instance was not compiled with the serviceability aspect. Exception triggered serviceability dumps are not available.
Feb 21, 2010 7:33:48 PM com.springsource.tcserver.serviceability.rmi.JmxSo cketListener init
INFO: Started up JMX registry on 127.0.0.1:6969
Feb 21, 2010 7:33:48 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Feb 21, 2010 7:33:48 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 3042 ms
Feb 21, 2010 7:33:48 PM com.springsource.tcserver.serviceability.Serviceab ilityLifecycleListener start
INFO: The tc Server serviceability listener has started.
Feb 21, 2010 7:33:48 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Feb 21, 2010 7:33:48 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: SpringSource tc Server/6.0.20.C
Feb 21, 2010 7:33:48 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive ROOT.war
Feb 21, 2010 7:33:49 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive app.war
Feb 21, 2010 7:33:54 PM org.apache.catalina.core.ApplicationContext log
INFO: Initializing Spring root WebApplicationContext
log4j:ERROR LogMananger.repositorySelector was null likely due to error in class reloading, using NOPLoggerRepository.
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.commons.daemon.support.DaemonLoader.sto p(DaemonLoader.java:200)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.startup.Bootstrap.stop(Bootstr ap.java:302)
... 5 more
Caused by: java.lang.NullPointerException
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.ja va:243)
at org.slf4j.bridge.SLF4JBridgeHandler.getSLF4JLogger (SLF4JBridgeHandler.java:159)
at org.slf4j.bridge.SLF4JBridgeHandler.publish(SLF4JB ridgeHandler.java:244)
at java.util.logging.Logger.log(Logger.java:472)
at java.util.logging.Logger.doLog(Logger.java:494)
at java.util.logging.Logger.logp(Logger.java:694)
at org.apache.juli.logging.DirectJDKLog.log(DirectJDK Log.java:167)
at org.apache.juli.logging.DirectJDKLog.error(DirectJ DKLog.java:135)
at org.apache.catalina.startup.Catalina.stop(Catalina .java:639)
... 10 more

The most likely reason for the alert is if you application does not respond to HTTP GETs on /context - i.e. no path after the context part of the URL.

Is this the case?

"log4j:ERROR LogMananger.repositorySelector w.. " is a SLF4J/log4j versioning conflict and occurs when you shutdown the tomcat server. See http://www.mail-archive.com/log4j-us.../msg09782.html

It is unrelated to the context unavailable problem. It might however cause the restart to fail. What happens if you try and restart the (presumably stopped) service now?