StarTeam transaction error

I see the following in the TeamCity project dashboard from time to time on seemingly unrelated projects. I can sometimes go to the version control settings and re-save them to get this to go away, however, it doesn't seem right to see this error message. Thanks!

Rick Cole
Principal Software Engineer
PitneyBowes Software, Inc.

Unable to complete transaction. Some of the required resources are currently in use by other users: Please retry the operation again in a few minutes.
jetbrains.buildServer.vcs.VcsException: Unable to complete transaction.
Some of the required resources are currently in use by other users:

Please retry the operation again in a few minutes.
at jetbrains.buildServer.buildTriggers.vcs.starteam.StarteamSupport.collectBuildChanges(StarteamSupport.java:118)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.collectBuildChanges(VcsChangesLoader.java:35)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.loadChanges(VcsChangesLoader.java:41)
at jetbrains.buildServer.vcs.impl.VcsManagerImpl.loadChanges(VcsManagerImpl.java:305)
at jetbrains.buildServer.vcs.impl.VcsManagerImpl.checkForModifications(VcsManagerImpl.java:400)
at jetbrains.buildServer.serverSide.impl.auth.SecuredVcsManager.checkForModifications(SecuredVcsManager.java:85)
at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$1.run(VcsModificationChecker.java:5)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
Caused by: Unable to complete transaction.
Some of the required resources are currently in use by other users:

Please retry the operation again in a few minutes.
at com.starbase.starteam.ServerException.wrap(ServerException.java:51)
at com.starbase.starteam.Server.wrap(Server.java:67)
at com.starbase.starteam.View.getRootFolder(View.java:778)
at jetbrains.buildServer.buildTriggers.vcs.starteam.adapt.SnapshotImpl.findFolderByLogicalPath(SnapshotImpl.java:26)
at jetbrains.buildServer.buildTriggers.vcs.starteam.StarteamSupport$2.collectBuildChanges(StarteamSupport.java:4)
at jetbrains.buildServer.vcs.VcsSupportUtil.collectBuildChanges(VcsSupportUtil.java:27)
at jetbrains.buildServer.buildTriggers.vcs.starteam.StarteamSupport.collectBuildChanges(StarteamSupport.java:20)
... 12 more
Unable to complete transaction.
Some of the required resources are currently in use by other users:

Please retry the operation again in a few minutes.
at com.starbase.starteam.ServerException.wrap(ServerException.java:51)
at com.starbase.starteam.Server.wrap(Server.java:67)
at com.starbase.starteam.View.getRootFolder(View.java:778)
at jetbrains.buildServer.buildTriggers.vcs.starteam.adapt.SnapshotImpl.findFolderByLogicalPath(SnapshotImpl.java:26)
at jetbrains.buildServer.buildTriggers.vcs.starteam.StarteamSupport$2.collectBuildChanges(StarteamSupport.java:4)
at jetbrains.buildServer.vcs.VcsSupportUtil.collectBuildChanges(VcsSupportUtil.java:27)
at jetbrains.buildServer.buildTriggers.vcs.starteam.StarteamSupport.collectBuildChanges(StarteamSupport.java:20)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.collectBuildChanges(VcsChangesLoader.java:35)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.loadChanges(VcsChangesLoader.java:41)
at jetbrains.buildServer.vcs.impl.VcsManagerImpl.loadChanges(VcsManagerImpl.java:305)
at jetbrains.buildServer.vcs.impl.VcsManagerImpl.checkForModifications(VcsManagerImpl.java:400)
at jetbrains.buildServer.serverSide.impl.auth.SecuredVcsManager.checkForModifications(SecuredVcsManager.java:85)
at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$1.run(VcsModificationChecker.java:5)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)

5 comments

Hello Rick,

I see the following in the TeamCity project dashboard from time to
time on seemingly unrelated projects. I can sometimes go to the
version control settings and re-save them to get this to go away,
however, it doesn't seem right to see this error message. Thanks!


Why do you think so?

VCS error messages on the dashbord desappear on the next successful connect.
To make them go away more quickly you can reduce checking interval for the
corresponding VCS roots.


Rick Cole
Principal Software Engineer
PitneyBowes Software, Inc.
Unable to complete transaction. Some of the required resources are
currently in use by other users: Please retry the
operation again in a few minutes.

jetbrains.buildServer.vcs.VcsException: Unable to complete
transaction.

Some of the required resources are currently in use by other users:



Please retry the operation again in a few minutes.

at
jetbrains.buildServer.buildTriggers.vcs.starteam.StarteamSupport.colle
ctBuildChanges(StarteamSupport.java:118)

at
jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.collectBuildC
hanges(VcsChangesLoader.java:35)

at
jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.loadChanges(V
csChangesLoader.java:41)

at
jetbrains.buildServer.vcs.impl.VcsManagerImpl.loadChanges(VcsManagerIm
pl.java:305)

at
jetbrains.buildServer.vcs.impl.VcsManagerImpl.checkForModifications(Vc
sManagerImpl.java:400)

