Hi all,
I have an JMS-based architecture at a customer where I try to fix a transaction flow issue. The basic pattern is a client that fires an async JMS message (with a send() method that instantly returns with a temporary message queue name) and then waits synchronously to receive the answer. The server in this example answers uses this temporary destination for the answer and delivers that message to the client waiting for it. See the sequence diagram:
Now the problem is that the returning call is not 'stitched back' into the receive() method waiting for it. Resulting in a picture like this:
Don't get confused by the blue node on the bottom - that's an 'observed tier'.
I would like to achieve that the messaging box on the lower right dissappears and goes back to the 'Loadgenerator' node where it started.
I wonder if this is actually possible - I could only manage to get this done when the receive() is running in a different thread than the send(). Here I actually try to connect a sub-path of the purepath tree to it's parent path.
Anybody has any idea ?
Cheers,
Torsten
can you explain this a bit better? i mean what ais the flow ? and what do you want ....
load generator sends call to tibco? tibco calls X that sends a jms to queue. who process the message? X? and it is not stitched to the purepath? i think you should edit jms receive entry point in order to see the process after the jms receive ... (if you can see receive ....) so explain this better with methods and so on ... please
JANUARY 15, 3:00 PM GMT / 10:00 AM ET