Sonar

Sonar analysis is affected by connection timeout

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 2.11
  • Fix Version/s: 3.5
  • Component/s: Batch, Database
  • Labels:
    None
  • Environment:
    MySQL
  • Number of attachments :
    1

Description

Our Sonar instance is coupled with a MySQL DB. When JUnit tests take too much time (in our case more than 6 minutes) the MySQL connection seems to be closed. then Sonar analysis fails with:

...
[INFO] [cobertura:cobertura {execution: default-cli}]
[INFO] Cobertura 1.9.4.1 - GNU GPL License (NO WARRANTY) - See COPYRIGHT file
Cobertura: Loaded information on 51 classes.
Report time: 6623ms

[INFO] Cobertura Report generation was successful.
[INFO]  Execute org.codehaus.mojo:cobertura-maven-plugin:2.5:cobertura done: 403111 ms
[INFO]  Execute maven plugin cobertura-maven-plugin done: 403111 ms
[INFO]  Initializer CoberturaMavenInitializer...
[INFO]  Initializer CoberturaMavenInitializer done: 2 ms
[INFO]  Sensor JavaSourceImporter...
[WARN]  SQL Error: 0, SQLState: 08S01
[ERROR]  Communications link failure

The last packet successfully received from the server was 403 647 milliseconds ago.  The last packet sent successfully to the server was 12 milliseconds ago.
[ERROR]  Could not toggle autocommit
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

The last packet successfully received from the server was 403 652 milliseconds ago.  The last packet sent successfully to the server was 17 milliseconds ago.
...

Maybe we could solve the problem by removing the timeout (we are investigating). But I feel Sonar could be improved by not keeping an open connection during long operations like JUnit/cobertura/cpd.

This issue is in favor of a 2 stage analysis (see SONAR-2119).

  1. File
    sonar_log
    25/Jun/12 1:23 AM
    30 kB
    Pallav Jakhotiya

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Pallav Jakhotiya added a comment - - edited

We are facing the same issue with our setup and are just not able to get rid of this issue, the time taken to execute our tests is close to 90 minutes and once this is completed, the communication failure occurs. We tried to solve this by changing the sonar.jdbc.* parameters as well as the MYSQL Database configurations but just not able to fix this issue.

Any help on this will be much appreciated

Show
Pallav Jakhotiya added a comment - - edited We are facing the same issue with our setup and are just not able to get rid of this issue, the time taken to execute our tests is close to 90 minutes and once this is completed, the communication failure occurs. We tried to solve this by changing the sonar.jdbc.* parameters as well as the MYSQL Database configurations but just not able to fix this issue. Any help on this will be much appreciated
Hide
Permalink
Pallav Jakhotiya added a comment -

Attached the failure log, just in case you want to give this a look

Show
Pallav Jakhotiya added a comment - Attached the failure log, just in case you want to give this a look
Hide
Permalink
David Gageot added a comment -

I enforced the validation query for batch. But it doesn't fix all the problems

Show
David Gageot added a comment - I enforced the validation query for batch. But it doesn't fix all the problems
Hide
Permalink
leslie.cao added a comment - - edited

I have tried below two ways to fix this issue,but both of them are failed,

  • modify configuration of mysql DB,change value 'wait_timeout=388000' and 'interactive_timeout=388000' in file my.cnf
  • change 'sonar.jdbc.maxWait:9999' in sonar.properties to extend the expired time of connection which is defined for sonar connection pool.

I see this issue is still not be fixed in latest sonar version 3.2,could you comment if you plan to fix the issues in coming release,thank you.If you need more logs,I can attach it for you.I use Jenkins to be my sonar runner.

Show
leslie.cao added a comment - - edited I have tried below two ways to fix this issue,but both of them are failed, modify configuration of mysql DB,change value 'wait_timeout=388000' and 'interactive_timeout=388000' in file my.cnf change 'sonar.jdbc.maxWait:9999' in sonar.properties to extend the expired time of connection which is defined for sonar connection pool. I see this issue is still not be fixed in latest sonar version 3.2,could you comment if you plan to fix the issues in coming release,thank you.If you need more logs,I can attach it for you.I use Jenkins to be my sonar runner.
Hide
Permalink
Julien HENRY added a comment -

JPA session will now be closed before running Maven goal and before each sensor. A new session will be opened on next operation trying to access the DB.

Show
Julien HENRY added a comment - JPA session will now be closed before running Maven goal and before each sensor. A new session will be opened on next operation trying to access the DB.
Hide
Permalink
Freddy Mallet added a comment -

I've managed to reproduce this issue with the following scenario :

  • Add the following piece of code to a unit test 
    Thread.sleep(60000);
  • Launch a Sonar analysis
  • While unit tests are executed, kill all JDBC connections relating to the Sonar batch
  • And we get exactly the same exception at the same place
Show
Freddy Mallet added a comment - I've managed to reproduce this issue with the following scenario : Add the following piece of code to a unit test Thread .sleep(60000); Launch a Sonar analysis While unit tests are executed, kill all JDBC connections relating to the Sonar batch And we get exactly the same exception at the same place
Hide
Permalink
Julien HENRY added a comment -

It seems that autocommit=true on DBCP was conflicting with MyBatis and preventing validation query to works as expected. Forcing DBCP to autocommit=false seems to fix the issue.

Show
Julien HENRY added a comment - It seems that autocommit=true on DBCP was conflicting with MyBatis and preventing validation query to works as expected. Forcing DBCP to autocommit=false seems to fix the issue.
Hide
Permalink
Freddy Mallet added a comment -

Works well Julien !!

Show
Freddy Mallet added a comment - Works well Julien !!
Hide
Permalink
Pallav Jakhotiya added a comment -

Thanks so much for the fix, finally we are able to see all our Integration Unit test reports with the Sonar analysis now. Thanks again !

Show
Pallav Jakhotiya added a comment - Thanks so much for the fix, finally we are able to see all our Integration Unit test reports with the Sonar analysis now. Thanks again !

People

  • Assignee:
    Julien HENRY
    Reporter:
    Julien HENRY
Vote (3)
Watch (7)

Dates

  • Created:
    Updated:
    Resolved: