5 Replies Latest reply on Feb 12, 2009 12:50 PM by Tom Fennelly

    Problem with WS invocation

    Vishal Novice

      I have configured the Hello world tutorial to pass the message to the webservice and get a response to another action , but i am getting following error

      properties: [ {org.jboss.soa.esb.message.time.dod=Sat Feb 07 01:08:09 IST 2009, org.jboss.soa.esb.message.time.dob=Deferred serialized value: 1d9c4c4, org.jboss.soa.esb.message.source=Deferred serialized value: 53345, org.jboss.soa.esb.message.transport.type=Deferred serialized value: 169369f, javax.jms.message.redelivered=false, org.jboss.soa.esb.gateway.original.queue.name=Deferred serialized value: 811e2b} ] ]
      01:08:09,765 INFO [STDOUT] Progress: 1 - Caching definition from url [http://localhost:8084//CalculatorWSApplication//NewWebService?wsdl]
      01:08:09,796 ERROR [WsdlContext] Loading of definition failed for [http://localhost:8084//CalculatorWSApplication//NewWebService?wsdl]; org.apache.commons.httpclient.HttpException: Received status code '404' on WSDL HTTP (GET) request: 'http://localhost:8084//CalculatorWSApplication//NewWebService?wsdl'.
      01:08:09,796 ERROR [STDERR] org.apache.commons.httpclient.HttpException: Received status code '404' on WSDL HTTP (GET) request: 'http://localhost:8084//CalculatorWSApplication//NewWebService?wsdl'.
      01:08:09,796 ERROR [STDERR] at org.jboss.soa.esb.services.soapui.EsbWsdlLoader.load(EsbWsdlLoader.java:69)
      01:08:09,796 ERROR [STDERR] at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlLoader.loadXmlObject(WsdlLoader.java:62)
      01:08:09,796 ERROR [STDERR] at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:412)
      01:08:09,796 ERROR [STDERR] at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:403)
      01:08:09,796 ERROR [STDERR] at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlLoader.cacheWsdl(WsdlLoader.java:116)
      01:08:09,796 ERROR [STDERR] at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlContext$Loader.construct(WsdlContext.java:200)
      01:08:09,796 ERROR [STDERR] at com.eviware.soapui.support.swing.SwingWorkerDelegator.construct(SwingWorkerDelegator.java:45)
      01:08:09,796 ERROR [STDERR] at com.eviware.soapui.support.swing.SwingWorker$2.run(SwingWorker.java:111)


      My web service is JAX-WS service on tomcat running on port 8084

      the jbossesb.xml contains following code
      <?xml version = "1.0" encoding = "UTF-8"?>
      <jbossesb xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.0.1.xsd" parameterReloadSecs="5">
      
       <providers>
       <jms-provider name="JBossMQ" connection-factory="ConnectionFactory">
       <jms-bus busid="quickstartGwChannel">
       <jms-message-filter
       dest-type="QUEUE"
       dest-name="queue/quickstart_helloworld_Request_gw"
       />
       </jms-bus>
       <jms-bus busid="quickstartEsbChannel">
       <jms-message-filter
       dest-type="QUEUE"
       dest-name="queue/quickstart_helloworld_Request_esb"
       />
       </jms-bus>
      
       </jms-provider>
       </providers>
      
       <services>
       <service
       category="FirstServiceESB"
       name="SimpleListener"
       description="Hello World">
       <listeners>
       <jms-listener name="JMS-Gateway"
       busidref="quickstartGwChannel"
       maxThreads="1"
       is-gateway="true"
       />
       <jms-listener name="helloWorld"
       busidref="quickstartEsbChannel"
       maxThreads="1"
       />
       </listeners>
       <actions mep="OneWay">
       <action name="action1"
       class="org.jboss.soa.esb.samples.quickstart.helloworld.MyJMSListenerAction"
       process="displayMessage"
       />
       <action name="action2" class="org.jboss.soa.esb.actions.SystemPrintln">
       <property name="printfull" value="true"/>
       </action>
       <!-- The next action is for Continuous Integration testing -->
       <action name="testStore" class="org.jboss.soa.esb.actions.TestMessageStore"/>
       <action name="soapui-client-action"
       class="org.jboss.soa.esb.actions.soap.SOAPClient">
       <property name="wsdl"
       value="http://localhost:8084//CalculatorWSApplication//NewWebService?wsdl" />
       <property name="responseAsOgnlMap" value="true" />
       <property name="SOAPAction" value="sayHello"/>
       </action>
       <action name="response-mapper"
       class="org.jboss.soa.esb.samples.quickstart.helloworld.ResponseAction">
       </action>
       </actions>
      
       </service>
       </services>
      
      </jbossesb>
      


        • 1. Re: Problem with WS invocation
          Daniel Bevenius Master

          Hi,

          can you connect to http://localhost:8084//CalculatorWSApplication//NewWebService?w
          sdl using a web browser or with a tool like soapui? Is the extra slash intentional?

          regards,

          /Daniel

          • 2. Re: Problem with WS invocation
            Vishal Novice

            yes i can connect to it from webbrowser, thats why i wonder

            • 3. Re: Problem with WS invocation
              Daniel Bevenius Master

              Have you looked at the webservice_consumer quickstart. It sounds like you are trying to do something similar if I'm not mistaken.
              Can you try reproducing this issue with that quickstart and send it to me and I'll take a look.

              Thanks,

              /Daniel

              • 4. Re: Problem with WS invocation
                Vishal Novice

                 

                18:45:43,156 INFO [QueueService] Queue[/queue/quickstart_webservice_consumer1_esb] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                18:45:43,156 INFO [QueueService] Queue[/queue/quickstart_webservice_consumer1_esb_reply] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                18:45:43,156 INFO [QueueService] Queue[/queue/quickstart_webservice_consumer1_Request_gw] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                18:45:43,171 WARN [ServiceController] Problem starting service jboss.esb:deployment=Quickstart_webservice_consumer1.esb
                java.lang.NoClassDefFoundError: AbstractActionLifecycle
                 at java.lang.ClassLoader.defineClass1(Native Method)
                 at java.lang.ClassLoader.defineClass(Unknown Source)
                 at java.security.SecureClassLoader.defineClass(Unknown Source)
                 at java.net.URLClassLoader.defineClass(Unknown Source)
                 at java.net.URLClassLoader.access$000(Unknown Source)
                 at java.net.URLClassLoader$1.run(Unknown Source)
                 at java.security.AccessController.doPrivileged(Native Method)
                 at java.net.URLClassLoader.findClass(Unknown Source)
                 at org.jboss.mx.loading.RepositoryClassLoader.findClassLocally(RepositoryClassLoader.java:682)
                 at org.jboss.mx.loading.RepositoryClassLoader.findClass(RepositoryClassLoader.java:662)
                 at java.lang.ClassLoader.loadClass(Unknown Source)
                 at org.jboss.mx.loading.RepositoryClassLoader.loadClassLocally(RepositoryClassLoader.java:200)
                 at org.jboss.mx.loading.ClassLoadingTask$ThreadTask.run(ClassLoadingTask.java:131)
                 at org.jboss.mx.loading.LoadMgr3.nextTask(LoadMgr3.java:399)
                 at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:527)
                 at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:415)
                 at java.lang.ClassLoader.loadClass(Unknown Source)
                 at java.lang.ClassLoader.loadClassInternal(Unknown Source)
                 at java.lang.Class.forName0(Native Method)
                 at java.lang.Class.forName(Unknown Source)
                 at org.jboss.soa.esb.util.ClassUtil.forName(ClassUtil.java:65)
                 at org.jboss.soa.esb.listeners.config.ServicePublisher.getConractPublisher(ServicePublisher.java:151)
                 at org.jboss.soa.esb.listeners.config.ServicePublisher.addServicePublishers(ServicePublisher.java:107)
                 at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration.java:120)
                 at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment.startServ
                
                


                This is the response i got ,there is an exception


                • 5. Re: Problem with WS invocation
                  Tom Fennelly Master

                  Oh dear... that looks completely fubar!!!

                  Are you trying to run this on the App Server and if so, are you sure you even have the ESB deployed there? This is one of the core ESB classes. If you're getting a NCDFE on that, something very fundamental is wrong!!