Connection pool does not create connections

[Dmitrii Apanasevich]

Hi!

I have faced with this problem on production server. JIRA becomes unavailable.

Query

select * from pg_stat_activity

returns only one connection.

PostgreSQL 9.2 and JIRA 5.0.4 run on the same server.

My dbconfig:

<jira-database-config>
  <name>defaultDS</name>
  <delegator-name>default</delegator-name>
  <database-type>postgres72</database-type>
  <schema-name>public</schema-name>
  <jdbc-datasource>
    <url>jdbc:postgresql://localhost:5432/jiradb</url>
    <driver-class>org.postgresql.Driver</driver-class>
    <username>***</username>
    <password>***</password>
    <pool-size>50</pool-size>
    <validation-query>select version();</validation-query>
    <validation-query-timeout>2</validation-query-timeout>
    <min-evictable-idle-time-millis>10000</min-evictable-idle-time-millis>
    <time-between-eviction-runs-millis>50000</time-between-eviction-runs-millis>

    <pool-max-idle>20</pool-max-idle>
    <pool-remove-abandoned>true</pool-remove-abandoned>
    <pool-remove-abandoned-timeout>50</pool-remove-abandoned-timeout>
    <pool-test-while-idle>true</pool-test-while-idle>
    <pool-prepared-statements>true</pool-prepared-statements>
  </jdbc-datasource>
</jira-database-config>

There are no exceptions in log file concerned with connection pool.

What is the problem?

I need to decrease some parameter?

[Dmitrii Apanasevich · Accepted solution]

Well, I have found in GC log concurrent mode failure. Also found that at the time the xml-backup service worked.

I turned off this service, as recommended here https://confluence.atlassian.com/display/JIRA/Automating+JIRA+Backups

I will look further.

[Nic Brough -Adaptavist-]

If there are no exceptions in the log, why do you think it's a connection pool error?

What does the log file actually say is wrong when "Jira becomes unavailable"? Have you looked at all the resources on the system? CPU, memory etc? You need to try to establish what the error really is, not just assume it's a database problem.

[Peter Van de Voorde]

Hi Dimitri,

Like Nic says: take a look in the JIRA log files.

Because the one connection that your query is returning is the connection you are using to execute that query. So it seems to me that there is already a problem before JIRA even tries to connect to the database.

Best regards,

Peter

[Dmitrii Apanasevich]

No Peter. I have one connection except that I have used to run the query.

[Dmitrii Apanasevich]

Thanks for your answer, Nic!

You are right I don't know a real cause. I started with DB problem because it is that i see.

What does the log file actually say is wrong when "Jira becomes unavailable"?

I can't find any appropriate exceptions, just

2014-06-24 10:42:30,711 http-8090-105 ERROR username 640x34291x15 ks7xg5 100.112.6.126 /secure/QuickCreateIssue.jspa [jira.issue.index.DefaultIndexManager] Wait attempt timed out - waited 30000 milliseconds
com.atlassian.jira.issue.index.IndexException: Wait attempt timed out - waited 30000 milliseconds

or

2014-06-24 12:28:54,810 http-8090-97 ERROR anotherusername 748x22138x146 16udnqy 100.112.6.157 /secure/Dashboard.jspa [renderer.internal.http.HttpClientFetcher] Unable to retrieve response
org.apache.http.conn.ConnectTimeoutException: Connect to myjira/127.0.0.1:8090 timed out

I have low CPU usage, less than 10% even when JIRA unavailable.

I can't access secure/admin/ViewMemoryInfo.jspa at problem time. At the other time i see something like this

I will enable GC log also.

Maybe there is a memory problem, how to check it?