continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Guther (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-1054) IllegalStateException stack adding pom
Date Wed, 29 Oct 2008 23:35:51 GMT


Andreas Guther commented on CONTINUUM-1054:


from reading all the other comments I do not think this is a simple and minor issue with nothing
more than a strack trace in the logs that is irritating but harmless.  If you read other comments
here an in the mailing archives you might agree with me that there a plenty of users complaining
that they are not able to use Continuum because they cannot add pom URLS as project definitions.
 For now i could get Continuum 1.2 running on Suse Linux to run using the workaround describe
in this issue as well.  But this is very, very impractical and makes 1.2 for us basically
useless.  We discuss right now going back to 1.1.  One of the main reasons for us to use Continuum
is the ease of setting up new projects based on just pointing to a pom file in our VCS.

I just noticed that you are talking about a 1.2.2 release candidate and maybe I should try
that one first.

> IllegalStateException stack adding pom
> --------------------------------------
>                 Key: CONTINUUM-1054
>                 URL:
>             Project: Continuum
>          Issue Type: Bug
>          Components: Web interface
>    Affects Versions: 1.1-alpha-1
>            Reporter: Carlos Sanchez
>            Assignee: Brett Porter
>            Priority: Minor
>             Fix For: 1.2
> Adding a m2 pom from a web location causes this stack trace, although seems to work fine
> 2006-12-13 10:46:07,109 [SocketListener0-1] INFO  DispatcherUtils                - Unable
to find 'webwork.multipart.saveDir' property setting. Defaulting to javax.servlet.context.tempdir
> 2006-12-13 10:46:07,156 [SocketListener0-1] WARN  MultiPartRequest               - Item
is a file upload of 0 size, ignoring
> 2006-12-13 10:46:07,156 [SocketListener0-1] ERROR DispatcherUtils                - Error
setting character encoding to 'UTF-8' - ignoring.
> java.lang.IllegalStateException: getReader() or getInputStream() called
>         at org.mortbay.jetty.servlet.ServletHttpRequest.setCharacterEncoding(
>         at javax.servlet.ServletRequestWrapper.setCharacterEncoding(
>         at com.opensymphony.webwork.dispatcher.DispatcherUtils.prepare(
>         at com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(
>         at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(
>         at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(
>         at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(
>         at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(
>         at com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(
>         at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(
>         at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(
>         at org.mortbay.jetty.servlet.ServletHandler.handle(
>         at org.mortbay.http.HttpContext.handle(
>         at org.mortbay.jetty.servlet.WebApplicationContext.handle(
>         at org.mortbay.http.HttpContext.handle(
>         at org.mortbay.http.HttpServer.service(
>         at org.mortbay.http.HttpConnection.service(
>         at org.mortbay.http.HttpConnection.handleNext(
>         at org.mortbay.http.HttpConnection.handle(
>         at org.mortbay.http.SocketListener.handleConnection(
>         at org.mortbay.util.ThreadedServer.handle(
>         at org.mortbay.util.ThreadPool$

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message