Uploaded image for project: 'Drools'
  1. Drools
  2. DROOLS-1114

Add ConversationId http header/jms property to allow dynamic routing of requests

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Major Major
    • 6.4.0.Final
    • 6.4.0.CR2
    • kie server
    • None
    • NEW
    • NEW

      to be able to implement rolling updates on openshift there is need to provide additional information so routing can properly navigate between server instances.

      Kie Server (both server and client) should use conversation id that is composed of:

      • kie server id
      • container id
      • release id (resolved release id if present)
      • unique UUID string

      all of these values are separated with : so it can be easily parsed. ReleaseId is by itself separated with : as it's GAV (group : artifact : version)

      Entire conversationId is URL encoded so it can be easily transferred over the wire.

              swiderski.maciej Maciej Swiderski (Inactive)
              swiderski.maciej Maciej Swiderski (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: