| 2015-07-07 08:04:34 |
Daniele Viganò |
bug |
|
|
added bug |
| 2015-07-07 08:04:48 |
Daniele Viganò |
bug |
|
|
added subscriber Paul Henshaw |
| 2015-07-07 08:05:26 |
Daniele Viganò |
description |
When for some reasons the GED DB server is not available or it is restarted (PostgreSQL restart, network issues) and the connection are closed on the PostgreSQL side the Exposure application stops working until the whole platform is restarted.
This happens also if the platform server is started before the GED DB is up and running.
The GED API should trap the exception and it should try to re-establish the connection to the GED server. If it's unable to re-establish the connection a clear error should be reported (at least in the logs). |
When for some reason the GED DB server is not available or it is restarted (PostgreSQL restart, network issues) and the connection are closed on the PostgreSQL side the Exposure application stops working until the whole platform is restarted.
This happens also if the platform server is started before the GED DB is up and running.
The GED API should trap the exception and it should try to re-establish the connection to the GED server. If it's unable to re-establish the connection a clear error should be reported (at least in the logs). |
|
| 2015-07-07 08:06:04 |
Daniele Viganò |
description |
When for some reason the GED DB server is not available or it is restarted (PostgreSQL restart, network issues) and the connection are closed on the PostgreSQL side the Exposure application stops working until the whole platform is restarted.
This happens also if the platform server is started before the GED DB is up and running.
The GED API should trap the exception and it should try to re-establish the connection to the GED server. If it's unable to re-establish the connection a clear error should be reported (at least in the logs). |
When for some reason the GED DB server is not available or it is restarted (PostgreSQL restart, network issues) thus the connections are closed on the PostgreSQL side the Exposure application stops working until the whole platform is restarted.
This happens also if the platform server is started before the GED DB is up and running.
The GED API should trap the exception and it should try to re-establish the connection to the GED server. If it's unable to re-establish the connection a clear error should be reported (at least in the logs). |
|
| 2015-07-07 13:12:24 |
Daniele Viganò |
bug watch added |
|
http://code.djangoproject.com/ticket/15802 |
|
| 2015-07-07 13:30:48 |
Daniele Viganò |
oq-platform: status |
New |
In Progress |
|
| 2015-07-08 07:24:32 |
Daniele Viganò |
oq-platform: status |
In Progress |
Fix Committed |
|
