If a user starts there application after naviagting to their FISHEYE_HOME directory via a symbolic link and have no FISHEYE_INST setup, they will not be able to start their application.

XMLWordPrintable

    • Type: Bug
    • Resolution: Answered
    • Priority: Medium
    • None
    • Affects Version/s: 1.6.3
    • Component/s: None
    • 5

      If a user sets up a symbolic link to their FISHEYE_HOME eg. they have installed in /home/crucible-1.6.3 but linked to it via /home/crucible and they have not set a FISHEYE_INST

      Then they will get the following:

      2008-11-13 11:45:25,808 ERROR [main] org.springframework.web.context.ContextLoader org.springframework.web.context.ContextLoader-initWebApplicationContext - Context initialization failed
org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from ServletContext resource [/WEB-INF/applicationContext.xml]; nested exception is java.lang.IllegalStateException: Annotation-specified bean name 'hostComponentProvider' for bean class [com.atlassian.plugin.spring.SpringHostComponentProvider] conflicts with existing, non-compatible bean definition of same name and class [com.atlassian.plugin.spring.SpringHostComponentProvider]

      Because their lib jar files are loaded twice.

      This is because fisheye thinks that the FISHEYE_HOME and the FISHEYE_INST are different directories (due to the symbolic link) when they are not.

      Setting priority as blocker as it this fix should be simple and it leads to many critical cases (i.e. my server won't start up)

              Assignee:
              Unassigned
              Reporter:
              Partha
              Votes:
              1 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: