.jazz5/.jazzlock issue after upgrade to 3.0.1.2

To rule out issues with Eclipse 3.7.2 vs 3.7, downloaded a fresh 3.7 "Classic" Eclipse (which is what the team is using), and installed the 3.0.1.2 client into it - no issues reported. Tried with that, and got the same issues. So it appears to not be related to the Eclipse level.

Environment: Linux 64 bit. Running Eclipse 3.7.2 with 3.0.1.2 client. We upgraded RTC from 3.0.0 ifixpak 1 to 3.0.1.2 last Saturday. Out of ~ 50 users, most are working OK, but some experience various Eclipse failures to build the Eclipse workspace - that say that the jazz5 lock can't be gotten.

If we run with an older Eclipse 3.7 (which has the 3.0.0 ifixpak 1 client), things work normally, no errors. (the older Eclipse client seems to work with the upgraded server).

The jazzlock file in .jazz5 comes and goes when you start Eclipse with the 3.0.1.2 RTC client, normally - that is, it's gone if you stop Eclipse, and back when you start it.

Any suggestions for the couple of users having this problem after the upgrade? One thing a user is trying now is to run with the old client, and check in all their changes into their local repo, and then run in the new client with a fresh Eclipse work space - I'll post something when we know if this works.

Some more details:

Eclipse "Clean" fails because it can't delet the output bin contents. That failure is associated with a failure to lock the .jazz5/.jazzlock file.

Here are stack traces; some path parts were replaced with xxxx and yyyy.

org.eclipse.core.internal.resources.ResourceException: Problems encountered while deleting resources. at org.eclipse.core.internal.resources.Resource.delete(Resource.java:793) at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.cleanOutputFolders(BatchImageBuilder.java:114) at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.build(BatchImageBuilder.java:46) at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll(JavaBuilder.java:254) at org.eclipse.jdt.internal.core.builder.JavaBuilder.build(JavaBuilder.java:173) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Contains: Could not delete '/yyyy/bin/com'.

org.eclipse.core.internal.resources.ResourceException: Problems encountered while deleting resources. at org.eclipse.core.internal.localstore.FileSystemResourceManager.delete(FileSystemResourceManager.java:352) at org.eclipse.core.internal.resources.ResourceTree.internalDeleteFolder(ResourceTree.java:352) at org.eclipse.core.internal.resources.ResourceTree.standardDeleteFolder(ResourceTree.java:798) at org.eclipse.core.internal.resources.Resource.unprotectedDelete(Resource.java:1935) at org.eclipse.core.internal.resources.Resource.delete(Resource.java:780) at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.cleanOutputFolders(BatchImageBuilder.java:114) at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.build(BatchImageBuilder.java:46) at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll(JavaBuilder.java:254) at org.eclipse.jdt.internal.core.builder.JavaBuilder.build(JavaBuilder.java:173) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Contains: Unable to lock file /home/xxxx/.jazz5/.jazzlock

Environment: Linux 64 bit. Running Eclipse 3.7.2 with 3.0.1.2 client. We upgraded RTC from 3.0.0 ifixpak 1 to 3.0.1.2 last Saturday. Out of ~ 50 users, most are working OK, but some experience various Eclipse failures to build the Eclipse workspace - that say that the jazz5 lock can't be gotten.

If we run with an older Eclipse 3.7 (which has the 3.0.0 ifixpak 1 client), things work normally, no errors. (the older Eclipse client seems to work with the upgraded server).

The jazzlock file in .jazz5 comes and goes when you start Eclipse with the 3.0.1.2 RTC client, normally - that is, it's gone if you stop Eclipse, and back when you start it.

Any suggestions for the couple of users having this problem after the upgrade? One thing a user is trying now is to run with the old client, and check in all their changes into their local repo, and then run in the new client with a fresh Eclipse work space - I'll post something when we know if this works.

Encountered the second issue, eclipse was unable to clean all projects.