Hi Scott, > Thanks for the report! It may be worth asking on the Tomcat list as well, as > it seems to be more to do with > Tomcat and APR than Wookie or Shindig?
Good suggestion! But I still have doubts about the origin of the problem, I think APR is another issue. As you can see into the Tomcat log file, Shindig is working well as Root webapp (ROOT.war). It's the Wookie app that failed! >> SEVERE: Error listenerStart >> Nov 30, 2010 5:48:45 PM org.apache.catalina.core.StandardContext start >> SEVERE: Context [/wookie] startup failed due to previous errors It seems to be related to the Wookie Context Listener (org.apache.wookie.server.ContextListener). Doesn't sound something familiar to you? > (Its also a reminder that we need to make sure we test Shindig integration > properly for the release, too) If you succeed to integrate Shindig and Tomcat, please share your findings : OS, Shindig version, Tomcat version. For instance, which version of Shindig and Tomcat are you using now? Thanks! Claude > > On 30 Nov 2010, at 23:24, Claude Coulombe wrote: > >> Greetings floks, >> >> I have problem to run Wookie on a Tomcat servlet container (6.0.29), >> >> I've followed the procedure about running Wookie with Tomcat and MySQL >> (modifying build.properties, creating widgetdb, adding >> mysql-connector-java-5.1.7.jar, etc). So I've got a BUILD SUCCESSFUL >> with ant clean-build deploy-webapp >> >> But when I've started the Tomcat server (catalina.sh run), I've got an >> error (Error listenerStart). >> >> You can check the catalina.out log below : >> >> ----------------------------------------------------------------- >> >> Using CATALINA_BASE: /usr/local/apache-tomcat-6.0.29 >> Using CATALINA_HOME: /usr/local/apache-tomcat-6.0.29 >> Using CATALINA_TMPDIR: /usr/local/apache-tomcat-6.0.29/temp >> Using JRE_HOME: >> /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/home >> Using CLASSPATH: /usr/local/apache-tomcat-6.0.29/bin/bootstrap.jar >> Nov 30, 2010 5:48:43 PM org.apache.catalina.core.AprLifecycleListener init >> SEVERE: An incompatible version 1.1.14 of the APR based Apache Tomcat >> Native library is installed, while Tomcat requires version 1.1.17 >> Nov 30, 2010 5:48:43 PM org.apache.coyote.http11.Http11Protocol init >> INFO: Initializing Coyote HTTP/1.1 on http-8080 >> Nov 30, 2010 5:48:43 PM org.apache.catalina.startup.Catalina load >> INFO: Initialization processed in 931 ms >> Nov 30, 2010 5:48:44 PM org.apache.catalina.core.StandardService start >> INFO: Starting service Catalina >> Nov 30, 2010 5:48:44 PM org.apache.catalina.core.StandardEngine start >> INFO: Starting Servlet Engine: Apache Tomcat/6.0.29 >> Nov 30, 2010 5:48:44 PM org.apache.catalina.startup.HostConfig >> deployDescriptor >> INFO: Deploying configuration descriptor host-manager.xml >> Nov 30, 2010 5:48:44 PM org.apache.catalina.startup.HostConfig >> deployDescriptor >> INFO: Deploying configuration descriptor manager.xml >> Nov 30, 2010 5:48:44 PM org.apache.catalina.startup.HostConfig >> deployDescriptor >> INFO: Deploying configuration descriptor wookie.xml >> INFO [main] (ContextListener.java:76) - Using local widget server >> properties file: >> /usr/local/apache-tomcat-6.0.29/bin/local.widgetserver.properties >> 17:48:45,473 INFO ContextListener:76 - Using local widget server >> properties file: >> /usr/local/apache-tomcat-6.0.29/bin/local.widgetserver.properties >> Nov 30, 2010 5:48:45 PM org.apache.catalina.core.StandardContext start >> SEVERE: Error listenerStart >> Nov 30, 2010 5:48:45 PM org.apache.catalina.core.StandardContext start >> SEVERE: Context [/wookie] startup failed due to previous errors >> Nov 30, 2010 5:48:45 PM org.apache.catalina.loader.WebappClassLoader >> clearReferencesJdbc >> SEVERE: The web application [/wookie] registered the JBDC driver >> [org.apache.derby.jdbc.AutoloadedDriver] but failed to unregister it >> when the web application was stopped. To prevent a memory leak, the >> JDBC Driver has been forcibly unregistered. >> Nov 30, 2010 5:48:46 PM org.apache.catalina.startup.HostConfig deployWAR >> INFO: Deploying web application archive ROOT.war >> Nov 30, 2010 5:48:49 PM >> org.apache.shindig.config.JsonContainerConfigLoader loadContainers >> INFO: Loading resources from: containers/default/container.js >> Nov 30, 2010 5:48:49 PM >> org.apache.shindig.config.JsonContainerConfigLoader loadResources >> INFO: Reading container config: containers/default/container.js >> Nov 30, 2010 5:48:49 PM >> org.apache.shindig.gadgets.features.FeatureRegistry register >> INFO: Loading resources from: res:features-extras/features.txt >> Nov 30, 2010 5:48:49 PM org.apache.shindig.common.xml.XmlUtil <clinit> >> INFO: Not using secure XML processing. >> Nov 30, 2010 5:48:49 PM org.apache.shindig.common.xml.XmlUtil <clinit> >> INFO: Reusing document builders >> Nov 30, 2010 5:48:49 PM >> org.apache.shindig.gadgets.features.FeatureRegistry register >> INFO: Loading resources from: res:features/features.txt >> Nov 30, 2010 5:48:50 PM >> org.apache.shindig.gadgets.servlet.CajaContentRewriter <init> >> INFO: Cajoled cache >> createdorg.apache.shindig.common.cache.ehcache.ehconfiguredca...@468034b6 >> Nov 30, 2010 5:48:50 PM >> org.apache.shindig.gadgets.servlet.CajaContentRewriter <init> >> INFO: Cajoled cache >> createdorg.apache.shindig.common.cache.ehcache.ehconfiguredca...@468034b6 >> Nov 30, 2010 5:48:50 PM >> org.apache.shindig.gadgets.oauth.OAuthModule$OAuthStoreProvider >> loadDefaultKey >> WARNING: Couldn't load OAuth signing key. To create a key, run: >> openssl req -newkey rsa:1024 -days 365 -nodes -x509 -keyout testkey.pem \ >> -out testkey.pem -subj '/CN=mytestkey' >> openssl pkcs8 -in testkey.pem -out oauthkey.pem -topk8 -nocrypt -outform >> PEM >> >> Then edit shindig.properties and add these lines: >> shindig.signing.key-file=<path-to-oauthkey.pem> >> shindig.signing.key-name=mykey >> >> Nov 30, 2010 5:48:50 PM >> org.apache.shindig.gadgets.oauth.OAuthModule$OAuthCrypterProvider >> <init> >> INFO: Using random key for OAuth client-side state encryption >> Nov 30, 2010 5:48:50 PM >> org.apache.shiro.config.IniSecurityManagerFactory isAutoApplyRealms >> INFO: Realms have been explicitly set on the SecurityManager instance >> - auto-setting of realms will not occur. >> Nov 30, 2010 5:48:50 PM org.apache.shiro.realm.AuthorizingRealm >> getAuthorizationCacheLazy >> INFO: No cache or cacheManager properties have been set. >> Authorization cache cannot be obtained. >> Nov 30, 2010 5:48:50 PM org.apache.catalina.startup.HostConfig >> deployDirectory >> INFO: Deploying web application directory docs >> Nov 30, 2010 5:48:51 PM org.apache.catalina.startup.HostConfig >> deployDirectory >> INFO: Deploying web application directory examples >> Nov 30, 2010 5:48:51 PM org.apache.catalina.startup.HostConfig >> deployDirectory >> INFO: Deploying web application directory ROOT-old >> Nov 30, 2010 5:48:51 PM org.apache.coyote.http11.Http11Protocol start >> INFO: Starting Coyote HTTP/1.1 on http-8080 >> Nov 30, 2010 5:48:51 PM org.apache.jk.common.ChannelSocket init >> INFO: JK: ajp13 listening on /0.0.0.0:8009 >> Nov 30, 2010 5:48:51 PM org.apache.jk.server.JkMain start >> INFO: Jk running ID=0 time=0/87 config=null >> Nov 30, 2010 5:48:51 PM org.apache.catalina.startup.Catalina start >> INFO: Server startup in 7529 ms >> >> ----------------------------------------------------------------- >> >> So I've suspected that the problem was related to the version of the >> APR (Apache Portable Runtime) but I'm not sure because I think APR >> more an issue for performance than a show stopper. >> >> Anyway, I've downloaded APR and compiled it, but I still did not find >> where to put the libraries in order to stop the APR incompability >> message. I just don't know where Tomcat has gotten the version 1.1.14 >> of the APR (apache portable runtime) ??? Maybe I can downgrade to >> Tomcat 5.5 but Shindig 2 seems not working with that version of Tomcat. >> >> Just for your info, I'm developping on Mac OS X 10.6.4 >> >> Any help is welcome! >> >> Claude Coulombe >> Université de Montréal > >
