]
Bela Ban commented on JGRP-1799:
--------------------------------
Most likely the box on which the timeout occurs is loaded. No, the response value is not
an exception, but null because we haven't received a response. Timeout exceptions are
only thrown on unicast invocations.
RpcDispatcher test fails when working with large values
-------------------------------------------------------
Key: JGRP-1799
URL:
https://issues.jboss.org/browse/JGRP-1799
Project: JGroups
Issue Type: Bug
Affects Versions: 3.2.13
Environment: RHEL, Win, Solaris
Reporter: Richard Achmatowicz
Assignee: Bela Ban
Fix For: 3.2.13, 3.5
The two tests:
* testLargeReturnValue
* testLargeReturnValueUnicastCall
make RPC calls with values which are increasingly large.
The values used are in this range:
{noformat}
SIZES={10000, 20000, 40000, 80000, 100000, 200000, 400000, 800000,1000000, 2000000,
5000000}
{noformat}
The tests have been see to fail with the values 1000000, 2000000 and 5000000, always with
the same error in each case.
In the case of testLargeReturnValue, the test fails because one of the returned values
from the RPC is null.
In the case of testLargeReturnValueUnicastCall, the test fails due to a timeout while
sending the RPC.
--
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: