- This topic has 9 replies, 4 voices, and was last updated 6 years, 4 months ago by
.
-
Topic
-
Hi, I am trying to configure a thread that receives query messages and sends RSP messages outbound from the same port. This is the first time I attempt this and I can’t find much information about how to configure it.
I have the thread set as a client, the Outbound Only check box deselected under the Inbound tab, the Outbound tab is configured not to await replies, and have added the RSP transaction types under the Route Replies tab. However, I do not see a dotted line connecting this thread to one that will be receiving the RSP messages (the Cloverleaf documentation states that reply route paths use a dotted line).
Why do I not see the dotted lines?
What other configuration am I missing?
Thank you for your help!
Francesca
-
Replies
-
-
-
The communication protocol is pdl-tcpip
The RSP message is generated by the application as a response to the query message and sent outbound.
The query message is generated by an application connected to thread A and sent to thread B (another system). Then the other system connected to thread B sends back a reply into Cloverleaf on the same port. It then actually send this reply to a different thread (let’s call it thread C), so the reply is not generated by cloverleaf. It is created by the same system that got the query and sent outbound on the same port.
-
On your outbound thread B you do want to select “await replies” in order to route those RSP messages back to thread A as replies.
to see the dotted lines, make sure you have
View->Show All Reply Routes enabled.edit: I see you want to route the replies to thread C. In this case make sure you have “Route Replies to original source only”
disabled under Process->Configure for the process that owns thread B.Rob Abbott
Cloverleaf Emeritus -
-
I don’t think that option (route replys to original thread) is available in 6.0.
What I have done in this situation is to use a Tcl proc to OVER the reply to the inbound side of the outbound thread. Then I routed the reply (now an inbound message) as a normal routing to Thread C in your case.
If you would like to discuss further and/or like the proc I used, email me.
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
-
Since I specified the destination thread as thread C in the Route Replies tab of thread B, I would think it should send all replies to thread C. Why wouldn’t that be the case? Not sure if this matters, but thread B does not send an ACK back after it receives they query message from thread A. The acknowledgement is sent as part of the response to thread C.
Unfortunately, I can’t test yet; otherwise, I would have a better idea of how the Route Reply option works
As a side note, thank you Jim for offering to discuss/share your code 🙂
-
Before Cloverleaf was changed to allow you to specify otherwise, all replies would only be attempted to be routed to the originating thread.
Thus at your release level, it does not matter what you specify for the replies, Cloverleaf will attempt to route them back to the originating thread.
In my experience, there was an issue with that as well in certain releases of Cloverleaf.
Hence if you turn the reply into a message and OVER it you can still get it where you want but it will be routed as a message rather than a reply.
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
-
Thank you very much for the explanation. Ok, then I think I will definitely need your proc. Where do you place it? In the each route in the Route Replies tab or in the TPS Outbound Data field of the Outbound tab? In the latter case I am guessing I would have to move the routes from the Route Replies tab to the Route Messages tab
-
-
- The forum ‘Cloverleaf’ is closed to new topics and replies.
