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

[gianclo_Lori]

Good morning,

[Florent_Guillau]

It works for me (the method setTcpKeepAlive of the XA datasource is called (checked with a breakpoint) when I add <property name="TcpKeepAlive">true</property> to the repository config.

[gianclo_Lori]

Hi Florent, thank you very much for you support. But probably there are some settings wrong that we made. I setted custom/template that replace the postgres default. We have tested it changing the property password with one wrong, and Nuxeo raise an error of wrong password, so we are sure that Nuxeo is using our custum tempalte, but the property TcpKeepAlive has no effect. We have only one datasource that works fine with the tcpkeepalive property as mentioned in the previuos comment. The datasources XA do not recognize the TcpKeepAlive property.

[Florent_Guillau]

Short of breakpointing in RepositoryBackend.initialize to see why the call to BeanUtils.setProperty doesn't do what you want, I don't see how to debug this.

[gianclo_Lori]

Solved.