Evening folks Re: the missing wookie.xml file - when I ploughed through an install of Tomcat, MySQL and Wookie about a year ago one particular gotcha that caught me out was that I was running all the Ant procedures as a user without write access credentials to the Tomcat areas where files got deployed. Late night sessions led to school boy errors where I redid everything as ROOT, so stuff got copied over, but then wasn't picked up by Tomcat properly because it didn't have credentials to use the files. All sorted in the end by doing the Ant stuff as ROOT and then chowning the files to whatever user your distro sets Tomcat up with. I think this cured a number of missing files in my installation.
Best Steve Nisbet Learning Resources Manager | LRT | http://lrt.mmu.ac.uk | LRIS | MMU | 0161 247 6753 > -----Original Message----- > From: Scott Wilson [mailto:[email protected]] > Sent: 01 December 2010 19:04 > To: Claude Coulombe > Cc: [email protected] > Subject: Re: Problem running Wookie on Tomcat > > > On 1 Dec 2010, at 18:56, Claude Coulombe wrote: > > > Hi Scott, > > > > Maybe it could help to know that the problem is there with Tomcat 5.5 too. > > > > Claude > > I just got it working on mine by following the instructions, using: > > Tomcat 6.0.20 > Latest wookie build from source > MySQL 5.0.45 > > However, I had to also copy the <Resource> definition in "wookie.xml" file in > /conf into /conf/context.xml as it didn't seem to pick it up automatically. I > think Tomcat 7 doesn't have that problem? > > > > > 2010/12/1 Claude Coulombe <[email protected]>: > >> Hi Scott, > >> > >>> Actually it does. > >>> > >>> Have you looked in your server log as well as catalina.out? > >>> > >>> When I just tried to replicate it on Tomcat 6.0.20, I got the same error > >>> in > catalina.out, plus this in my localhost log: > >>> > >>> <openjpa-2.0.0-r422266:935683 fatal store error> > org.apache.openjpa.util.StoreException: Cannot create JDBC driver of class '' > for connect URL 'null' > >>> > >>> ... which is a JPA configuration issue. > >>> > >>> I think Paul and Kris have been testing on Tomcat - have you come across > something similar? > >> > >> > >> Yes, I have error messages related to persistance in the localhost log > >> > >> Maybe, the database was not correctly initialized... > >> > >> Caused by: java.lang.reflect.InvocationTargetException > >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > >> at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j > ava:39) > >> at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > >> at java.lang.reflect.Method.invoke(Method.java:597) > >> at > org.apache.wookie.beans.util.PersistenceManagerFactory.initialize(Persiste > nceManagerFactory.java:70) > >> ... 25 more > >> Caused by: java.lang.RuntimeException: Unable to initialize: > >> java.lang.IllegalArgumentException: Unsupported database type: > >> at > org.apache.wookie.beans.jpa.JPAPersistenceManager.initialize(JPAPersisten > ceManager.java:276) > >> ... 30 more > >> Caused by: java.lang.IllegalArgumentException: Unsupported database > type: > >> at > org.apache.wookie.beans.jpa.JPAPersistenceManager.initialize(JPAPersisten > ceManager.java:201) > >> ... 30 more > >> 1 d?c. 2010 13:25:35 org.apache.catalina.core.StandardContext > listenerStop > >> GRAVE: Exception lors de l'envoi de l'?v?nement contexte d?truit > >> (context destroyed) ? l'instance de classe d'?coute > >> org.apache.wookie.server.ContextListener > >> java.lang.RuntimeException: PersistenceManagerFactory not initialized > >> at > org.apache.wookie.beans.util.PersistenceManagerFactory.terminate(Persist > enceManagerFactory.java:350) > >> at > org.apache.wookie.server.ContextListener.contextDestroyed(ContextListen > er.java:262) > >> at > org.apache.catalina.core.StandardContext.listenerStop(StandardContext.jav > a:4174) > >> at > org.apache.catalina.core.StandardContext.stop(StandardContext.java:4778) > >> at > org.apache.catalina.core.StandardContext.start(StandardContext.java:4675) > >> at > org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java > :791) > >> at > org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) > >> at > org.apache.catalina.core.StandardHost.addChild(StandardHost.java:546) > >> at > org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:63 > 7) > >> at > org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:5 > 63) > >> at > org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:498) > >> at > >> org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277) > >> at > org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:321) > >> at > org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport. > java:119) > >> at > org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) > >> at > >> org.apache.catalina.core.StandardHost.start(StandardHost.java:785) > >> at > org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) > >> at > org.apache.catalina.core.StandardEngine.start(StandardEngine.java:445) > >> at > org.apache.catalina.core.StandardService.start(StandardService.java:519) > >> at > org.apache.catalina.core.StandardServer.start(StandardServer.java:710) > >> at org.apache.catalina.startup.Catalina.start(Catalina.java:581) > >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > >> at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j > ava:39) > >> at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > >> at java.lang.reflect.Method.invoke(Method.java:597) > >> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) > >> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) > >>> > >> > >> Thanks > >> > >> Claude > >> > >> > >> > >>>> > >>>> > >>>>> (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...@46 > 8034b6 > >>>>>> Nov 30, 2010 5:48:50 PM > >>>>>> org.apache.shindig.gadgets.servlet.CajaContentRewriter <init> > >>>>>> INFO: Cajoled cache > >>>>>> > createdorg.apache.shindig.common.cache.ehcache.ehconfiguredca...@46 > 8034b6 > >>>>>> 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 > >>>>> > >>>>> > >>> > >>> > >> "Before acting on this email or opening any attachments you should read the Manchester Metropolitan University email disclaimer available on its website http://www.mmu.ac.uk/emaildisclaimer "
