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

Connection between kie-server and business-central not re-established after bc was restarted

XMLWordPrintable

    • Release Notes
    • CR1
    • ?
    • Hide

      1. Starts business central
      2. Starts kie-server
      ----> As you can see in this point, the connection between each other is established.
      3. Shutdown business-central ( CTRL+C)

      Following can be observed in kie-server logs:

      INFO 77800 --- [lient-AsyncIO-1] o.k.s.c.w.common.WebSocketClientImpl     : Session 0 is closed due to CloseReason: code [1001], reason [null]
      Exception in thread "Kie Server - Web Socket reconnect" java.lang.IllegalStateException: The WebSocket session [0] has been closed and no method (apart from close()) may be called on a closed session
      	at org.apache.tomcat.websocket.WsSession.checkState(WsSession.java:836)
      	at org.apache.tomcat.websocket.WsSession.getRequestURI(WsSession.java:737)
      	at org.kie.server.controller.websocket.common.WebSocketClientImpl.lambda$onClose$0(WebSocketClientImpl.java:82)
      	at java.lang.Thread.run(Thread.java:748)
      

      4. Start up business central again
      5. The connection (business central and kie-server) is not re-established again.
      6. Access and navigate through business-central and it is showing no containers, etc.

      Settings notes:
      --------------------
      1. It needs to customize what KJAR to deploy in application.properties (look for deployment prefix)

      2. Make sure to define these properties in BC/JBoss side:
      <property name="org.kie.server.user" value="kieserver"/>
      <property name="org.kie.server.pwd" value="kieserver1!"/>

      2. The user from business-central needs to be added in this class DefaultWebSecurityConfig.java

      Show
      1. Starts business central 2. Starts kie-server ----> As you can see in this point, the connection between each other is established. 3. Shutdown business-central ( CTRL+C) Following can be observed in kie-server logs: INFO 77800 --- [lient-AsyncIO-1] o.k.s.c.w.common.WebSocketClientImpl : Session 0 is closed due to CloseReason: code [1001], reason [ null ] Exception in thread "Kie Server - Web Socket reconnect" java.lang.IllegalStateException: The WebSocket session [0] has been closed and no method (apart from close()) may be called on a closed session at org.apache.tomcat.websocket.WsSession.checkState(WsSession.java:836) at org.apache.tomcat.websocket.WsSession.getRequestURI(WsSession.java:737) at org.kie.server.controller.websocket.common.WebSocketClientImpl.lambda$onClose$0(WebSocketClientImpl.java:82) at java.lang. Thread .run( Thread .java:748) 4. Start up business central again 5. The connection (business central and kie-server) is not re-established again. 6. Access and navigate through business-central and it is showing no containers, etc. Settings notes: -------------------- 1. It needs to customize what KJAR to deploy in application.properties (look for deployment prefix) 2. Make sure to define these properties in BC/JBoss side: <property name="org.kie.server.user" value="kieserver"/> <property name="org.kie.server.pwd" value="kieserver1!"/> 2. The user from business-central needs to be added in this class DefaultWebSecurityConfig.java
    • 2020 Week 34-36 (from Aug 17)

      It uses spring boot embedding kie server which brings tomcat.
      It was changed tomcat to undertow in spring boot and same issue occurred.
      It's not happening running kie-servers on EAP the connection is re-established

        1. KS_Exception.png
          KS_Exception.png
          249 kB
        2. reproducer.zip
          230 kB

            elguardian@gmail.com Enrique González Martínez (Inactive)
            rhn-support-luzrodri Luz Rodriguez
            Gonzalo Muñoz Fernández Gonzalo Muñoz Fernández
            Gonzalo Muñoz Fernández Gonzalo Muñoz Fernández
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: