Open meghnas opened 9 years ago
On Thursday, we had a new release of AIDR (v2.0), which required stopping all collections and restarting when the new release was deployed. That is why the collection was stopped.
The collection history did not get updated because the collections were not manually stopped from the UI. So all collections that were running on Thursday when the system was stopped for upgrade would have a missing entry from collection history
@collected tweets not being updated - yes that is an issue I noticed in your collection. Investigating why it wasnt being updated even though the collection status was "running" but no new tweets were being generated.
For the same collection, when Ingmar tried to login to AIDR to restart the collection, the following error was received:
HTTP Status 401 - Authentication Failed: SpringSocialSecurity sign in details not found in session type: Status report message: Authentication Failed: SpringSocialSecurity sign in details not found in session description: This request requires HTTP authentication.
We found the reason for tweets not being updated - there was a thread pool issue in the glassfish server which caused the collections to stop working, and an issue in the code that did not update the status to "not running" and continued to display "running" status. The thread pool issue has now been resolved. The next release of AIDR will address the code issue.
As reported by Ingmar Webber: