locked
Send Port Subscription issue on Failure RRS feed

  • Question

  • WalmartIn > WalmartOut

    JohnIn > JohnOut

    WalmartOut subscribes where RecieveLocationName == WalmartIn.

    JohnOut subscribes where RecieveLocationName == JohnIn

    I have an orchestration involved to send emails for error/tracking etc. Whenever WalmartOut fails the file is sent to JohnOut. What am I missing? 

    Friday, November 7, 2014 5:22 PM

All replies

  • For clarity, under normal circumstances, you can't use BTS.ReceiveLocationName for routing because it is not Promoted coming off the Receive Port.

    BTS.ReceivePortName is Promoted.

    Friday, November 7, 2014 5:28 PM
    Moderator
  • In this case, ReceiveLocationName is Promoted. 

    I used a correlation set on the send port to promote ReceiveLocationName 

    http://btsguru.blogspot.com/2011/09/how-to-expose-promote-bts.html

    • Edited by JordanJ08 Friday, November 7, 2014 7:36 PM
    Friday, November 7, 2014 7:32 PM
  • To diagnose, Stop, don't Unenlist, JohnOut then fail WalmartOut and see why WalmartOut is getting pickup by JohnOut.
    Friday, November 7, 2014 8:09 PM
    Moderator
  • Great! Thanks for the suggestion. 

    The failure is all about WalmartOut. No sign of JohnOut in the error. 

    I am simply renaming the WalmartOut folder to get the error. Having JohnOut stopped didnt not give me any insight as to why this would be happening.  I have checked the subscriptions and they dont match. SPID does not match either. I am baffled. 


    Friday, November 7, 2014 8:17 PM