at
jetbrains.buildServer.serverSide.impl.auth.SecuredVcsManager.checkForM
odifications(SecuredVcsManager.java:85)

at
jetbrains.buildServer.serverSide.impl.VcsModificationChecker$1.run(Vcs
ModificationChecker.java:5)

at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417
)

at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)

at java.util.concurrent.FutureTask.run(FutureTask.java:123)

at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecu
tor.java:650)

at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.
java:675)

at java.lang.Thread.run(Thread.java:595)

Caused by: Unable to complete transaction.

Some of the required resources are currently in use by other users:



Please retry the operation again in a few minutes.

at com.starbase.starteam.ServerException.wrap(ServerException.java:51)

at com.starbase.starteam.Server.wrap(Server.java:67)

at com.starbase.starteam.View.getRootFolder(View.java:778)

at
jetbrains.buildServer.buildTriggers.vcs.starteam.adapt.SnapshotImpl.fi
ndFolderByLogicalPath(SnapshotImpl.java:26)

at
jetbrains.buildServer.buildTriggers.vcs.starteam.StarteamSupport$2.col
lectBuildChanges(StarteamSupport.java:4)

at
jetbrains.buildServer.vcs.VcsSupportUtil.collectBuildChanges(VcsSuppor
tUtil.java:27)

at
jetbrains.buildServer.buildTriggers.vcs.starteam.StarteamSupport.colle
ctBuildChanges(StarteamSupport.java:20)

.. 12 more

Unable to complete transaction.

Some of the required resources are currently in use by other users:



Please retry the operation again in a few minutes.

at com.starbase.starteam.ServerException.wrap(ServerException.java:51)

at com.starbase.starteam.Server.wrap(Server.java:67)

at com.starbase.starteam.View.getRootFolder(View.java:778)

at
jetbrains.buildServer.buildTriggers.vcs.starteam.adapt.SnapshotImpl.fi
ndFolderByLogicalPath(SnapshotImpl.java:26)

at
jetbrains.buildServer.buildTriggers.vcs.starteam.StarteamSupport$2.col
lectBuildChanges(StarteamSupport.java:4)

at
jetbrains.buildServer.vcs.VcsSupportUtil.collectBuildChanges(VcsSuppor
tUtil.java:27)

at
jetbrains.buildServer.buildTriggers.vcs.starteam.StarteamSupport.colle
ctBuildChanges(StarteamSupport.java:20)

at
jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.collectBuildC
hanges(VcsChangesLoader.java:35)

at
jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.loadChanges(V
csChangesLoader.java:41)

at
jetbrains.buildServer.vcs.impl.VcsManagerImpl.loadChanges(VcsManagerIm
pl.java:305)

at
jetbrains.buildServer.vcs.impl.VcsManagerImpl.checkForModifications(Vc
sManagerImpl.java:400)

at
jetbrains.buildServer.serverSide.impl.auth.SecuredVcsManager.checkForM
odifications(SecuredVcsManager.java:85)

at
jetbrains.buildServer.serverSide.impl.VcsModificationChecker$1.run(Vcs
ModificationChecker.java:5)

at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417
)

at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)

at java.util.concurrent.FutureTask.run(FutureTask.java:123)

at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecu
tor.java:650)

at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.
java:675)

at java.lang.Thread.run(Thread.java:595)

--
Sergey Anchipolevsky
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

I haven't seen this error with any other client applications for StarTeam I have worked with (StarTeam Client, IntelliJ). Plus, it seems to have cropped up after our upgrade to 3.1.1. We have been using TeamCity for about 5 months.

Rick Cole

0

Hello Rick,

Could you please describe what actions are usually performed under user BUILD-CDQauto?
Does TeamCity connect to StarTeam using the same account?

I haven't seen this error with any other client applications for
StarTeam I have worked with (StarTeam Client, IntelliJ). Plus, it
seems to have cropped up after our upgrade to 3.1.1. We have been
using TeamCity for about 5 months.

Rick Cole

--
Sergey Anchipolevsky
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

Yes. This is our build account, which is used to connect to StarTeam from TeamCity. No one else uses BUILD-CDQauto other than TeamCity.

Rick

0

Hello Rick,

For now I would suggest trying the following workarounds:

1. Since version 3.1 there have been two directory naming options - by working
folders, and by folder names.
Before 3.1 only the latter was present. Stacktrace tells me the problem might
me connected to the new naming method.
If the logical folder structure of your project is the same as the local
directory structure (folder names are equal to working folders -- this is
by default) you can try switching to "by folder names".

2. Increase check intervals and make them different for all VCS roots to
reduce the probability of conflicts during accessing the same StarTeam resources
in different user sessions.

3. There are a couple of fixes in the StarTeam support not included into
3.1.1, one of which is related to working folders support. If you wish to
try it I'll send yo the patch.

Also please tell me what version of StarTeam and StarTeam SDK you're using.

Thank you.

Yes. This is our build account, which is used to connect to StarTeam
from TeamCity. No one else uses BUILD-CDQauto other than TeamCity.

Rick

--
Sergey Anchipolevsky
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

Please sign in to leave a comment.