hi folks,
i was setting up the master cloudstack by building the fresh rpms from the
souce
it seems tomcat is not listening to redirected port 8443, but i can see
the tomcat process running .
SEVERE: Error listenerStart
Jun 20, 2014 2:52:47 PM org.apache.catalina.core.StandardContext start
SEVERE: Context [/client] startup failed due to previous errors
Jun 20, 2014 2:52:47 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: A web application appears to have started a thread named
[FileWatchdog] but has failed to stop it. This is very likely to create a
memory leak.
Jun 20, 2014 2:52:47 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: A web application appears to have started a thread named [Timer-0]
but has failed to stop it. This is very likely to create a memory leak.
Jun 20, 2014 2:52:47 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: A web application appears to have started a thread named
[ConnectionConcierge-1] but has failed to stop it. This is very likely to
create a memory leak.
Jun 20, 2014 2:52:47 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: A web application appears to have started a thread named
[ClusteredAgentManager Timer] but has failed to stop it. This is very
likely to create a memory leak.
Jun 20, 2014 2:52:47 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: A web application appears to have started a thread named [Timer-1]
but has failed to stop it. This is very likely to create a memory leak.
Jun 20, 2014 2:52:47 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: A web application appears to have started a thread named [Multicast
Heartbeat Receiver Thread] but has failed to stop it. This is very likely
to create a memory leak.
Jun 20, 2014 2:52:47 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: A web application appears to have started a thread named [Multicast
Heartbeat Sender Thread] but has failed to stop it. This is very likely to
create a memory leak.
Jun 20, 2014 2:52:47 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
INFO: Starting Coyote HTTP/1.1 on http-7080
Jun 20, 2014 2:53:13 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 126934 ms
Jun 20, 2014 2:53:20 PM org.apache.catalina.loader.WebappClassLoader
loadClass
INFO: Illegal access: this web application instance has been stopped
already. Could not load
org.apache.cloudstack.managed.context.ManagedContextTimerTask$1. The
eventual following stack trace is caused by an error thrown for debugging
purposes as well as to attempt to terminate the thread which caused the
illegal access, and has no functional impact.
java.lang.IllegalStateException
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1369)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1329)
at
org.apache.cloudstack.managed.context.ManagedContextTimerTask.run(ManagedContextTimerTask.java:27)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
Exception in thread "Timer-1" java.lang.NoClassDefFoundError:
org/apache/cloudstack/managed/context/ManagedContextTimerTask$1
at
org.apache.cloudstack.managed.context.ManagedContextTimerTask.run(ManagedContextTimerTask.java:27)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
Caused by: java.lang.ClassNotFoundException:
org.apache.cloudstack.managed.context.ManagedContextTimerTask$1
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1483)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1329)
... 3 more
any thoughts to fix this issue?
--
regards,
punith s
cloudbyte.com
