-
March 20th, 2012, 09:16 AM
#2
The LSClient object enforces serialization on the OpenConnection and CloseConnection methods.
This means that if one OpenConnection is blocked, the block may propagate to any subsequent CloseConnection and OpenConnection that you invoke on different threads.
In this regard, using different instances of the LSClient object is better.
In fact, there is no important reason to suggest keeping the same object.
But note that connections blocked for any reason can keep other connection attempts blocked anyway, in case the client runtime keeps a small connection pool.
Can your case fall within the above scenarios?
If not, could you manage to get a full thread dump of the .NET client process while it is blocked?
Similar Threads
-
By LS_Developer in forum Client SDKs
Replies: 1
Last Post: March 20th, 2012, 08:51 AM
-
By deltron0 in forum Client SDKs
Replies: 6
Last Post: September 15th, 2010, 08:33 AM
-
By pacesie in forum General
Replies: 1
Last Post: March 26th, 2008, 09:01 AM
-
By indrajit in forum Adapter SDKs
Replies: 1
Last Post: February 22nd, 2008, 08:39 AM
-
By deltron0 in forum Client SDKs
Replies: 2
Last Post: February 5th, 2008, 05:28 PM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 10:42 AM.
Bookmarks