10 Replies Latest reply on Aug 11, 2004 9:26 AM by Nir Gertner

    Warning for session-webservice-invoker

    rtg Newbie

      Hello,
      I have the following Warning during the start of JBoss 4.0

      01:03:29,031 WARN [EjbModule] The Container Invoker session-webservice-invoker (in jboss.xml or standardjboss.xml) could not be created because of java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.net.ws4ee.server.EJBProxyFactoryImpl We will ignore this error, but you may miss a transport for this bean.


      After this the webservices are not working on my machine.
      Thanks for help,
      rtg

        • 1. Re: Warning for session-webservice-invoker
          bcmodi Newbie

          I am having the same problem with DR4 on XP as well as Linux.

          thanks,
          -Bijal

          "rtg" wrote:
          Hello,
          I have the following Warning during the start of JBoss 4.0

          01:03:29,031 WARN [EjbModule] The Container Invoker session-webservice-invoker (in jboss.xml or standardjboss.xml) could not be created because of java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.net.ws4ee.server.EJBProxyFactoryImpl We will ignore this error, but you may miss a transport for this bean.


          After this the webservices are not working on my machine.
          Thanks for help,
          rtg


          • 2. Re: Warning for session-webservice-invoker
            pepet Newbie

            Hello!
            I am using Win2000 Professional and have the same warning during the start of JBoss 4.0.

            thanks
            pepet

            • 3. Re: Warning for session-webservice-invoker
              Thomas Diesler Master

              We are currently into some changes with respect to webservices in jboss. This is mainly due to our effort to reach J2EE-1.4 certification, which cannot be done with JBoss.Net

              With the jboss-4.0DRs, you will find two conflicting ws implementations. This is jboss-net.sar and jboss-ws4ee.sar (i.e. you can only deploy one or the other)

              The JSR-109 (web services for J2EE) functionality has been removed from jboss-net and found a new home in jboss-ws4ee.

              If you can, I suggest you use JSR-109 style deployment and the new jboss-ws4ee.sar. The functionality of jboss-net that is not part of the j2ee spec will be migrated gradually to jboss-ws4ee.

              If you don't use JSR-109 ws you should remove jboss-ws4ee and deploy jboss.net

              xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
              Thomas Diesler
              Senior Developer & Consultant
              JBoss Group (Europe) SàRL
              xxxxxxxxxxxxxxxxxxxxxxxxxxxxx

              • 4. Re: Warning for session-webservice-invoker
                pepet Newbie

                One time I tried to deploy with jboss-net.sar and without jboss-ws4ee.sar other time with jboss-ws4ee.sar and without jboss-net.sar and the result was the same. Nothing has changed. I still get the warning:
                WARN [EjbModule] The Container Invoker session-webservice-invoker (in jboss.xml or standardjboss.xml) could not be created because of java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.net.ws4ee.server.EJBProxyFactoryImpl We will ignore this error, but you may miss a transport for this bean.

                thanks for help,
                pepet

                • 5. Re: Warning for session-webservice-invoker
                  Thomas Diesler Master

                  I'll repair it as soon as certification is done. Please bare with me.

                  • 6. Re: Warning for session-webservice-invoker
                    Merten Schumann Newbie

                    Just tried to deploy an .ear generated with Sun J2EE 1.4 RI in JBoss and was facing this problem with EJBProxyFactoryImpl too.

                    So I'm looking forward to try this in J2EE-1.4 certified JBoss! :-)

                    Another issue is: http://<host:port>/ws4ee/services (View list of deployed Web Services) is not working, exception

                    ERROR [Engine] StandardWrapperValve[JBossAxisServlet]:
                    Servlet.service() for servlet JBossAxisServlet threw exception
                    java.lang.IncompatibleClassChangeError at
                    org.jboss.webservice.server.JBossAxisServlet.reportAvailableServices(
                    JBossAxisServlet.java:218)

                    But I guess this problem is in he same area ...

                    Merten

                    • 7. Re: Warning for session-webservice-invoker
                      Merten Schumann Newbie

                      Tried my sample J2EE 1.4 .ear, which is working in Sun App Server 8 and IBM WebSphere 6, now in JBoss 4.0RC1.
                      There's still the same exception:

                      10:31:47,152 INFO [EARDeployer] Init J2EE application: file:/D:/work/soap/jboss-4.0.0RC1/server/default/deploy/RoSrapScriptExecService.ear
                      10:31:47,527 INFO [EjbModule] Deploying RoSrapScriptExecServiceImpl
                      10:31:47,542 WARN [EjbModule] The Container Invoker session-webservice-invoker
                      (in jboss.xml or standardjboss.xml) could not be created because of java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.net.ws4ee.server.EJBProxyFactoryImpl We will ignore this error, but you may miss a transport for this bean.


                      Tried to add an meta-inf/jboss.xml to my .jar in the .ear, but the problem is still there.

                      <?xml version="1.0" encoding="UTF-8"?>

                      <enterprise-beans>

                      <ejb-name>RoSrapScriptExecServiceImpl</ejb-name>
                      <jndi-name>/rochade/srap/scriptExec</jndi-name>


                      <ejb-name>RoSrapScriptExecServiceImplWSI</ejb-name>
                      <jndi-name>/rochade/srap/scriptExecWSI</jndi-name>

                      </enterprise-beans>


                      cu
                      Merten

                      • 8. Re: Warning for session-webservice-invoker
                        adrian-o-matic Newbie

                        Hi,

                        I have the same problem with jboss.net.ws4ee package.
                        When will it be fixed ?
                        How can I change the deployment method in the meantime ?

                        "tdiesler" wrote:
                        I'll repair it as soon as certification is done. Please bare with me.


                        • 9. Re: Warning for session-webservice-invoker
                          Thomas Diesler Master

                          The warning is irrelevant for j2ee deployments. It is correct that the classloader cannot see anything in jboss.net, because jboss.net should not be deployed when you experiment with j2ee web services.

                          If you want to get rid of the warning remove the jboss.net invoker proxy binding and all jboss.net invoker interceptors from standard-jboss.xml.

                          It will be ironed out when we release jboss-4.0, which is planed in Sep.

                          • 10. Re: Warning for session-webservice-invoker
                            Nir Gertner Newbie

                            The EJBProxyFactoryImpl related working is indeed insignificat. Webservices are well deployed even when this warning occurs.

                            As mentioned before, removing:

                            <invoker-proxy-binding>
                            session-webservice-invoker
                            ...
                            </invoker-proxy-binding>

                            and multiple instances of:

                            <invoker-proxy-binding-name>session-webservice-invoker</invoker-proxy-binding-name>

                            from standardjboss.xml removes the warning.

                            As for the IncompatibleClassChangeError that Merten (mesc) mentions. This is a result of incompatible axis.jar that is found in the jboss-net.sar deployment. It may also result an IllegalAccessException when trying to access a web service or its wsdl. Silmply remove jboss-net.sar from the "deploy" directory and restart jboss.

                            I hope this helps.

                            Cheers,
                            Nir.