|
clouds, hotspot, violations not displaying/IndexOutOfBoundsException in GWT
Yesterday, after analyzing some older code snapshots (using -Dsonar.projectVersion=... -Dsonar.projectDate=...) with sonar 1.10.1, the clouds, hotspots and violations drilldown stopped displaying for the analyzed projects. These features continue to work correctly for other projects.
A quick check of the browser javascript console (Chrome and FF+Firebug) when forcing a refresh of the clouds shows:
" uncaught exception: java.lang.IndexOutOfBoundsException /sonar/deploy/gwt/org.sonar.plugins.core.clouds.GwtClouds/3117E30EE95648FD75D9A24B2E376C75.cache.html:599"
I searched around and found this thread[1] and decided to upgrade in hope this problem may have already been fixed.
The upgrade went smoothly and we're now running sonar 1.11.1 but all the same problems exist for the effected projects. Note, I haven't yet been able to run an analysis due to a NPE during maven execution. I suspect this is a result of the same problem with the clouds and hotspots.
Returning to the email thread[1], I upped the servers maxmemory to 1024, restarted, and tried calling some of the REST apis directly from FF. The first service call[2] for one of the effected projects results in a "resources.php" file containing only "callback5([]);" -- the sonar.log contains no errors for this request. Repeating the service call for an unaffected project returns callback5 with a whole bunch more JSON content.
Also, after the upgrade, one of the projects is displayed 3 times in the sonar project list where it used to only be displayed once. Each project has a different index, as shown in the url, and appear to be separated by time. The most recent of these projects contains all the events (versions) of the other 2 -- not sure if this is related at all.
The upgrade docs[3] mention a purge process that triggers after each analysis. Is there a way to trigger this manually (e.g, SQL)?
Other info that may be relavant:
* using postgres 8.3.8 * CentOS 5.3
Any help is appreciated.
TIA, Doug
|
|
Re: clouds, hotspot, violations not displaying/IndexOutOfBoundsException in GWT
Hello Doug, Let's try the initial problem first. I don't think that you hit the problem described in [1] as this problem occurred after an upgrade in 1.11 and did not exist in 1.10. I think you have found a bug that occurs on Clouds and Hotspots after running a project with projectDate parameter. What I would recommend is that after the analysis with "projectDate", to run a "normal" analysis and make sure everything goes back to normal. If that is the case, can I then ask you to file an issue in Jira ?
On the second issue, the most important thing is to be able to run the first analysis as it will put many things squared. Could you have a look at
SONAR-1118, it looks similar to your issue... There is a work around in it. If that is not ok, can you give some more information (log file, special config) or ideally send a sample project to reproduce the issue ?
Olivier
On Thu, Nov 5, 2009 at 5:33 PM, Doug Douglass <douglass.doug@...> wrote:
Yesterday, after analyzing some older code snapshots (using -Dsonar.projectVersion=... -Dsonar.projectDate=...) with sonar 1.10.1, the clouds, hotspots and violations drilldown stopped displaying for the analyzed projects. These features continue to work correctly for other projects.
A quick check of the browser javascript console (Chrome and FF+Firebug) when forcing a refresh of the clouds shows:
" uncaught exception: java.lang.IndexOutOfBoundsException /sonar/deploy/gwt/org.sonar.plugins.core.clouds.GwtClouds/3117E30EE95648FD75D9A24B2E376C75.cache.html:599"
I searched around and found this thread[1] and decided to upgrade in hope this problem may have already been fixed.
The upgrade went smoothly and we're now running sonar 1.11.1 but all the same problems exist for the effected projects. Note, I haven't yet been able to run an analysis due to a NPE during maven execution. I suspect this is a result of the same problem with the clouds and hotspots.
Returning to the email thread[1], I upped the servers maxmemory to 1024, restarted, and tried calling some of the REST apis directly from FF. The first service call[2] for one of the effected projects results in a "resources.php" file containing only "callback5([]);" -- the sonar.log contains no errors for this request. Repeating the service call for an unaffected project returns callback5 with a whole bunch more JSON content.
Also, after the upgrade, one of the projects is displayed 3 times in the sonar project list where it used to only be displayed once. Each project has a different index, as shown in the url, and appear to be separated by time. The most recent of these projects contains all the events (versions) of the other 2 -- not sure if this is related at all.
The upgrade docs[3] mention a purge process that triggers after each analysis. Is there a way to trigger this manually (e.g, SQL)?
Other info that may be relavant:
* using postgres 8.3.8 * CentOS 5.3
Any help is appreciated.
TIA, Doug
|
|
Re: clouds, hotspot, violations not displaying/IndexOutOfBoundsException in GWT
Thanks Olivier! Your diagnosis of both problems was spot on.
One of the effected projects was not a maven multi-project, so not effected by SONAR-1118. Running a new, trunk analysis fixed that project. For the other, multi-module project, running the analysis after a separate mvn clean package fixed that one.
Doug On Thu, Nov 5, 2009 at 1:27 PM, Olivier Gaudin <gaudol@...> wrote:
Hello Doug,
Let's try the initial problem first. I don't think that you hit the problem described in [1] as this problem occurred after an upgrade in 1.11 and did not exist in 1.10. I think you have found a bug that occurs on Clouds and Hotspots after running a project with projectDate parameter. What I would recommend is that after the analysis with "projectDate", to run a "normal" analysis and make sure everything goes back to normal. If that is the case, can I then ask you to file an issue in Jira ?
On the second issue, the most important thing is to be able to run the first analysis as it will put many things squared. Could you have a look at
SONAR-1118, it looks similar to your issue... There is a work around in it. If that is not ok, can you give some more information (log file, special config) or ideally send a sample project to reproduce the issue ?
Olivier
On Thu, Nov 5, 2009 at 5:33 PM, Doug Douglass <douglass.doug@...> wrote:
Yesterday, after analyzing some older code snapshots (using -Dsonar.projectVersion=... -Dsonar.projectDate=...) with sonar 1.10.1, the clouds, hotspots and violations drilldown stopped displaying for the analyzed projects. These features continue to work correctly for other projects.
A quick check of the browser javascript console (Chrome and FF+Firebug) when forcing a refresh of the clouds shows:
" uncaught exception: java.lang.IndexOutOfBoundsException /sonar/deploy/gwt/org.sonar.plugins.core.clouds.GwtClouds/3117E30EE95648FD75D9A24B2E376C75.cache.html:599"
I searched around and found this thread[1] and decided to upgrade in hope this problem may have already been fixed.
The upgrade went smoothly and we're now running sonar 1.11.1 but all the same problems exist for the effected projects. Note, I haven't yet been able to run an analysis due to a NPE during maven execution. I suspect this is a result of the same problem with the clouds and hotspots.
Returning to the email thread[1], I upped the servers maxmemory to 1024, restarted, and tried calling some of the REST apis directly from FF. The first service call[2] for one of the effected projects results in a "resources.php" file containing only "callback5([]);" -- the sonar.log contains no errors for this request. Repeating the service call for an unaffected project returns callback5 with a whole bunch more JSON content.
Also, after the upgrade, one of the projects is displayed 3 times in the sonar project list where it used to only be displayed once. Each project has a different index, as shown in the url, and appear to be separated by time. The most recent of these projects contains all the events (versions) of the other 2 -- not sure if this is related at all.
The upgrade docs[3] mention a purge process that triggers after each analysis. Is there a way to trigger this manually (e.g, SQL)?
Other info that may be relavant:
* using postgres 8.3.8 * CentOS 5.3
Any help is appreciated.
TIA, Doug
|
|
Re: clouds, hotspot, violations not displaying/IndexOutOfBoundsException in GWT
Cool. Thanks for creating the ticket. Olivier
On Fri, Nov 6, 2009 at 4:52 PM, Doug Douglass <douglass.doug@...> wrote:
Thanks Olivier! Your diagnosis of both problems was spot on.
One of the effected projects was not a maven multi-project, so not effected by SONAR-1118. Running a new, trunk analysis fixed that project. For the other, multi-module project, running the analysis after a separate mvn clean package fixed that one.
Doug
On Thu, Nov 5, 2009 at 1:27 PM, Olivier Gaudin <gaudol@...> wrote:
Hello Doug,
Let's try the initial problem first. I don't think that you hit the problem described in [1] as this problem occurred after an upgrade in 1.11 and did not exist in 1.10. I think you have found a bug that occurs on Clouds and Hotspots after running a project with projectDate parameter. What I would recommend is that after the analysis with "projectDate", to run a "normal" analysis and make sure everything goes back to normal. If that is the case, can I then ask you to file an issue in Jira ?
On the second issue, the most important thing is to be able to run the first analysis as it will put many things squared. Could you have a look at
SONAR-1118, it looks similar to your issue... There is a work around in it. If that is not ok, can you give some more information (log file, special config) or ideally send a sample project to reproduce the issue ?
Olivier
On Thu, Nov 5, 2009 at 5:33 PM, Doug Douglass <douglass.doug@...> wrote:
Yesterday, after analyzing some older code snapshots (using -Dsonar.projectVersion=... -Dsonar.projectDate=...) with sonar 1.10.1, the clouds, hotspots and violations drilldown stopped displaying for the analyzed projects. These features continue to work correctly for other projects.
A quick check of the browser javascript console (Chrome and FF+Firebug) when forcing a refresh of the clouds shows:
" uncaught exception: java.lang.IndexOutOfBoundsException /sonar/deploy/gwt/org.sonar.plugins.core.clouds.GwtClouds/3117E30EE95648FD75D9A24B2E376C75.cache.html:599"
I searched around and found this thread[1] and decided to upgrade in hope this problem may have already been fixed.
The upgrade went smoothly and we're now running sonar 1.11.1 but all the same problems exist for the effected projects. Note, I haven't yet been able to run an analysis due to a NPE during maven execution. I suspect this is a result of the same problem with the clouds and hotspots.
Returning to the email thread[1], I upped the servers maxmemory to 1024, restarted, and tried calling some of the REST apis directly from FF. The first service call[2] for one of the effected projects results in a "resources.php" file containing only "callback5([]);" -- the sonar.log contains no errors for this request. Repeating the service call for an unaffected project returns callback5 with a whole bunch more JSON content.
Also, after the upgrade, one of the projects is displayed 3 times in the sonar project list where it used to only be displayed once. Each project has a different index, as shown in the url, and appear to be separated by time. The most recent of these projects contains all the events (versions) of the other 2 -- not sure if this is related at all.
The upgrade docs[3] mention a purge process that triggers after each analysis. Is there a way to trigger this manually (e.g, SQL)?
Other info that may be relavant:
* using postgres 8.3.8 * CentOS 5.3
Any help is appreciated.
TIA, Doug
|
