This content has been marked as final. Show 1 reply
I have done a great investigation, so I would answer my question myself.
- We don't recommend to use JMS for transporting of Async Human Task in jBPM 5.x, HornetQ is the default and only one supported/well-QA transport, Apache Mina/JMS are experimental options.
- If use JMS, JMSTaskClientConnector should create/connect/disconnect per request. These because JMS session objects are single threaded and can only be used by single thread that created them. An attempt to use them from another thread would result in an exception or some very strange errors. This is as per JMS specifications.