[
https://issues.jboss.org/browse/JGRP-1617?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1617:
--------------------------------
Sanne, you didn't provide enough information on this case. The scenario you describe
has been tested a lot and should work. I've attached a use case that shows that a sync
RPC returns as soon as the 2 acks have been received, and itdoes *not* wait until the
timeout kicks in.
If you can, do provide me with a unit test (or some code) that fails, *then* I can take a
look...
Sync dispatcher castMessage does not awake blocked thread on ACK
----------------------------------------------------------------
Key: JGRP-1617
URL:
https://issues.jboss.org/browse/JGRP-1617
Project: JGroups
Issue Type: Bug
Affects Versions: 3.3
Reporter: Sanne Grinovero
Assignee: Bela Ban
Attachments: bla.java
On version 3.3.0.CR1 we observed that the following code:
{code}final RequestOptions options = RequestOptions.SYNC();
dispatcher.castMessage( null, message, options );
{code}
will always block until the timeout defined in _RequestOptions_, even if the remote
operation is very quick in responding.
We could workaround the issue by setting a custom _RspFilter_, but this filter is
otherwise not needed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira