Uploaded image for project: 'RiftSaw'
  1. RiftSaw
  2. RIFTSAW-468

BPEL Process instance stuck in running state if JBoss shutdown while a BPEL INVOKE is running

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.3.0.Final
    • Fix Version/s: 2.4.0
    • Component/s: Integration
    • Labels:
      None
    • Environment:
    • Steps to Reproduce:
      Hide

      Use the attached ant BPEL project (based on Quickstart Examples - Simple Invoke).

      Scenario 1 - Standalone JBoss
      1. ant runtestserver (to start a standalone web service process outside JBoss, this web service will send a response after a delay of 2 minutes)
      2. ant deploy (to deploy the BPEL to the JBoss server)
      3. ant runtestclient (to invoke the BPEL process)
      4. When the INVOKE activity is run a request will be sent to the standalone web service. Now Shutdown JBoss.
      5. Server does not shutdown until response is received. After response is received a transaction related exception is logged to the server log. (logs attached)
      6. Start JBoss
      7. BPEL process left in running state, it's execution is not resumed.

      Scenario 2 - 2 Node JBoss Cluster
      1. ant runtestserver (to start a standalone web service process outside JBoss, this web service will send a response after a delay of 2 minutes)
      2. ant deploy (to deploy the BPEL to the JBoss server)
      3. Manually deploy the BPEL jar file to the other JBoss server node.
      3. ant runtestclient (to invoke the BPEL process)
      4. When the INVOKE activity is run a request will be sent to the standalone web service. Now Shutdown JBoss.
      5. Server does not shutdown until response is received. After response is received a transaction related exception is logged to the server log. (logs attached)
      6. BPEL process left in running state, it's execution is not resumed by the other JBoss node. (log attached)

      Show
      Use the attached ant BPEL project (based on Quickstart Examples - Simple Invoke). Scenario 1 - Standalone JBoss 1. ant runtestserver (to start a standalone web service process outside JBoss, this web service will send a response after a delay of 2 minutes) 2. ant deploy (to deploy the BPEL to the JBoss server) 3. ant runtestclient (to invoke the BPEL process) 4. When the INVOKE activity is run a request will be sent to the standalone web service. Now Shutdown JBoss. 5. Server does not shutdown until response is received. After response is received a transaction related exception is logged to the server log. (logs attached) 6. Start JBoss 7. BPEL process left in running state, it's execution is not resumed. Scenario 2 - 2 Node JBoss Cluster 1. ant runtestserver (to start a standalone web service process outside JBoss, this web service will send a response after a delay of 2 minutes) 2. ant deploy (to deploy the BPEL to the JBoss server) 3. Manually deploy the BPEL jar file to the other JBoss server node. 3. ant runtestclient (to invoke the BPEL process) 4. When the INVOKE activity is run a request will be sent to the standalone web service. Now Shutdown JBoss. 5. Server does not shutdown until response is received. After response is received a transaction related exception is logged to the server log. (logs attached) 6. BPEL process left in running state, it's execution is not resumed by the other JBoss node. (log attached)

      Description

      If I try to shutdown JBoss while a BPEL process instance is executing an INVOKE activity, the server does not shutdown completely until the response is received from the external web service (or the request timeouts). The process is left in the running/active state and it is not resumed when the JBoss server is brought back up.

      If running in a clustered environment with 2 JBoss nodes and one node is shutdown during an INVOKE, even then the server does not shutdown until a response is received also the other JBoss node is not able to retry the INVOKE or resume execution of the process after the INVOKE.

        Gliffy Diagrams

          Attachments

          1. restart_test_bpel.zip
            340 kB
          2. Scenario1-server.log
            321 kB
          3. Scenario2-Logs.zip
            43 kB

            Activity

              People

              • Assignee:
                jeff.yuchang Jeff Yu
                Reporter:
                anujbhatia anuj bhatia
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: