BP Forms threading uses unique user names to cause multiple instances of Open Office to run simultaneously on the BP Forms server. Commands are sent from the BP Forms phantom running on the multivalue server to the BP Forms server where Open Office runs. For this to work, a trust must be established between the MultiValue server and the BP Forms server using a conventional SSH Keychain. If the keychain is not properly asserted, then the MultiValue phantom issuing the document print requests to the BP Forms server will send its request which will be challenged and eventually fail. This failure can take up to 30 seconds during which time the lock set on the document by the phantom will be active which prevents any other phantom thread from discovering and printing that document.
To determine if this is the cause, first you should review the logs that are kept by BP Forms by summoning the bpi.form.phantom.menu then selecting a phantom and pressing 'L' to view the log file. If you find an entry in the log that looks like this:
0000044 echo_directive=_ssudo -u xxxform4 ssh -l xxxform4 192.168.160.233 'echo
0000045 Host key verification failed..
The above text appearing in your log file should be your first indicator that there are issues with your ssh key assertion and that corrective action is required.
You may also test each phantom thread by entering the bpi.form.phantom.menu, then selecting each phantom and then choosing the $ option from the menu. If the menu logs you into the BP Forms server and you are not challenged for a password, then the ssh key for the user defined for that thread is properly asserted. Repeat the process for each thread until you find the offending threat and then assert the ssh key for the user named by that thread yourself or by using the bpi.ssh.keygen utility documented on this site.