JDBC connections not closed immediately

Hello,

we are facing an issue that the JDBC connections, which are created during the test execution, are not closed immediately, instead after a significant duration (say 5 seconds).

We have a limitation of 200 JDBC connections in our pool. The consequence of the issue is that, if multiple users are using SoapUI (say 10 users from 10 different machines), then SoapUI hangs almost every other minute and remains unusable for a certain period of time.

Strangely, the same version of the software, when executed in local LAN network, accessing the same database, closes all the created database connections immediately after database interaction is finished. Ofcourse it is the same test case in both the scenarios and executed in the exact same manner.

The remote access is done via VPN access. The access to webservices from the application seems to be unaffected in both the locations but the JDBC connections seem to take a significant amount of time while creating and closing the connections.

Does anybody know if the underlying network affect the functionality of SoapUI? Where can the problem be? Any suggestions?

Thanks and Regards,
Gokul Krishnan