Delivery methods defined in partner profile not picked up by processing service
[TNS.0005.4027W] An exception occurred invoking a processing service for document . The processing service was xxx, and the original error message was: com.wm.lang.flow.FlowException: No HTTP or HTTPS transport found. Cannot deliver message.
Two delivery methods(Primary & Secondary HTTP) have been defined in the receiver profile. But still above error is thrown whenever a partner is sending to this partner.
TN Console is behaving wierd, like there is no Enable trading partner logo(the bright bulb) even for a profile which is inactive. For some profiles it is visible, most profiles it is not visible. We only can disable profile from TN, not enable.
1.Two delivery methods(Primary & Secondary HTTP) have been defined in the receiver profile. But still above error is thrown whenever a partner is sending to this partner. → Out of those 2 methoids which is set check mark "Use as Preferred protocol?
2.I believe there should be some conflict in your TN configuration or DB side issues on the enable/disable issues…
Also IS your IS/TN running in a cluster and also what TNS fix level are you on?
I don’t think there are any other processing rules invoking the same service. NO recent fixes/patches applied too. Is there anything that needs to be checked from DB side?