|
|
|
|
 | |  |
| Basically the current implementation is not threaded and hence there is no timeout on a Db call. | |
 | |  |
|
 |
| | |
| So it is geocoded and geo-assigned now after the restart? | |
| | |
|
|
|
|
|
|
|
| | |
| Well, sometimes the Db Call does not return and the call waits on it forever! No idea why. | |
| | |
|
 |
| | |
| Maybe the new implementation in QA is threaded and times out automatically. | |
| | |
|
|
|
|
|
|
|
| | |
| After waiting for a specified time? | |
| | |
|
|
|
|
