Multiple instances problem

Amplus · Post by **Amplus** » Fri Mar 02, 2007 10:06 am

Hello,

does SourceOffside not support having multiple instances of Visual Studio 2003 open at the same time? I am working in one solution and it works fine but as soon as I open another Visual Studio solution in another instance everything hangs.

I have also noticed that if I open the SOS client and have a Visual Studio 2003 project open, then everything hangs as well. Can I only work in one project at a time?

Beth · Post by **Beth** » Fri Mar 02, 2007 10:37 am

I have found that depends on the environment. I have always been able to do that, but I have a few other customers who can't. It hasn't been narrowed down to what prevents some from being able to do that. There is a chance I think that the cache could get a bit confused with multiple instances writing to it at the same time.

Are you opening up the same project multiple times?
Are the projects very large?
Are any errors showing up in your server log?
Are you using the secure or unsecure port for connecting?

Amplus · Post by **Amplus** » Fri Mar 02, 2007 12:23 pm

Hello Beth,

I think things have become a little better after I followed the instructions in this post: http://support.sourcegear.com/viewtopic.php?t=10

I'm connecting to the server via VPN on an unsecure connection (secured with VPN). I do not have multiple instances of the same project open, always a different project that I open and yes, I guess you can say that the project is large - 162 objects in one project folder and 235 in the other.

Here is a portion of the error log. The last error is another issue I'm having but I know it has nothing to do with SOS.

2.3.2007 17:06:23 - Connection accepted from 10.15.20.156:2126 on local address 192.168.212.121:8888, session id is 4.
2.3.2007 17:06:28 - 4: Unable to get hostname from address: 10.15.20.156
2.3.2007 17:36:48 - Connection accepted from 10.15.20.156:2197 on local address 192.168.212.121:8888, session id is 5.
2.3.2007 17:36:53 - 5: Unable to get hostname from address: 10.15.20.156
2.3.2007 18:07:22 - 4: Exception: An existing connection was forcibly closed by the remote host
2.3.2007 18:07:46 - Connection accepted from 10.15.20.156:2242 on local address 192.168.212.121:8888, session id is 6.
2.3.2007 18:07:51 - 6: Unable to get hostname from address: 10.15.20.156
2.3.2007 18:12:14 - 6: SourceSafe was unable to finish writing a file. Check your available disk space, and ask the administrator to analyze your SourceSafe database. (8004d838)

Beth · Post by **Beth** » Fri Mar 02, 2007 2:53 pm

Since things have changed with the change in the automation component, what is it's behavior now?

Amplus · Post by **Amplus** » Tue Mar 06, 2007 8:15 am

Well I was able to open up 2 different projects in VisualStudio 2003 at the same time without a crash. Maybe I was just a little bit more patient waiting this time, maybe there is no difference at all.

If I am connected via the SOS client, before I open VS2003 and allow it to connect, the client crashes with the following message in the server log:

6.3.2007 14:08:47 - 8: Exception: An existing connection was forcibly closed by the remote host

Any ideas?

Amplus · Post by **Amplus** » Tue Mar 06, 2007 8:45 am

After the SOS client crashed I launched another VS2003 project with the following result in the server log:

6.3.2007 14:07:43 - 10: Unable to get hostname from address: 10.15.20.186
6.3.2007 14:08:47 - 8: Exception: An existing connection was forcibly closed by the remote host -> This is where the SOS client crashed
6.3.2007 14:25:53 - Connection accepted from 10.15.20.186:2693 on local address 192.168.212.121:8888, session id is 11. -> Connection ok for VS2003 project #1
6.3.2007 14:25:58 - 11: Unable to get hostname from address: 10.15.20.186
6.3.2007 14:26:09 - Connection accepted from 10.15.20.186:2696 on local address 192.168.212.121:8888, session id is 12. -> Connection ok for VS2003 project #2
6.3.2007 14:26:13 - 12: Unable to get hostname from address: 10.15.20.186

--- This is from VS2003 Source Control output: ----
---- Operation started at time 14:32:08 ----
Retrieving File List: $/.....
---- Operation completed successfully at time 14:32:10 ----
---- Operation started at time 14:32:10 ----
Retrieving File List: $/.....

By that I can see that VS2003 vas non responsive for 6 minutes (14:26:13 - 14:32:10) but eventually came back online. Patience is the key here. Do you have any idea why it hangs for 6 minutes when 2x projects are open?

lbauer · Post by **lbauer** » Tue Mar 06, 2007 10:23 am

Beth is out of the office today.

Do you have any idea why it hangs for 6 minutes when 2x projects are open?

Not really, though it could be because both clients are using the same client-side cache, and that cache might be locked while on client is writing to it. Also, two clients connecting at the same time and retrieving informaiton from the server takes longer than if one client is working.

Amplus · Post by **Amplus** » Tue Mar 06, 2007 2:25 pm

Can I do something to optimize the cache? I doubt that the latter explanation is at fault since the projects were not communicating at the same time. Project #1 was idle when I opened #2, unless SOS is constantly polling the SOS server?

Anther thing, why do you think the SOS client crashes when I open a SOS project in VS2003?

lbauer · Post by **lbauer** » Wed Mar 07, 2007 8:55 am

There's no way to optimize the cache.

The one thing all the clients have in common is that they use the same cache file. Do you experience these crashes when you use only one client at a time?

The SOS client or IDE may be locking the cache file even when it's not actively writing to it. Since we haven't tested the results of using multiple client instances I'm afraid I don't have a definitive answer for your questions.