Tomcat error deploying Sonar 1.11.1

[dhowe01]

I just downloaded Sonar to evaluate.  I built the war from the script and deployed on our Tomcat6 server. No additional configuration- so embedded derby.  The war deploys, but fails to start:
I get a series of these, with stacktraces.
---- Debugging information ----
message             : Cannot construct org.sonar.plugins.checkstyle.xml.Module as it does not have a no-args constructor
cause-exception     : com.thoughtworks.xstream.converters.reflection.ObjectAccessException
cause-message       : Cannot construct org.sonar.plugins.checkstyle.xml.Module as it does not have a no-args constructor
class               : org.sonar.plugins.checkstyle.xml.Module
required-type       : org.sonar.plugins.checkstyle.xml.Module
path                : /module
line number         : 5
-------------------------------

Attempting to hit the servlet with a browser just brings up the error 500 page with "We're sorry, but something went wrong."

any hints on what to check?  There is no sonar log file. These errors appear in my tomcat log.

[Olivier Gaudin-2]

Hello,

Can you provide a bit more information ?

Which version of Sonar ? OS ? DId you make any configuration before or after building the war, including adding extensions or plugin ?

Olivier

On Fri, Oct 23, 2009 at 8:14 PM, dhowe01 <dhowe01@...> wrote:

I just downloaded Sonar to evaluate.  I built the war from the script and
deployed on our Tomcat6 server. No additional configuration- so embedded
derby.  The war deploys, but fails to start:
I get a series of these, with stacktraces.
---- Debugging information ----
message             : Cannot construct
org.sonar.plugins.checkstyle.xml.Module as it does not have a no-args
constructor
cause-exception     :
com.thoughtworks.xstream.converters.reflection.ObjectAccessException
cause-message       : Cannot construct
org.sonar.plugins.checkstyle.xml.Module as it does not have a no-args
constructor
class               : org.sonar.plugins.checkstyle.xml.Module
required-type       : org.sonar.plugins.checkstyle.xml.Module
path                : /module
line number         : 5
-------------------------------

Attempting to hit the servlet with a browser just brings up the error 500
page with "We're sorry, but something went wrong."

any hints on what to check?  There is no sonar log file. These errors appear
in my tomcat log.


--
View this message in context: http://www.nabble.com/Tomcat-error-deploying-Sonar-1.11.1-tp26030975p26030975.html
Sent from the Sonar user mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

[dhowe01]

sure. The version of Sonar is 1.11.1
The war was built using the sh script; no modification to the config, and no additional extensions/plugins.
Its installed on Tomcat6, on a FreeBSD7.2 (64bit) machine.
Its the SunJDK1.6 Diablo build.

Olivier Gaudin-2 wrote:

Hello,

Can you provide a bit more information ?

Which version of Sonar ? OS ? DId you make any configuration before or after
building the war, including adding extensions or plugin ?

Olivier



On Fri, Oct 23, 2009 at 8:14 PM, dhowe01 <[e-mail]> wrote:

>
> I just downloaded Sonar to evaluate.  I built the war from the script and
> deployed on our Tomcat6 server. No additional configuration- so embedded
> derby.  The war deploys, but fails to start:
> I get a series of these, with stacktraces.
> ---- Debugging information ----
> message             : Cannot construct
> org.sonar.plugins.checkstyle.xml.Module as it does not have a no-args
> constructor
> cause-exception     :
> com.thoughtworks.xstream.converters.reflection.ObjectAccessException
> cause-message       : Cannot construct
> org.sonar.plugins.checkstyle.xml.Module as it does not have a no-args
> constructor
> class               : org.sonar.plugins.checkstyle.xml.Module
> required-type       : org.sonar.plugins.checkstyle.xml.Module
> path                : /module
> line number         : 5
> -------------------------------
>
> Attempting to hit the servlet with a browser just brings up the error 500
> page with "We're sorry, but something went wrong."
>
> any hints on what to check?  There is no sonar log file. These errors
> appear
> in my tomcat log.
>
>
> --
> View this message in context:
> http://www.nabble.com/Tomcat-error-deploying-Sonar-1.11.1-tp26030975p26030975.html
> Sent from the Sonar user mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

[Simon Brandhof-2]

Can you send the full stacktrace ? To check if the problems comes from Tomcat, could you also try to start the standalone app ?
Thank you

[dhowe01]

