Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-7762

Redirects (Virtual URI mapping) not working

    XMLWordPrintable

    Details

    • Release notes required:
      Yes
    • Documentation update required:
      Yes
    • Epic Link:
    • Sprint:
      Maintenance 3, Maintenance 4, Maintenance 5, Maintenance 6
    • Story Points:
      5
    • Magnolia Release:
      5.7.7, 6.1.6, 6.2.1

      Description

      It seems that when having big amount of virtual URI mappings (500+) in light modules, loading and processing of mappings get randomly interrupted with misleading error

      WARN  info.magnolia.config.source.yaml.YamlConfigurationSource 19.03.2020 15:04:09 -- 
      Severity type:   MAJOR 
      Title:           /: [Definition resolution] - Source data processing problem 
      Problem details: Failed to instantiate an object of type [interface info.magnolia.virtualuri.VirtualUriMapping] due to [No suitable constructor found for class [interface info.magnolia.virtualuri.VirtualUriMapping]], null is returned
      

      The error is posted in the logs despite the fact that same yaml file loads on different instance w/o any issues and class used for the mapping is default mapping included in Magnolia installation OOTB.
      Error also appears at random when reloading of definitions is forced by adding new one.
      And at random might get fixed (or not) by restart of the instance.
      There are no errors reported on any other of the existing mappings thus making it impossible to figure out if any other file might be the cause. There is also no known debug setting that would help ti triage the issue nor means to verify all existing mappings to figure out if there is conflict elsewhere.

      Details of existing investigation in linked tickets:

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              efochr Evzen Fochr
              Reporter:
              dlopez David Lopez
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 2d 1h
                  2d 1h