Description Caspar D. 2011-07-19 04:54:55 EDT

As far as I've been able to determine, the Objy test suites currently
require that an Objy lock manager be running on the host where the tests
are run. (At least that's how I've set things up, and the tests are 
executing.)

The drawback of using an external LM, is that when the tests hang or
crash, they leave locks in the LM, making it impossible to re-start
the tests without manually terminating and re-starting the lock manager.

Here's the output I'm seeing:

main [org.eclipse.emf.cdo.server.internal.objectivity.db.FdManager] Createing FD: '/tmp/Objy5855682600670795564data/test.boot'.
main [org.eclipse.emf.cdo.server.internal.objectivity.db.FdManager] ** System Error #3001: Cannot grant the requested lock; conflict with an
                       existing lock.
                       - context = #0-0-0-0
** Error #4301: Storage Manager: Cannot create or open file
                caspar-pc::/tmp/Objy5855682600670795564data/test.fdb (No
                such file or directory) (100107)
** System Error #2533: Object Manager was unable to open a Database file
                       - context = #1-0-0-0
** System Error #2520: Object Manager was unable to abort the existing
                       transaction
** Error #2928: oonewfd : An error has occurred. Processing terminated.

It's my understanding that the Objy LM can optionally be run in-process..
it'd be nice if we could set the Objy tests suites up that way, so that re-starting the test suite would create a fresh LM and avoid these
hangups and the need for manual intervention.