We have installed vibe 3.2 basic installation on Sles11 sp1. Everything worked fine and we were able to access the vibe site with admin and Users alike. However, with the release of Vibe 3.3, when we updated the 3.2 to 3.3 and run the upgrade script ,we started facing problems getting to open the URL even with localhost ( http and https). the Problem it shows is the foll:

eg: http://localhost:8080
eg:https://localhost:8443

HTTP Status 404 -

type Status report

message

description The requested resource () is not available.
Apache Tomcat/6.0.35


Later, we did a fresh install of Vibe 3.3 on Sles SP1 but still facing the same problem. However, installing Vibe 3.2 again using the same installation procedure does not give any problems.

The following is the transcript of Catalina.log:
Jun 25, 2012 2:31:46 PM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '0' did not find a matching property.
Jun 25, 2012 2:31:46 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Jun 25, 2012 2:31:47 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8443
Jun 25, 2012 2:31:47 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 2284 ms
Jun 25, 2012 2:31:47 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Jun 25, 2012 2:31:47 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.35
Jun 25, 2012 2:31:48 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor ssfs.xml
Jun 25, 2012 2:31:51 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor ssr.xml
Jun 25, 2012 2:31:52 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor rest.xml
Jun 25, 2012 2:31:53 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor ssf.xml
Jun 25, 2012 2:32:10 PM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart

Jun 25, 2012 2:32:10 PM org.apache.catalina.core.StandardContext start
SEVERE: Context [/ssf] startup failed due to previous errors
Jun 25, 2012 2:32:10 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/ssf] appears to have started a thread named [Timer-4] but has failed to stop it. This is very likely to create a memory leak.
Jun 25, 2012 2:32:10 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory mobile
Jun 25, 2012 2:32:11 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory vibe
Jun 25, 2012 2:32:11 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory teaming
Jun 25, 2012 2:32:11 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Jun 25, 2012 2:32:11 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8443
Jun 25, 2012 2:32:11 PM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
Jun 25, 2012 2:32:11 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/114 config=null
Jun 25, 2012 2:32:11 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 24371 ms


In catalina.log it is showing SEVERE: Error listenerStart this is where seems to be the problem but unable to resolve yet. However, my catalina.out shows the following:

.............un 25, 2012 2:32:10 PM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Jun 25, 2012 2:32:10 PM org.apache.catalina.core.StandardContext start
SEVERE: Context [/ssf] startup failed due to previous errors
2012-06-25 14:32:10,862 INFO [main] [org.kablink.teaming.util.SimpleProfiler] - Simple Profiler

Jun 25, 2012 2:32:10 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/ssf] appears to have started a thread named [Timer-4] but has failed to stop it. This is very likely to create a memory leak.
Jun 25, 2012 2:32:10 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory mobile
Jun 25, 2012 2:32:11 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory vibe
Jun 25, 2012 2:32:11 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory teaming
Jun 25, 2012 2:32:11 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Jun 25, 2012 2:32:11 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8443
Jun 25, 2012 2:32:11 PM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
Jun 25, 2012 2:32:11 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/114 config=null
Jun 25, 2012 2:32:11 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 24371 ms


Any helpful ideas to resolve the problem will be highly appreciated.