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

Storage and notification services are not picked by standalone controller

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 7.5.0.Final
    • Fix Version/s: 7.8.0.Final
    • Component/s: KieServer
    • Labels:
      None
    • Environment:

      Tomcat 8

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  cristiano.nicolai Cristiano Nicolai
                  Reporter:
                  ksuta Karel Suta
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: