Hi Boris, your configuration below looks good, Roller is acting like it
isn't detecting your roller-custom.properties file because those are the
JNDI defaults defined in roller.properties. For tomcat, the
roller-custom.properties needs to be in the $CATALINA_HOME/lib folder.
Currently, this is in roller.properties:
# For database configuration type 'jndi',this will be used.
# If it does not start 'java:' then 'java:comp/env/' will be prepended
database.jndi.name=jdbc/rollerdb
Could you put database.jndi.name=jdbc/xyz
in your roller-custom.properties and see if the SUCCESS message below:
SUCCESS: located JNDI DataSource [java:comp/env/jdbc/rollerdb] now will
say "java:comp/env/jdbc/xyz"? I want to determine if Roller is reading
your customization file.
BTW, sorry but an ugly bug fixed in Roller 5.1.1-SNAPSHOT today:
http://rollerweblogger.org/project/entry/roller-5-1-smartphones-tablets,
you might wish to build the tagged release linked to in that blog
article and deploy that instead.
Glen
On 09/02/2014 05:49 PM, Boris wrote:
Hi!
Where Roller gets jndi connection, if in roller-custom.properties file is
jdbc connection?
database.configurationType=jdbc
database.jdbc.driverClass=com.mysql.jdbc.Driver
database.jdbc.connectionURL=jdbc:mysql://
teldomdbinstance.catzggttyu5l.eu-west-1.rds.amazonaws.com:3306/rollerdb?autoReconnect=true&useUnicode=true&characterEncoding=utf-8&mysqlEncoding=utf8
database.jdbc.username=scott
INFO 2014-09-02 08:33:56,374 DatabaseProvider:successMessage - -- Using
JNDI datasource name: java:comp/env/jdbc/rollerdb
INFO 2014-09-02 08:33:56,376 DatabaseProvider:successMessage - SUCCESS:
located JNDI DataSource [java:comp/env/jdbc/rollerdb]
ERROR 2014-09-02 08:33:56,379 DatabaseProvider:errorMessage - ERROR: unable
to obtain database connection. Likely problem: bad connection parameters or
database unavailable.
FATAL 2014-09-02 08:33:56,381 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.
Boris
[image: Facebook] <http://www.facebook.com/borismil> [image: Twitter]
<http://www.twitter.com/borismi>
