I have a orchestration which is receive a request from local rest service then send request to another remote Rest Service then if the remote service returns a response succ
Yes there is an issue with the WCF-WebHttp adapter in that it does not set the Message Type context property if there is a fault and so it then does not go the the Fault type defined on the port.
The only way to catch it is in a System.Exception block.
See my blog post BizTalk 2013 R2 known bugs, issues & quirks, BUG: BIZTALK WCF-WEBHTTP ADAPTER DOES NOT SET MESSAGE TYPE ON ERROR
Update: The below is no longer true after CU 5 for BizTalk 2013 R2, it now throws an error.
Also please note that if the end systems throws a 500 status code, it is NOT thrown as an error at all and you have to check the status code yourself.
See BizTalk WCF-WebHttp adapter does not detect 500 error