Dave wrote:
On 9/17/07, Matt Raible <[EMAIL PROTECTED]> wrote:
Any idea *why* it's trying to use JNDI?
I bet Roller can't find it's roller-custom.properties file.
There should be an INFO level message about that somewhere in the logs
like this:
"Roller Weblogger: Successfully loaded custom properties file from classpath"
Dave, If I am not mistaken the "found (or not found) custom properties"
message is a system.out message and not a log message.
regards
Peter Petersson
Or this: "Roller Weblogger: No custom properties file found in classpath"
You sure that TOMCAT/lib is the right place for it?
I can't remember if that's where I put it when I tried TC6.
- Dave
On 9/17/07, Matt Raible <[EMAIL PROTECTED]> wrote:
You mean this?
INFO 2007-09-17 16:33:56,063 DatabaseProvider:successMessage -
SUCCESS: Got parameters. Using configuration type JNDI_NAME
INFO 2007-09-17 16:33:56,066 DatabaseProvider:successMessage - --
Using JNDI datasource name: java:comp/env/jdbc/rollerdb
INFO 2007-09-17 16:33:56,068 DatabaseProvider:successMessage -
SUCCESS: located JNDI DataSource [java:comp/env/jdbc/rollerdb]
ERROR 2007-09-17 16:33:56,073 DatabaseProvider:errorMessage - ERROR:
unable to obtain database connection. Likely problem: bad connection
parameters or database unavailable.
FATAL 2007-09-17 16:33:56,080 RollerContext:contextInitialized -
Roller Weblogger startup failed during app preparation
org.apache.roller.weblogger.business.startup.StartupException: ERROR:
unable to obtain database connection. Likely problem: bad connection
parameters or database unavailable.
at
org.apache.roller.weblogger.business.DatabaseProvider.<init>(DatabaseProvider.java:148)
at
org.apache.roller.weblogger.business.startup.WebloggerStartup.prepare(WebloggerStartup.java:171)
at
org.apache.roller.weblogger.ui.core.RollerContext.contextInitialized(RollerContext.java:138)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4334)
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:525)
at
org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:920)
at
org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:883)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at
org.apache.catalina.core.StandardService.start(StandardService.java:516)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:566)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
--- ROOT CAUSE ---
org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create JDBC
driver of class '' for connect URL 'null'
at
org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1150)
at
org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
at
org.apache.roller.weblogger.business.DatabaseProvider.getConnection(DatabaseProvider.java:179)
at
org.apache.roller.weblogger.business.DatabaseProvider.<init>(DatabaseProvider.java:141)
at
org.apache.roller.weblogger.business.startup.WebloggerStartup.prepare(WebloggerStartup.java:171)
at
org.apache.roller.weblogger.ui.core.RollerContext.contextInitialized(RollerContext.java:138)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4334)
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:525)
at
org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:920)
at
org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:883)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at
org.apache.catalina.core.StandardService.start(StandardService.java:516)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:566)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: java.sql.SQLException: No suitable driver
at java.sql.DriverManager.getDriver(DriverManager.java:243)
at
org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1143)
... 29 more
WARN 2007-09-17 16:33:56,582 Settings:getLocale - Settings: Could not
parse struts.locale setting, substituting default VM locale
On 9/17/07, Dave <[EMAIL PROTECTED]> wrote:
I did try 4.0 on Tomcat 6.0 a while back. Is there anything else in
the logs? There should be some message early on when Roller tries to
bootstrap itself.
- Dave
On 9/17/07, Matt Raible <[EMAIL PROTECTED]> wrote:
OK, I created a roller-custom.properties in $CATALINA_HOME/lib:
installation.type=auto
database.configurationType=jdbc
database.jdbc.driverClass=com.mysql.jdbc.Driver
database.jdbc.connectionURL=jdbc:mysql://localhost:3306/roller
database.jdbc.username=root
database.jdbc.password=
mail.configurationType=properties
mail.hostName=localhost
The MySQL Driver, activation.jar and mail.jar are all in this same directory.
Here's the stack trace:
WARN 2007-09-17 15:33:53,696 WebloggerRuntimeConfig:getProperty -
Trouble accessing property: site.frontpage.weblog.handle
java.lang.IllegalStateException: Roller Weblogger has not been bootstrapped yet
at
org.apache.roller.weblogger.business.WebloggerFactory.getWeblogger(WebloggerFactory.java:60)
at
org.apache.roller.weblogger.config.WebloggerRuntimeConfig.getProperty(WebloggerRuntimeConfig.java:66)
at org.apache.jsp.index_jsp._jspService(index_jsp.java:55)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:393)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
Have you tested 4.x with Tomcat 6? If not, what version have you
tested it on? I'm more keen on getting it up and running than getting
it running on Tomcat 6.
Matt
On 9/17/07, Dave <[EMAIL PROTECTED]> wrote:
You should definitely read the install guide. It has been totally
rewritten. We've got a five minute install now that needs only one
properties file and can create/upgrade tables automatically.
- Dave
On 9/17/07, Matt Raible <[EMAIL PROTECTED]> wrote:
I tried dropping the database altogether and starting with a clean
database. This gives me the following error. Maybe I need to read the
install guide? ;-)
--
http://raibledesigns.com
--
http://raibledesigns.com
--
http://raibledesigns.com
