Jira DC 10.3.6
Ubuntu-24
Postgresql-14
Driver: postgresql-42.7.3.jar
Puppet 7
puppet-jira 6.2.1
The puppet-jira by default set SocketTimeout=240 but Jira ignores/removes it during startup and puppet changes it on every run.
https://github.com/voxpupuli/puppet-jira/blob/master/manifests/config.pp#L154
Notice: /Stage[main]/Jira::Config/File[/home/jira/dbconfig.xml]/content:
--- /home/jira/dbconfig.xml 2025-06-03 12:57:18.678776295 +0200
+++ /tmp/puppet-file20250603-6059-keruy1 2025-06-03 13:02:50.682048189 +0200
@@ -21,6 +21,6 @@
<pool-remove-abandoned-timeout>300</pool-remove-abandoned-timeout>
<pool-test-on-borrow>false</pool-test-on-borrow>
<pool-test-while-idle>true</pool-test-while-idle>
- <connection-properties>tcpKeepAlive=true</connection-properties>
+ <connection-properties>tcpKeepAlive=true;socketTimeout=240</connection-properties>
</jdbc-datasource>
</jira-database-config>
As Workaround, we set the connection_settings with no socketTimeout=240:
connection_settings => 'tcpKeepAlive=true',
https://support.atlassian.com/jira/kb/connection-problems-to-postgresql-result-in-stuck-threads-in-jira/
"This property will no longer be added to database configuration since Jira 9.4 and will be ignored for existing configurations."
Jira DC 10.3.6
Ubuntu-24
Postgresql-14
Driver: postgresql-42.7.3.jar
Puppet 7
puppet-jira 6.2.1
The puppet-jira by default set SocketTimeout=240 but Jira ignores/removes it during startup and puppet changes it on every run.
https://github.com/voxpupuli/puppet-jira/blob/master/manifests/config.pp#L154
As Workaround, we set the connection_settings with no socketTimeout=240:
connection_settings => 'tcpKeepAlive=true',https://support.atlassian.com/jira/kb/connection-problems-to-postgresql-result-in-stuck-threads-in-jira/
"This property will no longer be added to database configuration since Jira 9.4 and will be ignored for existing configurations."