Results 1 to 2 of 2
  1. #1
    Member
    Join Date
    Oct 2008
    Location
    Abu Dhabi
    Posts
    3

    Current delay in log file

    Quote Originally Posted by DarioCrivelli View Post
    I confirm that, upon the above kind of closure, the Server finds the socket closed by the client.
    So, the Server can no longer send updates to the client and it can only wait for the client to connect again and open a new session.
    When the client resubscribes to the same items, the lost updates can still be sent to it as part of the snapshot. The way depends on the subscription mode and other subscription settings.

    If you see many 38 closures at the same time, that could be caused by an interruption at network level.
    Serious problems on the Server side, leading to repeated "current delay ..." log messages could also cause that.
    If you see many subsequent 38 closures for the same client, client side problems are also possible; see this thread, for instance.
    i am receiving a lot of "Current delay " messages in the log file and the data is not loading:

    14-Feb-12 13:34:52,717 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 869 seconds
    14-Feb-12 13:34:54,717 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 871 seconds
    14-Feb-12 13:34:56,718 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 873 seconds
    14-Feb-12 13:34:58,720 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 875 seconds
    14-Feb-12 13:35:00,730 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 877 seconds
    14-Feb-12 13:35:02,740 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 879 seconds
    14-Feb-12 13:35:04,750 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 881 seconds
    14-Feb-12 13:35:06,755 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 883 seconds
    14-Feb-12 13:35:08,760 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 885 seconds
    14-Feb-12 13:35:10,760 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 887 seconds
    14-Feb-12 13:35:12,761 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 889 seconds
    14-Feb-12 13:35:14,761 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 891 seconds
    14-Feb-12 13:35:16,762 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 893 seconds
    14-Feb-12 13:35:18,762 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 895 seconds
    14-Feb-12 13:35:20,763 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 897 seconds
    14-Feb-12 13:35:22,770 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 899 seconds
    14-Feb-12 13:35:24,774 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 901 seconds
    14-Feb-12 13:35:26,774 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 903 seconds
    14-Feb-12 13:35:28,780 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 905 seconds
    14-Feb-12 13:35:30,790 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 907 seconds
    14-Feb-12 13:35:32,800 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 909 seconds
    14-Feb-12 13:35:34,805 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 911 seconds
    14-Feb-12 13:35:36,806 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 913 seconds
    14-Feb-12 13:35:38,810 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 915 seconds
    14-Feb-12 13:35:40,819 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 917 seconds
    14-Feb-12 13:35:42,824 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 919 seconds
    14-Feb-12 13:35:44,830 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 921 seconds
    14-Feb-12 13:35:46,840 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 923 seconds
    14-Feb-12 13:35:48,850 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 925 seconds
    14-Feb-12 13:35:50,855 |WARN |LightstreamerLogger.scheduler |Thread-9 |Current delay for tasks scheduled on thread pool DATA GetData.DEFAULT is 927 seconds

  2. #2
    Administrator
    Join Date
    Jul 2006
    Location
    Milan
    Posts
    851
    The specified thread pool has been configured in association with the "GetData" Adapter Set and, in particular, with the "DEFAULT" Data Adapter (Note that a Data Adapter configured with no name takes the "DEFAULT" name).

    When you see that message, it means that the tasks performed by the pool are very slow, or even blocked.
    In particular, this pool is used to perform subscriptions and unsubscriptions to the associated Data Adapter. This may involve many invocations to the Data Adapter and also the Metadata Adapter and we assume that the blocks occur there.
    You should just take a full thread dump of the Server JVM and this should allow you to find the points in which the threads are blocked.

 

 

Similar Threads

  1. Unexpected Delay
    By omidqrose in forum Architecture - Integration - Deployment
    Replies: 2
    Last Post: May 23rd, 2011, 01:44 PM
  2. Log file error
    By colmfield in forum JavaScript Client API
    Replies: 4
    Last Post: September 21st, 2010, 12:11 PM
  3. Delay in notifyUser() causes erratic create_session behavior
    By brianjohnson in forum Java Adapter API
    Replies: 2
    Last Post: April 5th, 2010, 01:02 PM
  4. Get current value in OverwiteTable.OnChangingValues
    By euroinvestor in forum JavaScript Client API
    Replies: 1
    Last Post: June 10th, 2009, 04:21 PM
  5. where to put the licence file?
    By janjons in forum Architecture - Integration - Deployment
    Replies: 1
    Last Post: September 23rd, 2008, 10:50 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Powered by vBulletin® Version 4.2.0
Copyright © 2014 vBulletin Solutions, Inc. All rights reserved.
All times are GMT +1. The time now is 10:42 AM.