Uploaded image for project: 'RiftSaw'
  1. RiftSaw
  2. RIFTSAW-376

Bpel process invoking a service that is taking more time to respond is causing the process failure in a particular environment, could be the mex.timeout parameter.

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 2.3.0.Final
    • None
    • None
    • None
    • Hide

      Build and deploy web service.
      Build and deploy the BPEL process.
      Invoke the BPEL process.
      Check the logs for the errors.

      Show
      Build and deploy web service. Build and deploy the BPEL process. Invoke the BPEL process. Check the logs for the errors.

    Description

      I have a simple hello bpel process and a simple helloworld web service. The process invokes the web service. The web service is replying with a string within 2 min and 30 sec (there is a simple sleep).The Bpel process, after invoking the web service just replies with the response from the web service. The Bpel process has configured the mex.timeout parameter to 10 minutes in the test.endpoint file.

      I have tested this use case in my local environment which is a Windows XP and on a remote Linux machine (i686 i686 i386 GNU/Linux). Both have the same
      JBoss, Riftsaw version which is jboss-soa-p-5 (the enterprise version).

      On Windows machine is working perfectly, but on the Linux environment the bpel process throws the following error:

      2011-04-20 13:48:59,554 INFO (LoggerStream.write:156) (ODEServer-8
      ProcessMessageExchangeEvent:
      Aspect = 3
      Operation = sayHelloLate
      MessageExchangeId = hqejbhcnphr67p66aq6v3u
      PortType =

      {http://test.com}

      HelloWorld
      Type = instanceLifecycle
      ProcessInstanceId = 215
      ProcessId =

      {com.test}HelloService-0
      ProcessName = {com.test}

      HelloService
      Timestamp = Wed Apr 20 13:48:59 CEST 2011
      LineNo = -1
      Class = class org.apache.ode.bpel.evt.ProcessMessageExchangeEvent
      2011-04-20 13:48:59,894 INFO (Logger.info:296) (ODEServer-7 Setting new service endpoint address in wsdl: http://10.10.210.14:8080/hello/HelloWorld
      2011-04-20 13:48:59,927 INFO (LoggerStream.write:156) (http-saascsf-dev-li%2F10.10.210.14-8080-2 wait for a while...
      2011-04-20 13:50:16,224 WARN (LogUtils.doLog:365) (ODEServer-7 Interceptor for

      {http://test.com}

      HelloWorldService#

      {http://cxf.apache.org/jaxws/dispatch}

      Invoke has thrown exception, unwinding now
      org.apache.cxf.interceptor.Fault: Could not send Message.
      at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:64)
      at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
      at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:487)
      at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:313)
      at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:265)
      at org.apache.cxf.endpoint.ClientImpl.invokeWrapped(ClientImpl.java:300)
      at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:263)
      at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:197)
      at org.jboss.soa.bpel.runtime.ws.WebServiceClient$TwoWayCallable$1.call(WebServiceClient.java:256)
      at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:284)
      at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:239)
      at org.jboss.soa.bpel.runtime.ws.WebServiceClient$TwoWayCallable.call(WebServiceClient.java:224)
      at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
      at java.util.concurrent.FutureTask.run(FutureTask.java:138)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      at java.lang.Thread.run(Thread.java:662)
      Caused by: java.net.SocketTimeoutException: SocketTimeoutException invoking http://10.10.210.14:8080/hello/HelloWorld: Read timed out
      at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
      at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
      at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
      at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
      at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:2058)
      at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:2043)
      at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66)
      at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:639)
      at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
      ... 16 more
      Caused by: java.net.SocketTimeoutException: Read timed out
      at java.net.SocketInputStream.socketRead0(Native Method)
      at java.net.SocketInputStream.read(SocketInputStream.java:129)
      at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
      at java.io.BufferedInputStream.read1(BufferedInputStream.java:258)
      at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
      at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:687)
      at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:632)
      at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1195)
      at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379)
      at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2165)
      at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:2134)
      at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1988)
      ... 19 more
      2011-04-20 13:50:16,228 ERROR (WebServiceClient$TwoWayCallable$1.call:304) (ODEServer-7 WS invocation failed
      javax.xml.ws.WebServiceException: Could not send Message.
      at org.apache.cxf.jaxws.DispatchImpl.mapException(DispatchImpl.java:223)
      at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:270)
      at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:197)
      at org.jboss.soa.bpel.runtime.ws.WebServiceClient$TwoWayCallable$1.call(WebServiceClient.java:256)
      at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:284)
      at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:239)
      at org.jboss.soa.bpel.runtime.ws.WebServiceClient$TwoWayCallable.call(WebServiceClient.java:224)
      at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
      at java.util.concurrent.FutureTask.run(FutureTask.java:138)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      at java.lang.Thread.run(Thread.java:662)
      Caused by: java.net.SocketTimeoutException: SocketTimeoutException invoking http://10.10.210.14:8080/hello/HelloWorld: Read timed out
      at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
      at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
      at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
      at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
      at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:2058)
      at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:2043)
      at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66)
      at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:639)
      at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
      at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
      at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:487)
      at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:313)
      at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:265)
      at org.apache.cxf.endpoint.ClientImpl.invokeWrapped(ClientImpl.java:300)
      at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:263)
      ... 10 more
      Caused by: java.net.SocketTimeoutException: Read timed out
      at java.net.SocketInputStream.socketRead0(Native Method)
      at java.net.SocketInputStream.read(SocketInputStream.java:129)
      at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
      at java.io.BufferedInputStream.read1(BufferedInputStream.java:258)
      at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
      at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:687)
      at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:632)
      at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1195)
      at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379)
      at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2165)
      at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:2134)
      at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1988)
      ... 19 more

      The error for me is very strange because for me, it looks like the service is not available, although it is there and working. If I don't have the sleep in the web service the process executes successfully.
      Could you please investigate this into your environment? I have spent a lot of time to investigate this, but I couldn't find any solution.
      Please let me know how I could attach my process and service examples.

      Attachments

        Issue Links

          is related to

          Task - Represents a small unit of work that is not end-user facing. RIFTSAW-378 Testcase required for jaxws client timeout

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Activity

            People

              gary@brownuk.com Gary Brown
              clsimone Laura Simona (Inactive)
              Archiver:
              rhn-support-adandapa Aitik Dandapat

              Dates

                Created:
                Updated:
                Resolved:
                Archived:

                PagerDuty