dm Server
  1. dm Server
  2. DMS-170

BRITS fails to start without network connection since schema cannot be found: looks like dm Server-related issue

    Details

    • Type: Defect Defect
    • Status: Done Done
    • Priority: Major Major
    • Resolution: Complete
    • Affects Version/s: None
    • Fix Version/s: 2.0.0.RELEASE
    • Component/s: None
    • Labels:
      None
    • Story Points:
      2

      Description

      ENGINE-1645:

      "I built the BRITS app for local demoing recently, and defined a local MySQL DB with a snapshot of the repository contents. Deploying the par after copying the required bundles to the repository works perfectly, the app runs successfully. (I also added two lines to the java5-server.profile as instructed by Scott Andrews)

      However, if I deploy when I don't have a network connection I get errors that the beans schema cannot be resolved anymore. I ran into this during a live demo I did today. I can reliably reproduce the behavior: with network (and internet) everything's fine, without I see the exception.
      I've attached the serviceability contents of a cleanly started server that has the error. Given the nature of this error I suspect that this is not a BRITS issue, but something that has to be fixed within the dm Server itself. I did no further investigation, so I don't know what component to assign this issue to."

        Activity

        Hide
        Andy Wilkinson added a comment -

        Joris, I've just tested this on dm Server 1.0.2.RELEASE using the embedded build of the EBR as you described on the Wiki: https://wiki.springsource.com/display/ENGINE/Running+a+local+copy+of+BRITS+for+demo+purposes

        I didn't see the problem described above when I ran the app without a network connection on dm Server 1.0.2.RELEASE.

        Have you seen this problem recently and, if so, can you please let me know what needs to be done to recreate it? Do I need to run the full version of the app, rather than the embedded version? I thought not as both contain the brows bundle, but I could well be wrong.

        Thanks,
        Andy

        Show
        Andy Wilkinson added a comment - Joris, I've just tested this on dm Server 1.0.2.RELEASE using the embedded build of the EBR as you described on the Wiki: https://wiki.springsource.com/display/ENGINE/Running+a+local+copy+of+BRITS+for+demo+purposes I didn't see the problem described above when I ran the app without a network connection on dm Server 1.0.2.RELEASE. Have you seen this problem recently and, if so, can you please let me know what needs to be done to recreate it? Do I need to run the full version of the app, rather than the embedded version? I thought not as both contain the brows bundle, but I could well be wrong. Thanks, Andy
        Hide
        Andy Wilkinson added a comment -

        The issue can be recreated using the embedded build, as described above on Joris' wiki page. It needs to be revision 461 of trunk (svn co https://src.springsource.com/svn/brits/trunk@461), as Scott (Andrews) added a workaround in a later revision.

        Show
        Andy Wilkinson added a comment - The issue can be recreated using the embedded build, as described above on Joris' wiki page. It needs to be revision 461 of trunk (svn co https://src.springsource.com/svn/brits/trunk@461 ), as Scott (Andrews) added a workaround in a later revision.
        Hide
        Andy Wilkinson added a comment -

        As expected, this issue is related to schema mapping and loading in an OSGi environment.

        PluggableEntityResolver attempts to find all of the META-INF/spring.schemas files available to its class loader. In this case the class loader is a BundleDelegatingClassLoader for the brows bundle. This class loader cannot see any META-INF/spring.schemas files so no mapping of the schema's location is performed and, therefore, the schema is loaded from the local specified in the application context xml file, i.e. over http.

        RCF-124, as being implemented by Spring-DM 2.0, is expected to fix this namespace handler / schema related problem, i.e. fixing this issue depends upon dm Server running on spring dm 2.0.

        Show
        Andy Wilkinson added a comment - As expected, this issue is related to schema mapping and loading in an OSGi environment. PluggableEntityResolver attempts to find all of the META-INF/spring.schemas files available to its class loader. In this case the class loader is a BundleDelegatingClassLoader for the brows bundle. This class loader cannot see any META-INF/spring.schemas files so no mapping of the schema's location is performed and, therefore, the schema is loaded from the local specified in the application context xml file, i.e. over http. RCF-124, as being implemented by Spring-DM 2.0, is expected to fix this namespace handler / schema related problem, i.e. fixing this issue depends upon dm Server running on spring dm 2.0.
        Hide
        Andy Wilkinson added a comment -

        I've lowered the priority as Scott has implemented a workaround.

        Show
        Andy Wilkinson added a comment - I've lowered the priority as Scott has implemented a workaround.
        Hide
        Andy Wilkinson added a comment -

        dm Server now propagates request for spring.schemas and spring.handlers files across bundles which fixes this problem.

        Show
        Andy Wilkinson added a comment - dm Server now propagates request for spring.schemas and spring.handlers files across bundles which fixes this problem.

          People

          • Assignee:
            Unassigned
            Reporter:
            Joris Kuipers
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              First Response Date:

              Time Tracking

              Estimated:
              Original Estimate - 4h
              4h
              Remaining:
              Time Spent - 0.5h Remaining Estimate - 3.5h
              3.5h
              Logged:
              Time Spent - 0.5h Remaining Estimate - 3.5h
              0.5h