[DDS-22] Recurrent problems with Nominatim. Created: 02/Nov/10 Updated: 02/Feb/21 Due: 02/Nov/10 Resolved: 03/Nov/10 |
|
| Status: | Closed |
| Project: | Demographic Data Server |
| Component/s: | None |
| Affects Version/s: | DemographicDataServer-1.2-GA |
| Fix Version/s: | DemographicDataServer-1.2-GA |
| Type: | Bug | Priority: | Medium |
| Reporter: | Nicolas Lefebvre | Assignee: | Nicolas Lefebvre |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 2 hours | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | 2 hours | ||
| Description |
|
I detected one problem with the Nominatim Web Services. In fact, sometimes, the Ws is unvailable. When this problem appears, the patient addresses generation is longer. It could be interesting, in this case, to only use the Google Ws during one or two hours. |
| Comments |
| Comment by Eric Poiseau [ 03/Nov/10 ] |
|
Integrated in DemographicDataServer #1100 (See http://sumo.irisa.fr:8080/hudson/job/DemographicDataServer/1100/) Add verification to intercept the Nominatim problems. |
| Comment by Nicolas Lefebvre [ 03/Nov/10 ] |
|
I added a verification for Nominatim using. Now, if the Nominatim Ws is unavailable, DDS uses Google Ws. DDS tests every hour if the Nominatim Ws is become available. For that, I add the "last_request_time" element in the "dds_web_service_information" table. |
| Comment by Eric Poiseau [ 04/Nov/10 ] |
|
Integrated in DemographicDataServer #1103 (See http://sumo.irisa.fr:8080/hudson/job/DemographicDataServer/1103/) |
| Comment by Nicolas Lefebvre [ 06/Jun/11 ] |
|
This issue has been fixed. |