Hi,
Hope you are doing well.
Say when you create a CRL and click on OK, a preview message with the needed configuration settings will be sent to the custom subscribed list manager. (2)The manager parses the message and creates a preview thread, whose reference is saved in a thread map. The preview thread will be started immediately and contacts the given web server from the CSL configuration with the help of a curl library. It downloads the list content and completes the CSL. The whole completed list will be hold in the thread process in memory and is not written to disk. The preview process is a good test, if the given user settings are correct. If the preview failed, the customer could have made an input error. (4). During the preview process the GUI polls the custom subscribed list manager about the preview status. If the process was successful the GUI gets the list from the preview thread and displays it to the customer. After the preview message was sent to the gui or two minutes passed, the preview thread will be destroyed and deleted from the thread map.
A main thread runs every second over the map and inspects the time settings of the list object. If the object was quite recently created or the next execution time was passed, the main thread creates a new working thread, puts it into the thread map and starts the thread. If the node is a member of a cluster, this process will be done on every node in the cluster in parallel. The started working thread asks all nodes in the cluster, if it is allowed to make an update of the corresponding list. (3) If it is authorized to do, it downloads the list content from the configured web server, completes the CSL and saves it under the directory (4)/opt/mwg/storage/subscribed_lists/customer_lists. In a cluster, it sends the completed list to all other nodes; all other subsequent described actions from step 5 run in parallel on all cluster nodes. (5)The working thread notifies the core about the completed list and terminates. The results of the working thread, for example the update time or errors during the download etc.., will be saved in the object map. The list object in the map will persist and the main thread calculates the next execute time for it. (7) The GUI can fetch the list if needed. By fetching the list, the last modified date and the last update date are available for the content. The update status can be also queried by the gui if needed.
During some say f a preview result is not called by the gui, the thread resources are not released any more. The thread is ended, but the thread pointer will be not joined and not deleted from the map. This decreases the number of maximal 10 threads. If this happens more often no threads can be
started any more and a restart of the coordinator would be necessary.
You can restart the coordinator service and check using below command:-
service mwg-coordinator restart
Also you can plan to increase Maximum no of threads.
Was my reply helpful?
If you find this post useful, Please give it a Kudos! Also, Please don't forget to select "Accept as a solution" if this reply resolves your query!
Regards
Alok Sarda
You Deserve an Award
