Does debugging require table locks?

Question

I guess I need someone with extensive knowledge to solve my current problem:

I use Eclipse to debug jUnit-tests that use Unitils. While debugging, some or all of the tables in my database are locked, even though they are not accessed at the moment.

The result is, that other developers working on the same database are unable to run tests as long as I'm debugging (or vice versa).

Logically I don't see a reason, why the tables should be locked the whole time. So, should I try to deactivate locking? Do you know how to configure that?

Though I can think of alternative approaches, I'd really like to have these questions answered, for this would be the most convenient solution.

EDIT: The tests run on an Oracle DB with empty tables. Before each test, Unitils empties EVERY table (unusual configuration for Unitils) and then inserts specific test data. All constraints are active, which again, is an unusual configuration. When I'm debugging and another developer starts a jUnit-Test, their IDE freezes until they get a DB timeout or I stop debugging, due to Unitils trying to empty the tables again.

Answer 1

Solution: Stopped using Unitils. DBUnit alone is enough and this problem is gone. Though this decision was made, because Unitils is no longer supported.