Rather than being a problem locating the Java Virtual Machine, as I’d previously thought, turns out it’s a memory allocation issue. In StarTeamCP.stjava, the default option set is “-Xmx1024m”. My machine doesn’t have a gig of RAM to spare for a Java VM, hence the error. By setting it to “-Xmx512m”, I was able to get up and running.

I’m posting this in the hopes someone can profit from my struggles this morning. Deep shame be unto Borland for:

1) Making the default 1 GB, which is unrealistic for quite a few machines, mine included2) Not putting it in their Platform Notes with the release documentation.

I watched StarTeam launch with Task Manager. As Tess Ferrandez points out in a post on .NET memory usage, Virtual Memory Size can be a more useful counter than the normal one.

It showed that StarTeam was using up hundreds of megabytes before I got the message. I asked myself why it was taking so much memory, so I did some internet research on Java virtual machine memory allocation, which led me to discover what I shared in the post.

Yeah! It worked for me two… I tryed everything and I spent a lot of hours trying to solve that. I reinstalled this SW thousand of times, I tryed to change some entries in the registry… but the solution was so simple that makes me feel embarissing! Thank you for sharing this with us.