We have a situation where a flow which potentially takes a long time to run starts by looking up data from a db and then calles a webservice which can take a while to come back. In this situation we have observed that the connection pool associated with the db in question has a busy connection until the flow finishes.
Is there a way in wm to explicitly release the connection after its use? I have made some tests and the only solution I have found so far is to use localTinvoke / joinT and executing the db lookup in a thread which seems to free up the DB connection as soon as the thread finishes exectuion.
Any other alternatives?