mirror of
https://github.com/alanorth/cgspace-notes.git
synced 2025-01-27 05:49:12 +01:00
Update notes for 2017-12-19
This commit is contained in:
@ -417,3 +417,116 @@ $ schedtool -D -e ionice -c2 -n7 nice -n19 dspace index-discovery
|
||||
```
|
||||
|
||||
- I don't have time now to look into this but the Solr sharding has long been an issue!
|
||||
- Looking into using JDBC / JNDI to provide a database pool to DSpace
|
||||
- The [DSpace 6.x configuration docs](https://wiki.duraspace.org/display/DSDOC6x/Configuration+Reference) have more notes about setting up the database pool than the 5.x ones (which actually have none!)
|
||||
- First, I uncomment `db.jndi` in _dspace/config/dspace.cfg_
|
||||
- Then I create a global `Resource` in the main Tomcat _server.xml_ (inside `GlobalNamingResources`):
|
||||
|
||||
```
|
||||
<Resource name="jdbc/dspace" auth="Container" type="javax.sql.DataSource"
|
||||
driverClassName="org.postgresql.Driver"
|
||||
url="jdbc:postgresql://localhost:5432/dspace"
|
||||
username="dspace"
|
||||
password="dspace"
|
||||
initialSize='5'
|
||||
maxActive='50'
|
||||
maxIdle='15'
|
||||
minIdle='5'
|
||||
maxWait='5000'
|
||||
validationQuery='SELECT 1'
|
||||
testOnBorrow='true' />
|
||||
```
|
||||
|
||||
- Most of the parameters are from comments by Mark Wood about his JNDI setup: https://jira.duraspace.org/browse/DS-3564
|
||||
- Then I add a `ResourceLink` to each web application context:
|
||||
|
||||
```
|
||||
<ResourceLink global="jdbc/dspace" name="jdbc/dspace" type="javax.sql.DataSource"/>
|
||||
```
|
||||
|
||||
- I am not sure why several guides show configuration snippets for _server.xml_ and web application contexts that use a Local and Global jdbc...
|
||||
- When DSpace can't find the JNDI context (for whatever reason) you will see this in the dspace logs:
|
||||
|
||||
```
|
||||
2017-12-19 13:12:08,796 ERROR org.dspace.storage.rdbms.DatabaseManager @ Error retrieving JNDI context: jdbc/dspace
|
||||
javax.naming.NameNotFoundException: Name [jdbc/dspace] is not bound in this Context. Unable to find [jdbc].
|
||||
at org.apache.naming.NamingContext.lookup(NamingContext.java:825)
|
||||
at org.apache.naming.NamingContext.lookup(NamingContext.java:173)
|
||||
at org.dspace.storage.rdbms.DatabaseManager.initDataSource(DatabaseManager.java:1414)
|
||||
at org.dspace.storage.rdbms.DatabaseManager.initialize(DatabaseManager.java:1331)
|
||||
at org.dspace.storage.rdbms.DatabaseManager.getDataSource(DatabaseManager.java:648)
|
||||
at org.dspace.storage.rdbms.DatabaseManager.getConnection(DatabaseManager.java:627)
|
||||
at org.dspace.core.Context.init(Context.java:121)
|
||||
at org.dspace.core.Context.<init>(Context.java:95)
|
||||
at org.dspace.app.util.AbstractDSpaceWebapp.register(AbstractDSpaceWebapp.java:79)
|
||||
at org.dspace.app.util.DSpaceContextListener.contextInitialized(DSpaceContextListener.java:128)
|
||||
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5110)
|
||||
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5633)
|
||||
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
|
||||
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:1015)
|
||||
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:991)
|
||||
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652)
|
||||
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:712)
|
||||
at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:2002)
|
||||
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
|
||||
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
|
||||
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
|
||||
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
|
||||
at java.lang.Thread.run(Thread.java:748)
|
||||
2017-12-19 13:12:08,798 INFO org.dspace.storage.rdbms.DatabaseManager @ Unable to locate JNDI dataSource: jdbc/dspace
|
||||
2017-12-19 13:12:08,798 INFO org.dspace.storage.rdbms.DatabaseManager @ Falling back to creating own Database pool
|
||||
```
|
||||
|
||||
- And indeed the Catalina logs show that it failed to set up the JDBC driver:
|
||||
|
||||
```
|
||||
org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot load JDBC driver class 'org.postgresql.Driver'
|
||||
```
|
||||
|
||||
- There are several copies of the PostgreSQL driver installed by DSpace:
|
||||
|
||||
```
|
||||
$ find ~/dspace/ -iname "postgresql*jdbc*.jar"
|
||||
/Users/aorth/dspace/webapps/jspui/WEB-INF/lib/postgresql-9.1-901-1.jdbc4.jar
|
||||
/Users/aorth/dspace/webapps/oai/WEB-INF/lib/postgresql-9.1-901-1.jdbc4.jar
|
||||
/Users/aorth/dspace/webapps/xmlui/WEB-INF/lib/postgresql-9.1-901-1.jdbc4.jar
|
||||
/Users/aorth/dspace/webapps/rest/WEB-INF/lib/postgresql-9.1-901-1.jdbc4.jar
|
||||
/Users/aorth/dspace/lib/postgresql-9.1-901-1.jdbc4.jar
|
||||
```
|
||||
|
||||
- These apparently come from the main DSpace `pom.xml`:
|
||||
|
||||
```
|
||||
<dependency>
|
||||
<groupId>postgresql</groupId>
|
||||
<artifactId>postgresql</artifactId>
|
||||
<version>9.1-901-1.jdbc4</version>
|
||||
</dependency>
|
||||
```
|
||||
|
||||
- So WTF? Let's try copying one to Tomcat's lib folder and restarting Tomcat:
|
||||
|
||||
```
|
||||
$ cp ~/dspace/lib/postgresql-9.1-901-1.jdbc4.jar /usr/local/opt/tomcat@7/libexec/lib
|
||||
```
|
||||
|
||||
- Oh that's fantastic, now at least Tomcat doesn't print an error during startup so I guess it succeeds to create the JNDI pool
|
||||
- DSpace starts up but I have no idea if it's using the JNDI configuration because I see this in the logs:
|
||||
|
||||
```
|
||||
2017-12-19 13:26:54,271 INFO org.dspace.storage.rdbms.DatabaseManager @ DBMS is '{}'PostgreSQL
|
||||
2017-12-19 13:26:54,277 INFO org.dspace.storage.rdbms.DatabaseManager @ DBMS driver version is '{}'9.5.10
|
||||
2017-12-19 13:26:54,293 INFO org.dspace.storage.rdbms.DatabaseUtils @ Loading Flyway DB migrations from: filesystem:/Users/aorth/dspace/etc/postgres, classpath:org.dspace.storage.rdbms.sqlmigration.postgres, classpath:org.dspace.storage.rdbms.migration
|
||||
2017-12-19 13:26:54,306 INFO org.flywaydb.core.internal.dbsupport.DbSupportFactory @ Database: jdbc:postgresql://localhost:5432/dspacetest (PostgreSQL 9.5)
|
||||
```
|
||||
|
||||
- Let's try again, but this time explicitly blank the PostgreSQL connection parameters in dspace.cfg and see if DSpace starts...
|
||||
- Wow, ok, that works, but having to copy the PostgreSQL JDBC JAR to Tomcat's lib folder totally blows
|
||||
- Also, it's likely this is only a problem on my local macOS + Tomcat test environment
|
||||
- Ubuntu's Tomcat distribution will probably handle this differently
|
||||
- So for reference I have:
|
||||
- a `<Resource>` defined globally in server.xml
|
||||
- a `<ResourceLink>` defined in each web application's context XML
|
||||
- unset the `db.url`, `db.username`, and `db.password` parameters in dspace.cfg
|
||||
- set the `db.jndi` in dspace.cfg to the name specified in the web application context
|
||||
|
||||
|
||||
Reference in New Issue
Block a user