Uploaded image for project: 'JBoss Enterprise SOA Platform'
  1. JBoss Enterprise SOA Platform
  2. SOA-3466

Dynapartner quickstart fails to invoke dynamically assigned endpoint reference.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Migrated to another ITS
    • Affects Version/s: 5.2.0.ER4
    • Fix Version/s: 5.3.0 GA
    • Component/s: Examples
    • Labels:
      None
    • Steps to Reproduce:
      Hide

      ant deploy
      ant runtest

      Show
      ant deploy ant runtest
    • Affects:
      Release Notes, Interactive Demo/Tutorial
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      Set properties

      bpel.uddi.registration=false
      bpel.uddi.lookup=false

      in ${server.home}/server/${server.config}/deploy/riftsaw.sar/bpel.properties

      Show
      Set properties bpel.uddi.registration=false bpel.uddi.lookup=false in ${server.home}/server/${server.config}/deploy/riftsaw.sar/bpel.properties
    • Release Notes Text:
      Hide
      https://issues.jboss.org/browse/SOA-3466

      The dynapartner quick start fails to invoke dynamically-assigned endpoint references. Currently there is a bug in the BPEL engine where the EPR is essentially cached with the partner link, so any subsequent changes after the first invoke do not take effect As a workaround, users should set the UDDI lookup/registration properties to false. It will then work.

      If the workaround is not employed, the user will not be able to use the UDDI register to look up partner web-services from a BPEL process, but will still be able to call local/remote web-services by including the WSDL of the service in the Java archive deployed on the server. Also, If a user wants to reuse a BPEL process as a web-service he or she must manually register the end-point in the UDDI as the engine will not do it automatically.
      Show
      https://issues.jboss.org/browse/SOA-3466 The dynapartner quick start fails to invoke dynamically-assigned endpoint references. Currently there is a bug in the BPEL engine where the EPR is essentially cached with the partner link, so any subsequent changes after the first invoke do not take effect As a workaround, users should set the UDDI lookup/registration properties to false. It will then work. If the workaround is not employed, the user will not be able to use the UDDI register to look up partner web-services from a BPEL process, but will still be able to call local/remote web-services by including the WSDL of the service in the Java archive deployed on the server. Also, If a user wants to reuse a BPEL process as a web-service he or she must manually register the end-point in the UDDI as the engine will not do it automatically.
    • Release Notes Docs Status:
      Documented as Known Issue

      Description

      Invoke fails with the following exception:

      2011-10-07 11:08:43,833 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/dynpartner/DynResponderService].[Endpoint-58b9dfee-734e-4c6a-a2a2-916edb2acc64]] (http-127.0.0.1-8080-2) Servlet.service() for servlet Endpoint-58b9dfee-734e-4c6a-a2a2-916edb2acc64 threw exception
      		 
      javax.servlet.ServletException: Cannot obtain destination for: //dynpartner/DynResponderService
      		 
      	at org.jboss.wsf.stack.cxf.ServletControllerExt.findDestination(ServletControllerExt.java:114)
      		 
      	at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:168)
      		 
      	at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:61)
      		 
      	at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:185)
      		 
      	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179)
      		 
      	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:103)
      		 
      	at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
      		 
      	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159)
      		 
      	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
      		 
      	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
      		 
      	at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
      		 
      	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
      		 
      	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
      		 
      	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
      		 
      	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
      		 
      	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183)
      		 
      	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95)
      		 
      	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
      		 
      	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
      		 
      	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
      		 
      	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
      		 
      	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
      		 
      	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
      		 
      	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
      		 
      	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
      		 
      	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:599)
      		 
      	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:451)
      		 
      	at java.lang.Thread.run(Thread.java:619)
      		 
      2011-10-07 11:08:43,894 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (ODEServer-2) Interceptor for {http://ode/bpel/responder.wsdl}DynResponderService#{http://cxf.apache.org/jaxws/dispatch}Invoke has thrown exception, unwinding now
      		 
      org.apache.cxf.interceptor.Fault: Response was of unexpected text/html ContentType.  Incoming portion of HTML stream: <html><head><title>JBoss Web/2.1.11.GA - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 500 - </h1><HR size="1" noshade="noshade"><p><b>type</b> Exception report</p><p><b>message</b> <u></u></p><p><b>description</b> <u>The server encountered an internal error () that prevented it from fulfilling this request.</u></p><p><b>exception</b> <pre>javax.servlet.ServletException: Cannot obtain destination for: //dynpartner/DynResponderService
      		 
      	org.jboss.wsf.stack.cxf.ServletControllerExt.findDestination(ServletControllerExt.java:114)
      		 
      	org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:168)
      		 
      	org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:61)
      		 
      	org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:185)
      		 
      	org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179)
      		 
      	org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:103)
      		 
      	javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
      		 
      	org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159)
      		 
      	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
      		 
      </pre></p><p><b>note</b> <u>The full stack trace of the root cause is available in the JBoss Web/2.1.11.GA logs.</u></p><HR size="1" noshade="noshade"><h3>JBoss Web/2.1.11.GA</h3></body></html>
      		 
      	at org.apache.cxf.interceptor.StaxInInterceptor.handleMessage(StaxInInterceptor.java:79)
      		 
      	at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
      		 
      	at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:755)
      		 
      	at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2408)
      		 
      	at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:2278)
      		 
      	at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:2121)
      		 
      	at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66)
      		 
      	at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:695)
      		 
      	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:516)
      		 
      	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:332)
      		 
      	at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:218)
      		 
      	at org.jboss.soa.bpel.runtime.ws.WebServiceClient$TwoWayCallable$1.call(WebServiceClient.java:274)
      		 
      	at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:294)
      		 
      	at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:251)
      		 
      	at org.jboss.soa.bpel.runtime.ws.WebServiceClient$TwoWayCallable.call(WebServiceClient.java:213)
      		 
      	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:619)
      		 
      2011-10-07 11:08:43,909 WARN  [org.jboss.soa.bpel.runtime.ws.WebServiceClient] (ODEServer-2) Fault response: faultType=(unknown)
      		 
      2011-10-07 11:08:43,973 ERROR [org.apache.ode.bpel.runtime.INVOKE] (ODEServer-1) Failure during invoke: Unspecified
      		 
      2011-10-07 11:08:43,982 INFO  [org.apache.ode.bpel.engine.BpelRuntimeContextImpl] (ODEServer-1) ActivityRecovery: Registering activity 9, failure reason: Unspecified on channel 18

      This exception is most probably related to SOA-3406 (see Kurt's comment from 27/Sep/11 10:42 AM).

        Gliffy Diagrams

          Attachments

          1. bpel_dynpartner.zip
            16 kB
          2. dynpartner_sample.zip
            9 kB
          3. DynPartnerMain.bpel
            6 kB
          4. NewDynPartnerMain.bpel
            6 kB
          5. SOA-3466-patch.txt
            2 kB

            Issue Links

            cloned to

            Bug - A problem which impairs or prevents the functions of the product. RIFTSAW-462 Avoid creating a WebserverBaseUrl with a double slash during rewriting the URL

            • Major - A request that should be considered seriously but is not a show stopper.
            • Closed
            is related to

            Task - A task that needs to be done. SOA-2974 Check that fix for assigning EPR is incorporated into EAP version to be used in SOA-P 5.2

            • Major - A request that should be considered seriously but is not a show stopper.
            • Closed

              Activity

                People

                • Assignee:
                  kurtstam Kurt Stam
                  Reporter:
                  mbaluch Marek Baluch
                  Writer:
                  David Le Sage
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: