On Dec 7, 2007 6:04 PM, ries van Twisk <[EMAIL PROTECTED]> wrote:
> Hey Guys,
>
> I get the below error when I enabled  planet.
> it looks like that planet want's to connect to a different JNDI then
> specified in my roller-custom.properties.
> If so, shall I create one to get it rolling?

Hmm... looks like a documentation bug.

Try this:

Create a planet-custom.properties file in the same directory as your
roller-custom.properties file. Copy the very same database connection
parameters that are in your roller-custom.properties file into
planet-custom.properties.

Does it work for you now?

- Dave



> INFO  2007-12-07 23:47:48,070 DatabaseProvider:successMessage -
> SUCCESS: Got parameters. Using configuration type JNDI_NAME
> INFO  2007-12-07 23:47:48,070 DatabaseProvider:successMessage - --
> Using JNDI datasource name: java:comp/env/jdbc/rollerdb
> INFO  2007-12-07 23:47:48,072 DatabaseProvider:successMessage -
> SUCCESS: located JNDI DataSource [java:comp/env/jdbc/rollerdb]
> ERROR 2007-12-07 23:47:48,074 DatabaseProvider:errorMessage - ERROR:
> unable to obtain database connection. Likely problem: bad connection
> parameters or database unavailable.
> FATAL 2007-12-07 23:47:48,077 RollerContext:contextInitialized -
> Roller Planet startup failed during app preparation
> org.apache.roller.planet.business.startup.StartupException: ERROR:
> unable to obtain database connection. Likely problem: bad connection
> parameters or database unavailable.
>          at
> org
> .apache
> .roller.planet.business.DatabaseProvider.<init>(DatabaseProvider.java:
> 147)
>          at
> org
> .apache
> .roller
> .planet.business.startup.PlanetStartup.prepare(PlanetStartup.java:86)
>          at
> org
> .apache
> .roller
> .weblogger.ui.core.RollerContext.contextInitialized(RollerContext.java:
> 173)
>          at
> org
> .apache
> .catalina.core.StandardContext.listenerStart(StandardContext.java:3830)
>          at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:
> 4337)
>          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:597)
>          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'
>
>
>
>
>
>

Reply via email to