Uploaded image for project: 'Publishing'
  1. Publishing
  2. PUBLISHING-324

6.3 public instance wrongly requires publishing microprofile config

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • 2.0.0
    • None
    • None

      In a 6.3 setup with author/public on different tomcat containers. If the public instance runs without a publish microconfig profile under smallrye.config.locations, publication related functions will not behave as usual. Some of the problem:

      • Cannot open Publishing tools and Configurations app on public instance, UI throw exception related to ActivationManager instantiation failures.
      • Cannot publish from author to public
        • author will report error 500
        • public will report below error:
      13-Mar-2024 09:29:14.978 WARNING [main] org.apache.catalina.core.StandardServer.await StandardServer.await: Invalid command '' received
      2024-03-13 09:30:15,003 WARN magnolia.jcr.node2bean.impl.Node2BeanProcessorImpl: Did not manage to create a bean for node [/server/activation], this part of configuration will be skipped
      2024-03-13 09:30:15,004 WARN fo.magnolia.objectfactory.ObservedComponentFactory: An instance of interface info.magnolia.cms.exchange.ActivationManager couldn't be loaded from config:/server/activation yet, returning null.
      

      Expected:

      Publication MP is only matter at author instance.

        Acceptance criteria

              ajuran AntonĂ­n Juran
              dai.ha Dai Ha
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:
                Work Started:

                  Bug DoR
                  Task DoD