Uploaded image for project: 'DSpace'
  1. DSpace
  2. DS-993

DSpace fails to start with spurious space character in dspace.cfg

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.8.0
    • Fix Version/s: 1.8.0
    • Component/s: DSpace API
    • Labels:
      None
    • Attachments:
      1
    • Comments:
      4
    • Documentation Status:
      Not Required

      Description

      DSpace trunk fails to start when there is an additional space character at the end of the dspace.dir line in dspace.cfg. Instead, I get an exception:

      Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Unable to read Avalon configuration from 'sitemap.xmap'.; nested exception is java.net.MalformedURLException: unknown protocol: resource

      The logfile shows that it's having problems reading the log4j configuration – it seems to find dspace.cfg but then inserts the space character in the path to log4j.properties.

      2011-08-17 15:16:11,153 INFO org.dspace.core.ConfigurationManager @ Loading from classloader: file:/home/dspace/DSpace/dspace/config/dspace.cfg
      2011-08-17 15:16:11,187 INFO org.dspace.core.ConfigurationManager @ Using dspace provided log configuration (log.init.config)
      2011-08-17 15:16:11,187 INFO org.dspace.core.ConfigurationManager @ File does not exist: /home/dspace/DSpace/dspace /config/log4j.properties

      If I remove the space character from the end of dspace.cfg and restart tomcat, it works fine.

        Attachments

          Activity

            People

            • Assignee:
              schweer Andrea Schweer
              Reporter:
              schweer Andrea Schweer
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: