5 Replies Latest reply on Jul 15, 2009 10:28 AM by peterj

    invoking WS

    jpredpos

      hi,

      I migrated an app from JBoss 4.0.5 GA to 5.1.0 GA.
      My app invoke some external web services.

      In 4.0.5 works fine, but in the 5.1.0 doesn't.

      Someone known how is the configuration to works ?

      thanks

        • 1. Re: invoking WS
          peterj

          Details please!!!

          Have you scanned the JBossAS5 forum? That's where most people place such migration issues.

          • 2. Re: invoking WS
            jpredpos

            yes, I scann the forum, looks like nobody invoke ws from JBoss 5

            here is details, my log

            11:02:22,389 ERROR [[ServletAdaptor]] Servlet.service() para servlet
            ServletAdaptor lanzó excepción
            javax.servlet.ServletException: non-HTTP request or response
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:829)
            at
            org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)

            at
            org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

            at
            org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

            at
            org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

            at
            org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

            at
            org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)

            at
            org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)

            at
            org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)

            at
            org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)

            at
            org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)

            at
            org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)

            at
            org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)

            at
            org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

            at
            org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)

            at
            org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

            at
            org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
            at
            org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
            at
            org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)

            at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
            at java.lang.Thread.run(Thread.java:619)

            • 3. Re: invoking WS
              peterj

              Do you have the servlet jar file embedded within your app? The line number for the exception you posted (829) does not match the line where that exception is thrown in 5.1.0 (715).

              Also, the details you provide still are not sufficient. You stated you are calling external web services, but this appears to be a stack trace servicing a request coming into the server. What is being done at the time that this error happens?

              • 4. Re: invoking WS
                jpredpos

                I 'm not using servlet jar.
                But my app. contains:

                Jersey 1.0 and Metro 1.4.

                It's strange that the same .war works fine at jboss 4.0.5 ...

                thanks

                • 5. Re: invoking WS
                  peterj

                  It is probably working in 4.0.5 because whatever older version of the servlet classes you are picking up probably matched what is in 4.0.5. You have to find where the old servlet classes are coming from. Try this. Add '-verbose:class' to the JAVA_OPTS in the run script and run the app server again. This option causes the JVM to print out each class loaded and the JAR file it came from. You will have to redirect stdout (or is it stderr?) because this option produces a lot of output. Look for where javax.servlet.http.HttpServlet comes from.