dcm4chee cannot reconnect to postgres after postgres restarted (for example after ubuntu security upgrade)

[Maximilien Renard]

Hi,

We have noticed that dcm4chee must be restarted in case the connection to postgres has been lost. At each attempt of a connection to the db after such an event, dcm4chee outputs a lot of Broken pipe socket exceptions.

This happens typically each time a security upgrade for postgresql is made. After it is installed, postrgres restarts and dcm4chee starts failing. 

Is this an expected behaviour? Shouldn't there be a mechanism to detect such events and try to reconnect to the db? If it is expected, what solution would you advise to circumvent that problem in production system?

Thanks in advance.

Best regards,

Maximilien Renard