I think we have a memory leak here, I don't see a call to isp.in, plus a call to isp.in is tricky, because it may or may not get you this particular value. In addition, I think that by using a LocalSpace and its notify method, we are opening in the TransactionManager a bug similar to the one we had with QMUX in jPOS-110 (https://jpos.org/issues/issue/jPOS-110). 

For backward compatibility, I think it might be easier to have a single thread pulling entries from isp and creating the TMTask jobs (plus we gain the source based timeout that we have been talking about).