we are using lighstremer for a while now , but unfortunately for the last month we are facing unknown problems with it, for example unsubscribe for items and a very strange delay on responding and this last one happened occasionally , i am sure that the fix is simple but i can't find it . so please i need your help to deal with this situation because i am only one week for launching my software that receive its data from the lightstreamer. and if you got paid service to help me to ensure the lightstreamer will work perfectly please tell me more
I checked the log and indeed, I found a scenario where unsubscribe delays occurs.
I am referring at 12:15:31 when two Lightstreamer sessions go down. In this case the server calls unsubscribe method of Data Adatpter for all Items subscribed by the sessions.
About 15 seconds later the log reports many messages like this:
"Exception caught while unsubscribing from item 'ts164': Timeout while waiting for an answer to request 4e100000147670276d9"
I count about 120 messages, so I suppose that the number of total unsubcribe calls is much higher.
Please could you confirm if your unsubscribe method implementation is particularly heavy and, maybe, it requires calls to external components? Please note that in a case such your, with Remote adapters and several hundreds of calls involved, just only a processing time of few tenths of a second may result in significant delays.
Since one of our suspicions is that the server remains for a long time waiting for answers from the Metadata Adapter, a first possibility of change in the Lightstreamer server configuration, in order to mitigate the issue, is to increase the size of the SERVER thread pool.
A first suggestion would be to raise it to 100. Please refer to <server_pool_max_size> parameter in "lightstreamer_conf.xml" configuration file.
Furthermore, please could you set to TRACE level this logger (lightstreamer_log_conf.xml):
and if the issue happens again send us the updated log?
Dears,
i am trying now your update 5.1.2 , and i have a license , but i found a message that say you have limited session or something like that.
in the attached pic for the 5.1.1 monitor after i started it.
The 20 session limit is the limit of the DEMO license: this means that the license was not correctly configured in the new installation.
Please check the conf/lightstreamer_version_conf.xml
<!-- Configure the type of license that should be used to run Lightstreamer. -->
<license>
<!-- License type to be used.
Can be one of the following:
- DEMO: The server is fully featured, has no time bomb, and puts a
limit of max 20 concurrent users sessions. Does not require either
a license file or access to the license server. Can be used only for
evaluation, testing, and development; not for production.
- LICENSE_FILE: A license file is required, which determines the
features to be enabled and any constraint.
- LICENSE_SERVER: Access to the online license server is required,
which determines the features to be enabled and any constraint. -->
<type>DEMO</type>
<!-- Used if license type is set to DEMO -->
<demo>
<!-- Make Lightstreamer Server run as any of the available editions.
Can be one of the following:
- Allegro
- Presto
- Vivace -->
<edition>Vivace</edition>
</demo>
<!-- Used if license type is set to LICENSE_FILE -->
<license_file>
<!-- Cumulative. Path and name of the license file
for Lightstreamer Server, relative to the conf directory.
If multiple occurrences of <license_path> are supplied, the files
are all evaluated and the first acceptable one is considered. This
is useful in case the visible MAC addresses may change among
a fixed set during the life of the Server.
Example: mylicensefile.lic -->
<license_path>STTI_005056830038_Allegro.lic</license_path>
</license_file>
<!-- Used if license type is set to LICENSE_SERVER -->
<license_server>
<!-- Make Lightstreamer Server run as any of the available editions,
only if the license server does not impose the edition.
Can be one of the following:
- Allegro
- Presto
- Vivace -->
<edition>Vivace</edition>
</license_server>
<!-- Path of the directory in which to store the audit log file,
relative to the conf directory. The audit log reports statistics
on the number of concurrent sessions and is produced for some
types of licenses only. -->
<audit_log_path>../audit</audit_log_path>
<!-- Configure the type of license that should be used to run Lightstreamer. -->
<license>
<!-- License type to be used.
Can be one of the following:
- DEMO: The server is fully featured, has no time bomb, and puts a
limit of max 20 concurrent users sessions. Does not require either
a license file or access to the license server. Can be used only for
evaluation, testing, and development; not for production.
- LICENSE_FILE: A license file is required, which determines the
features to be enabled and any constraint.
- LICENSE_SERVER: Access to the online license server is required,
which determines the features to be enabled and any constraint. -->
<type>LICENSE_FILE</type>
<!-- Used if license type is set to DEMO -->
<demo>
<!-- Make Lightstreamer Server run as any of the available editions.
Can be one of the following:
- Allegro
- Presto
- Vivace -->
<edition>Vivace</edition>
</demo>
<!-- Used if license type is set to LICENSE_FILE -->
<license_file>
<!-- Cumulative. Path and name of the license file
for Lightstreamer Server, relative to the conf directory.
If multiple occurrences of <license_path> are supplied, the files
are all evaluated and the first acceptable one is considered. This
is useful in case the visible MAC addresses may change among
a fixed set during the life of the Server.
Example: mylicensefile.lic -->
<license_path>STTI_005056830038_Allegro.lic</license_path>
</license_file>
<!-- Used if license type is set to LICENSE_SERVER -->
<license_server>
<!-- Make Lightstreamer Server run as any of the available editions,
only if the license server does not impose the edition.
Can be one of the following:
- Allegro
- Presto
- Vivace -->
<edition>Vivace</edition>
</license_server>
<!-- Path of the directory in which to store the audit log file,
relative to the conf directory. The audit log reports statistics
on the number of concurrent sessions and is produced for some
types of licenses only. -->
<audit_log_path>../audit</audit_log_path>
</license>
<!--
-------------------------
and its the same
what i suppose to insert in client_id or where i can get it , and i have to delete <type>DEMO</type> ??
the 5.1.1 file is correct, notice the <type>LICENSE_FILE</type> and that the <client_id> is filled with your client id.
You can use this 5.1.1 file with your 5.1.2 installation
Bookmarks