The JmsClientInterceptor is expecting multiple responses always when using a Topic (versus single response if multiple responses is not froced when using a Queue).
It should be enough to have the multiple responses as the default for a Topic, but one should be able to disable it. For example, in some cases it might be enough to get a response from a single service, even if more are listening to the topic.
Description
The JmsClientInterceptor is expecting multiple responses always when using a Topic (versus single response if multiple responses is not froced when using a Queue).
It should be enough to have the multiple responses as the default for a Topic, but one should be able to disable it. For example, in some cases it might be enough to get a response from a single service, even if more are listening to the topic.
Actually, seems that there is a way to get around this by setting minimumResults to 0 and maximumResults to 1 in the join strategy. The timeout issue, LINGO-33 still does make this unusable though.
Mikko Wilkman - 15/Aug/06 02:36 AM Actually, seems that there is a way to get around this by setting minimumResults to 0 and maximumResults to 1 in the join strategy. The timeout issue, LINGO-33 still does make this unusable though.
Bug
Resolved
Major
Using a Topic forces the JMS client to expect multiple responses
LINGO-33still does make this unusable though.