BPMS http threads dead lock due to aborting processes

Solution In Progress - Updated -

Issue

The BPMS http thread dead lock causes many sockets in CLOSE_WAIT state and http threads leak. Eventually user has to restart their production server.
When trying to abort the process with REST api like the following, it got hung and need to kill it by CTRL+C.

curl -sS --connect-timeout 10 -u bpmsUser:bpmsPassword -X POST http://hostname:8080/business-central/rest/runtime/com.example:project1:1.0.0/process/instance/92642/abort

Environment

  • Red Hat JBoss BPM suite
    • 6.4.0
  • PER_PROCESS_INSTANCE strategy is used

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.