Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.0
-
None
-
None
-
W2K java version 1.4.2_05
Description
I have confirmed that while a temporary destination is propgated between broker instances across NetworkChannels, it is happening to late to work for request/reply (RPC) operations.
To test two brokers are required to be interconnected. Attach to broker1 a "replier" process and on broker2 a "requestor" process.
The replier process need only send back a reply message on the "replyTo" destination contained in the received message.
The requestor process performs the following steps:
1) create temporary topic
2) create producer topic TOOL.DEFAULT
3) create consumer topic from step 1
4) producer send msg
5) consumer receive msg
Broker1 log show that the registration of the consumer for the temporary topic arrives after the message is received from the producer. The result is an exception condition that the destination is no longer valid because the client no longer exists.
Given the order of execution, I suspect one of the follow problems:
a) registration of a consumer is happening at the time the first receive() is executed and not when the consumer is created.
b) network propogation of consumers is done in background thread.