11 Replies Latest reply on Aug 1, 2005 2:33 PM by aberezin

    Proxy error

      When I use the JNDI context to look up a bean thir error occurs:

      Ex:
      InitialContext ctx = new InitialContext();
      container = (TeamContainer) ctx.lookup(TeamContainer.class.getName());

      Error:
      $Proxy136 (org.apache.jsp.team_jsp)
      in org.apache.jsp.team_jsp.jspInit, line 28
      in org.apache.jasper.runtime.HttpJspBase.init, line 78
      in org.apache.jasper.servlet.JspServletWrapper.getServlet, line 145
      in org.apache.jasper.servlet.JspServletWrapper.service, line 305
      ...

      Any ideas? I use jboss-4.0.3RC1...

      Regards!

        • 1. Re: Proxy error
          jaikiran

          Please post the detailed log

          • 2. Re: Proxy error

            $Proxy131 (org.apache.jsp.team_jsp)
            in org.apache.jsp.team_jsp.jspInit, line 28
            in org.apache.jasper.runtime.HttpJspBase.init, line 78
            in org.apache.jasper.servlet.JspServletWrapper.getServlet, line 145
            in org.apache.jasper.servlet.JspServletWrapper.getDependants, line 246
            in org.apache.jasper.compiler.Compiler.isOutDated, line 389
            in org.apache.jasper.compiler.Compiler.isOutDated, line 315
            in org.apache.jasper.JspCompilationContext.compile, line 553
            in org.apache.jasper.servlet.JspServletWrapper.service, line 293
            in org.apache.jasper.servlet.JspServlet.serviceJspFile, line 314
            in org.apache.jasper.servlet.JspServlet.service, line 264
            in javax.servlet.http.HttpServlet.service, line 810
            in org.apache.catalina.core.ApplicationFilterChain.internalDoFilter, line 252
            in org.apache.catalina.core.ApplicationFilterChain.doFilter, line 173
            in org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter, line 81
            in org.apache.catalina.core.ApplicationFilterChain.internalDoFilter, line 202
            in org.apache.catalina.core.ApplicationFilterChain.doFilter, line 173
            in org.apache.catalina.core.StandardWrapperValve.invoke, line 213
            in org.apache.catalina.core.StandardContextValve.invoke, line 178
            in org.jboss.web.tomcat.security.CustomPrincipalValve.invoke, line 39
            in org.jboss.web.tomcat.security.SecurityAssociationValve.invoke, line 153
            in org.apache.catalina.authenticator.AuthenticatorBase.invoke, line 407
            in org.jboss.web.tomcat.security.JaccContextValve.invoke, line 59
            in org.apache.catalina.core.StandardHostValve.invoke, line 126
            in org.apache.catalina.valves.ErrorReportValve.invoke, line 105
            in org.apache.catalina.core.StandardEngineValve.invoke, line 107
            in org.apache.catalina.connector.CoyoteAdapter.service, line 148
            in org.apache.coyote.http11.Http11Processor.process, line 856
            in org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection, line 744
            in org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket, line 527
            in org.apache.tomcat.util.net.MasterSlaveWorkerThread.run, line 112
            in java.lang.Thread.run, line 595

            • 3. Re: Proxy error
              darranl

              Are you sure that is all of the error? doesn't the error start higher?

              Have you packaged the beans interface in the web app as well as in the war file?

              Are you sure you the error is a proxy error? Are you sure that it is not a ClassCastException?

              If it is a class cast exception and you have packaged the interfaces in the war, remove the interfaces from the war.

              • 4. Re: Proxy error

                Yes, I am sure this is the error...

                The only thing that is changing is the proxy number (look at the errormessages I pasted earlier).

                I get the same error if I have the interfaces in the war file and vice versa. Should I have the interfaces in the war?

                • 5. Re: Proxy error

                  ...and you are right...

                  ...it is a ClassCastException whith the errormessage given...

                  When I debugged the exceptiontype this class was what has been thrown...

                  • 6. Re: Proxy error

                    Anyone who got an idea about what is causing this ClassCastException/proxy failure?

                    This is an annoying show-stopper, and I don't have a clue abaout what could be wrong. I thought I followed the EJBTrail examples thorough and I can't backtrace the failure... I can't see that what I have done is different from that... The only thing that I have done different from the example is using entity beans in generic collections. But if this is the problem, I thought it would bring me some different errormessage than a class cast exception with a proxy error...

                    Please... Anybody: help!

                    • 7. Re: Proxy error
                      jaikiran

                      As darranl has already mentioned:

                      Remove the bean classes and their interfaces from the war file

                      • 8. Re: Proxy error

                        ... as I already said: I get the same error anyway.

                        At least now I know that they should not be there...

                        Any others idea?

                        • 9. Re: Proxy error

                          I am working on several things on my server and things suddenly start woking, so I must have done something that has the right sideeffect.

                          Thanx for the tips anyway!

                          • 10. Re: Proxy error
                            aberezin

                            I am seeing a similar problem. If you get an answer, please let me know at aberezin@drillinginfo.com. If I find out, Ill post the answer here.

                            • 11. Re: Proxy error
                              aberezin

                              See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=67287 for my solution. Instead of packaging an EAR, I got it all running out of eclipse using 2 source (and build) paths. This keeps the interfaces out of the web-inf/classes path.