Hello everyone,
I have a similar problem. After the upgrage from 3.1 to 4.2 I copied all
the webapps in Tomcat installation folder. I use jspui but, when in the
webapps folder exist xmlui, sword and swordv2, Tomcat becomes
unresponsive, does not restart or stop (only kill process) and jspui
loads forever. When I delete those webapps, jspui works normally.
Maybe in the future I need sword so, it is something I need to solve.
My system is a VM with Windows 2008 R2 Standard (64-bit), Apache Tomcat
8, Apache Ant 1.9.4, Apache Maven 3.2.2, PostgreSQL 9.2, JDK 1.7.0_65
with JRE 7.
In a development machine it works fine. This machine has different
versions of Apache Tomcat and PosgreSQL but I don't believe this is the
problem, I tested it in my machine with Tomcat 7 too. I also used
PosgreSQL 9.2 with DSpace 3.1 and worked fine.
John
On 3/9/2014 5:41 μμ, Nason Bimbe wrote:
Hi,
I just wanted to let you know that I have now successfully upgraded
the Dspace on my dev. The problem was actually to do with @mire cua
module which was being referenced in spring configs but whose jar
files are not deployed for now.
Thank you so much for your help.
Best
Nason
On 2 September 2014 15:44, Nason Bimbe nasonbi...@gmail.com
mailto:nasonbi...@gmail.com wrote:
Thanks for this, will try it out.
On 2 September 2014 15:43, Pottinger, Hardy J.
pottinge...@missouri.edu mailto:pottinge...@missouri.edu wrote:
Hi, Nason, here is the init script I use for running a binary
install of Tomcat 7 on RHEL [1] Note that it gets
progressively more aggressive when shutting down Tomcat. This
script is a mash-up of a few sample Tomcat init scripts I
found online, citations are given in the code.
[1] https://gist.github.com/hardyoyo/9903387
*From:* Nason Bimbe [nasonbi...@gmail.com
mailto:nasonbi...@gmail.com]
*Sent:* Tuesday, September 02, 2014 9:25 AM
*To:* Pottinger, Hardy J.
*Cc:* Peter Dietz; dspace-tech
*Subject:* Re: [Dspace-tech] Dspace 3.1 to 4.2 upgrade: XMLUI
webapp not running and can not be started
Hi Hardy,
I will be trying it out again tomorrow afresh after restoring
the system to before the attempted upgrade. I am using a
script I created in /etc/init.d for starting/stopping Tomcat.
I will also try Shaun Donovan's information which he sent
directly to me and shown below. I will update you how it on
progress. Thanks again for the help.
Best
Nason
I had this problem, not on xmlui but on oai. I found the
following on the web and tried it, and it worked.
Check Inside the Following Directory for the jar file el-api.jar
:C:\apache-tomcat-7.0.39\lib\el-api.jar if it exists then in this
directory of your web application WEB-INF\lib\el-api.jar the jar
should be removed
What I did is find the file, and moved it, then the app
started without issues. This was on a development machine. I
then tried it on the production machine and my oai would still
not start. I had other issues in my catalina.out which pointed
to the web.xml file in tomcats conf directory which had !--
comments within a comment, which I also removed, and then
production worked as well.
On 2 September 2014 13:59, Pottinger, Hardy J.
pottinge...@missouri.edu mailto:pottinge...@missouri.edu
wrote:
Hi, Nason, did you ever configure Tomcat to run as the
DSpace user? What are you using for a service init script?
--Hardy
Sent from my iPad
On Sep 1, 2014, at 1:52 PM, Nason Bimbe
nasonbi...@gmail.com mailto:nasonbi...@gmail.com wrote:
Hi,
I am still having the same problem. I have made sure
dspace is the owner of all files and I am also using
dspace user to build the DSpace. I am running Debian Wheezy.
This is how Tomcat was installed
=
- downloaded, copied Tomact 7 files into /usr/local,
created a symbolic link
mv /home/dspace/Downloads/apache-tomcat-7.0.54 /usr/local
unlink tomcat
ln -s apache-tomcat-7.0.54 tomcat
- made sure that tomcat folder is owned by the dspace user
cd /usr/local
chown -R dspace:dspace apache-tomcat-7.0.54
- restarted tomcat
/etc/init.d/tomcat restart
- checked if tomcat is running and is running ok
http://localhost:8080
This the change I made to the top level POM as advised
by Bram by adding scope tag
===
dependency
groupIdjavax.servlet/groupId
