Sorry, forgot to mention, logs do show that the DataSource is being found in JNDI, so maybe my hypothesis doesn't hold any water after all:
INFO 2012-08-22 08:53:27,492 DatabaseProvider:successMessage - SUCCESS: Got parameters. Using configuration type JNDI_NAME INFO 2012-08-22 08:53:27,493 DatabaseProvider:successMessage - -- Using JNDI datasource name: java:comp/env/jdbc/rollerdb INFO 2012-08-22 08:53:27,494 DatabaseProvider:successMessage - SUCCESS: located JNDI DataSource [java:comp/env/jdbc/rollerdb] INFO 2012-08-22 08:53:27,494 JPAPersistenceStrategy:<init> - hibernate.transaction.manager_lookup_class: org.hibernate.transaction.JBossTransactionManagerLookup INFO 2012-08-22 08:53:27,494 JPAPersistenceStrategy:<init> - hibernate.transaction.factory_class: org.hibernate.transaction.JTATransactionFactory Checked the connection properties from Context.xml and can connect fine manually too. Any further ideas? Cheers, Edd On 22 August 2012 16:51, Edd Grant <[email protected]> wrote: > Thanks Dave, > > Interesting. I'm not entirely sure as to whether I have a working Database > connection. On the one hand the roller tables are being created correctly, > however when I then try and complete the installation I get the following > JPA error: > > A JDBC Driver or DataSource class name must be specified in the > ConnectionDriverName property. > > > I noticed that Matt also had this error ( > http://raibledesigns.com/rd/entry/upgraded_to_apache_roller_5) however > his fix didn't work for me, perhaps as I'm using a JNDI bound Datasource > whereas he wasn't. > > Does table creation use a different connection mechanism to normal app > usage? If so then perhaps my DataSource isn't correctly registered in JNDI. > I think there's a way to check that in the Tomcat manager so I will try > that. Does that sound like a reasonable first step? > > Cheers, > > Edd > > > On 22 August 2012 16:41, Dave <[email protected]> wrote: > >> On Tue, Aug 21, 2012 at 8:14 AM, Edd Grant <[email protected]> wrote: >> > I'm performing a fresh install of Roller 5.0.1 on 32 bit Ubuntu, using >> > OpenJDK 1.6.0_24, MySQL5 and Tomcat 6. Deployment of the app seems to >> work >> > fine but when I call http://<servername>/roller I see the following >> error >> > in the logs: >> > >> > ERROR 2012-08-21 05:04:58,309 LoadSaltFilter:doFilter - Error loading >> salt >> > java.lang.IllegalStateException: Roller Weblogger has not been >> bootstrapped >> > yet >> > at >> > >> org.apache.roller.weblogger.business.WebloggerFactory.getWeblogger(WebloggerFactory.java:60) >> > >> > Interestingly the browser *does *serve me the installation configuration >> > page, should I be concerned about the salt exception? Any ideas what >> might >> > cause it? From the code it seems that the *webloggerProvider* in * >> > WebloggerFactory* must be null but I can't quite see why that would be >> the >> > case. >> >> I suspect there is some sort of database configuration error that is >> preventing Roller from starting up. Do you see anything in the logs >> that confirms you have a good database connection? >> >> - Dave >> > > > > -- > Web: http://www.eddgrant.com > Email: [email protected] > Mobile: +44 (0) 7861 394 543 > > > -- Web: http://www.eddgrant.com Email: [email protected] Mobile: +44 (0) 7861 394 543
