Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-1354

Kie server loses connection to the Business Central

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.3.0.GA
    • 7.0.1.GA
    • Cloud, Kie-Server
    • WebSocket connection
      EAP 7.1 (should be reproducible also with other application servers)

    • +
    • Hide

      Start Kie server in one EAP, Business central in another EAP, connect them together using WebSockets.
      Create a new project in Business Central, deploy it to the Kie server using embedded controller.
      Shut down the Business Central and turn it on again.
      =>
      The errors are shown in server log and Kie server doesn't react on any controller command any more.

      The scenario is covered by WorkbenchPersistenceIntegrationTest

      Show
      Start Kie server in one EAP, Business central in another EAP, connect them together using WebSockets. Create a new project in Business Central, deploy it to the Kie server using embedded controller. Shut down the Business Central and turn it on again. => The errors are shown in server log and Kie server doesn't react on any controller command any more. The scenario is covered by WorkbenchPersistenceIntegrationTest

      The issue happens just in case Kie server is connected to the Business Central using WebSockets.
      In case Business Central is restarted the Kie server is able to reconnect back to restarted Business Central, however then the Kie server is unable to process any request from the Business Central.

      The issue seems to be related to the message handler used for reconnecting Kie server in case the connection is lost.

              elguardian@gmail.com Enrique González Martínez (Inactive)
              ksuta Karel Suta
              Karel Suta Karel Suta
              Karel Suta Karel Suta
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: