Running config.sh as part of Jira standalone installation and getting comm link failure to MySQL database.

randy hill September 4, 2012

Error is:

Attempting to connect to the MySQL database server...

Could not connect to the DB: Communications link failure

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.

I've modified the dbconfig.xml in $JIRA_HOME per your recommendations on your site and still get the error. I've also tried different ports for MySQL and still the same error. Help please!

Contents of dbconfig.xml:

<jira-database-config>

<name>defaultDS</name>

<delegator-name>default</delegator-name>

<database-type>mysql</database-type>

<jdbc-datasource>

<url>jdbc:mysql://localhost:3306/jira?useUnicode=true&characterEncoding=UTF8&sessionVariables=storage_engine=InnoDB</url>

<driver-class>com.mysql.jdbc.Driver</driver-class>

<username>jira</username>

<password> jira</password>

<pool-min-size> 20</pool-min-size>

<pool-max-size> 20</pool-max-size>

<pool-max-wait> 30000</pool-max-wait>

<validation-query>select 1</validation-query>

<min-evictable-idle-time-millis>60000</min-evictable-idle-time-millis>

<time-between-eviction-runs-millis>300000</time-between-eviction-runs-millis>

<pool-max-idle> 20</pool-max-idle>

<pool-remove-abandoned> true</pool-remove-abandoned>

<pool-remove-abandoned-timeout> 300</pool-remove-abandoned-timeout>

<pool-test-while-idle> true</pool-test-while-idle>

<validation-query-timeout>3</validation-query-timeout>

</jdbc-datasource>

</jira-database-config>

2 answers

1 accepted

0 votes
Answer accepted
randy hill October 9, 2012

Reinstalled MySQL and resolvd.

0 votes
Radu Dumitriu
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 4, 2012

Well, MySQL cannot be contacted. However, this is just a generic exception wrapped on the real cause. Please check the logs, and look for "caused by" stach trace. That should tell you what's wrong.

Suggest an answer

Log in or Sign up to answer