Crucible
  1. Crucible
  2. CRUC-931

Getting "The ResourceConfig instance does not contain any root resource classes" when trying to configure Jira Fisheye Plugin

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.6.6
    • Fix Version/s: None
    • Component/s: API
    • Labels:
      None
    • Environment:

      JIRA 3.13.4

    • Complexity:
      3
    • Value:
      2
    • Regular Expression:
      The ResourceConfig instance does not contain any root resource classes

      Description

      Symptoms

      This is mostly seen when trying to configure Jira Fisheye Plugin, but can also occur if you are trying to login using the Rest API.

      The error throw in your Jira logs will look like:

      2009-05-19 14:02:29,838 http-8080-Processor25 ERROR [fisheye.rest.fisheye.FishEyeRestAuthenticationManagerImpl] Failed to authenticate user 'username': http://FISHEYE_HOST:8060/rest-service/auth-v1/login?password=********&userName=username returned 500 Internal Server Error
      2009-05-19 14:02:29,838 http-8080-Processor25 ERROR [jira.ext.fisheye.FishEyeManagerImpl] Failed to retrieve FishEye repositories from http://FISHEYE_HOST:8060/ 
      java.io.IOException: Failed to authenticate with FishEye. See logs for more details.
      	at com.atlassian.jira.ext.fisheye.rest.fisheye.FishEyeRestAuthenticationManagerImpl.authenticate(FishEyeRestAuthenticationManagerImpl.java:43)
      	at com.atlassian.jira.ext.fisheye.rest.fisheye.FishEyeRestAuthenticationManagerImpl.authenticateWithCrucible(FishEyeRestAuthenticationManagerImpl.java:58)
      

      In your fisheye-error.log.* logs you see:

      2009-05-19 16:07:14,311 ERROR [btpool0-3] org.mortbay.log sun.reflect.NativeMethodAccessorImpl-invoke0 - /rest-service/auth-v1/login
      com.sun.jersey.api.container.ContainerException: The ResourceConfig instance does not contain any root resource classes.
      	at com.sun.jersey.impl.application.WebApplicationImpl.processRootResources(WebApplicationImpl.java:774)
      	at com.sun.jersey.impl.application.WebApplicationImpl.initiate(WebApplicationImpl.java:671)
      	at com.sun.jersey.spi.spring.container.servlet.SpringServlet.initiate(SpringServlet.java:66)
      

      Your Fishye server is installed on a windows machine under a folder which contains a space, for example "C:\Program Files\crucible-1.6.6".

      To check where your Fisheye is installed go to Fisheye Administration > Sys Info/Support > System Info, and check your FISHEYE_HOME variable which represents where your Fisheye or Crucible is installed.

      Workaround

      Move your Fisheye or Crucible Installation to somewhere without a space, for example C:\crucible-1.6.6

        Issue Links

          Activity

          Mads Nissen created issue -
          Brendan Humphreys [Atlassian] made changes -
          Field Original Value New Value
          Workflow reviewflow [ 149184 ] review flow with triage [ 151266 ]
          Brendan Humphreys [Atlassian] made changes -
          Workflow review flow with triage [ 151266 ] Copy of review flow with triage [ 153256 ]
          Brendan Humphreys [Atlassian] made changes -
          Workflow Copy of review flow with triage [ 153256 ] Simple review flow with triage [ 155197 ]
          Brendan Humphreys [Atlassian] made changes -
          Status Open [ 1 ] Needs Triage [ 10030 ]
          Partha Kamal [Atlassian] made changes -
          Summary There was a problem connecting to your FishEye instance: Failed to authenticate with FishEye. See logs for more details. Getting "The ResourceConfig instance does not contain any root resource classes" when trying to configure Jira Fisheye Plugin
          Regular Expression The ResourceConfig instance does not contain any root resource classes
          Affects Version/s 1.6.6 [ 14440 ]
          Environment JIRA 3.13.1
          Crucible/Fisheye: 1.6.4
          JIRA 3.13.4
          Description Might be related to the default Windows x64 install folder "Program Files (x86)"`?

          From Crucible/Fisheye log:

          INFO | jvm 1 | 2008/12/09 13:12:49 | 09.des.2008 13:12:49 com.sun.jersey.api.core.PackagesResourceConfig init
          INFO | jvm 1 | 2008/12/09 13:12:49 | INFO: Scanning for root resource and provider classes in the packages:
          INFO | jvm 1 | 2008/12/09 13:12:49 | com.atlassian.crucible.spi.rpc
          INFO | jvm 1 | 2008/12/09 13:12:49 | 09.des.2008 13:12:49 com.sun.jersey.impl.container.config.AnnotatedClassScanner scan
          INFO | jvm 1 | 2008/12/09 13:12:49 | WARNING: URL, jar:file:/C:/Program Files (x86)/crucible-1.6.4/fisheye.jar!/com/atlassian/crucible/spi/rpccannot be converted to a URI
          INFO | jvm 1 | 2008/12/09 13:12:49 | 09.des.2008 13:12:49 com.sun.jersey.spi.spring.container.servlet.SpringServlet springComponentAnnotationAvailable
          INFO | jvm 1 | 2008/12/09 13:12:49 | INFO: The spring Component annotation is present: using spring >= 2.5
          INFO | jvm 1 | 2008/12/09 13:12:49 | 09.des.2008 13:12:49 com.sun.jersey.impl.application.WebApplicationImpl processRootResources
          INFO | jvm 1 | 2008/12/09 13:12:49 | SEVERE: The ResourceConfig instance does not contain any root resource classes.
          INFO | jvm 1 | 2008/12/09 13:12:49 | 09.des.2008 13:12:49 com.sun.jersey.spi.spring.container.servlet.SpringServlet initiate
          INFO | jvm 1 | 2008/12/09 13:12:49 | SEVERE: Exception occurred when intialization
          INFO | jvm 1 | 2008/12/09 13:12:49 | com.sun.jersey.api.container.ContainerException: The ResourceConfig instance does not contain any root resource classes.
          INFO | jvm 1 | 2008/12/09 13:12:49 | at com.sun.jersey.impl.application.WebApplicationImpl.processRootResources(WebApplicationImpl.java:774)
          INFO | jvm 1 | 2008/12/09 13:12:49 | at com.sun.jersey.impl.application.WebApplicationImpl.initiate(WebApplicationImpl.java:671)
          INFO | jvm 1 | 2008/12/09 13:12:49 | at com.sun.jersey.spi.spring.container.servlet.SpringServlet.initiate(SpringServlet.java:66)
          INFO | jvm 1 | 2008/12/09 13:12:49 | at com.sun.jersey.spi.container.servlet.ServletContainer.load(ServletContainer.java:538)
          INFO | jvm 1 | 2008/12/09 13:12:49 | at com.sun.jersey.spi.container.servlet.ServletContainer.init(ServletContainer.java:197)
          INFO | jvm 1 | 2008/12/09 13:12:49 | at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:433)
          INFO | jvm 1 | 2008/12/09 13:12:49 | at org.mortbay.jetty.servlet.ServletHolder.getServlet(ServletHolder.java:342)
          INFO | jvm 1 | 2008/12/09 13:12:49 | at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:463)
          INFO | jvm 1 | 2008/12/09 13:12:49 | at org.mortbay.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.j
          h3. Symptoms

          This is mostly seen when trying to configure Jira Fisheye Plugin, but can also occur if you are trying to login using the Rest API.

          The error throw in your Jira logs will look like:

          {code}
          2009-05-19 14:02:29,838 http-8080-Processor25 ERROR [fisheye.rest.fisheye.FishEyeRestAuthenticationManagerImpl] Failed to authenticate user 'username': http://FISHEYE_HOST:8060/rest-service/auth-v1/login?password=********&userName=username returned 500 Internal Server Error
          2009-05-19 14:02:29,838 http-8080-Processor25 ERROR [jira.ext.fisheye.FishEyeManagerImpl] Failed to retrieve FishEye repositories from http://FISHEYE_HOST:8060/
          java.io.IOException: Failed to authenticate with FishEye. See logs for more details.
          at com.atlassian.jira.ext.fisheye.rest.fisheye.FishEyeRestAuthenticationManagerImpl.authenticate(FishEyeRestAuthenticationManagerImpl.java:43)
          at com.atlassian.jira.ext.fisheye.rest.fisheye.FishEyeRestAuthenticationManagerImpl.authenticateWithCrucible(FishEyeRestAuthenticationManagerImpl.java:58)
          {code}

          In your fisheye-error.log.* logs you see:

          {code}
          2009-05-19 16:07:14,311 ERROR [btpool0-3] org.mortbay.log sun.reflect.NativeMethodAccessorImpl-invoke0 - /rest-service/auth-v1/login
          com.sun.jersey.api.container.ContainerException: The ResourceConfig instance does not contain any root resource classes.
          at com.sun.jersey.impl.application.WebApplicationImpl.processRootResources(WebApplicationImpl.java:774)
          at com.sun.jersey.impl.application.WebApplicationImpl.initiate(WebApplicationImpl.java:671)
          at com.sun.jersey.spi.spring.container.servlet.SpringServlet.initiate(SpringServlet.java:66)
          {code}

          Your Fishye server is installed on a windows machine under a folder which contains a space, for example "C:\Program Files\crucible-1.6.6".

          To check where your Fisheye is installed go to Fisheye Administration > Sys Info/Support > System Info, and check your FISHEYE_HOME variable which represents where your Fisheye or Crucible is installed.

          h3. Workaround

          Move your Fisheye or Crucible Installation to somewhere without a space, for example C:\crucible-1.6.6
          Partha Kamal [Atlassian] made changes -
          Comment [ Mads, it definitely looks like a problem related to the fact that you are running Crucible from a directory that contains a space.

          Could you move the crucible installation folder to another directory that doesn't contain spaces, and try again? ]
          Brendan Humphreys [Atlassian] made changes -
          Value Unknown
          Complexity Unknown
          Paul Slade [Atlassian] made changes -
          Value Unknown 2
          Complexity Unknown 3
          Paul Slade [Atlassian] made changes -
          Status Needs Triage [ 10030 ] Open [ 1 ]
          Seb Ruiz [Atlassian] made changes -
          Workflow Simple review flow with triage [ 155197 ] FECRU Development Workflow (Triage) [ 315034 ]
          Matt Ryall [Atlassian] made changes -
          Link This issue relates to CRUC-526 [ CRUC-526 ]

            People

            • Votes:
              1 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Last commented:
                4 years, 47 weeks ago