]
Richard Achmatowicz commented on JGRP-1799:
-------------------------------------------
The memory settings in the testsuite are set to: -Xms600M -Xmx800M
Two points to note:
- in the case of testLargeReturnValue, shouldn't an exception be returned if the value
cannot be transported back to the caller, as opposed to null?
- in the case of testLargeReturnValueUnicastCall, could this be the result of longer than
usual processing in de-fragmentation or bundling (due to slower machine) which causes the
timeout on the send?
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
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: