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-class>org.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-class>org.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

Reply via email to