Deployment Issue

28 views
Skip to first unread message

Nikkie m

unread,
Apr 23, 2020, 6:12:23 PM4/23/20
to OpenOlat
Hello Dear,

I am new to this platform. When i am trying to connect the application to heroku postgress instance, I am getting following error in my eclipse console :

SEVERE: Exception sending context initialized event to listener instance of class [org.springframework.web.context.ContextLoaderListener]
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'baseSecurityManager': Unsatisfied dependency expressed through field 'dbInstance'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'databaseUpgrader' defined in class path resource [org/olat/upgrade/_spring/databaseUpgradeContext.xml]: Cannot resolve reference to bean 'postgresql_jndi_DataSource' while setting bean property 'dataSource'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'postgresql_jndi_DataSource' defined in class path resource 

I have attached my properties files please have a look into it.

If you could help me with heroku db instance connection and heroku deployment then that would be great. Kindly help me out with this.

Regards,

Nikkie M
olat.local.properties
olat.properties

Stéphane Rossé

unread,
Apr 24, 2020, 12:14:12 AM4/24/20
to OpenOlat
Hello

In your olat.local.properties configuration you specify "db.source=jndi". This means that your database credentials are in a resource in Tomcat. Change this setting to "db.source=local" and OpenOlat will use its internal database connection pool with the credentials you specified in olat.local.properties

Best regards
Stéphane

Nikkie m

unread,
Apr 24, 2020, 2:59:34 AM4/24/20
to OpenOlat
Dear Stéphane,

Thank you so much for your response.

After changing "db.source= local", I am still facing similar issue. Getting following exception.

SEVERE: Exception sending context initialized event to listener instance of class [org.springframework.web.context.ContextLoaderListener]
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'baseSecurityManager': Unsatisfied dependency expressed through field 'dbInstance'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'databaseUpgrader' defined in class path resource [org/olat/upgrade/_spring/databaseUpgradeContext.xml]: Cannot resolve reference to bean 'postgresql_jndi_DataSource' while setting bean property 'dataSource'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'postgresql_jndi_DataSource' defined in class path resource [org/olat/core/commons/persistence/_spring/databaseCorecontext.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: Name [easylist] is not bound in this Context. Unable to find [easylist].
Related cause: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mysql_jndi_DataSource' defined in class path resource [org/olat/core/commons/persistence/_spring/databaseCorecontext.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: Name [easylist] is not bound in this Context. Unable to find [easylist].
Related cause: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'postgresql_jndi_DataSource' defined in class path resource [org/olat/core/commons/persistence/_spring/databaseCorecontext.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: Name [easylist] is not bound in this Context. Unable to find [easylist].
Related cause: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'oracle_jndi_DataSource' defined in class path resource [org/olat/core/commons/persistence/_spring/databaseCorecontext.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: Name [easylist] is not bound in this Context. Unable to find [easylist].

My local db name was easylist but i am not using it anymore and i have also remove local db configuration from properties file but still getting NameNotFoundException for 'easylist'.

Here is my tomacat server.xml configuaration

<Context docBase="openolat-lms" path="/openolat-lms"
reloadable="false" source="org.eclipse.jst.jee.server:openolat-lms">
<Resource auth="Container"
driverClassName="org.postgresql.Driver"
type="javax.sql.DataSource" maxIdle="4" maxTotal="16"
maxWaitMillis="-1" name="jdbc/d840ru9019d0cj"
username="xqvwhlbepabkpo"
password="496cbe5854fde67b47de3525d3780ac32553f045bdf795a5f0921c311d5cb1c2"
testOnBorrow="true" testOnReturn="false"
validationQuery="SELECT 1" validationQueryTimeout="-1" />


</Context>

I have also attached properties files . Kindly help me out with this issue.

Regards,

Nikkie M
olat.local.properties
olat.properties

Florian Gnägi

unread,
Apr 24, 2020, 3:26:55 AM4/24/20
to open...@googlegroups.com
Hi Nikkie

I hope the posting below was not copy paste from your production! If yes, I suggest you immediately change your passwords at AWS and reset all the databases that are accessible with those credentials!

Cheers
Florian

--
--
Sie erhalten diese Nachricht, weil Sie Mitglied sind von Google
Groups-Gruppe "OpenOlat".
Für das Erstellen von Beiträgen in dieser Gruppe senden Sie eine E-Mail
an open...@googlegroups.com
Um sich von dieser Gruppe abzumelden, senden Sie eine E-Mail an
openolat+u...@googlegroups.com
Weitere Optionen finden Sie in dieser Gruppe unter
http://groups.google.com/group/openolat?hl=de
-------------------------------------------------------------------------------------------------------------------
OpenOlat - infinite learning - http://www.openolat.org
---
You received this message because you are subscribed to the Google Groups "OpenOlat" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openolat+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openolat/7e96c4ea-c0d8-4506-939d-a1c97de94f72%40googlegroups.com.
<olat.local.properties><olat.properties>

--------------------------------------------------------------------
professional services for the e-learning system OpenOlat
hosting - operating - support - development - mobile - consulting
--------------------------------------------------------------------
frentix  GmbH
Florian Gnägi, Geschäftsführer
Okenstrasse 6
CH-8037 Zürich, Switzerland


Find me on wire skype twitter xing linkedin 
--------------------------------------------------------------------

Nikkie m

unread,
Apr 24, 2020, 3:30:02 AM4/24/20
to OpenOlat
Hi Florian,

Thank you for your concern, Its not actual url and password. Please help me with my issue.

Regards,
Nikkie m

On Friday, April 24, 2020 at 12:56:55 PM UTC+5:30, Florian Gnägi wrote:
Hi Nikkie

I hope the posting below was not copy paste from your production! If yes, I suggest you immediately change your passwords at AWS and reset all the databases that are accessible with those credentials!

Cheers
Florian


Weitere Optionen finden Sie in dieser Gruppe unter
http://groups.google.com/group/openolat?hl=de
-------------------------------------------------------------------------------------------------------------------
OpenOlat - infinite learning - http://www.openolat.org
---
You received this message because you are subscribed to the Google Groups "OpenOlat" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openolat/7e96c4ea-c0d8-4506-939d-a1c97de94f72%40googlegroups.com.
<olat.local.properties><olat.properties>

Stéphane Rossé

unread,
Apr 24, 2020, 3:38:42 AM4/24/20
to OpenOlat
Hi

Do you have still db.jndi=.....easylist somewhere. The error says that. Check that you don't have db.jndi defined twice in your olat.local.properties, or that you use the right olat.local.properties.

Best regards
Stéphane
Reply all
Reply to author
Forward
0 new messages