Vault API will periodically hang when calling .login

This forum is now locked, since Gold Support is no longer offered.

Moderator: SourceGear

Locked
dking513
Posts: 48
Joined: Tue Apr 20, 2004 3:23 pm

Vault API will periodically hang when calling .login

Post by dking513 » Tue Aug 17, 2004 11:05 pm

Periodically my .net assembly will hang when calling the .login method of the vault api.

If I launch the GUI client while experiencing this problem, and login with the same credentials, it suffers no delay.

I have to ctrl-alt-delete the program using the api, and then try again. It always works the second time, and usually doesn't hang but once every couple dozen tries.

I have a VPN connection to the Vault server - which is running windows 2000 server.

Any ideas of what is causing this, or how I can further trace the problem?

Thanks,
Dave

sterwill
Posts: 256
Joined: Thu Nov 06, 2003 10:01 am
Location: SourceGear

Post by sterwill » Wed Aug 18, 2004 8:42 am

It's possible that the login process in the API is hanging on a few different web service calls that are made under your call to ClientInstance.Login. You can turn your Vault server's log level to "Debug" (can be done in the admin tool) and watch the server logs to see which web service methods have been invoked before the hang.
Shaw Terwilliger
SourceGear LLC
`echo sterwill5sourcegear6com | tr 56 @.`

dking513
Posts: 48
Joined: Tue Apr 20, 2004 3:23 pm

Debug option doesn't record any activity when .login hangs.

Post by dking513 » Fri Aug 20, 2004 11:32 am

I turned on the debug option on the server.
When the call to .login hangs, I do not see any activity in the log at all.
If I then launch the GUI client, it logs in fine, and I see all the login activity in the log file.

Any ideas?

sterwill
Posts: 256
Joined: Thu Nov 06, 2003 10:01 am
Location: SourceGear

Post by sterwill » Fri Aug 20, 2004 12:13 pm

Do you see any entries in the IIS log file (usually in C:\WINDOWS\SYSTEM32\Logfiles\W3SVC1) that would correspond to the (hung) login attempt? If not, you may need to use a TCP/IP level packet inspector (Ethereal is very good, and free) to make sure the login web request is actually making it to the network.
Shaw Terwilliger
SourceGear LLC
`echo sterwill5sourcegear6com | tr 56 @.`

dking513
Posts: 48
Joined: Tue Apr 20, 2004 3:23 pm

Finally figured it out.

Post by dking513 » Sat Nov 06, 2004 10:21 am

I ran across another post regarding intermittent problems with the vault client:
http://support.sourcegear.com/viewtopic.php?t=994

This suggested a problem with http keep-alive enabled.

I disabled this on my vault server, and am no longer having issues with my api application.

Just thought I would post this in case others are having similar difficulty.

Locked