Our operating system is: Solaris 10 (SunOS 5.10)
And java version is: java version "1.5.0_12" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode) I tried some stuff with our test instance, and have somehow got it to replicate the same problem (but don't ask me how). Thanks Jennifer Jennifer Whalan Systems Support Officer Innovation & Access, Northern Territory Library Department of Natural Resources, Environment, The Arts and Sport Northern Territory Government Phone: (08) 8922 0757 Fax: (08) 8922 0722 Email: [email protected] Web: www.ntl.nt.gov.au The information contained in this message and any attachments may be confidential information and may be subject to legal privilege, public interest or legal profession privilege. If you are not the intended recipient, any use, disclosure or copying of this message or any attachments is unauthorised. If you have received this document in error, please advise the sender. No representation or warranty is given that attached files are free from viruses or other defects. The recipient assumes all responsibility for any loss or damage resulting directly or indirectly from the use of any attached files. -----Original Message----- From: Mark Diggory [mailto:[email protected]] Sent: Tuesday, 30 June 2009 3:34 PM To: Jennifer Whalan Cc: [email protected]; Paulo Jobim Subject: Re: [Dspace-tech] Funny things with upgrading 1.5.1 to 1.5.2 Jennifer, This is the second time I've observed someone having this issue. Paulo Jobim was the first. Paulo, did you come to a resolution on this issue? On Mon, Jun 29, 2009 at 8:45 PM, Jennifer Whalan<[email protected]> wrote: > but that 1.5.2 doesn't and seems to use DSpaceCocoonServletFilter > instead(?)\ Correct, DSpace 1.5.2 requires a different configuration in its web.xml than 1.5.1 You should not use the 1.5.1 web.xml in your 1.5.2 xmlui installation. > After playing around a bit more, moving files here and there, finally > I received no more errors and could view the webpage. However it turns > out that all I did was return the xmlui/WEB-INF folder to its exact > state before upgrading to 1.5.2, so that technically the site was > still running on 1.5.1 code. This is true, you are not runnning 1.5.2 XMLUI. > What I would like is any assistance if possible, as to why I would get > this error on one instance of dspace, after another instance had been > upgraded properly. > > To go through my processes for upgrading: > > ran mvn package in src/dspace-1.5.2-src-release turned off tomcat > (which by the way, both instances of dspace are using the same > instance of tomcat) ran ant update in > src/dspace-1.5.2-src-release/dspace/target/dspace-1.5.2-build.dir > ran ant update_configs in > src/dspace-1.5.2-src-release/dspace/target/dspace-1.5.2-build.dir > (which is > redudant?) > restarted tomcat Can you give me more details on your platform? Java Vendor Version and Operating System. I would like to try to find a way to replicate the issue so we can verify if it is a bug or not. I've seen some comments about URL Protocol handlers on different OS and I'm trying to determine what the issue may be. Cheers, Mark -- Mark R. Diggory @mire - http://www.atmire.com ------------------------------------------------------------------------------ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
