Re: [Dspace-tech] problem with build failing in Dspace 3.2
Hi!
The change of http to https in pom.xml file (+ removal of appropiate
.m2 folders) seems to have fixed my problem. The problem had occurred
quite lately because the build was working ok about a week ago, but
this week we run into this problem.
By the way: I tested rebuild in 1.7.2 test server and it does not seem
to be affected with the problem.
Thanks for all for the help !
Päivi
Quoting Kiriaki Roditi krod...@elidoc.gr:
I honestly do not know what this is.
Trying to solve this, I found (in a 2012 thread unrelated to DSpace,
which I unfortunately did not save) that this failure was caused by
a bad http redirection. But why now?
In my case it occurred in a rebuild after some .java files
modifications in a working 3.1 installation. Prior to this my latest
build must have been around 8 months ago and it worked fine.
I am kind of speculating here but notice that we all dealt with it
during a version 3 build. Is that relevant?
Best regards,
Kiriaki
On 3/4/2014 5:14 μμ, Hilton Gibson wrote:
Isn't this is a bug with the pom.xml file.
I think this happens with new installs.
Upgrades are Ok, it seems, since the Sonatype files are already in
the .m2 folder.
This was my first problem during our upgrade from 1.8.2 to 3.2.
I simply copied all the files in the .m2 folder from a working test
system to do our fix.
Cheers
hg
*Hilton Gibson*
Ubuntu Linux Systems Administrator
JS Gericke Library
Room 1025D
Stellenbosch University
Private Bag X5036
Stellenbosch
7599
South Africa
Tel: +27 21 808 4100 | Cell: +27 84 646 4758
http://scholar.sun.ac.za
http://bit.ly/goodir
http://library.sun.ac.za
http://za.linkedin.com/in/hiltongibson
On 3 April 2014 15:33, Kiriaki Roditi krod...@elidoc.gr
mailto:krod...@elidoc.gr wrote:
Hello Päivi and everybody interested,
I dealt the same error just yesterday with a DSpace 3.1 build.
This is how I managed to complete the build successfully:
Sonatype has changed the URL from http to https, so you need to
change this in your [dspace-src]/pom.xml
But you also need to force maven to find the new sonatype URL. In
order to do that delete (or if you want to be super safe cut to
another directory) the folders dspace-api and dspace-api-lang from
your local .m2 repository, like you already tried as stated in
your email. To determine which are the faulty .m2 repository
directories, check the date they were modified. It should be when
your build failed.
Hope this helps.
Best regards,
Kiriaki
On 3/4/2014 1:49 μμ, Päivi Rosenström wrote:
Hi !
While attempting to build DSpace 3.2 code (previously worked ok)
getting the following error message:
INFO] Building jar:
/data/source-dspace/dspace-api/target/dspace-api-3.2.jar
[INFO] [jar:test-jar {execution: default}]
[INFO] Skipping packaging of the test-jar
[INFO]
[INFO] Building DSpace Addon Modules
[INFO]task-segment: [package]
[INFO]
[INFO] [enforcer:enforce {execution: enforce-maven}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO]
[INFO] Building DSpace Kernel :: Additions and Local Customizations
[INFO]task-segment: [package]
[INFO]
[INFO] artifact org.dspace:dspace-api-lang: checking for updates from
sonatype-releases
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'ef3dc2ec718a24931364e81249c0933d3d0cc682'; remote = 'html
headtitle301' - RETRYING
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'ef3dc2ec718a24931364e81249c0933d3d0cc682'; remote = 'html
headtitle301' - IGNORING
[INFO] artifact org.dspace:dspace-api-lang: checking for
updates from central
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Unable to get dependency information: Unable to read local copy of
metadata: Cannot read metadata from
'/home/tomcat/.m2/repository/org/dspace/dspace-api-lang/maven-metadata-sonatype-releases.xml':
end tag name /body must match start tag name hr from line 5 (position:
TEXT seen
.../center\r\n/body...
@6:8)
org.dspace:dspace-api-lang:jar:null
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
sonatype-nexus-snapshots
(https://oss.sonatype.org/content/repositories/snapshots),
sonatype-releases
Re: [Dspace-tech] problem with build failing in Dspace 3.2
Hi All
Can you point us to the relevant pom.xml file on github and also reference
the line number where a change is needed.
Thx in advance.
Cheers
hg
*Hilton Gibson*
Ubuntu Linux Systems Administrator
JS Gericke Library
Room 1025D
Stellenbosch University
Private Bag X5036
Stellenbosch
7599
South Africa
Tel: +27 21 808 4100 | Cell: +27 84 646 4758
http://scholar.sun.ac.za
http://bit.ly/goodir
http://library.sun.ac.za
http://za.linkedin.com/in/hiltongibson
On 4 April 2014 09:42, Päivi Rosenström paivi.rosenst...@helsinki.fiwrote:
Hi!
The change of http to https in pom.xml file (+ removal of appropiate .m2
folders) seems to have fixed my problem. The problem had occurred quite
lately because the build was working ok about a week ago, but this week we
run into this problem.
By the way: I tested rebuild in 1.7.2 test server and it does not seem to
be affected with the problem.
Thanks for all for the help !
Päivi
Quoting Kiriaki Roditi krod...@elidoc.gr:
I honestly do not know what this is.
Trying to solve this, I found (in a 2012 thread unrelated to DSpace,
which I unfortunately did not save) that this failure was caused by a bad
http redirection. But why now?
In my case it occurred in a rebuild after some .java files modifications
in a working 3.1 installation. Prior to this my latest build must have been
around 8 months ago and it worked fine.
I am kind of speculating here but notice that we all dealt with it during
a version 3 build. Is that relevant?
Best regards,
Kiriaki
On 3/4/2014 5:14 μμ, Hilton Gibson wrote:
Isn't this is a bug with the pom.xml file.
I think this happens with new installs.
Upgrades are Ok, it seems, since the Sonatype files are already in the
.m2 folder.
This was my first problem during our upgrade from 1.8.2 to 3.2.
I simply copied all the files in the .m2 folder from a working test
system to do our fix.
Cheers
hg
*Hilton Gibson*
Ubuntu Linux Systems Administrator
JS Gericke Library
Room 1025D
Stellenbosch University
Private Bag X5036
Stellenbosch
7599
South Africa
Tel: +27 21 808 4100 | Cell: +27 84 646 4758
http://scholar.sun.ac.za
http://bit.ly/goodir
http://library.sun.ac.za
http://za.linkedin.com/in/hiltongibson
On 3 April 2014 15:33, Kiriaki Roditi krod...@elidoc.gr mailto:
krod...@elidoc.gr wrote:
Hello Päivi and everybody interested,
I dealt the same error just yesterday with a DSpace 3.1 build.
This is how I managed to complete the build successfully:
Sonatype has changed the URL from http to https, so you need to
change this in your [dspace-src]/pom.xml
But you also need to force maven to find the new sonatype URL. In
order to do that delete (or if you want to be super safe cut to
another directory) the folders dspace-api and dspace-api-lang from
your local .m2 repository, like you already tried as stated in
your email. To determine which are the faulty .m2 repository
directories, check the date they were modified. It should be when
your build failed.
Hope this helps.
Best regards,
Kiriaki
On 3/4/2014 1:49 μμ, Päivi Rosenström wrote:
Hi !
While attempting to build DSpace 3.2 code (previously worked ok)
getting the following error message:
INFO] Building jar: /data/source-dspace/dspace-
api/target/dspace-api-3.2.jar
[INFO] [jar:test-jar {execution: default}]
[INFO] Skipping packaging of the test-jar
[INFO]
[INFO] Building DSpace Addon Modules
[INFO]task-segment: [package]
[INFO]
[INFO] [enforcer:enforce {execution: enforce-maven}]
[INFO] [site:attach-descriptor {execution:
default-attach-descriptor}]
[INFO]
[INFO] Building DSpace Kernel :: Additions and Local Customizations
[INFO]task-segment: [package]
[INFO]
[INFO] artifact org.dspace:dspace-api-lang: checking for updates from
sonatype-releases
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'ef3dc2ec718a24931364e81249c0933d3d0cc682'; remote = 'html
headtitle301' - RETRYING
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'ef3dc2ec718a24931364e81249c0933d3d0cc682'; remote = 'html
headtitle301' - IGNORING
[INFO] artifact org.dspace:dspace-api-lang: checking for updates
from central
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Unable to get dependency information: Unable to read local copy of
metadata: Cannot read
Re: [Dspace-tech] problem with build failing in Dspace 3.2
Hi, This is the pom.xml: https://github.com/DSpace/DSpace/blob/dspace-3_x/pom.xml The sonatype URL modification is required in line 1200: - urlhttp://oss.sonatype.org/content/repositories/releases//url + urlhttps://oss.sonatype.org/content/repositories/releases//url Since we started it, please let me point out another change that might be needed if someone tries to install xpdf filter in version 3.1. It is for the javax.media dependency. The new version that is downloaded is 1.1.3, not 1.1.2_01 In line 863: -version1.1.2_01/version + version1.1.3/version Thank you Hilton. Best regards, Kiriaki *Kiriaki Roditi* Systems Engineer ELiDOC Systems Services Irakliou Str. 162-164 | Athens, Greece | P.C. 111 42 | www.elidoc.gr Phone: +30 210 2588510 | Fax: +30 210 2514572 e-mail: krod...@elidoc.gr On 4/4/2014 10:46 πμ, Hilton Gibson wrote: Hi All Can you point us to the relevant pom.xml file on github and also reference the line number where a change is needed. Thx in advance. Cheers hg *Hilton Gibson* Ubuntu Linux Systems Administrator JS Gericke Library Room 1025D Stellenbosch University Private Bag X5036 Stellenbosch 7599 South Africa Tel: +27 21 808 4100 | Cell: +27 84 646 4758 http://scholar.sun.ac.za http://bit.ly/goodir http://library.sun.ac.za http://za.linkedin.com/in/hiltongibson On 4 April 2014 09:42, Päivi Rosenström paivi.rosenst...@helsinki.fi mailto:paivi.rosenst...@helsinki.fi wrote: Hi! The change of http to https in pom.xml file (+ removal of appropiate .m2 folders) seems to have fixed my problem. The problem had occurred quite lately because the build was working ok about a week ago, but this week we run into this problem. By the way: I tested rebuild in 1.7.2 test server and it does not seem to be affected with the problem. Thanks for all for the help ! Päivi Quoting Kiriaki Roditi krod...@elidoc.gr mailto:krod...@elidoc.gr: I honestly do not know what this is. Trying to solve this, I found (in a 2012 thread unrelated to DSpace, which I unfortunately did not save) that this failure was caused by a bad http redirection. But why now? In my case it occurred in a rebuild after some .java files modifications in a working 3.1 installation. Prior to this my latest build must have been around 8 months ago and it worked fine. I am kind of speculating here but notice that we all dealt with it during a version 3 build. Is that relevant? Best regards, Kiriaki On 3/4/2014 5:14 μμ, Hilton Gibson wrote: Isn't this is a bug with the pom.xml file. I think this happens with new installs. Upgrades are Ok, it seems, since the Sonatype files are already in the .m2 folder. This was my first problem during our upgrade from 1.8.2 to 3.2. I simply copied all the files in the .m2 folder from a working test system to do our fix. Cheers hg *Hilton Gibson* Ubuntu Linux Systems Administrator JS Gericke Library Room 1025D Stellenbosch University Private Bag X5036 Stellenbosch 7599 South Africa Tel: +27 21 808 4100 tel:%2B27%2021%20808%204100 | Cell: +27 84 646 4758 tel:%2B27%2084%20646%204758 http://scholar.sun.ac.za http://bit.ly/goodir http://library.sun.ac.za http://za.linkedin.com/in/hiltongibson On 3 April 2014 15:33, Kiriaki Roditi krod...@elidoc.gr mailto:krod...@elidoc.gr mailto:krod...@elidoc.gr mailto:krod...@elidoc.gr wrote: Hello Päivi and everybody interested, I dealt the same error just yesterday with a DSpace 3.1 build. This is how I managed to complete the build successfully: Sonatype has changed the URL from http to https, so you need to change this in your [dspace-src]/pom.xml But you also need to force maven to find the new sonatype URL. In order to do that delete (or if you want to be super safe cut to another directory) the folders dspace-api and dspace-api-lang from your local .m2 repository, like you already tried as stated in your email. To determine which are the faulty .m2 repository directories, check the date they were modified. It should be when your build failed. Hope this helps. Best regards, Kiriaki On 3/4/2014 1:49 μμ, Päivi Rosenström wrote:
Re: [Dspace-tech] problem with build failing in Dspace 3.2
Thx *Kiriaki*
*See:
**http://wiki.lib.sun.ac.za/index.php/SUNScholar/Upgrading/DSpace/Release_Notes/3.2#Build_Issues
http://wiki.lib.sun.ac.za/index.php/SUNScholar/Upgrading/DSpace/Release_Notes/3.2#Build_Issues
for a permanent record.*
*Cheers*
*hg*
*Hilton Gibson*
Ubuntu Linux Systems Administrator
JS Gericke Library
Room 1025D
Stellenbosch University
Private Bag X5036
Stellenbosch
7599
South Africa
Tel: +27 21 808 4100 | Cell: +27 84 646 4758
http://scholar.sun.ac.za
http://bit.ly/goodir
http://library.sun.ac.za
http://za.linkedin.com/in/hiltongibson
On 4 April 2014 11:32, Kiriaki Roditi krod...@elidoc.gr wrote:
Hi,
This is the pom.xml:
https://github.com/DSpace/DSpace/blob/dspace-3_x/pom.xml
The sonatype URL modification is required in line 1200:
-urlhttp://oss.sonatype.org/content/repositories/releases//url
+urlhttps://oss.sonatype.org/content/repositories/releases//url
Since we started it, please let me point out another change that might be
needed if someone tries to install xpdf filter in version 3.1.
It is for the javax.media dependency. The new version that is downloaded
is 1.1.3, not 1.1.2_01
In line 863:
-version1.1.2_01/version
+ version1.1.3/version
Thank you Hilton.
Best regards,
Kiriaki
*Kiriaki Roditi*
Systems Engineer
--
ELiDOC Systems Services
Irakliou Str. 162-164 | Athens, Greece | P.C. 111 42 | www.elidoc.gr
Phone: +30 210 2588510 | Fax: +30 210 2514572
e-mail: krod...@elidoc.gr
On 4/4/2014 10:46 πμ, Hilton Gibson wrote:
Hi All
Can you point us to the relevant pom.xml file on github and also
reference the line number where a change is needed.
Thx in advance.
Cheers
hg
*Hilton Gibson*
Ubuntu Linux Systems Administrator
JS Gericke Library
Room 1025D
Stellenbosch University
Private Bag X5036
Stellenbosch
7599
South Africa
Tel: +27 21 808 4100 | Cell: +27 84 646 4758
http://scholar.sun.ac.za
http://bit.ly/goodir
http://library.sun.ac.za
http://za.linkedin.com/in/hiltongibson
On 4 April 2014 09:42, Päivi Rosenström paivi.rosenst...@helsinki.fiwrote:
Hi!
The change of http to https in pom.xml file (+ removal of appropiate .m2
folders) seems to have fixed my problem. The problem had occurred quite
lately because the build was working ok about a week ago, but this week we
run into this problem.
By the way: I tested rebuild in 1.7.2 test server and it does not seem to
be affected with the problem.
Thanks for all for the help !
Päivi
Quoting Kiriaki Roditi krod...@elidoc.gr:
I honestly do not know what this is.
Trying to solve this, I found (in a 2012 thread unrelated to DSpace,
which I unfortunately did not save) that this failure was caused by a bad
http redirection. But why now?
In my case it occurred in a rebuild after some .java files modifications
in a working 3.1 installation. Prior to this my latest build must have been
around 8 months ago and it worked fine.
I am kind of speculating here but notice that we all dealt with it
during a version 3 build. Is that relevant?
Best regards,
Kiriaki
On 3/4/2014 5:14 μμ, Hilton Gibson wrote:
Isn't this is a bug with the pom.xml file.
I think this happens with new installs.
Upgrades are Ok, it seems, since the Sonatype files are already in the
.m2 folder.
This was my first problem during our upgrade from 1.8.2 to 3.2.
I simply copied all the files in the .m2 folder from a working test
system to do our fix.
Cheers
hg
*Hilton Gibson*
Ubuntu Linux Systems Administrator
JS Gericke Library
Room 1025D
Stellenbosch University
Private Bag X5036
Stellenbosch
7599
South Africa
Tel: +27 21 808 4100 | Cell: +27 84 646 4758
http://scholar.sun.ac.za
http://bit.ly/goodir
http://library.sun.ac.za
http://za.linkedin.com/in/hiltongibson
On 3 April 2014 15:33, Kiriaki Roditi krod...@elidoc.gr mailto:
krod...@elidoc.gr wrote:
Hello Päivi and everybody interested,
I dealt the same error just yesterday with a DSpace 3.1 build.
This is how I managed to complete the build successfully:
Sonatype has changed the URL from http to https, so you need to
change this in your [dspace-src]/pom.xml
But you also need to force maven to find the new sonatype URL. In
order to do that delete (or if you want to be super safe cut to
another directory) the folders dspace-api and dspace-api-lang from
your local .m2 repository, like you already tried as stated in
your email. To determine which are the faulty .m2 repository
directories, check the date they were modified. It should be when
your build failed.
Hope this helps.
Best regards,
Kiriaki
On 3/4/2014 1:49 μμ, Päivi Rosenström wrote:
Hi !
While attempting to build DSpace 3.2 code (previously worked ok)
getting the following error message:
INFO] Building jar:
/data/source-dspace/dspace-api/target/dspace-api-3.2.jar
[INFO] [jar:test-jar {execution:
[Dspace-tech] ChoiceAuthority using LDAP
Hey Guys, we are using LDAP at our institution and I would like to implement a choice authority based on it. Has anyone of you ever done something like that? Best Christian -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] problem with build failing in Dspace 3.2
Odd: I just moved my ~/.m2/repository/org/sonatype/oss/oss-parent directory aside, ran 'mvn clean install', and it had no trouble using http://oss.sonatype.org/content/repositories/releases/; to fetch oss-parent. But we may as well secure the connection. The cost is negligible. I've submitted an issue to Jira. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Machines should not be friendly. Machines should be obedient. signature.asc Description: Digital signature -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] changing name of custom metadata field
I have the request to change the metadata field “pu.date.graduation” to “pu.date.classyear” Is this simply a question of changing the name in the database and making sure that all references in config files are changed as well ? Do I have to worry about rye search index ? Monika Monika Mevenkamp phone: 609-258-4161 Lewis Library,Washington Road and Ivy Lane, Princeton University, Princeton, NJ 08544 -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] can't get /sorl deployed in 4.1
when I try to deploy /solr with tomcat I get: log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. I've looked at the log4j files and nothing catches my eye. Thank you! Jose -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] changing name of custom metadata field
Hi Monika, yes, you have to worry about the search indexing and the browse indexing as well if this metadata fields place any role in the browse. You will need to re-index. Regards, Kostas On Apr 4, 2014, at 6:46 PM, Monika C. Mevenkamp moni...@princeton.edu wrote: I have the request to change the metadata field “pu.date.graduation” to “pu.date.classyear” Is this simply a question of changing the name in the database and making sure that all references in config files are changed as well ? Do I have to worry about rye search index ? Monika Monika Mevenkamp phone: 609-258-4161 Lewis Library,Washington Road and Ivy Lane, Princeton University, Princeton, NJ 08544 -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] can't get /sorl deployed in 4.1
Before this error takes place I see this in the log file: Apr 04, 2014 3:27:49 PM org.apache.catalina.loader.WebappClassLoader validateJarFile INFO: validateJarFile(/deepblue/dspace/repository/dev/webapps_dev/solr/WEB-INF/lib/jsp-api-2.1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/jsp/JspPage.class Apr 04, 2014 3:27:49 PM org.apache.catalina.startup.ContextConfig applicationWebConfig I grabbed jsp-api-2.1.jar from the web, which was a different size and I still get this error. -Jose On Fri, Apr 4, 2014 at 1:40 PM, Jose Blanco blan...@umich.edu wrote: when I try to deploy /solr with tomcat I get: log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. I've looked at the log4j files and nothing catches my eye. Thank you! Jose -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] can't get /sorl deployed in 4.1
Hi, Jose, can you tell us the version numbers of the stuff in your stack? OS, Java, Tomcat? Thanks! --Hardy From: Jose Blanco [blan...@umich.edu] Sent: Friday, April 04, 2014 2:31 PM To: Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 Before this error takes place I see this in the log file: Apr 04, 2014 3:27:49 PM org.apache.catalina.loader.WebappClassLoader validateJarFile INFO: validateJarFile(/deepblue/dspace/repository/dev/webapps_dev/solr/WEB-INF/lib/jsp-api-2.1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/jsp/JspPage.class Apr 04, 2014 3:27:49 PM org.apache.catalina.startup.ContextConfig applicationWebConfig I grabbed jsp-api-2.1.jar from the web, which was a different size and I still get this error. -Jose On Fri, Apr 4, 2014 at 1:40 PM, Jose Blanco blan...@umich.edu wrote: when I try to deploy /solr with tomcat I get: log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. I've looked at the log4j files and nothing catches my eye. Thank you! Jose -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] can't get /sorl deployed in 4.1
I just got it deployed, but I'm not sure it's working. I got it deployed by (1) deleting jsp-api-2.1.jar from the solr lib area, since it was complaining about it. AND (2) removing listener listener-classorg.dspace.solr.filters.ConfigureLog4jListener/listener-class /listener from the solr web.xml file sine it could not load this. Here is the info you asked for: -bash-3.2$ java -version java version 1.7.0_51 Java(TM) SE Runtime Environment (build 1.7.0_51-b13) Java HotSpot(TM) Server VM (build 24.51-b03, mixed mode) Apache Tomcat/5.5.26 OS is linux Thank you! Jose On Fri, Apr 4, 2014 at 3:40 PM, Pottinger, Hardy J. pottinge...@missouri.edu wrote: Hi, Jose, can you tell us the version numbers of the stuff in your stack? OS, Java, Tomcat? Thanks! --Hardy From: Jose Blanco [blan...@umich.edu] Sent: Friday, April 04, 2014 2:31 PM To: Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 Before this error takes place I see this in the log file: Apr 04, 2014 3:27:49 PM org.apache.catalina.loader.WebappClassLoader validateJarFile INFO: validateJarFile(/deepblue/dspace/repository/dev/webapps_dev/solr/WEB-INF/lib/jsp-api-2.1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/jsp/JspPage.class Apr 04, 2014 3:27:49 PM org.apache.catalina.startup.ContextConfig applicationWebConfig I grabbed jsp-api-2.1.jar from the web, which was a different size and I still get this error. -Jose On Fri, Apr 4, 2014 at 1:40 PM, Jose Blanco blan...@umich.edu wrote: when I try to deploy /solr with tomcat I get: log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. I've looked at the log4j files and nothing catches my eye. Thank you! Jose -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] can't get /sorl deployed in 4.1
Is this all because I don't have tomcat 7. -Jose On Fri, Apr 4, 2014 at 4:00 PM, Jose Blanco blan...@umich.edu wrote: I just got it deployed, but I'm not sure it's working. I got it deployed by (1) deleting jsp-api-2.1.jar from the solr lib area, since it was complaining about it. AND (2) removing listener listener-classorg.dspace.solr.filters.ConfigureLog4jListener/listener-class /listener from the solr web.xml file sine it could not load this. Here is the info you asked for: -bash-3.2$ java -version java version 1.7.0_51 Java(TM) SE Runtime Environment (build 1.7.0_51-b13) Java HotSpot(TM) Server VM (build 24.51-b03, mixed mode) Apache Tomcat/5.5.26 OS is linux Thank you! Jose On Fri, Apr 4, 2014 at 3:40 PM, Pottinger, Hardy J. pottinge...@missouri.edu wrote: Hi, Jose, can you tell us the version numbers of the stuff in your stack? OS, Java, Tomcat? Thanks! --Hardy From: Jose Blanco [blan...@umich.edu] Sent: Friday, April 04, 2014 2:31 PM To: Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 Before this error takes place I see this in the log file: Apr 04, 2014 3:27:49 PM org.apache.catalina.loader.WebappClassLoader validateJarFile INFO: validateJarFile(/deepblue/dspace/repository/dev/webapps_dev/solr/WEB-INF/lib/jsp-api-2.1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/jsp/JspPage.class Apr 04, 2014 3:27:49 PM org.apache.catalina.startup.ContextConfig applicationWebConfig I grabbed jsp-api-2.1.jar from the web, which was a different size and I still get this error. -Jose On Fri, Apr 4, 2014 at 1:40 PM, Jose Blanco blan...@umich.edu wrote: when I try to deploy /solr with tomcat I get: log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. I've looked at the log4j files and nothing catches my eye. Thank you! Jose -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] can't get /sorl deployed in 4.1
Hi Jose, I think your problem is more or less conflicts between some DSpace libs and some that Tomcat already has. For example, the one that you mention that you deleted, the jsp-api one, is a library that Tomcat has as well. So, lib version mismatching problem :) I think that some other libraries may conflict as well. Take a look at the XML ones (I think it is called xml-api ore something like that). Regards, Kostas On Apr 4, 2014, at 11:20 PM, Jose Blanco blan...@umich.edu wrote: Is this all because I don't have tomcat 7. -Jose On Fri, Apr 4, 2014 at 4:00 PM, Jose Blanco blan...@umich.edu wrote: I just got it deployed, but I'm not sure it's working. I got it deployed by (1) deleting jsp-api-2.1.jar from the solr lib area, since it was complaining about it. AND (2) removing listener listener-classorg.dspace.solr.filters.ConfigureLog4jListener/listener-class /listener from the solr web.xml file sine it could not load this. Here is the info you asked for: -bash-3.2$ java -version java version 1.7.0_51 Java(TM) SE Runtime Environment (build 1.7.0_51-b13) Java HotSpot(TM) Server VM (build 24.51-b03, mixed mode) Apache Tomcat/5.5.26 OS is linux Thank you! Jose On Fri, Apr 4, 2014 at 3:40 PM, Pottinger, Hardy J. pottinge...@missouri.edu wrote: Hi, Jose, can you tell us the version numbers of the stuff in your stack? OS, Java, Tomcat? Thanks! --Hardy From: Jose Blanco [blan...@umich.edu] Sent: Friday, April 04, 2014 2:31 PM To: Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 Before this error takes place I see this in the log file: Apr 04, 2014 3:27:49 PM org.apache.catalina.loader.WebappClassLoader validateJarFile INFO: validateJarFile(/deepblue/dspace/repository/dev/webapps_dev/solr/WEB-INF/lib/jsp-api-2.1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/jsp/JspPage.class Apr 04, 2014 3:27:49 PM org.apache.catalina.startup.ContextConfig applicationWebConfig I grabbed jsp-api-2.1.jar from the web, which was a different size and I still get this error. -Jose On Fri, Apr 4, 2014 at 1:40 PM, Jose Blanco blan...@umich.edu wrote: when I try to deploy /solr with tomcat I get: log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. I've looked at the log4j files and nothing catches my eye. Thank you! Jose -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] can't get /sorl deployed in 4.1
So you are suggesting I get rid of xml-apis-1.0.b2.jar and add listener listener-classorg.dspace. solr.filters.ConfigureLog4jListener/listener-class /listener back in? What about the version of tomcat. According to the documentation I need to have 7 but right now I have 5.5.26. Could updating tomcat resolve this problem? Thank you! Jose On Fri, Apr 4, 2014 at 4:30 PM, Kostas Stamatis kstama...@ekt.gr wrote: Hi Jose, I think your problem is more or less conflicts between some DSpace libs and some that Tomcat already has. For example, the one that you mention that you deleted, the jsp-api one, is a library that Tomcat has as well. So, lib version mismatching problem :) I think that some other libraries may conflict as well. Take a look at the XML ones (I think it is called xml-api ore something like that). Regards, Kostas On Apr 4, 2014, at 11:20 PM, Jose Blanco blan...@umich.edu wrote: Is this all because I don't have tomcat 7. -Jose On Fri, Apr 4, 2014 at 4:00 PM, Jose Blanco blan...@umich.edu wrote: I just got it deployed, but I'm not sure it's working. I got it deployed by (1) deleting jsp-api-2.1.jar from the solr lib area, since it was complaining about it. AND (2) removing listener listener-classorg.dspace.solr.filters.ConfigureLog4jListener/listener-class /listener from the solr web.xml file sine it could not load this. Here is the info you asked for: -bash-3.2$ java -version java version 1.7.0_51 Java(TM) SE Runtime Environment (build 1.7.0_51-b13) Java HotSpot(TM) Server VM (build 24.51-b03, mixed mode) Apache Tomcat/5.5.26 OS is linux Thank you! Jose On Fri, Apr 4, 2014 at 3:40 PM, Pottinger, Hardy J. pottinge...@missouri.edu wrote: Hi, Jose, can you tell us the version numbers of the stuff in your stack? OS, Java, Tomcat? Thanks! --Hardy From: Jose Blanco [blan...@umich.edu] Sent: Friday, April 04, 2014 2:31 PM To: Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 Before this error takes place I see this in the log file: Apr 04, 2014 3:27:49 PM org.apache.catalina.loader.WebappClassLoader validateJarFile INFO: validateJarFile(/deepblue/dspace/repository/dev/webapps_dev/solr/WEB-INF/lib/jsp-api-2.1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/jsp/JspPage.class Apr 04, 2014 3:27:49 PM org.apache.catalina.startup.ContextConfig applicationWebConfig I grabbed jsp-api-2.1.jar from the web, which was a different size and I still get this error. -Jose On Fri, Apr 4, 2014 at 1:40 PM, Jose Blanco blan...@umich.edu wrote: when I try to deploy /solr with tomcat I get: log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. I've looked at the log4j files and nothing catches my eye. Thank you! Jose -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] can't get /sorl deployed in 4.1
I just got rid of xml-apis-1.0.b2.jar, and it still did not like the listner. -Jose On Fri, Apr 4, 2014 at 4:37 PM, Jose Blanco blan...@umich.edu wrote: So you are suggesting I get rid of xml-apis-1.0.b2.jar and add listener listener-classorg.dspace. solr.filters.ConfigureLog4jListener/listener-class /listener back in? What about the version of tomcat. According to the documentation I need to have 7 but right now I have 5.5.26. Could updating tomcat resolve this problem? Thank you! Jose On Fri, Apr 4, 2014 at 4:30 PM, Kostas Stamatis kstama...@ekt.gr wrote: Hi Jose, I think your problem is more or less conflicts between some DSpace libs and some that Tomcat already has. For example, the one that you mention that you deleted, the jsp-api one, is a library that Tomcat has as well. So, lib version mismatching problem :) I think that some other libraries may conflict as well. Take a look at the XML ones (I think it is called xml-api ore something like that). Regards, Kostas On Apr 4, 2014, at 11:20 PM, Jose Blanco blan...@umich.edu wrote: Is this all because I don't have tomcat 7. -Jose On Fri, Apr 4, 2014 at 4:00 PM, Jose Blanco blan...@umich.edu wrote: I just got it deployed, but I'm not sure it's working. I got it deployed by (1) deleting jsp-api-2.1.jar from the solr lib area, since it was complaining about it. AND (2) removing listener listener-classorg.dspace.solr.filters.ConfigureLog4jListener/listener-class /listener from the solr web.xml file sine it could not load this. Here is the info you asked for: -bash-3.2$ java -version java version 1.7.0_51 Java(TM) SE Runtime Environment (build 1.7.0_51-b13) Java HotSpot(TM) Server VM (build 24.51-b03, mixed mode) Apache Tomcat/5.5.26 OS is linux Thank you! Jose On Fri, Apr 4, 2014 at 3:40 PM, Pottinger, Hardy J. pottinge...@missouri.edu wrote: Hi, Jose, can you tell us the version numbers of the stuff in your stack? OS, Java, Tomcat? Thanks! --Hardy From: Jose Blanco [blan...@umich.edu] Sent: Friday, April 04, 2014 2:31 PM To: Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 Before this error takes place I see this in the log file: Apr 04, 2014 3:27:49 PM org.apache.catalina.loader.WebappClassLoader validateJarFile INFO: validateJarFile(/deepblue/dspace/repository/dev/webapps_dev/solr/WEB-INF/lib/jsp-api-2.1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/jsp/JspPage.class Apr 04, 2014 3:27:49 PM org.apache.catalina.startup.ContextConfig applicationWebConfig I grabbed jsp-api-2.1.jar from the web, which was a different size and I still get this error. -Jose On Fri, Apr 4, 2014 at 1:40 PM, Jose Blanco blan...@umich.edu wrote: when I try to deploy /solr with tomcat I get: log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. I've looked at the log4j files and nothing catches my eye. Thank you! Jose -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] can't get /sorl deployed in 4.1
Yes, you can try that. Maybe you need to remove the “xercesImpl” jar as well. Also, take a look in your tomcat directory for a folder named “endorsed”. There are located some of these jars that usually conflict. I think moving to Tomcat7 could be a wise choice. Regards, Kostas On Apr 4, 2014, at 11:37 PM, Jose Blanco blan...@umich.edu wrote: So you are suggesting I get rid of xml-apis-1.0.b2.jar and add listener listener-classorg.dspace. solr.filters.ConfigureLog4jListener/listener-class /listener back in? What about the version of tomcat. According to the documentation I need to have 7 but right now I have 5.5.26. Could updating tomcat resolve this problem? Thank you! Jose On Fri, Apr 4, 2014 at 4:30 PM, Kostas Stamatis kstama...@ekt.gr wrote: Hi Jose, I think your problem is more or less conflicts between some DSpace libs and some that Tomcat already has. For example, the one that you mention that you deleted, the jsp-api one, is a library that Tomcat has as well. So, lib version mismatching problem :) I think that some other libraries may conflict as well. Take a look at the XML ones (I think it is called xml-api ore something like that). Regards, Kostas On Apr 4, 2014, at 11:20 PM, Jose Blanco blan...@umich.edu wrote: Is this all because I don't have tomcat 7. -Jose On Fri, Apr 4, 2014 at 4:00 PM, Jose Blanco blan...@umich.edu wrote: I just got it deployed, but I'm not sure it's working. I got it deployed by (1) deleting jsp-api-2.1.jar from the solr lib area, since it was complaining about it. AND (2) removing listener listener-classorg.dspace.solr.filters.ConfigureLog4jListener/listener-class /listener from the solr web.xml file sine it could not load this. Here is the info you asked for: -bash-3.2$ java -version java version 1.7.0_51 Java(TM) SE Runtime Environment (build 1.7.0_51-b13) Java HotSpot(TM) Server VM (build 24.51-b03, mixed mode) Apache Tomcat/5.5.26 OS is linux Thank you! Jose On Fri, Apr 4, 2014 at 3:40 PM, Pottinger, Hardy J. pottinge...@missouri.edu wrote: Hi, Jose, can you tell us the version numbers of the stuff in your stack? OS, Java, Tomcat? Thanks! --Hardy From: Jose Blanco [blan...@umich.edu] Sent: Friday, April 04, 2014 2:31 PM To: Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 Before this error takes place I see this in the log file: Apr 04, 2014 3:27:49 PM org.apache.catalina.loader.WebappClassLoader validateJarFile INFO: validateJarFile(/deepblue/dspace/repository/dev/webapps_dev/solr/WEB-INF/lib/jsp-api-2.1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/jsp/JspPage.class Apr 04, 2014 3:27:49 PM org.apache.catalina.startup.ContextConfig applicationWebConfig I grabbed jsp-api-2.1.jar from the web, which was a different size and I still get this error. -Jose On Fri, Apr 4, 2014 at 1:40 PM, Jose Blanco blan...@umich.edu wrote: when I try to deploy /solr with tomcat I get: log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. I've looked at the log4j files and nothing catches my eye. Thank you! Jose -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] can't get /sorl deployed in 4.1
Hi, I agree with Kostas, I think moving to Tomcat 7 will resolve these issues. I suspect, given that you're using Tomcat 5.5, that you're using RHEL or CentOS 6? I'm in the process of setting up new staging and production boxes using RHEL6, Tomcat 5.5 is the best I can get with Yum, so I'm using a binary version of Tomcat 7 straight from Apache. --Hardy From: Kostas Stamatis [kstama...@ekt.gr] Sent: Friday, April 04, 2014 3:42 PM To: Jose Blanco Cc: Pottinger, Hardy J.; Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 Yes, you can try that. Maybe you need to remove the “xercesImpl” jar as well. Also, take a look in your tomcat directory for a folder named “endorsed”. There are located some of these jars that usually conflict. I think moving to Tomcat7 could be a wise choice. Regards, Kostas On Apr 4, 2014, at 11:37 PM, Jose Blanco blan...@umich.edu wrote: So you are suggesting I get rid of xml-apis-1.0.b2.jar and add listener listener-classorg.dspace. solr.filters.ConfigureLog4jListener/listener-class /listener back in? What about the version of tomcat. According to the documentation I need to have 7 but right now I have 5.5.26. Could updating tomcat resolve this problem? Thank you! Jose On Fri, Apr 4, 2014 at 4:30 PM, Kostas Stamatis kstama...@ekt.gr wrote: Hi Jose, I think your problem is more or less conflicts between some DSpace libs and some that Tomcat already has. For example, the one that you mention that you deleted, the jsp-api one, is a library that Tomcat has as well. So, lib version mismatching problem :) I think that some other libraries may conflict as well. Take a look at the XML ones (I think it is called xml-api ore something like that). Regards, Kostas On Apr 4, 2014, at 11:20 PM, Jose Blanco blan...@umich.edu wrote: Is this all because I don't have tomcat 7. -Jose On Fri, Apr 4, 2014 at 4:00 PM, Jose Blanco blan...@umich.edu wrote: I just got it deployed, but I'm not sure it's working. I got it deployed by (1) deleting jsp-api-2.1.jar from the solr lib area, since it was complaining about it. AND (2) removing listener listener-classorg.dspace.solr.filters.ConfigureLog4jListener/listener-class /listener from the solr web.xml file sine it could not load this. Here is the info you asked for: -bash-3.2$ java -version java version 1.7.0_51 Java(TM) SE Runtime Environment (build 1.7.0_51-b13) Java HotSpot(TM) Server VM (build 24.51-b03, mixed mode) Apache Tomcat/5.5.26 OS is linux Thank you! Jose On Fri, Apr 4, 2014 at 3:40 PM, Pottinger, Hardy J. pottinge...@missouri.edu wrote: Hi, Jose, can you tell us the version numbers of the stuff in your stack? OS, Java, Tomcat? Thanks! --Hardy From: Jose Blanco [blan...@umich.edu] Sent: Friday, April 04, 2014 2:31 PM To: Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 Before this error takes place I see this in the log file: Apr 04, 2014 3:27:49 PM org.apache.catalina.loader.WebappClassLoader validateJarFile INFO: validateJarFile(/deepblue/dspace/repository/dev/webapps_dev/solr/WEB-INF/lib/jsp-api-2.1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/jsp/JspPage.class Apr 04, 2014 3:27:49 PM org.apache.catalina.startup.ContextConfig applicationWebConfig I grabbed jsp-api-2.1.jar from the web, which was a different size and I still get this error. -Jose On Fri, Apr 4, 2014 at 1:40 PM, Jose Blanco blan...@umich.edu wrote: when I try to deploy /solr with tomcat I get: log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. I've looked at the log4j files and nothing catches my eye. Thank you! Jose -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette:
Re: [Dspace-tech] can't get /sorl deployed in 4.1
Hi, here's some of the back and forth from the dspace-devel archive: http://sourceforge.net/p/dspace/mailman/message/31032016/ From: Jose Blanco [blan...@umich.edu] Sent: Friday, April 04, 2014 3:54 PM To: Pottinger, Hardy J. Cc: Kostas Stamatis; Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 Do you know why version dspace 4.1 now requires tomcat 7? Someone here told me that solr is doesn't really needed it? Is it for another dspace webapp that needs 7. I just want to understand the reason for 7. I'm hoping it has to do with solr, because that would explain the problem I'm seeing. Manakin seems to work fine with the tomcat I have. Thank you! Jose On Fri, Apr 4, 2014 at 4:48 PM, Pottinger, Hardy J. pottinge...@missouri.edu wrote: Hi, I agree with Kostas, I think moving to Tomcat 7 will resolve these issues. I suspect, given that you're using Tomcat 5.5, that you're using RHEL or CentOS 6? I'm in the process of setting up new staging and production boxes using RHEL6, Tomcat 5.5 is the best I can get with Yum, so I'm using a binary version of Tomcat 7 straight from Apache. --Hardy From: Kostas Stamatis [kstama...@ekt.gr] Sent: Friday, April 04, 2014 3:42 PM To: Jose Blanco Cc: Pottinger, Hardy J.; Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 Yes, you can try that. Maybe you need to remove the xercesImpl jar as well. Also, take a look in your tomcat directory for a folder named endorsed. There are located some of these jars that usually conflict. I think moving to Tomcat7 could be a wise choice. Regards, Kostas On Apr 4, 2014, at 11:37 PM, Jose Blanco blan...@umich.edu wrote: So you are suggesting I get rid of xml-apis-1.0.b2.jar and add listener listener-classorg.dspace. solr.filters.ConfigureLog4jListener/listener-class /listener back in? What about the version of tomcat. According to the documentation I need to have 7 but right now I have 5.5.26. Could updating tomcat resolve this problem? Thank you! Jose On Fri, Apr 4, 2014 at 4:30 PM, Kostas Stamatis kstama...@ekt.gr wrote: Hi Jose, I think your problem is more or less conflicts between some DSpace libs and some that Tomcat already has. For example, the one that you mention that you deleted, the jsp-api one, is a library that Tomcat has as well. So, lib version mismatching problem :) I think that some other libraries may conflict as well. Take a look at the XML ones (I think it is called xml-api ore something like that). Regards, Kostas On Apr 4, 2014, at 11:20 PM, Jose Blanco blan...@umich.edu wrote: Is this all because I don't have tomcat 7. -Jose On Fri, Apr 4, 2014 at 4:00 PM, Jose Blanco blan...@umich.edu wrote: I just got it deployed, but I'm not sure it's working. I got it deployed by (1) deleting jsp-api-2.1.jar from the solr lib area, since it was complaining about it. AND (2) removing listener listener-classorg.dspace.solr.filters.ConfigureLog4jListener/listener-class /listener from the solr web.xml file sine it could not load this. Here is the info you asked for: -bash-3.2$ java -version java version 1.7.0_51 Java(TM) SE Runtime Environment (build 1.7.0_51-b13) Java HotSpot(TM) Server VM (build 24.51-b03, mixed mode) Apache Tomcat/5.5.26 OS is linux Thank you! Jose On Fri, Apr 4, 2014 at 3:40 PM, Pottinger, Hardy J. pottinge...@missouri.edu wrote: Hi, Jose, can you tell us the version numbers of the stuff in your stack? OS, Java, Tomcat? Thanks! --Hardy From: Jose Blanco [blan...@umich.edu] Sent: Friday, April 04, 2014 2:31 PM To: Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 Before this error takes place I see this in the log file: Apr 04, 2014 3:27:49 PM org.apache.catalina.loader.WebappClassLoader validateJarFile INFO: validateJarFile(/deepblue/dspace/repository/dev/webapps_dev/solr/WEB-INF/lib/jsp-api-2.1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/jsp/JspPage.class Apr 04, 2014 3:27:49 PM org.apache.catalina.startup.ContextConfig applicationWebConfig I grabbed jsp-api-2.1.jar from the web, which was a different size and I still get this error. -Jose On Fri, Apr 4, 2014 at 1:40 PM, Jose Blanco blan...@umich.edu wrote: when I try to deploy /solr with tomcat I get: log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. I've looked at the log4j files and nothing catches my eye. Thank you! Jose -- ___ DSpace-tech mailing list
Re: [Dspace-tech] can't get /sorl deployed in 4.1
Do you know why version dspace 4.1 now requires tomcat 7? Someone here told me that solr is doesn't really needed it? Is it for another dspace webapp that needs 7. I just want to understand the reason for 7. I'm hoping it has to do with solr, because that would explain the problem I'm seeing. Manakin seems to work fine with the tomcat I have. Thank you! Jose On Fri, Apr 4, 2014 at 4:48 PM, Pottinger, Hardy J. pottinge...@missouri.edu wrote: Hi, I agree with Kostas, I think moving to Tomcat 7 will resolve these issues. I suspect, given that you're using Tomcat 5.5, that you're using RHEL or CentOS 6? I'm in the process of setting up new staging and production boxes using RHEL6, Tomcat 5.5 is the best I can get with Yum, so I'm using a binary version of Tomcat 7 straight from Apache. --Hardy From: Kostas Stamatis [kstama...@ekt.gr] Sent: Friday, April 04, 2014 3:42 PM To: Jose Blanco Cc: Pottinger, Hardy J.; Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 Yes, you can try that. Maybe you need to remove the xercesImpl jar as well. Also, take a look in your tomcat directory for a folder named endorsed. There are located some of these jars that usually conflict. I think moving to Tomcat7 could be a wise choice. Regards, Kostas On Apr 4, 2014, at 11:37 PM, Jose Blanco blan...@umich.edu wrote: So you are suggesting I get rid of xml-apis-1.0.b2.jar and add listener listener-classorg.dspace. solr.filters.ConfigureLog4jListener/listener-class /listener back in? What about the version of tomcat. According to the documentation I need to have 7 but right now I have 5.5.26. Could updating tomcat resolve this problem? Thank you! Jose On Fri, Apr 4, 2014 at 4:30 PM, Kostas Stamatis kstama...@ekt.gr wrote: Hi Jose, I think your problem is more or less conflicts between some DSpace libs and some that Tomcat already has. For example, the one that you mention that you deleted, the jsp-api one, is a library that Tomcat has as well. So, lib version mismatching problem :) I think that some other libraries may conflict as well. Take a look at the XML ones (I think it is called xml-api ore something like that). Regards, Kostas On Apr 4, 2014, at 11:20 PM, Jose Blanco blan...@umich.edu wrote: Is this all because I don't have tomcat 7. -Jose On Fri, Apr 4, 2014 at 4:00 PM, Jose Blanco blan...@umich.edu wrote: I just got it deployed, but I'm not sure it's working. I got it deployed by (1) deleting jsp-api-2.1.jar from the solr lib area, since it was complaining about it. AND (2) removing listener listener-classorg.dspace.solr.filters.ConfigureLog4jListener/listener-class /listener from the solr web.xml file sine it could not load this. Here is the info you asked for: -bash-3.2$ java -version java version 1.7.0_51 Java(TM) SE Runtime Environment (build 1.7.0_51-b13) Java HotSpot(TM) Server VM (build 24.51-b03, mixed mode) Apache Tomcat/5.5.26 OS is linux Thank you! Jose On Fri, Apr 4, 2014 at 3:40 PM, Pottinger, Hardy J. pottinge...@missouri.edu wrote: Hi, Jose, can you tell us the version numbers of the stuff in your stack? OS, Java, Tomcat? Thanks! --Hardy From: Jose Blanco [blan...@umich.edu] Sent: Friday, April 04, 2014 2:31 PM To: Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 Before this error takes place I see this in the log file: Apr 04, 2014 3:27:49 PM org.apache.catalina.loader.WebappClassLoader validateJarFile INFO: validateJarFile(/deepblue/dspace/repository/dev/webapps_dev/solr/WEB-INF/lib/jsp-api-2.1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/jsp/JspPage.class Apr 04, 2014 3:27:49 PM org.apache.catalina.startup.ContextConfig applicationWebConfig I grabbed jsp-api-2.1.jar from the web, which was a different size and I still get this error. -Jose On Fri, Apr 4, 2014 at 1:40 PM, Jose Blanco blan...@umich.edu wrote: when I try to deploy /solr with tomcat I get: log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. I've looked at the log4j files and nothing catches my eye. Thank you! Jose -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list
Re: [Dspace-tech] can't get /sorl deployed in 4.1
Thank you for the link. It sounds like solr uses some jars that can only be loaded with tomcat 7 and higher, like jsp-api-2.1.jar, and so we need to go to tomcat 7 for this reason. Right? I want to be able to explain this clearly to the sysadmin that will be installing tomcat 7. The new solr must have a UI interface, is that right? Thank you, again! Jose On Fri, Apr 4, 2014 at 5:12 PM, Pottinger, Hardy J. pottinge...@missouri.edu wrote: Hi, here's some of the back and forth from the dspace-devel archive: http://sourceforge.net/p/dspace/mailman/message/31032016/ From: Jose Blanco [blan...@umich.edu] Sent: Friday, April 04, 2014 3:54 PM To: Pottinger, Hardy J. Cc: Kostas Stamatis; Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 Do you know why version dspace 4.1 now requires tomcat 7? Someone here told me that solr is doesn't really needed it? Is it for another dspace webapp that needs 7. I just want to understand the reason for 7. I'm hoping it has to do with solr, because that would explain the problem I'm seeing. Manakin seems to work fine with the tomcat I have. Thank you! Jose On Fri, Apr 4, 2014 at 4:48 PM, Pottinger, Hardy J. pottinge...@missouri.edu wrote: Hi, I agree with Kostas, I think moving to Tomcat 7 will resolve these issues. I suspect, given that you're using Tomcat 5.5, that you're using RHEL or CentOS 6? I'm in the process of setting up new staging and production boxes using RHEL6, Tomcat 5.5 is the best I can get with Yum, so I'm using a binary version of Tomcat 7 straight from Apache. --Hardy From: Kostas Stamatis [kstama...@ekt.gr] Sent: Friday, April 04, 2014 3:42 PM To: Jose Blanco Cc: Pottinger, Hardy J.; Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 Yes, you can try that. Maybe you need to remove the xercesImpl jar as well. Also, take a look in your tomcat directory for a folder named endorsed. There are located some of these jars that usually conflict. I think moving to Tomcat7 could be a wise choice. Regards, Kostas On Apr 4, 2014, at 11:37 PM, Jose Blanco blan...@umich.edu wrote: So you are suggesting I get rid of xml-apis-1.0.b2.jar and add listener listener-classorg.dspace. solr.filters.ConfigureLog4jListener/listener-class /listener back in? What about the version of tomcat. According to the documentation I need to have 7 but right now I have 5.5.26. Could updating tomcat resolve this problem? Thank you! Jose On Fri, Apr 4, 2014 at 4:30 PM, Kostas Stamatis kstama...@ekt.gr wrote: Hi Jose, I think your problem is more or less conflicts between some DSpace libs and some that Tomcat already has. For example, the one that you mention that you deleted, the jsp-api one, is a library that Tomcat has as well. So, lib version mismatching problem :) I think that some other libraries may conflict as well. Take a look at the XML ones (I think it is called xml-api ore something like that). Regards, Kostas On Apr 4, 2014, at 11:20 PM, Jose Blanco blan...@umich.edu wrote: Is this all because I don't have tomcat 7. -Jose On Fri, Apr 4, 2014 at 4:00 PM, Jose Blanco blan...@umich.edu wrote: I just got it deployed, but I'm not sure it's working. I got it deployed by (1) deleting jsp-api-2.1.jar from the solr lib area, since it was complaining about it. AND (2) removing listener listener-classorg.dspace.solr.filters.ConfigureLog4jListener/listener-class /listener from the solr web.xml file sine it could not load this. Here is the info you asked for: -bash-3.2$ java -version java version 1.7.0_51 Java(TM) SE Runtime Environment (build 1.7.0_51-b13) Java HotSpot(TM) Server VM (build 24.51-b03, mixed mode) Apache Tomcat/5.5.26 OS is linux Thank you! Jose On Fri, Apr 4, 2014 at 3:40 PM, Pottinger, Hardy J. pottinge...@missouri.edu wrote: Hi, Jose, can you tell us the version numbers of the stuff in your stack? OS, Java, Tomcat? Thanks! --Hardy From: Jose Blanco [blan...@umich.edu] Sent: Friday, April 04, 2014 2:31 PM To: Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 Before this error takes place I see this in the log file: Apr 04, 2014 3:27:49 PM org.apache.catalina.loader.WebappClassLoader validateJarFile INFO: validateJarFile(/deepblue/dspace/repository/dev/webapps_dev/solr/WEB-INF/lib/jsp-api-2.1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/jsp/JspPage.class Apr 04, 2014 3:27:49 PM org.apache.catalina.startup.ContextConfig applicationWebConfig I grabbed jsp-api-2.1.jar from the web, which was a different size and I still get this error. -Jose On Fri, Apr 4, 2014 at 1:40 PM, Jose Blanco blan...@umich.edu wrote: when I try to deploy /solr with tomcat I get: log4j:WARN No
Re: [Dspace-tech] can't get /sorl deployed in 4.1
I think the primary argument for bumping up the DSpace-recommended Tomcat version, as explained by Mark Wood in that attached mail list thread, is that Tomcat 5.5 will very shortly be EOL. You really don't want to be building a brand new server on top of an EOL stack. I'm certain your sysadmin will understand that. Now, if they balk at doing a binary install of Tomcat7, you can always ask them to move to CentOS6 (I understand CentOS has Tomcat 6 in its Yum repositories). OR, you can always move to JBoss--which is the RedHat way of doing a Java servlet container, and is probably why RH is falling behind on supporting a recent-enough version of Tomcat (note, that's just a guess, I wouldn't dream of speaking for RH). --Hardy From: Jose Blanco [blan...@umich.edu] Sent: Friday, April 04, 2014 4:26 PM To: Pottinger, Hardy J. Cc: Kostas Stamatis; Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 Thank you for the link. It sounds like solr uses some jars that can only be loaded with tomcat 7 and higher, like jsp-api-2.1.jar, and so we need to go to tomcat 7 for this reason. Right? I want to be able to explain this clearly to the sysadmin that will be installing tomcat 7. The new solr must have a UI interface, is that right? Thank you, again! Jose On Fri, Apr 4, 2014 at 5:12 PM, Pottinger, Hardy J. pottinge...@missouri.edu wrote: Hi, here's some of the back and forth from the dspace-devel archive: http://sourceforge.net/p/dspace/mailman/message/31032016/ From: Jose Blanco [blan...@umich.edu] Sent: Friday, April 04, 2014 3:54 PM To: Pottinger, Hardy J. Cc: Kostas Stamatis; Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 Do you know why version dspace 4.1 now requires tomcat 7? Someone here told me that solr is doesn't really needed it? Is it for another dspace webapp that needs 7. I just want to understand the reason for 7. I'm hoping it has to do with solr, because that would explain the problem I'm seeing. Manakin seems to work fine with the tomcat I have. Thank you! Jose On Fri, Apr 4, 2014 at 4:48 PM, Pottinger, Hardy J. pottinge...@missouri.edu wrote: Hi, I agree with Kostas, I think moving to Tomcat 7 will resolve these issues. I suspect, given that you're using Tomcat 5.5, that you're using RHEL or CentOS 6? I'm in the process of setting up new staging and production boxes using RHEL6, Tomcat 5.5 is the best I can get with Yum, so I'm using a binary version of Tomcat 7 straight from Apache. --Hardy From: Kostas Stamatis [kstama...@ekt.gr] Sent: Friday, April 04, 2014 3:42 PM To: Jose Blanco Cc: Pottinger, Hardy J.; Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 Yes, you can try that. Maybe you need to remove the xercesImpl jar as well. Also, take a look in your tomcat directory for a folder named endorsed. There are located some of these jars that usually conflict. I think moving to Tomcat7 could be a wise choice. Regards, Kostas On Apr 4, 2014, at 11:37 PM, Jose Blanco blan...@umich.edu wrote: So you are suggesting I get rid of xml-apis-1.0.b2.jar and add listener listener-classorg.dspace. solr.filters.ConfigureLog4jListener/listener-class /listener back in? What about the version of tomcat. According to the documentation I need to have 7 but right now I have 5.5.26. Could updating tomcat resolve this problem? Thank you! Jose On Fri, Apr 4, 2014 at 4:30 PM, Kostas Stamatis kstama...@ekt.gr wrote: Hi Jose, I think your problem is more or less conflicts between some DSpace libs and some that Tomcat already has. For example, the one that you mention that you deleted, the jsp-api one, is a library that Tomcat has as well. So, lib version mismatching problem :) I think that some other libraries may conflict as well. Take a look at the XML ones (I think it is called xml-api ore something like that). Regards, Kostas On Apr 4, 2014, at 11:20 PM, Jose Blanco blan...@umich.edu wrote: Is this all because I don't have tomcat 7. -Jose On Fri, Apr 4, 2014 at 4:00 PM, Jose Blanco blan...@umich.edu wrote: I just got it deployed, but I'm not sure it's working. I got it deployed by (1) deleting jsp-api-2.1.jar from the solr lib area, since it was complaining about it. AND (2) removing listener listener-classorg.dspace.solr.filters.ConfigureLog4jListener/listener-class /listener from the solr web.xml file sine it could not load this. Here is the info you asked for: -bash-3.2$ java -version java version 1.7.0_51 Java(TM) SE Runtime Environment (build 1.7.0_51-b13) Java HotSpot(TM) Server VM (build 24.51-b03, mixed mode) Apache Tomcat/5.5.26 OS is linux Thank you! Jose On Fri, Apr 4, 2014 at 3:40 PM, Pottinger, Hardy J. pottinge...@missouri.edu wrote: Hi, Jose, can you
Re: [Dspace-tech] can't get /sorl deployed in 4.1
It looks like Tomcat 5.5 is already considered end-of-life: https://tomcat.apache.org/tomcat-55-eol.html In general, when something becomes end-of-life (Java, Tomcat, etc), the DSpace Committers stop testing on it. Therefore, DSpace 4.x is completely untested on Tomcat 5.5 (and we cannot guarantee stability on that version of Tomcat). So, really, it's best to upgrade your Tomcat to ensure the stability of DSpace 4. - Tim On 4/4/2014 4:38 PM, Pottinger, Hardy J. wrote: I think the primary argument for bumping up the DSpace-recommended Tomcat version, as explained by Mark Wood in that attached mail list thread, is that Tomcat 5.5 will very shortly be EOL. You really don't want to be building a brand new server on top of an EOL stack. I'm certain your sysadmin will understand that. Now, if they balk at doing a binary install of Tomcat7, you can always ask them to move to CentOS6 (I understand CentOS has Tomcat 6 in its Yum repositories). OR, you can always move to JBoss--which is the RedHat way of doing a Java servlet container, and is probably why RH is falling behind on supporting a recent-enough version of Tomcat (note, that's just a guess, I wouldn't dream of speaking for RH). --Hardy From: Jose Blanco [blan...@umich.edu] Sent: Friday, April 04, 2014 4:26 PM To: Pottinger, Hardy J. Cc: Kostas Stamatis; Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 Thank you for the link. It sounds like solr uses some jars that can only be loaded with tomcat 7 and higher, like jsp-api-2.1.jar, and so we need to go to tomcat 7 for this reason. Right? I want to be able to explain this clearly to the sysadmin that will be installing tomcat 7. The new solr must have a UI interface, is that right? Thank you, again! Jose On Fri, Apr 4, 2014 at 5:12 PM, Pottinger, Hardy J. pottinge...@missouri.edu wrote: Hi, here's some of the back and forth from the dspace-devel archive: http://sourceforge.net/p/dspace/mailman/message/31032016/ From: Jose Blanco [blan...@umich.edu] Sent: Friday, April 04, 2014 3:54 PM To: Pottinger, Hardy J. Cc: Kostas Stamatis; Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 Do you know why version dspace 4.1 now requires tomcat 7? Someone here told me that solr is doesn't really needed it? Is it for another dspace webapp that needs 7. I just want to understand the reason for 7. I'm hoping it has to do with solr, because that would explain the problem I'm seeing. Manakin seems to work fine with the tomcat I have. Thank you! Jose On Fri, Apr 4, 2014 at 4:48 PM, Pottinger, Hardy J. pottinge...@missouri.edu wrote: Hi, I agree with Kostas, I think moving to Tomcat 7 will resolve these issues. I suspect, given that you're using Tomcat 5.5, that you're using RHEL or CentOS 6? I'm in the process of setting up new staging and production boxes using RHEL6, Tomcat 5.5 is the best I can get with Yum, so I'm using a binary version of Tomcat 7 straight from Apache. --Hardy From: Kostas Stamatis [kstama...@ekt.gr] Sent: Friday, April 04, 2014 3:42 PM To: Jose Blanco Cc: Pottinger, Hardy J.; Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 Yes, you can try that. Maybe you need to remove the xercesImpl jar as well. Also, take a look in your tomcat directory for a folder named endorsed. There are located some of these jars that usually conflict. I think moving to Tomcat7 could be a wise choice. Regards, Kostas On Apr 4, 2014, at 11:37 PM, Jose Blanco blan...@umich.edu wrote: So you are suggesting I get rid of xml-apis-1.0.b2.jar and add listener listener-classorg.dspace. solr.filters.ConfigureLog4jListener/listener-class /listener back in? What about the version of tomcat. According to the documentation I need to have 7 but right now I have 5.5.26. Could updating tomcat resolve this problem? Thank you! Jose On Fri, Apr 4, 2014 at 4:30 PM, Kostas Stamatis kstama...@ekt.gr wrote: Hi Jose, I think your problem is more or less conflicts between some DSpace libs and some that Tomcat already has. For example, the one that you mention that you deleted, the jsp-api one, is a library that Tomcat has as well. So, lib version mismatching problem :) I think that some other libraries may conflict as well. Take a look at the XML ones (I think it is called xml-api ore something like that). Regards, Kostas On Apr 4, 2014, at 11:20 PM, Jose Blanco blan...@umich.edu wrote: Is this all because I don't have tomcat 7. -Jose On Fri, Apr 4, 2014 at 4:00 PM, Jose Blanco blan...@umich.edu wrote: I just got it deployed, but I'm not sure it's working. I got it deployed by (1) deleting jsp-api-2.1.jar from the solr lib area, since it was complaining about it. AND (2) removing listener
Re: [Dspace-tech] can't get /sorl deployed in 4.1
Hi, Jose, if you do elect to move to a binary install of Tomcat 7 on RHEL6, this init script might come in handy: https://gist.github.com/hardyoyo/9903387 --Hardy From: Tim Donohue [tdono...@duraspace.org] Sent: Friday, April 04, 2014 4:48 PM To: Pottinger, Hardy J.; Jose Blanco Cc: Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 It looks like Tomcat 5.5 is already considered end-of-life: https://tomcat.apache.org/tomcat-55-eol.html In general, when something becomes end-of-life (Java, Tomcat, etc), the DSpace Committers stop testing on it. Therefore, DSpace 4.x is completely untested on Tomcat 5.5 (and we cannot guarantee stability on that version of Tomcat). So, really, it's best to upgrade your Tomcat to ensure the stability of DSpace 4. - Tim On 4/4/2014 4:38 PM, Pottinger, Hardy J. wrote: I think the primary argument for bumping up the DSpace-recommended Tomcat version, as explained by Mark Wood in that attached mail list thread, is that Tomcat 5.5 will very shortly be EOL. You really don't want to be building a brand new server on top of an EOL stack. I'm certain your sysadmin will understand that. Now, if they balk at doing a binary install of Tomcat7, you can always ask them to move to CentOS6 (I understand CentOS has Tomcat 6 in its Yum repositories). OR, you can always move to JBoss--which is the RedHat way of doing a Java servlet container, and is probably why RH is falling behind on supporting a recent-enough version of Tomcat (note, that's just a guess, I wouldn't dream of speaking for RH). --Hardy From: Jose Blanco [blan...@umich.edu] Sent: Friday, April 04, 2014 4:26 PM To: Pottinger, Hardy J. Cc: Kostas Stamatis; Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 Thank you for the link. It sounds like solr uses some jars that can only be loaded with tomcat 7 and higher, like jsp-api-2.1.jar, and so we need to go to tomcat 7 for this reason. Right? I want to be able to explain this clearly to the sysadmin that will be installing tomcat 7. The new solr must have a UI interface, is that right? Thank you, again! Jose On Fri, Apr 4, 2014 at 5:12 PM, Pottinger, Hardy J. pottinge...@missouri.edu wrote: Hi, here's some of the back and forth from the dspace-devel archive: http://sourceforge.net/p/dspace/mailman/message/31032016/ From: Jose Blanco [blan...@umich.edu] Sent: Friday, April 04, 2014 3:54 PM To: Pottinger, Hardy J. Cc: Kostas Stamatis; Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 Do you know why version dspace 4.1 now requires tomcat 7? Someone here told me that solr is doesn't really needed it? Is it for another dspace webapp that needs 7. I just want to understand the reason for 7. I'm hoping it has to do with solr, because that would explain the problem I'm seeing. Manakin seems to work fine with the tomcat I have. Thank you! Jose On Fri, Apr 4, 2014 at 4:48 PM, Pottinger, Hardy J. pottinge...@missouri.edu wrote: Hi, I agree with Kostas, I think moving to Tomcat 7 will resolve these issues. I suspect, given that you're using Tomcat 5.5, that you're using RHEL or CentOS 6? I'm in the process of setting up new staging and production boxes using RHEL6, Tomcat 5.5 is the best I can get with Yum, so I'm using a binary version of Tomcat 7 straight from Apache. --Hardy From: Kostas Stamatis [kstama...@ekt.gr] Sent: Friday, April 04, 2014 3:42 PM To: Jose Blanco Cc: Pottinger, Hardy J.; Dspace-Tech Subject: Re: [Dspace-tech] can't get /sorl deployed in 4.1 Yes, you can try that. Maybe you need to remove the xercesImpl jar as well. Also, take a look in your tomcat directory for a folder named endorsed. There are located some of these jars that usually conflict. I think moving to Tomcat7 could be a wise choice. Regards, Kostas On Apr 4, 2014, at 11:37 PM, Jose Blanco blan...@umich.edu wrote: So you are suggesting I get rid of xml-apis-1.0.b2.jar and add listener listener-classorg.dspace. solr.filters.ConfigureLog4jListener/listener-class /listener back in? What about the version of tomcat. According to the documentation I need to have 7 but right now I have 5.5.26. Could updating tomcat resolve this problem? Thank you! Jose On Fri, Apr 4, 2014 at 4:30 PM, Kostas Stamatis kstama...@ekt.gr wrote: Hi Jose, I think your problem is more or less conflicts between some DSpace libs and some that Tomcat already has. For example, the one that you mention that you deleted, the jsp-api one, is a library that Tomcat has as well. So, lib version mismatching problem :) I think that some other libraries may conflict as well. Take a look at the XML ones (I think it is called xml-api ore something like that). Regards,
