Why BlockingTaskOperationResponseHandler requires using waitTillDone(...) in order to work properly ?

Solution Unverified - Updated -

Issue

  • Users often uses BlockingTaskOperationResponseHandler to start and complete tasks like below.
...
client = getTaskClient();
BlockingTaskOperationResponseHandler handler = new BlockingTaskOperationResponseHandler();
client.start(taskId, user, handler);
client.complete(taskId, user, contentData, handler);
...

It has been observed that sometimes the operation does not complete successfully unless users call the function handler.waitTillDone(100) .

  • Why do users need to call this function ?
  • What's the proper value to use in waitTillDone(...) method ?

Environment

  • Red Hat JBoss BRMS (BRMS)
    • 5.3.x

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.