-
April 30th, 2010, 12:07 PM
#1
I've been meaning to post a quick heads up as to what was going wrong since we solved the issue (on the Friday of the week of the last post here, sorry about the delay). .Net has a limit on the number of external connections but not internal ones. As such, when running locally all the connections could connect. Running external mean only the first 2 (the .Net default on a 32 bit Vista machine) connections were allowed. The rest received a .Net exception which the Lightstreamer library was catching and throwing it's own (which is why it wasn't trivial to find the solution.). To solve this we increased the .Net limit for external connections. In future we will move to a single connection for all subscriptions.
-
May 3rd, 2010, 09:31 AM
#2
Hi Stephen,
Thanks for this update, much appreciated.
Alessandro
-
May 3rd, 2010, 11:25 AM
#3
About .NET library exception management, which unfortunately has been misleading for you,
I would like to clarify that the source system exception is available to application code
as the "InnerException" property of the PushConnException received.
Similar Threads
-
By webmons in forum Adapter SDKs
Replies: 3
Last Post: March 7th, 2013, 09:30 AM
-
By kclerc in forum Adapter SDKs
Replies: 7
Last Post: April 12th, 2010, 11:40 AM
-
By mnfjorge in forum Client SDKs
Replies: 1
Last Post: March 24th, 2010, 08:52 AM
-
By tstojano in forum Adapter SDKs
Replies: 3
Last Post: August 18th, 2008, 12:55 PM
-
Replies: 1
Last Post: March 15th, 2007, 02:44 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 06:56 PM.
Bookmarks