RE: unable to obtain lock

Thanks,

 

This problem started happening after our solaris box crashed during some checkouts.

I had to run truss while StarTeam was failing and realized there was a .lck file it could not find.

 

Just had to remove the .starbase folder where CC starts and restart CC.

-----Original Message-----
From: Jeffrey Fredrick [mailto:jtf@xxxxxxxxxx]
Sent: Wednesday, December 17, 2003 1:15 PM
To: Lu, David; cruisecontrol-user@xxxxxxxxxxxxxxxxxxxxx
Subject: RE: [Cruisecontrol-user] unable to obtain lock

 

I'd guess it is a file used by Starteam to avoid collisions between their clients.

 

Jtf

-----Original Message-----
From: cruisecontrol-user-admin@xxxxxxxxxxxxxxxxxxxxx [mailto:cruisecontrol-user-admin@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of Lu, David
Sent: Tuesday, December 16, 2003 2:03 PM
To: cruisecontrol-user@xxxxxxxxxxxxxxxxxxxxx
Subject: [Cruisecontrol-user] unable to obtain lock

Has anyone seen this error before?

 

BUILD FAILED
file:/home/buildmaster/projects/SeamlessGate/implementation/build_config/build.xml:374: java.lang.RuntimeException: unable to obtain lock on sync file

where build.xml:374 is the checkout task:

 

<stcheckout username="${starteam.user}" password="${starteam.passwd}" rootstarteamfolder="${starteam.folder}" rootlocalfolder="${starteam.checkoutfolder}" projectname="${starteam.project}" viewname="${starteam.view}" deleteuncontrolled="true" forced="false" servername="${starteam.server}" serverport="${starteam.port}"/>

 

what sync file is it complaining about?

Technologist

Lu, David

485 Lexington Avenue
3rd Floor, MS-10
New York, NY 10017

dlu@xxxxxxxxxxxxx

tel: fax:

212.490.9000 x7004 212.916.6050

Powered by Plaxo

Want a signature like this?

 



**************************************************************
This message, including any attachments, contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, please contact sender immediately by reply e-mail and destroy all copies. You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
TIAA-CREF
**************************************************************


**************************************************************
This message, including any attachments, contains confidential information intended for a specific individual and purpose, and is protected by law.  If you are not the intended recipient, please contact sender immediately by reply e-mail and destroy all copies.  You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
TIAA-CREF
**************************************************************