Contributions
CodeCollaborator v7.3.7303 64 bit server memory leak and corruption
In an environment with only a few reviews per day, our CodeCollaborator server process starts out taking about 80 MB for RAM, and as users access it shortly goes up to about 110 MB. This seems pretty normal. Over a week or two, the process continues to grow. When it gets over half a gigabyte or so, the server starts rejecting some randomreviews. I've seen it up to 800 MB. Bouncing the CC server process clears the issue up. The log doesn't appear to have anything out of the ordinary in it. Platform info: Windows Server 2008 R2 64 bit SQL Server 2008 R2 LDAP authentication Java was initially the recommended version now 1.6u384.7KViews0likes2CommentsRe: Upgrading from 32 bit 6.5 to 64 bit 7.3
I stopped the server, uninstalled the 32 bit version 6 and installed the 64 bit current version 7 as a new installation using the old database. I also installed a 64 bit JRE.. Two minor issues: When filling in the database info in the installer, since there is not a field to enter a "connection URL", I ignored trying to figure it out and left Schema at the default. It turns out that the Schema field would have populated the ROOT.xml correctly with a connection URL. What's up with that? Using the example LDAP configuration as a template didn't work, but that was easy to fix in the ROOT.xml file. I edited both in the ROOT.xml and life was good. This is SO much easier than the upgrade procedure in the manual of dumping and restoring the database. Now I just have to get past my Perforce trigger authentication issues. Remember to back everything up before you do anything.844Views0likes0CommentsUpgrading from 32 bit 6.5 to 64 bit 7.3
What is the best path for upgrading from 32 bit v6.5 to 64 bit v7.3 without having to install in the "Program Files (x86)" folder. I want to install v7.3 in the default installation folder and migrate my current settings to the new installation.8.4KViews0likes2Comments