Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-6743

Storage and notification services are not picked by standalone controller

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.8.0.Final
    • 7.5.0.Final
    • KieServer
    • None
    • 2018 Week 13-14

    Description

      Standalone controller on Tomcat doesn't use custom storage and notification services if they are defined. Logs show just:

      [INFO] [talledLocalContainer] Jan 15, 2018 11:04:18 AM org.kie.server.controller.service.StandaloneKieServerControllerImpl <init>
[WARNING] [talledLocalContainer] WARNING: No server template storage defined. Default storage: InMemoryKieServerTemplateStorage will be used
[INFO] [talledLocalContainer] Jan 15, 2018 11:04:18 AM org.kie.server.controller.service.StandaloneKieServerControllerImpl <init>
[WARNING] [talledLocalContainer] WARNING: Notification service not defined. Default notification: LoggingNotificationService will be used

      even when FileBasedServerTemplateStorageService is defined as PersistingServerTemplateStorageService.

      The issue seems to be caused by wrongly placed META-INF folder with service definitions in war file. They are currently placed in META-INF/services folder in war root. They should be moved to WEB-INF/classes/META-INF/services.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. RHPAM-673 IOException for concurrent write to WebSocket on WebSphere

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. RHDM-372 Storage and notification services are not picked by standalone controller

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. RHPAM-408 Storage and notification services are not picked by standalone controller

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. RHPAM-667 Storage and notification services are not picked by standalone controller

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              cnicolai@redhat.com Cristiano Nicolai
              ksuta Karel Suta
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: