- This topic has 7 replies, 4 voices, and was last updated 14 years, 3 months ago by .
I have an HTTPS Client protocol thread set up that is connecting to the outbound system; POSTing the message; and receiving a response.
Now the issue I have is routing that response.
I am using the provided httpquery proc modified so that I am using tclCurl for the essence of the POST (actually using the tclCurl httppost command). I did not change the setting of the metadata for directing the flow of the response.
I tried configuring the thread both to Await Replies (so that the response would be handled as a REPLY) and to not Await Replies (so that the response would be handled as DATA). Not at the same time of course.
I have aqppropriate Route Messages and Route Replies configured.
When configured to handle as a REPLY, the response message ends up in the Error DB with a 101 (Invalid TrxID) – curiously there is no entry in either the process log or any error log that I can see indicating a TrxID error which I would expect to see and more importantly would tell me what the offending TrxId detected was.
Even more curiously, I can take that very same message out of the Error DB and submit it as a REPLY to the same thread configuration and it routes as expected. So I am sure my Route configuration is correct.
When configured to handle as DATA, I do not end up with anything in the Error DB, but also nothing gets routed. With EO up I can see the message getting OVER’d to the Inbound Side and I see my Inbound Tps proc being executed, and I see the message beign prepared for the xlate pthread, then nothing.
I have double and triple checked my thread configuration. There must be something I have configured incorrectly but I just do not see it.
Everything I can see in the log with the ‘noise’ turned up all the way indicates to me everything is proceeding as expected- just no tangible result. The message generated via the httpquery proc is just gone. Not in the Recovery or Error DB.
Anyone have any ideas?
- The forum ‘Cloverleaf’ is closed to new topics and replies.