Nuxeo DM 5.5 and PostgreSQL Locks

[gianclo_Lori]

Hi all,

We are using Nuxeo DM 5.5 with PostgreSQL 8.4.and we have a singular (almost for us) behavior of the system. For long period of time Nuxeo works well, we are able to insert, upload delete document and so on. Then after a several operation the system do not respond, but the server (tomcat) is up and the database also. After some investigation we have noted that during the period where nuxeo do not respond there are some transaction running in the database that i think create some locks. After 10-15 minutes the transactions are closed and Nuxeo respond and .. incredible the last operation has been done correctly. Any suggestions in order to solve this issue.. I attach the evidence of locks during the session where Nuxeo do not respond. Apologies in case the image is too big. Thanks in advance. Giancarlo

[Florent_Guillau]

Please use the jstack command to get a stack trace of the Nuxeo server while it's doing something unknown. Having the stack trace would help us understand what it's doing.

[gianclo_Lori]

Here part of stack error, when happens the problem. Thanks in advance.

[Florent_Guillau]

Seriously, this was unreadable. Such a huge stack trace is not suitable for this site. I removed it. Please post it to an external site designed for pastes (pastebin.com for instance) or give us just an extract.

[gianclo_Lori]

Sorry

[Florent_Guillau]

The error Resetting connection means that connection to the database was lost and had to be reset. You also see things like An I/O error occured while sending to the backend or Connection timed out.

[gianclo_Lori]

Thanks very much. We will investigate in our infrastructure firewalls, etc

[gianclo_Lori]

We have investigated in our infrastructure and yes we have some problem with firewalls that drops the connection after a certain period of time.

[Florent_Guillau]

To enable keep-alive on PostgreSQL connections you need to change:

1. the datasources (server.xml or nuxeo.xml or the relevant templates) to add tcpKeepAlive=true to the <Resource> for your datasource(s),
2. the repository configuration (default-repository-config.xml or its template) to add <property name="TcpKeepAlive">true</property>.

[gianclo_Lori]

Thank you very much. In reality we already made this configuration, but the datasource related to the repository seems do not keep in consideration the property. The difference is that we have typed "tcpKeepAlive" instead "TcpKeepAlive". As soon as possible we will made this change, and try again.