AFAIK it's simply impossible!
In fact, from a client point of view the process execution is always asynchronous.
So to get the results back, you should follow an asynchronous pattern:
1) start the process and forget it
2) wait for the process effects (e.g. the process write the result on a DBMS, the process write the result as a message on JMS queue)
I think you are right, the process I spawned is small and finished quickly so didn't realize its actually asynchronous.
Can you point me to any examples for enabling persistence to MYSQL and JMS queue. Will implement one of it whichever suits our needs.
I am using jbpm workbench on docker container.
You can performs such kind of activities in an external services (more reusable) or you can embed in the process execution thread thru the Work Item Handlers. Here some examples of WorkItem Handlers: https://github.com/droolsjbpm/jbpm/tree/master/jbpm-workitems/src/main/java/org/jbpm/process/workitem