Can't find Starteam*.jar after upgrading to 64 bit JVM !!!
Hi,
I recently migrated to MySQL55 and upgraded the TeamCity app to 6.5.5. That was finally successful after many problems. Once that was finished I started getting out of memory errors in the TeamCity server log and then the server would become unresponsive and/or crash. From what I could tell I was max'd out as far as memory was conerned and couldn't bump it any higher with the 32 bit jvm. I installed and pointed the TeamCity installation to the 64 bit jvm.
The TeamCity server was much happier and peformed much better. The server app hasn't crashed or hung and I haven't seen any additional out of memory problems since I was able to increase the allocated memory.
HOwever, I cannot connect to my STarteam VCS roots. I have the appropriate jar file(s) is the correct place but TeamCity can't seem to find them. I'm wondering if it's because I'm not using a 64 bit jvm and the Starteam jars are 32bit. I assume it would work since they are just class libraries.
I have the following messages for each starteam root:
Could not locate StarTeam SDK. Please ensure it is installed and put SDK's starteam*.jar into <TeamCity home>/webapps/ROOT/WEB-INF/lib directory.
« Hide stacktrace
Could not locate StarTeam SDK. Please ensure it is installed and put SDK's starteam*.jar into <TeamCity home>/webapps/ROOT/WEB-INF/lib directory.
at jetbrains.buildServer.buildTriggers.vcs.starteam.adapt.StarteamConnectionFactoryImpl.createConnection(StarteamConnectionFactoryImpl.java:43)
at jetbrains.buildServer.buildTriggers.vcs.starteam.StarteamSupport.getChangeCollector(StarteamSupport.java:160)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.collectChangesByIncludeRules(VcsChangesLoader.java:61)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.collectChanges(VcsChangesLoader.java:66)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.collectBuildChanges(VcsChangesLoader.java:110)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.collectChangesForCheckoutRules(VcsChangesLoader.java:101)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.collectChanges(VcsChangesLoader.java:56)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader._loadChangesForRoot(VcsChangesLoader.java:8)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.loadChangesForRoot(VcsChangesLoader.java:18)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.loadChangesForRoot(VcsChangesLoader.java:120)
at jetbrains.buildServer.vcs.impl.VcsManagerImpl.loadChanges(VcsManagerImpl.java:446)
at jetbrains.buildServer.serverSide.impl.auth.SecuredVcsManager.loadChanges(SecuredVcsManager.java:53)
at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$1.run(VcsModificationChecker.java:1)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.borland.starteam.impl.util.Platform
at com.borland.starteam.impl.ClientContext.<init>(Unknown Source)
at com.borland.starteam.impl.Server.<init>(Unknown Source)
at com.borland.starteam.impl.Server.<init>(Unknown Source)
at com.starbase.starteam.Server.<init>(Unknown Source)
at com.starbase.starteam.StarTeamFinder.openServer(Unknown Source)
at com.starbase.starteam.StarTeamFinder.openProject(Unknown Source)
at com.starbase.starteam.StarTeamFinder.openViewWithOverride(Unknown Source)
at com.starbase.starteam.StarTeamFinder.openView(Unknown Source)
at jetbrains.buildServer.buildTriggers.vcs.starteam.adapt.StarteamConnectionImpl.<init>(StarteamConnectionImpl.java:52)
at jetbrains.buildServer.buildTriggers.vcs.starteam.adapt.StarteamConnectionFactoryImpl.createConnection(StarteamConnectionFactoryImpl.java:41)
... 18 more
java.lang.NoClassDefFoundError: Could not initialize class com.borland.starteam.impl.util.Platform
at com.borland.starteam.impl.ClientContext.<init>(Unknown Source)
at com.borland.starteam.impl.Server.<init>(Unknown Source)
at com.borland.starteam.impl.Server.<init>(Unknown Source)
at com.starbase.starteam.Server.<init>(Unknown Source)
at com.starbase.starteam.StarTeamFinder.openServer(Unknown Source)
at com.starbase.starteam.StarTeamFinder.openProject(Unknown Source)
at com.starbase.starteam.StarTeamFinder.openViewWithOverride(Unknown Source)
at com.starbase.starteam.StarTeamFinder.openView(Unknown Source)
at jetbrains.buildServer.buildTriggers.vcs.starteam.adapt.StarteamConnectionImpl.<init>(StarteamConnectionImpl.java:52)
at jetbrains.buildServer.buildTriggers.vcs.starteam.adapt.StarteamConnectionFactoryImpl.createConnection(StarteamConnectionFactoryImpl.java:41)
at jetbrains.buildServer.buildTriggers.vcs.starteam.StarteamSupport.getChangeCollector(StarteamSupport.java:160)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.collectChangesByIncludeRules(VcsChangesLoader.java:61)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.collectChanges(VcsChangesLoader.java:66)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.collectBuildChanges(VcsChangesLoader.java:110)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.collectChangesForCheckoutRules(VcsChangesLoader.java:101)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.collectChanges(VcsChangesLoader.java:56)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader._loadChangesForRoot(VcsChangesLoader.java:8)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.loadChangesForRoot(VcsChangesLoader.java:18)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.loadChangesForRoot(VcsChangesLoader.java:120)
at jetbrains.buildServer.vcs.impl.VcsManagerImpl.loadChanges(VcsManagerImpl.java:446)
at jetbrains.buildServer.serverSide.impl.auth.SecuredVcsManager.loadChanges(SecuredVcsManager.java:53)
at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$1.run(VcsModificationChecker.java:1)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
All the needed Starteam SDK libraries are in the <TeamCity home>/webapps/ROOT/WEB-INF/lib directory. This wasn't a problem before upgrading the JVM to 64bit. I could connect to the VCS roots but kept getting an out of memory problem. I don't think there is a separate 64 bit Starteam SDK.
I'm somewhat stuck now. Any help would be greatly appreciated.
Thanks,
Lee
Please sign in to leave a comment.
Hi
Waht OS do you use?
As I see in Starteam docs, there are separate SDK packages for 32-bit and 64-bit versions of Windows.
Related issue: TW-19100
Michael
We are using 64bit Windows Server 2003 on this machine. Starteam support says that they do not have a separate 64bit java SDK (or separate starteam110.jar); however, they do have 64bit runtime and that the 32 bit java SDK components should work with the 64bit jre.
I have tried everything but I still can't get TeamCity to recognize the starteam110.jar. It is in the location where TeamCity is asking me to put it but I keep getting the message that it cannot be found.
Thanks,
Lee
Hi Lee,
According to the stacktrace TeamCity does find the jar but it cannot be initialized properly.
...
Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.borland.starteam.impl.util.Platform
..
The reason is probably in incorrect or incomplete installation of 64-bit SDK. I've never seen such an error before so I can only guess.
Thanks for all the responses. I did finally receive some updated libraries from Starteam that did in fact support 64 bit Windows. After installing initially I still had the same problem. The problem was with the installer they sent me. When I ran it, a popup would flash briefly and close before I could tell what was happening. It turns out that the new SDK and runtimes were being installed to a different location without my knowledge. Once I found this out and copied over the updated SDK to where it was expected everything worked fine.
Thanks again for the replies.
Lee