David If you can capture tcpmon traces between the ESB and the backend that would help a lot.
Paul On 15 November 2010 19:44:27 UTC, David Borja <adbo...@gmail.com> wrote: > Hi, > > > I was trying the solution but i have the same result. I have attached the > new in-sequence flow. > > Thanks for your help > > > Regards > > > On Mon, Nov 15, 2010 at 1:08 PM, Hiranya Jayathilaka <hira...@wso2.com> > wrote: >> >> >> On Mon, Nov 15, 2010 at 12:45 PM, Paul Fremantle <p...@wso2.com> wrote: >>> >>> David >>> >>> Is there any way of getting tech support from the service authors? >>> >>> Hiranya, is there any way to turn off the Axis2 WS-Addressing handler >>> for this flow? >> >> Add the following to the in-sequence: >> <property name="disableAddressingForOutMessages" value="true" >> scope="axis2"/> >> >> Thanks, >> Hiranya >>> >>> Paul >>> >>> On 14 November 2010 22:07, David Borja <adbo...@gmail.com> wrote: >>> > In fact, the custom mediator doesn't do nothing, the ESB puts a >>> > MessageID >>> > different to Custom Mediator. >>> > >>> > Regards. >>> > >>> > >>> > >>> > On Sun, Nov 14, 2010 at 5:05 PM, David Borja <adbo...@gmail.com> wrote: >>> >> >>> >> HI, >>> >> >>> >> The custom mediator was an option that another developer gave me for >>> >> resolving the issue, but the problem always was the same: with or >>> >> without >>> >> the custom mediator. >>> >> >>> >> >>> >> Regards >>> >> >>> >> On Sun, Nov 14, 2010 at 2:47 PM, Hiranya Jayathilaka >>> >> <hira...@wso2.com> >>> >> wrote: >>> >>> >>> >>> Hi David, >>> >>> Have you done any tests without the custom mediator which alters the >>> >>> message ID? If you haven't, can you please try that option too? Is it >>> >>> possible that message contains an encrypted payload which contains a >>> >>> set of >>> >>> addressing headers based on which the server responds? >>> >>> Thanks, >>> >>> Hiranya >>> >>> >>> >>> On Mon, Nov 15, 2010 at 12:02 AM, David Borja <adbo...@gmail.com> >>> >>> wrote: >>> >>>> >>> >>>> Hi Paul, >>> >>>> >>> >>>> >>> >>>> I have attached the request/response when i remove WS-Addressing >>> >>>> header. >>> >>>> >>> >>>> I just know that backend service is implemented with Microsoft's WSE >>> >>>> 3 >>> >>>> technology. >>> >>>> >>> >>>> >>> >>>> >>> >>>> >>> >>>> Regards >>> >>>> >>> >>>> On Sun, Nov 14, 2010 at 12:40 PM, Paul Fremantle <p...@wso2.com> >>> >>>> wrote: >>> >>>>> >>> >>>>> David >>> >>>>> >>> >>>>> Please can you send a tcpmon trace of the link between the ESB and >>> >>>>> the >>> >>>>> Backend when you have disabled WS-Addressing? >>> >>>>> >>> >>>>> Thanks >>> >>>>> Paul >>> >>>>> >>> >>>>> On 14 November 2010 13:11, David Borja <adbo...@gmail.com> wrote: >>> >>>>> > Hi, >>> >>>>> > >>> >>>>> > Well, really the backend service is working actually because is a >>> >>>>> > payment >>> >>>>> > system used in my country for several e-commerce implementations, >>> >>>>> > the >>> >>>>> > project that i am working is a e-commerce application which needs >>> >>>>> > to >>> >>>>> > make >>> >>>>> > payments by this way. >>> >>>>> > >>> >>>>> > Any another idea? >>> >>>>> > >>> >>>>> > Thanks for your time! >>> >>>>> > >>> >>>>> > >>> >>>>> > Regards >>> >>>>> > >>> >>>>> > On Sat, Nov 13, 2010 at 7:03 PM, Hiranya Jayathilaka >>> >>>>> > <hira...@wso2.com> >>> >>>>> > wrote: >>> >>>>> >> >>> >>>>> >> >>> >>>>> >> On Sun, Nov 14, 2010 at 4:05 AM, David Borja <adbo...@gmail.com> >>> >>>>> >> wrote: >>> >>>>> >>> >>> >>>>> >>> Hi, >>> >>>>> >>> >>> >>>>> >>> Exactly! that is the problem, the ESB cannot to correlate the >>> >>>>> >>> message ID. >>> >>>>> >>> The custom mediator is trying to set a message id (i got this >>> >>>>> >>> solution from >>> >>>>> >>> other developer) but is not working , in log message the >>> >>>>> >>> message id >>> >>>>> >>> is not >>> >>>>> >>> equal. I don't know why the response has another message id. >>> >>>>> >>> >>> >>>>> >>> Any ideas?? >>> >>>>> >> >>> >>>>> >> I ran some tests with a similar configuration with Axis2 as my >>> >>>>> >> back-end >>> >>>>> >> service (with your custom mediator and the >>> >>>>> >> PRESERVE_WS_ADDRESSING >>> >>>>> >> option). >>> >>>>> >> Axis2 always make sure that the RelatesTo header of the response >>> >>>>> >> is >>> >>>>> >> equal to >>> >>>>> >> the MessageID header of the request. Not sure why your back-end >>> >>>>> >> service is >>> >>>>> >> sending an incorrect RelatesTo header. What is your back-end >>> >>>>> >> service >>> >>>>> >> anyway? >>> >>>>> >> Thanks, >>> >>>>> >> Hiranya >>> >>>>> >> >>> >>>>> >>> >>> >>>>> >>> Regards >>> >>>>> >>> >>> >>>>> >>> On Sat, Nov 13, 2010 at 1:01 PM, Hiranya Jayathilaka >>> >>>>> >>> <hira...@wso2.com> >>> >>>>> >>> wrote: >>> >>>>> >>>> >>> >>>>> >>>> Hi, >>> >>>>> >>>> The message ID of the request >>> >>>>> >>>> is urn:uuid:7CB6245CA223363571552999096573667-464880822. But >>> >>>>> >>>> the >>> >>>>> >>>> RelatesTo >>> >>>>> >>>> header of the response has the >>> >>>>> >>>> value urn:uuid:c639cbc1-fb18-4ac2-87c8-b014b9b6128b. Is this >>> >>>>> >>>> correct? I >>> >>>>> >>>> think this is why ESB is unable to correlate responses back to >>> >>>>> >>>> the >>> >>>>> >>>> request. >>> >>>>> >>>> Also you are setting a new message ID on the request using a >>> >>>>> >>>> custom >>> >>>>> >>>> mediator. Why do you do that? >>> >>>>> >>>> Thanks, >>> >>>>> >>>> Hiranya >>> >>>>> >>>> >>> >>>>> >>>> On Sat, Nov 13, 2010 at 5:21 AM, David Borja >>> >>>>> >>>> <adbo...@gmail.com> >>> >>>>> >>>> wrote: >>> >>>>> >>>>> >>> >>>>> >>>>> Do you mean xml for each artifact (proxy service and >>> >>>>> >>>>> sequences) >>> >>>>> >>>>> ?? >>> >>>>> >>>>> >>> >>>>> >>>>> >>> >>>>> >>>>> I have attached 4 files: GetBankList_WSExport is the proxy >>> >>>>> >>>>> service, >>> >>>>> >>>>> PSE_GetBankList_Req_Sec (Request sequence), >>> >>>>> >>>>> PSE_GetBankList_Resp_Sec >>> >>>>> >>>>> (Response sequence), CustomHeaderMediator.java is a mediator >>> >>>>> >>>>> for >>> >>>>> >>>>> setting >>> >>>>> >>>>> MessageContext ID. >>> >>>>> >>>>> >>> >>>>> >>>>> I did the same test without ws-addressing and i got the same >>> >>>>> >>>>> error. >>> >>>>> >>>>> >>> >>>>> >>>>> In addition, i have attached the request and the response for >>> >>>>> >>>>> backend >>> >>>>> >>>>> service (Taken from TCP Monitor) >>> >>>>> >>>>> >>> >>>>> >>>>> >>> >>>>> >>>>> Thanks for your help. >>> >>>>> >>>>> >>> >>>>> >>>>> Regards >>> >>>>> >>>>> >>> >>>>> >>>>> On Fri, Nov 12, 2010 at 6:02 PM, Hiranya Jayathilaka >>> >>>>> >>>>> <hira...@wso2.com> >>> >>>>> >>>>> wrote: >>> >>>>> >>>>>> >>> >>>>> >>>>>> >>> >>>>> >>>>>> On Sat, Nov 13, 2010 at 4:12 AM, David Borja >>> >>>>> >>>>>> <adbo...@gmail.com> >>> >>>>> >>>>>> wrote: >>> >>>>> >>>>>>> >>> >>>>> >>>>>>> Please!! i need help with this!! i.m going slightly mad! >>> >>>>> >>>>>>> urgent!!, >>> >>>>> >>>>>>> i.m doing a demo for a customer!!! >>> >>>>> >>>>>> >>> >>>>> >>>>>> Is it possible to share the synapse.xml? >>> >>>>> >>>>>> Thanks, >>> >>>>> >>>>>> Hiranya >>> >>>>> >>>>>> >>> >>>>> >>>>>>> >>> >>>>> >>>>>>> >>> >>>>> >>>>>>> Thanks!! >>> >>>>> >>>>>>> >>> >>>>> >>>>>>> Regards >>> >>>>> >>>>>>> >>> >>>>> >>>>>>> On Fri, Nov 12, 2010 at 5:06 PM, David Borja >>> >>>>> >>>>>>> <adbo...@gmail.com> >>> >>>>> >>>>>>> wrote: >>> >>>>> >>>>>>>> >>> >>>>> >>>>>>>> Hi Devs!! >>> >>>>> >>>>>>>> >>> >>>>> >>>>>>>> I am getting the following warning message: >>> >>>>> >>>>>>>> >>> >>>>> >>>>>>>> "Synapse received a response for the request with message >>> >>>>> >>>>>>>> id: >>> >>>>> >>>>>>>> urn:xxxxxxxxxxxxxxxxxxx but a callback is not registered >>> >>>>> >>>>>>>> (anymore) to >>> >>>>> >>>>>>>> process this response". >>> >>>>> >>>>>>>> >>> >>>>> >>>>>>>> Then a Read time out exception is thrown. >>> >>>>> >>>>>>>> >>> >>>>> >>>>>>>> I am working with a TCP monitor and i can see the server >>> >>>>> >>>>>>>> responds >>> >>>>> >>>>>>>> with normal message, but the ESB cannot process the >>> >>>>> >>>>>>>> Response >>> >>>>> >>>>>>>> sequence. >>> >>>>> >>>>>>>> >>> >>>>> >>>>>>>> I.m not working with WS-Addressing, however in Backend >>> >>>>> >>>>>>>> response i >>> >>>>> >>>>>>>> can see WS-Addressing tags. >>> >>>>> >>>>>>>> >>> >>>>> >>>>>>>> Any ideas? >>> >>>>> >>>>>>>> >>> >>>>> >>>>>>>> >>> >>>>> >>>>>>>> Regards, >>> >>>>> >>>>>>>> >>> >>>>> >>>>>>> >>> >>>>> >>>>>>> >>> >>>>> >>>>>>> _______________________________________________ >>> >>>>> >>>>>>> Carbon-dev mailing list >>> >>>>> >>>>>>> Carbon-dev@wso2.org >>> >>>>> >>>>>>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>>>> >>>>>>> >>> >>>>> >>>>>> >>> >>>>> >>>>>> >>> >>>>> >>>>>> >>> >>>>> >>>>>> -- >>> >>>>> >>>>>> Hiranya Jayathilaka >>> >>>>> >>>>>> Senior Software Engineer; >>> >>>>> >>>>>> WSO2 Inc.; http://wso2.org >>> >>>>> >>>>>> E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 >>> >>>>> >>>>>> Blog: http://techfeast-hiranya.blogspot.com >>> >>>>> >>>>>> >>> >>>>> >>>>>> _______________________________________________ >>> >>>>> >>>>>> Carbon-dev mailing list >>> >>>>> >>>>>> Carbon-dev@wso2.org >>> >>>>> >>>>>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>>>> >>>>>> >>> >>>>> >>>>> >>> >>>>> >>>>> >>> >>>>> >>>>> _______________________________________________ >>> >>>>> >>>>> Carbon-dev mailing list >>> >>>>> >>>>> Carbon-dev@wso2.org >>> >>>>> >>>>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>>>> >>>>> >>> >>>>> >>>> >>> >>>>> >>>> >>> >>>>> >>>> >>> >>>>> >>>> -- >>> >>>>> >>>> Hiranya Jayathilaka >>> >>>>> >>>> Senior Software Engineer; >>> >>>>> >>>> WSO2 Inc.; http://wso2.org >>> >>>>> >>>> E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 >>> >>>>> >>>> Blog: http://techfeast-hiranya.blogspot.com >>> >>>>> >>>> >>> >>>>> >>>> _______________________________________________ >>> >>>>> >>>> Carbon-dev mailing list >>> >>>>> >>>> Carbon-dev@wso2.org >>> >>>>> >>>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>>>> >>>> >>> >>>>> >>> >>> >>>>> >>> >>> >>>>> >>> _______________________________________________ >>> >>>>> >>> Carbon-dev mailing list >>> >>>>> >>> Carbon-dev@wso2.org >>> >>>>> >>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>>>> >>> >>> >>>>> >> >>> >>>>> >> >>> >>>>> >> >>> >>>>> >> -- >>> >>>>> >> Hiranya Jayathilaka >>> >>>>> >> Senior Software Engineer; >>> >>>>> >> WSO2 Inc.; http://wso2.org >>> >>>>> >> E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 >>> >>>>> >> Blog: http://techfeast-hiranya.blogspot.com >>> >>>>> >> >>> >>>>> >> _______________________________________________ >>> >>>>> >> Carbon-dev mailing list >>> >>>>> >> Carbon-dev@wso2.org >>> >>>>> >> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>>>> >> >>> >>>>> > >>> >>>>> > >>> >>>>> > _______________________________________________ >>> >>>>> > Carbon-dev mailing list >>> >>>>> > Carbon-dev@wso2.org >>> >>>>> > https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>>>> > >>> >>>>> > >>> >>>>> >>> >>>>> >>> >>>>> >>> >>>>> -- >>> >>>>> Paul Fremantle >>> >>>>> CTO and Co-Founder, WSO2 >>> >>>>> OASIS WS-RX TC Co-chair, VP, Apache Synapse >>> >>>>> >>> >>>>> Office: +44 844 484 8143 >>> >>>>> Cell: +44 798 447 4618 >>> >>>>> >>> >>>>> blog: http://pzf.fremantle.org >>> >>>>> twitter.com/pzfreo >>> >>>>> p...@wso2.com >>> >>>>> >>> >>>>> wso2.com Lean Enterprise Middleware >>> >>>>> >>> >>>>> Disclaimer: This communication may contain privileged or other >>> >>>>> confidential information and is intended exclusively for the >>> >>>>> addressee/s. If you are not the intended recipient/s, or believe >>> >>>>> that >>> >>>>> you may have received this communication in error, please reply to >>> >>>>> the >>> >>>>> sender indicating that fact and delete the copy you received and in >>> >>>>> addition, you should not print, copy, retransmit, disseminate, or >>> >>>>> otherwise use the information contained in this communication. >>> >>>>> Internet communications cannot be guaranteed to be timely, secure, >>> >>>>> error or virus-free. The sender does not accept liability for any >>> >>>>> errors or omissions. >>> >>>>> >>> >>>>> _______________________________________________ >>> >>>>> Carbon-dev mailing list >>> >>>>> Carbon-dev@wso2.org >>> >>>>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>>> >>> >>>> >>> >>>> _______________________________________________ >>> >>>> Carbon-dev mailing list >>> >>>> Carbon-dev@wso2.org >>> >>>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>>> >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> Hiranya Jayathilaka >>> >>> Senior Software Engineer; >>> >>> WSO2 Inc.; http://wso2.org >>> >>> E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 >>> >>> Blog: http://techfeast-hiranya.blogspot.com >>> >>> >>> >>> _______________________________________________ >>> >>> Carbon-dev mailing list >>> >>> Carbon-dev@wso2.org >>> >>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >>> >> >>> > >>> > >>> > _______________________________________________ >>> > Carbon-dev mailing list >>> > Carbon-dev@wso2.org >>> > https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> > >>> > >>> >>> >>> >>> -- >>> Paul Fremantle >>> CTO and Co-Founder, WSO2 >>> OASIS WS-RX TC Co-chair, VP, Apache Synapse >>> >>> Office: +44 844 484 8143 >>> Cell: +44 798 447 4618 >>> >>> blog: http://pzf.fremantle.org >>> twitter.com/pzfreo >>> p...@wso2.com >>> >>> wso2.com Lean Enterprise Middleware >>> >>> Disclaimer: This communication may contain privileged or other >>> confidential information and is intended exclusively for the >>> addressee/s. If you are not the intended recipient/s, or believe that >>> you may have received this communication in error, please reply to the >>> sender indicating that fact and delete the copy you received and in >>> addition, you should not print, copy, retransmit, disseminate, or >>> otherwise use the information contained in this communication. >>> Internet communications cannot be guaranteed to be timely, secure, >>> error or virus-free. The sender does not accept liability for any >>> errors or omissions. >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> Carbon-dev@wso2.org >>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> >> >> -- >> Hiranya Jayathilaka >> Senior Software Engineer; >> WSO2 Inc.; http://wso2.org >> E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 >> Blog: http://techfeast-hiranya.blogspot.com >> >> _______________________________________________ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse Office: +44 844 484 8143 Cell: +44 798 447 4618 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. _______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
