Re: [Dspace-tech] Tomcat 501 error during SWORD deposit
That did it. Thanks, Stuart! Jason Stuart Lewis s.le...@auckland.ac.nz 1/7/2010 5:48 PM Hi Jason, Try following the upgrade step 14 from the DSpace 15 upgrade instructions. This should insert any missing metadata elements for you. • Update the Metadata Registry New Metadata Registry updates are required to support SWORD. cp [dspace-source]/dspace/config/registries/sword-metadata.xml [dspace]/config/registries/sword-metadata.xml; [dspace]/bin/dsrun org.dspace.administer.MetadataImporter -f [dspace]/config/registries/sword-metadata.xml Thanks, Stuart Lewis IT Innovations Analyst and Developer Te Tumu Herenga The University of Auckland Library Auckland Mail Centre, Private Bag 92019, Auckland 1142, New Zealand Ph: 64 9 373-7599 x81928 http://www.library.auckland.ac.nz/ On 8/01/2010, at 12:24 PM, Jason Stirnaman wrote: OK, so I dialed up the DSpace logs and problem seems to be bad metadata in the SQL. Is this a Facebook SWORD app problem or a DSpace SWORD problem? 2010-01-07 17:19:29,297 WARN org.dspace.content.Item @ stirnam...@gmail.com:session_id=0:ip_addr=10.2.104.25:bad_dc:Bad DC field. schema=dc, element\colon; rights qualifier\colon; holder value\colon; jason stirnaman 2010-01-07 17:19:29,297 ERROR org.dspace.sword.SWORDMETSIngester @ caught exception: java.sql.SQLException: bad_dublin_core schema=dc, rights holder at org.dspace.content.Item.update(Item.java:1550) at org.dspace.content.WorkspaceItem.update(WorkspaceItem.java:511) at org.dspace.content.packager.AbstractMETSIngester.ingest(AbstractMETSIngester.java:454) at org.dspace.sword.SWORDMETSIngester.ingest(SWORDMETSIngester.java:115) at org.dspace.sword.CollectionDepositor.doDeposit(CollectionDepositor.java:179) at org.dspace.sword.DepositManager.deposit(DepositManager.java:173) at org.dspace.sword.DSpaceSWORDServer.doDeposit(DSpaceSWORDServer.java:150) at org.purl.sword.server.DepositServlet.doPost(DepositServlet.java:331) at javax.servlet.http.HttpServlet.service(HttpServlet.java:647) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:875) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) at java.lang.Thread.run(Thread.java:595) 2010-01-07 17:19:29,298 ERROR org.dspace.sword.DSpaceSWORDServer @ caught exception: org.dspace.sword.DSpaceSWORDException: java.sql.SQLException: bad_dublin_core schema=dc, rights holder at org.dspace.sword.SWORDMETSIngester.ingest(SWORDMETSIngester.java:171) at org.dspace.sword.CollectionDepositor.doDeposit(CollectionDepositor.java:179) at org.dspace.sword.DepositManager.deposit(DepositManager.java:173) at org.dspace.sword.DSpaceSWORDServer.doDeposit(DSpaceSWORDServer.java:150) at org.purl.sword.server.DepositServlet.doPost(DepositServlet.java:331) at javax.servlet.http.HttpServlet.service(HttpServlet.java:647) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at
Re: [Dspace-tech] Problem with authorization error display in DSpace 1.5.1 - SOLVED
I just wanted to let everyone know that I finally solved this problem by commenting out the following line in /error/authorize.jsp: %@ page isErrorPage=true % I also had to do it in the other error JSPs in order for them to be correctly displayed when the corresponding error occurred (invalid-id, integrity, 404, etc). This is actually great because it corrects the display of an Internal Server Error when a User types or clicks on a bad link for a handle. Now the correct error message displays, indicating: Invalid Identifier The identifier 2122/35e8e8e does not correspond to a valid Object.. Now I'm wondering if other folks have had this problem and, if so, should this be considered a bug and be corrected in a future release? Thanks, Sue Walker-Thornton NASA Langley Research Center, Hampton, VA 23666 757-224-4074 From: Thornton, Susan M. (LARC-B702)[RAYTHEON TECHNICAL SERVICES COMPANY] [mailto:susan.m.thorn...@nasa.gov] Sent: Tuesday, January 05, 2010 12:50 PM To: dspace-tech@lists.sourceforge.net Subject: [Dspace-tech] Problem with authorization error display in DSpace 1.5.1 In a DSpace instance where we have some secure collections that are only viewable by certain epersongroups, we are not getting the correct message when a User clicks on an item they do *not* have access to. Instead of getting the authorize.jsp screen, we are getting the internal.jsp screen where the standard server error message displays. I've tracked this down and here's what I've found: 1. In org.dspace.app.webui.util.JSPManager.showAuthorizeError, the line that says response.setStatus(HttpServletResponse.SC_FORBIDDEN); correctly sets the response status code to 403 (Forbidden). 2. org.dspace.app.webui.util.JSPManager.showJSP is then executed with parameters (request, response, /error/authorize.jsp) 3. request.getRequestDispatcher(jsp).forward(request, response); is then executed. 4. org.apache.jsp.error.authorize.jsp then gets a java.lang.NullPointerException error on this line: response.setStatus(((Integer)request.getAttribute(javax.servlet.error.status_code)).intValue()); It appears that when the code in line 4 gets executed, javax.servlet.error.status_code is null and that's why it's getting a java.lang.NullPointerException error, so I'm not sure where the status code 403 is being lost. The strange thing is that we have another DSpace instance where the auth. error displays just fine. In this instance, we have the same DSpace version installed (1.5.1), however there is a different Java version on this machine: java version 1.6.0_07 Java(TM) SE Runtime Environment (build 1.6.0_07-b06) Java HotSpot(TM) Server VM (build 10.0-b23, mixed mode) The version of Java on the machine where we're having the problem is: java version 1.5.0_18 Java(TM) Platform, Standard Edition for Business (build 1.5.0_18-b02) Java HotSpot(TM) Server VM (build 1.5.0_18-b02, mixed mode) Is it possible that the difference in the Java versions is causing our problem? I'm thinking maybe this is the answer because when I look at org.apache.jsp.error.authorize.jsp.java on each machine, they are very different. I saw somewhere too that if no authorization response code is passed in, a general error message will display (can't remember where I saw that). I know this is a lot of detail, but I sure would appreciate any help if anyone has the time. Thanks in advance, Sue Sue Walker-Thornton ConITS Contract NASA Langley Research Center Integrated Library Systems Application Database Administrator 130 Research Drive Hampton, VA 23666 Office: (757) 224-4074 Fax:(757) 224-4001 Mobile: (757) 506-9903 Email: susan.m.thorn...@nasa.govmailto:susan.m.thorn...@nasa.gov -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Problem Running Multiple Instances of Dspace
Originally I had two instances of Dspace running just fine on my server. My client then decided that they wanted to switch both instances from a .com domain to .org. I made this switch, .org is now the main domain and .com domains forward to the .org. However, now i've encountered a problem with my second instance of dspace. It works almost 90% correctly but I have one error below: When I visit dspace with this url it works fine: http://www.mywebsite.org/dspace/ However, when i remove the www from the url as such: http://mywebsite.org/dspace/ It now links to the dspace installation contained in the other instance. I find it very strange that the same domain name can link to two different instances of dspace just by removing the www. A little about my configuration. Initially I had a single instance of dspace and then decided to setup a second instance. Both instances are contained within different directories but share the same root. Dspace runs on tomcat but uses the Apache mod_jk connector to remove the port number from the url. Thanks for your help and let me know if you need some more information. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
