Which version of jBPM are you using?
Reading your description that's the expected behaviour. The activities in the process flow needs to be executed in sequence, no matter if they are sync or async. If you want to execute all the activities that are after something that is handled by a job executor, you can just create a gateway so they can be executed in "parallel".
Thank you Very Much..
I am using JBPM version 3.2.6.
I know that's the expected behaviour of job executor but the problem is once the job executor has finished the processing the node and it is in the wait state after the sync node, it has still lock on the token and if I query the token I am still in the Async node even though it has finished executing the node after the async node.