Simon Brandhof-2 wrote:

Can you send the full stacktrace ? To check if the problems comes from
Tomcat, could you also try to start the standalone app ?
Thank you

Sure. Sent to your email, to avoid thread spam.
I cant test the standalone, since there isn't a runner for Freebsd.

[Simon Brandhof-2]

Did you add some libraries to shared tomcat classpath ?

[dhowe01]

Simon Brandhof-2 wrote:

Did you add some libraries to shared tomcat classpath ?

Hi Simon.  The answer to your question is no.  The only value in the classpath is for the bootloader jar.

As I was poking around the system to get the answer for you, I wanted to look at the error, and recreate the log entry, so I hit the html page for sonar and guess what, it displays now.

The only thing that I can think of that changed since I initially attempted this and now is that I have configured our system to use Xvmb virtual frame buffer, while before it was purely headless.
If sonar requires X11 to startup, perhaps that's why I was receiving the errors.  The error message and stacktrace don't really give any hints in that direction though.

[dhowe01]

Simon Brandhof-2 wrote:

Did you add some libraries to shared tomcat classpath ?

Simon: I have some more information for you.

During my testing The database hung up and I was unable to recover. My projects are large and I was using the derby database and there was also viewing going on in the browser, so I guess that can be expected? The error occured when my maven plugin was doing a database purge. The log ended up showing various errors about not being able to establish a lock.  anways, the end result is I did a reinstall of the war.

Doing this brought my original problem back. Same symtoms. starting stopping the servlet didn't fix it.  I had to stop and restart Tomcat itself.  After I did this, I still received the stack trace but it recovered and the startup page is now up.

[Simon Brandhof-2]

Indeed the standalone application starts with the headless mode (see conf/wrapper.conf).
All I remember is that it's needed for generate JFreeChart images.

If sonar requires X11 to startup, perhaps that's why I was receiving the
errors.  The error message and stacktrace don't really give any hints in
that direction though.

I think that the best way is to update the installation guide. I'm not sure of how to improve stacktrace logs.

[Simon Brandhof-2]

During my testing The database hung up and I was unable to recover. My
projects are large and I was using the derby database and there was also
viewing going on in the browser, so I guess that can be expected? The error
occured when my maven plugin was doing a database purge. The log ended up
showing various errors about not being able to establish a lock.  anways,
the end result is I did a reinstall of the war.

The embedded database is not really stable. That's why we recommend to use it only for demo and tests. You should upgrade to an enterprise database if you have large projects and more than one user.

[dhowe01]

Update:
 I have installed mySql. so far no deadlocks.

My original errors though remained.
ie:
---- Debugging information ----
message             : Cannot construct org.sonar.plugins.checkstyle.xml.Module as it does not have a no-args constructor
cause-exception     : com.thoughtworks.xstream.converters.reflection.ObjectAccessException
cause-message       : Cannot construct org.sonar.plugins.checkstyle.xml.Module as it does not have a no-args constructor
class               : org.sonar.plugins.checkstyle.xml.Module
required-type       : org.sonar.plugins.checkstyle.xml.Module
path                : /module
line number         : 5
-------------------------------
and the stack trace that I sent you.

After some debugging, I tracked to problem down to xstream.  I went to the xstream site, and discovered that the already fixed their problem.
ie:  "Support for Diablo JDK on FreeBSD (by Reto Bachmann-Gmür)."

This fix appears in xstream 1.3.1.
I replaced the jar on my system, and the error went away. With the new jar the system is working flawlessly on freebsd.

Can a developer update the build so that xstream1.3.1 is a dependency rather than just 1.3?

thanks!

Simon Brandhof-2 wrote:

> During my testing The database hung up and I was unable to recover. My
> projects are large and I was using the derby database and there was also
> viewing going on in the browser, so I guess that can be expected? The error
> occured when my maven plugin was doing a database purge. The log ended up
> showing various errors about not being able to establish a lock.  anways,
> the end result is I did a reinstall of the war.
>

The embedded database is not really stable. That's why we recommend to use
it only for demo and tests. You should upgrade to an enterprise database if
you have large projects and more than one user.

[Simon Brandhof-2]

I'm afraid it's not so simple to change the version of xstream directly from the distribution. You'll have to wait SONAR-1258 [1] to be resolved. It's planned for release 1.12.

Regards
Simon
[1] http://jira.codehaus.org/browse/SONAR-1258