1 Reply Latest reply on May 15, 2006 6:19 PM by Alejandro Guizar

    SOAP-Request to Hello-service cause Exception: callerServlet

    njipwo Bertrand Newbie

      Hello community,

      i don't know if this is the right forum to pose my problem. I'm triying to run the hello example in the jbpm extension. Till now i have successfull install and deploy my application.

      My configuration is:

      MySQL server-4.1.
      JBoss AS 4.0.3SP1
      JBPM 3.0.2
      Java(jdk + jre) 1.5.06
      Ant 1.6.5
      JWSDP 1.6 (have first tried 2.0) There is no difference.

      Running "run-test" script with ant cause the same problem that why i first test my web service to be sure that there is no issues using ant.

      I send a SOAP-Request to the hello-service using the XML-Spy-tool. JBoss server answer with following error:

      20:10:03,428 ERROR [[callerServlet]] Servlet.service() for servlet callerServlet
       threw exception java.lang.NoSuchMethodError: org.apache.commons.lang.StringUtils.isWhitespace(Ljava/lang/String;)Z
       at org.jbpm.bpel.xml.util.XmlUtil.copyChildNodes(XmlUtil.java:700)
       at org.jbpm.bpel.xml.util.XmlUtil.copy(XmlUtil.java:623)
       at org.jbpm.bpel.service.messager.PortHandler.processResponse(PortHandle
      r.java:495)
       at org.jbpm.bpel.service.messager.PortHandler.handleResponse(PortHandler
      .java:248)
       at org.jboss.webservice.handler.HandlerWrapper.handleResponse(HandlerWra
      pper.java:127)
       at org.jboss.webservice.handler.HandlerChainBaseImpl.handleResponse(Hand
      lerChainBaseImpl.java:279)
       at org.jboss.webservice.handler.ServerHandlerChain.handleResponse(Server
      HandlerChain.java:83)
       at org.jboss.webservice.server.InvokerProviderJSE.invokeTarget(InvokerPr
      oviderJSE.java:117)
       at org.jboss.axis.providers.java.RPCProvider.processMessage(RPCProvider.
      java:121)
       at org.jboss.axis.providers.java.JavaProvider.invoke(JavaProvider.java:3
      58)
       at org.jboss.axis.strategies.InvocationStrategy.visit(InvocationStrategy
      .java:73)
       at org.jboss.axis.SimpleChain.doVisiting(SimpleChain.java:160)
       at org.jboss.axis.SimpleChain.invoke(SimpleChain.java:123)
       at org.jboss.axis.handlers.soap.SOAPService.invoke(SOAPService.java:560)
      
       at org.jboss.webservice.server.ServerEngine.invokeInternal(ServerEngine.
      java:200)
       at org.jboss.webservice.server.ServerEngine.invoke(ServerEngine.java:89)
      
       at org.jboss.axis.transport.http.AxisServlet.doPost(AxisServlet.java:911
      )
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
       at org.jboss.axis.transport.http.AxisServletBase.service(AxisServletBase
      .java:370)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
       at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
      icationFilterChain.java:252)
       at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
      ilterChain.java:173)
       at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFi
      lter.java:81)
       at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
      icationFilterChain.java:202)
       at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
      ilterChain.java:173)
       at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
      alve.java:213)
       at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
      alve.java:178)
       at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrinc
      ipalValve.java:39)
       at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Securit
      yAssociationValve.java:159)
       at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv
      e.java:59)
       at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
      ava:126)
       at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
      ava:105)
       at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
      ve.java:107)
       at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
      a:148)
       at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
      :856)
       at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
      ssConnection(Http11Protocol.java:744)
       at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo
      int.java:527)
       at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWor
      kerThread.java:112)
       at java.lang.Thread.run(Thread.java:595)
      


      What strange hier is that after deploying successfull the the process on the Jboss server i have the following output:


      
      20:21:05,821 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
      20:21:05,921 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=MySqlDS' to JNDI name 'java:MySqlDS'
      20:21:06,121 INFO [A] Bound to JNDI name: queue/A
      20:21:06,121 INFO [B] Bound to JNDI name: queue/B
      20:21:06,121 INFO [C] Bound to JNDI name: queue/C
      20:21:06,131 INFO [D] Bound to JNDI name: queue/D
      20:21:06,141 INFO [ex] Bound to JNDI name: queue/ex
      20:21:06,161 INFO [testTopic] Bound to JNDI name: topic/testTopic
      20:21:06,161 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
      20:21:06,161 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
      
      20:21:06,171 INFO [testQueue] Bound to JNDI name: queue/testQueue
      20:21:06,211 INFO [UILServerILService] JBossMQ UIL service available at : /0.0.0.0:8093
      20:21:06,251 INFO [DLQ] Bound to JNDI name: queue/DLQ
      20:21:06,281 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
      20:21:06,412 INFO [EARDeployer] Init J2EE application: file:/C:/OrdnerHyrarchie/MyCourses/Diplomarbeit/KOM/jBPM/Engine/jBossAS-4.0.3SP1/server/default/deploy/hello-application.ear
      20:21:06,632 INFO [ClientDeployer] Client ENC bound under: hello-client
      20:21:06,642 INFO [TomcatDeployer] deploy, ctxPath=/hello, warUrl=.../tmp/deploy/tmp36133hello-application.ear-contents/hello-web-exp.war/
      20:21:07,864 INFO [[/hello]] messagerServlet: BPEL application started: helloWorld
      20:21:08,515 INFO [WSDLFilePublisher] WSDL published to: file:/C:/OrdnerHyrarchie/MyCourses/Diplomarbeit/KOM/jBPM/Engine/jBossAS-4.0.3SP1/server/default/data/wsdl/hello-application.ear/hello-web.war/service.wsdl
      20:21:08,655 INFO [AxisService] WSDD published to: C:\OrdnerHyrarchie\MyCourses\Diplomarbeit\KOM\jBPM\Engine\jBossAS-4.0.3SP1\server\default\data\wsdl\hello-application.ear\hello-web.war\callerPort.wsdd
      20:21:09,105 INFO [AxisService] Web Service deployed: http://Bertrand:8080/hello/caller
      20:21:09,125 INFO [EARDeployer] Started J2EE application: file:/C:/OrdnerHyrarchie/MyCourses/Diplomarbeit/KOM/jBPM/Engine/jBossAS-4.0.3SP1/server/default/deploy/hello-application.ear
      20:21:09,266 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
      20:21:09,326 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
      20:21:09,336 INFO [JkMain] Jk running ID=0 time=0/30 config=null
      20:21:09,346 INFO [Server] JBoss (MX MicroKernel) [4.0.3SP1 (build: CVSTag=JBos
      s_4_0_3_SP1 date=200510231751)] Started in 40s:619ms
      
      


      Therefore when in take a look in the table bpel_processinstace in the database i can see that an instance of my process has been created and was up only for one or 2 miliseconds. Furthermore i can see the right SOAP-Request that was send to the server and the corresponding SOAP-Response. But i can't confirm that the server sends this response back.


      Did some one has a idea what can be the problem hier ?. Is it possible that the server get the request and generate a response but this can be routed to the client ? or there is something wrong with the process deployment ?.


      Every suggestion will be helpfull.


      Thanks once again.


      Bertrand Njipwo