Re: [Dev] [ESB - 4.8.1] Clarification regarding message processor
On Sun, Aug 2, 2015 at 12:51 PM, Tishan Dahanayakage wrote: > Hi Shafreen/Isuru, > > On Sun, Aug 2, 2015 at 10:38 AM, Isuru Udana wrote: > >> Hi Shafreen, >> >> On Sun, Aug 2, 2015 at 10:11 AM, Shafreen Anfar >> wrote: >> >>> Hi Tishan, >>> >>> We haven't tested for each and every status code. But ideally, it should >>> retry for most of the non 200 series status codes. >>> >> AFAIK, by default we are retrying only for connection errors/timeouts >> etc. but not for business level faults of the backend. But we have the >> option to retry for business level errors also by specifying retry codes, >> non-retry codes. >> > > Which means if we receive HTTP 400 from BE message will not be retried > for default configuration. Isn't it? > > > Yes. > I have setup a sample to test this with a mocked BE service which > responds with 400. I observed that messages are getting removed from store. > > To confirm the behavior I enabled wire logs. But wire logs did not show the > request to BE through message processor and response from BE. Is this the > expected behavior? Are we bypassing transport layer when using Message > Processor? If so please point a way to confirm mock BE service is sending > 400 to ESB. > MP doesn't use the non-blocking http transports, It uses the blocking transport (CommonsHTTPSender). So the way to enable wirelogs for MP is different. Please refer to ESB troubleshoot guide. Thanks. > > Thanks > Tishan > > >> Thanks. >> >>> >>> On Fri, Jul 31, 2015 at 2:37 PM, Tishan Dahanayakage >>> wrote: >>> Hi, What HTTP status codes will be retried by default when using message processor? Thanks Tishan -- Tishan Dahanayakage Software Engineer WSO2, Inc. Mobile:+94 716481328 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, re-transmit, 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. >>> >>> >>> >>> -- >>> Regards, >>> *Shafreen* >>> Software Engineer >>> WSO2 Inc >>> Mobile : 077-556-395-1 >>> >> >> >> >> -- >> *Isuru Udana* >> Associate Technical Lead >> WSO2 Inc.; http://wso2.com >> email: isu...@wso2.com cell: +94 77 3791887 >> blog: http://mytecheye.blogspot.com/ >> > > > > -- > Tishan Dahanayakage > Software Engineer > WSO2, Inc. > Mobile:+94 716481328 > > 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, re-transmit, 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. > -- *Isuru Udana* Associate Technical Lead WSO2 Inc.; http://wso2.com email: isu...@wso2.com cell: +94 77 3791887 blog: http://mytecheye.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB - 4.8.1] Clarification regarding message processor
Hi Shafreen/Isuru, On Sun, Aug 2, 2015 at 10:38 AM, Isuru Udana wrote: > Hi Shafreen, > > On Sun, Aug 2, 2015 at 10:11 AM, Shafreen Anfar wrote: > >> Hi Tishan, >> >> We haven't tested for each and every status code. But ideally, it should >> retry for most of the non 200 series status codes. >> > AFAIK, by default we are retrying only for connection errors/timeouts etc. > but not for business level faults of the backend. But we have the option to > retry for business level errors also by specifying retry codes, non-retry > codes. > Which means if we receive HTTP 400 from BE message will not be retried for default configuration. Isn't it? I have setup a sample to test this with a mocked BE service which responds with 400. I observed that messages are getting removed from store. To confirm the behavior I enabled wire logs. But wire logs did not show the request to BE through message processor and response from BE. Is this the expected behavior? Are we bypassing transport layer when using Message Processor? If so please point a way to confirm mock BE service is sending 400 to ESB. Thanks Tishan > Thanks. > >> >> On Fri, Jul 31, 2015 at 2:37 PM, Tishan Dahanayakage >> wrote: >> >>> Hi, >>> >>> What HTTP status codes will be retried by default when using message >>> processor? >>> >>> Thanks >>> Tishan >>> >>> -- >>> Tishan Dahanayakage >>> Software Engineer >>> WSO2, Inc. >>> Mobile:+94 716481328 >>> >>> 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, re-transmit, 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. >>> >> >> >> >> -- >> Regards, >> *Shafreen* >> Software Engineer >> WSO2 Inc >> Mobile : 077-556-395-1 >> > > > > -- > *Isuru Udana* > Associate Technical Lead > WSO2 Inc.; http://wso2.com > email: isu...@wso2.com cell: +94 77 3791887 > blog: http://mytecheye.blogspot.com/ > -- Tishan Dahanayakage Software Engineer WSO2, Inc. Mobile:+94 716481328 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, re-transmit, 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. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB - 4.8.1] Clarification regarding message processor
Hi Shafreen, On Sun, Aug 2, 2015 at 10:11 AM, Shafreen Anfar wrote: > Hi Tishan, > > We haven't tested for each and every status code. But ideally, it should > retry for most of the non 200 series status codes. > AFAIK, by default we are retrying only for connection errors/timeouts etc. but not for business level faults of the backend. But we have the option to retry for business level errors also by specifying retry codes, non-retry codes. Thanks. > > On Fri, Jul 31, 2015 at 2:37 PM, Tishan Dahanayakage > wrote: > >> Hi, >> >> What HTTP status codes will be retried by default when using message >> processor? >> >> Thanks >> Tishan >> >> -- >> Tishan Dahanayakage >> Software Engineer >> WSO2, Inc. >> Mobile:+94 716481328 >> >> 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, re-transmit, 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. >> > > > > -- > Regards, > *Shafreen* > Software Engineer > WSO2 Inc > Mobile : 077-556-395-1 > -- *Isuru Udana* Associate Technical Lead WSO2 Inc.; http://wso2.com email: isu...@wso2.com cell: +94 77 3791887 blog: http://mytecheye.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB - 4.8.1] Clarification regarding message processor
Hi Tishan, We haven't tested for each and every status code. But ideally, it should retry for most of the non 200 series status codes. On Fri, Jul 31, 2015 at 2:37 PM, Tishan Dahanayakage wrote: > Hi, > > What HTTP status codes will be retried by default when using message > processor? > > Thanks > Tishan > > -- > Tishan Dahanayakage > Software Engineer > WSO2, Inc. > Mobile:+94 716481328 > > 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, re-transmit, 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. > -- Regards, *Shafreen* Software Engineer WSO2 Inc Mobile : 077-556-395-1 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [ESB - 4.8.1] Clarification regarding message processor
Hi, What HTTP status codes will be retried by default when using message processor? Thanks Tishan -- Tishan Dahanayakage Software Engineer WSO2, Inc. Mobile:+94 716481328 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, re-transmit, 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. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
