-
August 13th, 2009, 09:43 AM
#1
Something is slowing down the accomplishment of subscription requests.
This is put into evidence by the compound requests:
After the log of:
<Subrequest 1: ....
<Subrequest 2: ....
<Subrequest 3: ....
in a normal case, you should see
<Controlling session: ....
<Controlling session: ....
<Controlling session: ....
in rapid sequence.
However, in your case, after the first occurrence, there is a significant time gap.
Such delays may cause the client to reissue some subscription requests
(just in case they got lost) until it eventually gets an answer.
The observed delays must have been introduced by some calls to the Metadata Adapter or in the "subscribe" calls to the Data Adapter.
In the forthcoming (3.6) release, the Server will be more robust to delays in Adapter calls;
for now, you should ensure that most of them don't introduce delays,
by following the guidelines suggested in the Adapter javadocs.
Similar Threads
-
By chanro4 in forum Client SDKs
Replies: 4
Last Post: January 19th, 2011, 09:29 AM
-
By mnenchev in forum General
Replies: 5
Last Post: September 8th, 2009, 03:07 PM
-
By webfg in forum Client SDKs
Replies: 3
Last Post: July 3rd, 2009, 08:44 AM
-
By pyuvienco in forum Client SDKs
Replies: 1
Last Post: July 2nd, 2008, 08:20 AM
-
By indrajit in forum General
Replies: 2
Last Post: March 5th, 2008, 06:29 AM
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:13 AM.
Bookmarks