Date: Fri, 29 Mar 2024 11:12:04 -0400 (EDT) Message-ID: <558318297.237.1711725124051@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_236_1717877673.1711725124050" ------=_Part_236_1717877673.1711725124050 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Since some users might want to get their test version up and running as = fast as possible, offered below is an unsupported outline of getti= ng DSpace to run quickly in a Unix-based environment.
Only experienced unix admins should even attempt the following without g= oing to the detailed Ins= tallation Instructions
useradd= -m dspace gunzip -c dspace-1.x-src-release.tar.gz | tar -xf - createuser -U postgres -d -A -P dspace createdb -U dspace -E UNICODE dspace cd [dspace-source]/dspace/config vi dspace.cfg mkdir [dspace] chown dspace [dspace] su - dspace cd [dspace-source]/dspace mvn package cd [dspace-source]/dspace/target/dspace-<version>-build.dir ant fresh_install cp -r [dspace]/webapps/* [tomcat]/webapps /etc/init.d/tomcat start [dspace]/bin/dspace create-administrator
The list below describes the third-party components and tools you'll nee= d to run a DSpace server. These are just guidelines. Since DSpace is built = on open source, standards-based tools, there are numerous other possibiliti= es and setups.
Also, please note that the configuration and installation guidelines rel= ating to a particular tool below are here for convenience. You should refer= to the documentation for each individual component for complete and up-to-= date details. Many of the tools are updated on a frequent basis, and the gu= idelines below may become out of date.
DSpace now requires Oracle Java 6 or greater because of= usage of new language capabilities introduced in 5 and 6 that make coding = easier and cleaner.
Java can be downloaded from the following location: http://java.sun.com/javase/downloads/index.jsp
Only Oracle's Java has been tested with each release and is known to wor= k correctly. Other flavors of Java may pose problems.
Known issue with Maven 2.0.x and Maven= 3.x and DSpace 1.7.x
DSpace 1.7.x does not build properly when using Maven 2.0.x or Maven 3.x= . This is a known issue. The quick fix is to use Maven 2.2.x. More information on this issue can be found in the following JIRA issue= : DS-788.
Maven is necessary in the first stage of the build process to assemble t= he installation package for your DSpace instance. It gives you the flexibil= ity to customize DSpace using the existing Maven projects found in the = [dspace-source]/dspace/modules directory or by adding in your own Mave= n project to build the installation package for DSpace, and apply any custo= m interface "overlay" changes.
Maven can be downloaded from the following location: htt= p://maven.apache.org/download.html
You can configure a proxy to use for some or all of your HTTP requests i=
n Maven 2.0. The username and password are only required if your proxy requ=
ires basic authentication (note that later releases may support storing you=
r passwords in a secured keystore=E2=80=9A in the mean time, please ensure =
your settings.xml file (usually ${user.home}/.m2/settings.xml<=
/em>) is secured with permissions appropriate for your operating system).=
p>
Example: Apache Ant is still required for the second stage of the build process. =
It is used once the installation package has been constructed in [dspac=
e-source]/dspace/target/dspace-<version>-build.dir and still use=
s some of the familiar ant build targets found in the 1.4.x build process.<=
/p>
Ant can be downloaded from the following location: http://ant.apache.org With the advent of a new Apache Maven 2 based b=
uild architecture (first introduced inDSpace 1.5.x), you now have two optio=
ns in how you may wish to install and manage your local installation of DSp=
ace. If you've used DSpace 1.4.x, please recognize that the initial build p=
rocedure has changed to allow for more customization. You will find the lat=
er 'Ant based' stages of the installation procedure familiar. Maven is used=
to resolve the dependencies of DSpace online from the 'Maven Central Repos=
itory' server. It is important to note that the strategies are identical in terms of th=
e list of procedures required to complete the build process, the only diffe=
rence being that the Source Release includes "more modules" that will be bu=
ilt given their presence in the distribution package. Before beginning an installation, it is important to get a general under=
standing of the DSpace directories and the names by which they are generall=
y referred. (Please attempt to use these below directory names when asking =
for help on the DSpace Mailing Lists, as it will help everyone better under=
stand what directory you may be referring to.) DSpace uses three separate directory trees. Although you don't need to k=
now all the details of them in order to install DSpace, you do need to know=
they exist and also know how they're referred to in this document: This method gets you up and running with DSpace quickly and easily. It i=
s identical in both the Default Release and Source Release distributions.=
p>
You can interpolate the value of one configuration variable in the value=
of another one. For example, to set feedback.recipient to the sam=
e value as mail.admin, the line would look like: Defaults to PostgreSQL settings Without any extra arguments, the DSpace installation package is initiali=
zed for PostgreSQL. _If you want to use Oracle instead, you should build th=
e DSpace installation package as follows: To see a complete list of build targets, run: In order to set up some communities and collections, you'll need to logi=
n as your DSpace Administrator (which you created with The above installation steps are sufficient to set up a test server to p=
lay around with, but there are a few other steps and options you should pro=
bably consider before deploying a DSpace production site. A couple of DSpace features require that a script is run regularly =E2=
=80=93 the e-mail subscription feature that alerts users of new items being=
deposited, and the new 'media filter' tool, that generates thumbnails of i=
mages and extracts the full-text of documents for indexing. To set these up, you just need to run the following command as the d=
space UNIX user: Then add the following lines: Naturally you should change the frequencies to suit your environment. PostgreSQL also benefits from regular 'vacuuming', which optimizes the i=
ndexes and clears out any deleted data. Become the postgres UNIX u=
ser, run crontab -e and add (for example): In order that statistical reports are generated regularly and thus kept =
up to date you should set up the following cron jobs: Obviously, you should choose execution times which are most useful to yo=
u, and you should ensure that the report scripts run a short while after the analysis s=
cripts to give them time to complete (a run of around 8 months worth of log=
s can take around 25 seconds to complete); the resulting reports will let y=
ou know how long analysis took and you can adjust your cron times according=
ly. In order to deploy a multilingual version of DSpace you have to configur=
e two parameters in [dspace-source]/config/dspace.cfg: The Locales might have the form country, country_language, country_langu=
age_variant. According to the languages you wish to support, you have to make sure, t=
hat all the i18n related files are available see the Multilingual User Inte=
rface Configuring MultiLingual Support section for the JSPUI or the Multili=
ngual Support for XMLUI in the configuration documentation. If your DSpace is configured to have users login with a username and pas=
sword (as opposed to, say, client Web certificates), then you should consid=
er using HTTPS. Whenever a user logs in with the Web form (e.g. dspace.=
myuni.edu/dspace/password-login) their DSpace password is exposed in p=
lain text on the network. This is a very serious security risk since networ=
k traffic monitoring is very common, especially at universities. If the ris=
k seems minor, then consider that your DSpace administrators also login thi=
s way and they have ultimate control over the archive. The solution is to use HTTPS (HTTP over SSL, i.e. Secure Socket=
Layer, an encrypted transport), which protects your passwords against bein=
g captured. You can configure DSpace to require SSL on all "authenticated" =
transactions so it only accepts passwords on SSL connections. The following sections show how to set up the most commonly-used Java Se=
rvlet containers to support HTTP over SSL. If you choose Apache HTTPD as your primary=
HTTP server, you can have it forward requests to the Tomcat servlet container via Apache Jakarta Tomcat Connector. T=
his can be configured to work over SSL as well. First, you must configure A=
pache for SSL; for Apache 2.0 see Apache SSL/TLS Encryption for information about using mod_ssl. If you are using X.509 Client Certificates for authenticatio=
n: add these configuration options to the appropriate htt=
pd configuration file, e.g. ssl.conf, and be sure they are in=
force for the virtual host and namespace locations dedicated to DSpace: Now consult the Apache Jakarta Tomcat Connector documentation to configure the mod_jk (note: NOTmod_jk2) module. Select th=
e AJP 1.3 connector protocol. Also follow the instructions there to configu=
re your Tomcat server to respond to AJP. To use SSL on Apache HTTPD with mod_webapp consult the =
DSpace 1.3.2 documentation. Apache have deprecated the mod_webapp =
connector and recommend using mod_jk. To use Jetty's HTTPS support consult the documentation =
for the relevant tool. First a few facts to clear up some common misconceptions: A Handle server runs as a separate process that receives TCP requests fr=
om other Handle servers, and issues resolution requests to a global server =
or servers if a Handle entered locally does not correspond to some local co=
ntent. The Handle protocol is based on TCP, so it will need to be installed=
on a server that can broadcast and receive TCP on port 2641. If you need to update the handle prefix on items created before the CNRI=
registration process you can run the [dspace]/bin/dspace update-handle=
-prefix script. You may need to do this if you loaded items prior to C=
NRI registration (e.g. setting up a demonstration system prior to migrating=
it to production). The script takes the current and new prefix as paramete=
rs. For example: This script will change any handles currently assigned prefix 123456789 =
to prefix 1303, so for example handle 123456789/23 will be updated to 1303/=
23 in the database. To aid web crawlers index the content within your repository, you can ma=
ke use of sitemaps. There are currently two forms of sitemaps included in D=
Space: Google sitemaps and HTML sitemaps. Sitemaps allow DSpace to expose its content without the crawlers having =
to index every page. HTML sitemaps provide a list of all items, collections=
and communities in HTML format, whilst Google sitemaps provide the same in=
formation in gzipped XML format. To generate the sitemaps, you need to run [dspace]/bin/dspace genera=
te-sitemaps This creates the sitemaps in [dspace]/sitemaps/=
p>
The sitemaps can be accessed from the following URLs: When running [dspace]/bin/dspace generate-sitemaps the script i=
nforms Google that the sitemaps have been updated. For this update to regis=
ter correctly, you must first register your Google sitemap index page (=
/dspace/sitemap) with Google at http://www.google.com/webmasters/sitema=
ps/. If your DSpace server requires the use of a HTTP proxy to connect =
to the Internet, ensure that you have set http.proxy.host and =
http.proxy.port in [dspace]/config/dspace.cfg The URL for pinging Google, and in future, other search engines, is conf=
igured in [dspace-space]/config/dspace.cfg using the sitemap.e=
ngineurls setting where you can provide a comma-separated list of URLs=
to 'ping'. You can generate the sitemaps automatically every day using an additiona=
l cron job: DSpace uses the Apache Solr application underlaying the statistics. Ther=
e is no need to download any separate software. All the necessary software =
is included. To understand all of the configuration property keys, the user=
should refer to 5.2.35 DSpace Statistic Configuration for detailed informa=
tion.<set=
tings>
.
.
<proxies>
<proxy>
<active>true</active>
<protocol>http</protocol>
<host>proxy.somewhere.com</host>
<port>8080</port>
<username>proxyuser</username>
<password>somepassword</password>
<nonProxyHosts>www.google.com|*.somewhere.com</nonProxyHosts=
>
</proxy>
</proxies>
.
.
</settings>
Apache Ant 1.7 o=
r later (Java build tool)
Relational=
Database: (PostgreSQL or Oracle).
Servlet Engine: (Apache Tomcat 5.5 or 6, Jetty, Caucho Resin=
or equivalent).
<!--=
Define a non-SSL HTTP/1.1 Connector on port 8080 -->
<Connector port=3D"8080"
maxThreads=3D"150"
minSpareThreads=3D"25"
=09 maxSpareThreads=3D"75"
enableLookups=3D"false"
redirectPort=3D"8443"
=09 acceptCount=3D"100"
connectionTimeout=3D"20000"
=09 disableUploadTimeout=3D"true"
URIEncoding=3D"UTF-8"/>
Pe=
rl (only required for [dspace]/bin/dspace-info.pl)
Installation Instructions<=
/h2>
Overview of Install Option=
s
Overview of DSpace Dire=
ctories
[dspa=
ce]
. This is the location where DSpace is installed and running off =
of it is the location that gets defined in the dspace.cfg
as "=
dspace.dir". It is where all the DSpace configuration files, command line s=
cripts, documentation and webapps will be installed to.[dspace-sou=
rce]
. This is the location where the DSpace release distribution ha=
s been unzipped into. It usually has the name of the archive that you expan=
ded such as dspace
-<version>
-release<=
/code> or
dspace
-<version>
-src
=
-release
. It is the directory where all of your "build" comman=
ds will be run.[dspace]/webapps
by default. However, if you a=
re using Tomcat, you may decide to copy your DSpace web applications from <=
code>[dspace]/webapps/ to [tomcat]/webapps/
(with [tomcat]
being wherever you installed Tomcat=E2=80=9A also known as=
$CATALINA_HOME
).
For details on the contents of these separate directory trees, refer to di=
rectories.html. Note that the [dspace-source]
and=
[dspace]
directories are always separate!Installation
useradd=
-m dspace
unzip d=
space-1.7-release.zip
gunzip =
-c dspace-1.7-release.tar.gz | tar -xf -
bunzip2=
dspace-1.7-release.tar.bz | tar -xf -
dspace}}database, owned by the {{dspace
PostgreSQ=
L user (you are still logged in at 'root'):=20
createu=
ser -U postgres -d -A -P dspace
createdb -U dspace -E UNICODE dspace
mvn ins=
tall:install-file -Dfile=3Dojdbc6.jar -DgroupId=3Dcom.oracle
-DartifactId=3Dojdbc6 -Dversion=3D11.2.0.2.0 -Dpackaging=3Djar -Dgenera=
tePom=3Dtrue
db.name=
=3D oracle
db.url =3D jdbc:oracle:thin:@//host:port/dspace
db.driver =3D oracle.jdbc.OracleDriver
[dspace-source]/dspa=
ce/config/dspace.cfg
, in particular you'll need to set these propert=
ies:=20
dspace.dir
- must be set to the [dspace] (install=
ation) directory.dspace.url
- complete URL of this server's DSpace home pag=
e.dspace.hostname
- fully-qualified domain name of web serve=
r.dspace.name
- "Proper" name of your server, e.g. "My Digit=
al Library".db.password
- the database password you entered in the pre=
vious step.mail.server
- fully-qualified domain name of your outgoing=
mail server.mail.from.address
- the "From:" address to put on email se=
nt by DSpace.feedback.recipient
- mailbox for feedback mail.mail.admin
- mailbox for DSpace site administrator.alert.recipient
- mailbox for server errors/alerts (not es=
sential but very useful!)registration.notify
- mailbox for emails when new users re=
gister (optional)=20
feedback.recipient =3D ${mail.admin
}
Refer to the General Configuration section for details and examples=
of the above.[dspace]
). As root (or a user with=
appropriate permissions), run:=20
mkdir [=
dspace]
chown dspace [dspace]
[dspace-source]/dsp=
ace
directory:=20
cd [dsp=
ace-source]/dspace/
mvn package
=
mvn -Ddb.name=3Doracle package
cd [dsp=
ace-source]/dspace/target/dspace-[version]-build.dir
ant fresh_install
ant help
=
The most likely thing to go wrong here is the database connection. See the<=
/em> Common Problems =
Section.
cp -R [dspace]/webapps/=
* [tomcat]/webapps*
(This will copy all the web applications to Tomc=
at). cp -R [dspace]/webapps/jspui [t=
omcat]/webapps*
(This will copy only the jspui web application to To=
mcat.)\<Hos=
t
> section of your [tomcat]/conf/server.xml
you coul=
d add lines similar to the following (but replace [dspace]
wit=
h your installation location:=20
<!--=
Define the default virtual host
=09Note: XML Schema validation will not work with Xerces 2.2.
=09-->
=09<Host name=3D"localhost" appBase=3D"[dspace]/webapps"
=09....
[dspace=
]/bin/dspace create-administrator
http://dspace.myu=
.edu:8080/jspui
ht=
tp://dspace.myu.edu:8080/xmlui
http://dspace.myu.edu:8080/oai/request?verb=3DIdentify
(Shou=
ld return an XML-based response)create-adminis=
trator
above) and access the administration UI in either the JSP or =
XML user interface.Advanced Installation
'cron' Jobs
crontab=
-e
# Send =
out subscription e-mails at 01:00 every day
0 1 * * * [dspace]/bin/dspace sub-daily
# Run the media filter at 02:00 every day
0 2 * * * [dspace]/bin/dspace filter-media
# Run the checksum checker at 03:00
0 3 * * * [dspace]/bin/dspace checker -lp
# Mail the results to the sysadmin at 04:00
0 4 * * * [dspace]/bin/dspace checker-emailer -c
# Clean=
up the database nightly at 4.20am
20 4 * * * vacuumdb --analyze dspace > /dev/null 2>&1
# Run s=
tat analysis
0 1 * * * [dspace]/bin/dspace stat-general
0 1 * * * [dspace]/bin/dspace stat-monthly
0 2 * * * [dspace]/bin/dspace stat-report-general
0 2 * * * [dspace]/bin/dspace stat-report-monthly
Multilingual Installation<=
/h3>
default.locale =3D en
webui.supported.locales =
=3D en, de
DSpace over HTTPS
To enable the H=
TTPS support in Tomcat 5.0:
$JAVA_H=
OME/bin/keytool -import -noprompt -v -storepass changeit
=09-keystore $CATALINA_BASE/conf/keystore -alias tomcat -file
=09myserver.pem
$JAVA_=
HOME/bin/keytool -import -noprompt -storepass changeit
=09-trustcacerts -keystore $CATALINA_BASE/conf/keystore -alias ServerCA
=09-file ca.pem
$JAVA_H=
OME/bin/keytool -import -noprompt -storepass changeit
=09-trustcacerts -keystore $CATALINA_BASE/conf/keystore -alias client1
=09-file client1.pem
&l=
t;Connector port=3D"8443"
maxThreads=3D"150" minSpareThreads=3D"25"
=09 maxSpareThreads=3D"75"
enableLookups=3D"false"
=09 disableUploadTimeout=3D"true"
acceptCount=3D"100" debug=3D"0"
scheme=3D"https" secure=3D"true" sslProtocol=3D"TLS"
=09keystoreFile=3D"conf/keystore" keystorePass=3D"changeit" clientAuth=3D"t=
rue" - ONLY if using client X.509 certs for authentication!
=09truststoreFile=3D"conf/keystore" trustedstorePass=3D"changeit" />
<Con=
nector port=3D"8080"
maxThreads=3D"150" minSpareThreads=3D"25"
=09 maxSpareThreads=3D"75"
enableLookups=3D"false"
=09 redirectPort=3D"8443"
acceptCount=3D"100" debug=3D"0" =09/>
$JAVA_H=
OME/bin/keytool -genkey -alias tomcat -keyalg RSA -keysize
=091024 \
-keystore $CATALINA_BASE/conf/keystore -storepass changeit
=09-validity 365 \
-dname 'CN=3Ddspace.myuni.edu, OU=3DMIT Libraries, O=3DMassachusetts
=09Institute of Technology, L=3DCambridge, S=3DMA, C=3DUS'
$JAVA_=
HOME/bin/keytool -keystore $CATALINA_BASE/conf/keystore
=09-storepass changeit \
-certreq -alias tomcat -v -file tomcat.csr
$JAVA_=
HOME/bin/keytool -keystore $CATALINA_BASE/conf/keystore
=09-storepass changeit \
-import -alias mitCA -trustcacerts -file mitCA.pem
$JAVA_=
HOME/bin/keytool -keystore $CATALINA_BASE/conf/keystore
=09-storepass changeit \
-import -alias tomcat -trustcacerts -file signed-cert.pem
$JAVA_=
HOME/bin/keytool -genkey -alias tomcat -keyalg RSA -keystore
=09$CATALINA_BASE/conf/keystore -storepass changeit
$JAVA_=
HOME/bin/keytool -import -noprompt -storepass changeit
=09-trustcacerts -keystore $CATALINA_BASE/conf/keystore -alias client1
=09-file client1.pem
To use SSL on Apac=
he HTTPD with mod_jk:
=
## SSLVerifyClient can be "optional" or
=09"require"
SSLVerifyClient optional
SSLVerifyDepth 10
SSLCACertificateFile
=09path-to-your-client-CA-certificate
SSLOptions StdEnvVars ExportCertData
The Handle Server
If you want to use the Handle system, you'll need to set up a Handle serve=
r. This is included with DSpace. Note that this is not required in order to=
evaluate DSpace; you only need one if you are running a production service=
. You'll need to obtain a Handle prefix from the central CNRI Handle site.
[dspace=
]/bin/dspace make-handle-config [dspace]/handle-server
"storag=
e_type" =3D "CUSTOM"
"storage_class" =3D "org.dspace.handle.HandlePlugin"
[dspace=
]/bin/start-handle-server
Updating Existing Ha=
ndle Prefixes
[dspace=
]/bin/dspace update-handle-prefix 123456789 1303
Google and HTML sitemaps
HTML sitemaps follow the same procedure:# Gener=
ate sitemaps
0 6 * * * [dspace]/bin/dspace generate-sitemaps
DSpace Statistics
:=20
solr.lo=
g.server =3D ${dspace.baseUrl}/solr/statistics
solr.dbfile =3D ${dspace.dir}/config/GeoLiteCity.dat
solr.spiderips.urls =3D http://iplists.com/google.txt, \
http://iplists.com/inktomi.txt, \
http://iplists.com/lycos.txt, \
http://iplists.com/infoseek.txt, \
http://iplists.com/altavista.txt, \
http://iplists.com/excite.txt, \
http://iplists.com/misc.txt, \
http://iplists.com/non_engines.txt
useProx= ies =3D true
cd [dsp= ace-source]/dspace mvn package cd [dspace-source]/dspace/target/dspace-<version>-build.dir ant -Dconfig=3D[dspace]/config/dspace.cfg update cp -R [dspace]/webapps/* [TOMCAT]/webapps
If you are installing DSpace on Windows, you will still need to install = all the same Prerequisite So= ftware, as listed above.
= dspace.dir config.template.log4j.properties config.template.log4j-handle-plugin.properties config.template.oaicat.properties assetstore.dir log.dir upload.temp.dir report.dir handle.dir
mvn pac= kage
mvn -Dd= b.name=3Doracle package
ant fre= sh_install
ant =
help
[dspace= ]\bin\dspace create-administrator
<!--= DEFINE A CONTEXT PATH FOR DSpace JSP User Interface --> <Context path=3D"/jspui" docBase=3D"[dspace]\webapps\jspui" debug=3D"0" =09reloadable=3D"true" cachingAllowed=3D"false" =09allowLinking=3D"true"/> <!-- DEFINE A CONTEXT PATH FOR DSpace OAI User Interface --> <Context path=3D"/oai" docBase=3D"[dspace]\webapps\oai" debug=3D"0" =09reloadable=3D"true" cachingAllowed=3D"false" =09allowLinking=3D"true"/>
The administrator needs to check the installation to make sure all compo= nents are working. Here is list of checks to be performed. In brackets afte= r each item, it the associated component or components that might be the is= sue needing resolution.
In any software project of the scale of DSpace, there will be bugs. Some= times, a stable version of DSpace includes known bugs. We do not always wai= t until every known bug is fixed before a release. If the software is suffi= ciently stable and an improvement on the previous release, and the bugs are= minor and have known workarounds, we release it to enable the community to= take advantage of those improvements.
The known bugs in a release are documented in the KNOWN_BUGS fi= le in the source package.
Please see the DSpace bug tracker for further informa= tion on current bugs, and to find out if the bug has subsequently been fixe= d. This is also where you can report any further bugs you find.
In an ideal world everyone would follow the above steps and have a fully= functioning DSpace. Of course, in the real world it doesn't always seem to= work out that way. This section lists common problems that people encounte= r when installing DSpace, and likely causes and fixes. This is likely to gr= ow over time as we learn about users' experiences.
ant fresh_ins=
tall
: There are two common errors that occur.=20
[java] = 2004-03-25 15:17:07,730 INFO =09 org.dspace.storage.rdbms.InitializeDatabase @ Initializing Database [java] 2004-03-25 15:17:08,816 FATAL =09 org.dspace.storage.rdbms.InitializeDatabase @ Caught exception: [java] org.postgresql.util.PSQLException: Connection refused. Check =09 that the hostname and port are correct and that the postmaster is =09 accepting TCP/IP connections. [java] at =09 org.postgresql.jdbc1.AbstractJdbc1Connection.openConnection(Abstract= Jd bc1Connection.java:204) [java] at org.postgresql.Driver.connect(Driver.java:139)
psql -U= dspace -W -h localhost
[java] = 2004-03-25 16:37:16,757 INFO =09 org.dspace.storage.rdbms.InitializeDatabase @ Initializing Database [java] 2004-03-25 16:37:17,139 WARN =09 org.dspace.storage.rdbms.DatabaseManager @ Exception initializing DB =09 pool [java] java.lang.ClassNotFoundException: org.postgresql.Driver [java] at java.net.URLClassLoader$1.run(URLClassLoader.java:198) [java] at java.security.AccessController.doPrivileged(Native =09 Method) [java] at =09 java.net.URLClassLoader.findClass(URLClassLoader.java:186)
ps -ef | grep java
and look for Tomcat's Java processes. If they stay around after running T=
omcat's shutdown.sh script, trying running kill
on th=
em (or kill -9
if necessary), then starting Tomcat again.ps -ef | grep postgres=
code>
dspace = 16325 1997 0 Feb 14 ? 0:00 postgres: dspace dspace 127.0.0.1= idle in transaction
dspace = 16325 1997 0 Feb 14 ? 0:00 postgres: dspace dspace 127.0.0.1= SELECT
kill
on t=
he process, and stopping and restarting Tomcat.