5 Replies Latest reply on Oct 26, 2007 10:26 AM by Vinicius Carvalho

    Problems with quickstart webservice_consumer1

    fabianw Newbie

      I try to run the webservice_consumer1 quickstart.

      What I've done so far:
      1) installed JBoss AS 4.2.1
      2) deployed JBoss ESB 4.2
      3) deployed JBoss WS native 2.0.1

      So far everything works fine, but the quickstart needs some additional stuff, so it won't work:
      BUILD FAILED
      C:\jbossesb-4.2GA\samples\quickstarts\conf\base-build.xml:435: ****DEPLOYMENT FAILED... Sorry, this Quickstart requires a modified JBoss Webservice container, please refer to the 'Configuring Webservice Integration' section of the Administration Guide.

      As soon as I do what is told me and patch JBossWS ('ant patch-jbossws') I get some serious errors at the startup of the AS and the quickstart still won't work.


      15:44:57,421 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

      --- MBeans waiting for other MBeans ---
      ObjectName: jboss.beans:service=JBossBeanDeployment,name='jbossws.sar#jbossws.beans'
      State: FAILED
      Reason: org.jboss.deployment.DeploymentException: Cannot start AbstractKernelDeployment@87cd5c{name=file:/C:/JBoss_AS_4.2.1/server/default/deploy/jbossws.sar/jbossws.beans/META-INF/jboss-beans.xml
      [......]

      *** DEPLOYMENTS IN ERROR:
      WSWebMetaDataAdapter -> java.lang.NoClassDefFoundError: org/jboss/wsf/container/jboss42/WebMetaDataAdapter
      WSEndpointJAXBIntrosCustomizationsDeployer -> java.lang.NoClassDefFoundError: org/jboss/wsf/spi/deployment/AbstractDeployer

      *** DEPLOYMENTS MISSING DEPENDENCIES:
      WSNativeDeploymentAspectInstallerPostJSE -> WSNativeEndpointHandlerDeploymentAspect{Configured:Installed}
      [.......]


      I shortened the errors drastically. You can see the whole error message here: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098331

      By the way: I can deploy the example successfully but http://localhost:8080/jbossws/ shows no deployed service.

      I have to get this working. Every help is appreciated!

        • 1. Re: Problems with quickstart webservice_consumer1
          Kevin Conner Master

          Please use jbossws 2.0.0 and not 2.0.1 :)

          • 2. Re: Problems with quickstart webservice_consumer1
            fabianw Newbie

            OK, this was my ignorance.... I still have this feeling that newer is better :)

            But I'm still not really happy!
            The errors at startup are gone - that's good. Now I did the steps to run the quickstart:
            1) 'ant undeploy-jms-dests' (btw, what is this for?)
            2) 'ant deploy' (http://localhost:8080/jbossws/services still shows no endpoints... why?)
            3) 'ant runtest'
            =>

            runtest:
             [echo] Send ESB message that triggers webservice call
             [java] Exception in thread "main" org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message to Service [MyServiceCategory:WebserviceConsumer1]. Check for errors.
             [java] at org.jboss.soa.esb.client.ServiceInvoker.post(ServiceInvoker.java:262)
             [java] at org.jboss.soa.esb.client.ServiceInvoker.deliverSync(ServiceInvoker.java:159)
             [java] at org.jboss.soa.esb.samples.quickstart.webservice_consumer1.test.SendEsbMessage.sendMessage(SendEsbMessage.java:54)
             [java] at org.jboss.soa.esb.samples.quickstart.webservice_consumer1.test.SendEsbMessage.main(SendEsbMessage.java:61)
            
            BUILD FAILED
            


            Now I get the following errors when I start the AS:
            12:52:24,906 ERROR [MainDeployer] Could not create deployment: file:/C:/JBoss_AS_4.2.1/server/default/tmp/deploy/tmp54562Quickstart_webservice_consumer1.esb-contents/Quickstart_webservice_consumer1.war
            java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/C:/JBoss_AS_4.2.1/server/default/tmp/deploy/tmp54416jaxb-impl.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
             at com.sun.xml.bind.v2.model.impl.ModelBuilder.<clinit>(ModelBuilder.java:136)
             at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:406)
             at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:270)
             at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:103)
             at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:89)
             at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:100)
             at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.createJAXBContext(JAXWSMetaDataBuilder.java:917)
             at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:142)
             at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:50)
             at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderJSE.buildMetaData(JAXWSMetaDataBuilderJSE.java:69)
             at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeployer.create(UnifiedMetaDataDeployer.java:67)
             at org.jboss.wsf.spi.deployment.BasicDeployerManager.deploy(BasicDeployerManager.java:69)
             at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97)
             at org.jboss.wsf.container.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:79)
             at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
             at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
             at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
             at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
             at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
             at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
             at $Proxy46.create(Unknown Source)
             at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
             at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
             at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
             at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
             at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source)
             at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
             at java.lang.reflect.Method.invoke(Unknown Source)
             at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
             at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
             at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
             at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
             at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
             at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
             at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
             at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
             at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
             at $Proxy9.deploy(Unknown Source)
             at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
             at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
             at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
             at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
             at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
            

            13:00:59,500 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
            
            --- Incompletely deployed packages ---
            org.jboss.deployment.DeploymentInfo@842807ca { url=file:/C:/JBoss_AS_4.2.1/server/default/deploy/Quickstart_webservice_consumer1.esb }
             deployer: org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer@e038c4
             status: Deployment FAILED reason: Could not create deployment: file:/C:/JBoss_AS_4.2.1/server/default/tmp/deploy/tmp24635Quickstart_webservice_consumer1.esb-contents/Quickstart_webservice_consumer1.war; - nested throwable: (java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/C:/JBoss_AS_4.2.1/server/default/tmp/deploy/tmp24551jaxb-impl.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/))
             state: FAILED
             watch: file:/C:/JBoss_AS_4.2.1/server/default/deploy/Quickstart_webservice_consumer1.esb
             altDD: null
             lastDeployed: 1193310051109
             lastModified: 1193310051078
             mbeans:


            What's up, now??

            • 3. Re: Problems with quickstart webservice_consumer1
              Burr Sutter Master

              If your goal is to simply get started, you might try download the ESB Server, it has everything preconfigured for the SOA/ESB-related use cases.

              http://labs.jboss.org/jbossesb/downloads/
              jbossesb-server-4.2GA.zip

              It would allow you to avoid the issues of which version of AS, Messaging, WS, JAXB, etc, etc.

              Burr

              • 4. Re: Problems with quickstart webservice_consumer1
                fabianw Newbie

                Well, I'm writing my master thesis about SOA and I chose JBoss to implement one. I have a business-process which I want to implement using Web Services and jBPM. Is this possible with the standalone ESB-Server?
                I expected that my way of installing everything would be the 'normal' one, so I chose this way to keep close to practice.

                • 5. Re: Problems with quickstart webservice_consumer1
                  Vinicius Carvalho Apprentice

                  I've downloaded the GA version, and when I run the example, and try to access the contract of the webservice (clicking at the contract on the screen) an exception is thrown:

                  org.apache.jasper.JasperException: An exception occurred processing JSP page /contract.jsp at line 50
                  
                  47: ContractPublisher contractPublisher = publisher.getContractPublisher();
                  48:
                  49: if(contractPublisher instanceof WebserviceContractPublisher) {
                  50: contractInfo = ((WebserviceContractPublisher)contractPublisher).getContractInfo(epr, request);
                  51: } else {
                  52: contractInfo = contractPublisher.getContractInfo(epr);
                  53: }
                  
                  
                  Stacktrace:
                   org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:518)
                   org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:429)
                   org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
                   org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
                   javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
                   org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
                  
                  root cause
                  
                  java.lang.NullPointerException
                   org.jboss.soa.esb.actions.soap.WebserviceContractPublisher.getContractInfo(WebserviceContractPublisher.java:104)
                   org.apache.jsp.contract_jsp._jspService(contract_jsp.java:113)
                   org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
                   javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
                   org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:387)
                   org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
                   org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
                   javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
                   org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
                  
                  


                  Is it possible to fix this?