[duerrt]

I’m running eclipse 5.1.1 on an intel MAC (10.4.9) and everything runs fine if all data files
are local.

The problem is that I’m getting the “workspace in use” error when I try to create OR access
an existing workspace on a shared drive on a linux server.

I have write access to the shared driver and I can see that a .metadata/.lock file is being created but I still get the “workspace in use” error.

Any ideas?

Java version is 1.5.0.7

Thanks,
Tom

[Riyad Kalla]

Tom,
When Eclipse opens a workspace, it drops a .lock file in the .metadata directory to mark that it’s currently open. It’s possible when you had this workspace open last, the platform crashes, leaving the lock file, or it’s possible that if it’s a shared drive, someone else on your team has the workspace open.

Because of how workspaces are constructed and used, you cannot open them and share them like this, all of Eclipse’s stateful metadata is stored/read/written/updated in the workspace, to have two instances banging on it at the same time is a recipe for disaster.

In the Eclipse/MyEclipse-world you get around this by creating local workspaces and using source control to house and manage code and information that needs to be shared.

[duerrt]

Riyad,

thanks for the reply.

I think there is some other problem. I’ve cleared all .lock files AND I’m only accessing the workspace from 1 installation.

I even tried creating a brand new workspace and I still got the same error. I should be able to create a workspace on a network shared drive, right?

tom

[Riyad Kalla]

Tom… yes definately assuming your permissions are correct… the platform (which is what is throwing up this error) shouldn’t care where the workspace is created.

Out of curiosity, try and create a new workspace locally. If it starts up, copy it to your networked location and then try and reopen it… does it suddenly fail? If so, check the log file <workspace dir>\.metadata\.log to see if anything interesting is in it.

[Author]

Posts