Continuum
  1. Continuum
  2. CONTINUUM-1054

IllegalStateException stack adding pom

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Minor Minor
    • Resolution: Won't Fix
    • Affects Version/s: 1.1-alpha-1
    • Fix Version/s: 1.2
    • Component/s: Web interface
    • Labels:
      None
    • Complexity:
      Intermediate
    • Number of attachments :
      0

      Description

      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(ServletHttpRequest.java:602)
      at javax.servlet.ServletRequestWrapper.setCharacterEncoding(ServletRequestWrapper.java:112)
      at com.opensymphony.webwork.dispatcher.DispatcherUtils.prepare(DispatcherUtils.java:392)
      at com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:160)
      at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
      at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118)
      at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)
      at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
      at com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88)
      at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
      at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471)
      at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
      at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
      at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633)
      at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
      at org.mortbay.http.HttpServer.service(HttpServer.java:909)
      at org.mortbay.http.HttpConnection.service(HttpConnection.java:816)
      at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982)
      at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)
      at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
      at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
      at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)

        Activity

        Hide
        Andreas Guther added a comment -

        I am using Version: 1.2 Build Number: 697023 and I still see the described behavior. We are unable to use continuum because of this issue.

        Show
        Andreas Guther added a comment - I am using Version: 1.2 Build Number: 697023 and I still see the described behavior. We are unable to use continuum because of this issue.
        Hide
        Wendy Smoak added a comment -

        This issue was for a minor problem with a stack trace showing up in the logs-- not the inability to add projects. As such it's marked as Won't Fix.

        (I tested adding the url that Carlos provided with the Continuum 1.2.2 release candidate and do not see the stack trace, so as Brett and Emmanuel mentioned, it was probably resolved as a side effect of upgrading some underlying components.)

        If you are having other problems such as the inability to add projects to Continuum, please ask on the user list or open a new issue with the details.

        Show
        Wendy Smoak added a comment - This issue was for a minor problem with a stack trace showing up in the logs-- not the inability to add projects. As such it's marked as Won't Fix. (I tested adding the url that Carlos provided with the Continuum 1.2.2 release candidate and do not see the stack trace, so as Brett and Emmanuel mentioned, it was probably resolved as a side effect of upgrading some underlying components.) If you are having other problems such as the inability to add projects to Continuum, please ask on the user list or open a new issue with the details.
        Hide
        Andreas Guther added a comment -

        Wendy,

        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.

        Show
        Andreas Guther added a comment - Wendy, 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.
        Hide
        Andreas Guther added a comment -

        We did some more experimenting and it appears that Continuum is able to retrieve the pom file via HTTP.

        What we believe now is that we had an issue with the used password for our SVN server that ended with an exclamation point "!". I tried to checkout the project on command line with the --password argument to SVN and got some errors. I omitted then passing the password as argument and had to enter the password after SVN asked me for it. That finally triggered the checkout.

        I think this is rather a shell problem. However, the error message provided by Continuum is very misleading and since I found the same error messages described in this issue in our log file I was wrongly concluding that I am facing the same problem.

        I guess I will open a new issue describing the actual problem and the possible cause.

        Show
        Andreas Guther added a comment - We did some more experimenting and it appears that Continuum is able to retrieve the pom file via HTTP. What we believe now is that we had an issue with the used password for our SVN server that ended with an exclamation point "!". I tried to checkout the project on command line with the --password argument to SVN and got some errors. I omitted then passing the password as argument and had to enter the password after SVN asked me for it. That finally triggered the checkout. I think this is rather a shell problem. However, the error message provided by Continuum is very misleading and since I found the same error messages described in this issue in our log file I was wrongly concluding that I am facing the same problem. I guess I will open a new issue describing the actual problem and the possible cause.
        Hide
        Wendy Smoak added a comment -

        This would be much easier to discuss on the user list. CONTINUUM-1199 is already open for the inability to use special characters in passwords.

        Show
        Wendy Smoak added a comment - This would be much easier to discuss on the user list. CONTINUUM-1199 is already open for the inability to use special characters in passwords.

          People

          • Assignee:
            Brett Porter
            Reporter:
            Carlos Sanchez
          • Votes:
            7 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: