[jboss-jira] [JBoss JIRA] (JGRP-1799) RpcDispatcher test fails when working with large values

[Richard Achmatowicz (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12950460#comment-12950460 ] 

Richard Achmatowicz commented on JGRP-1799:
-------------------------------------------

One reason why the test is failing is that with ever larger values, the RPC call times out:

{noformat}
testing with 10000 bytes
test took: 23 ms
rsps:
10000 bytes from B
10000 bytes from A
10000 bytes from C

testing with 20000 bytes
test took: 30 ms
rsps:
20000 bytes from B
20000 bytes from A
20000 bytes from C

testing with 40000 bytes
test took: 31 ms
rsps:
40000 bytes from B
40000 bytes from A
40000 bytes from C

testing with 80000 bytes
test took: 33 ms
rsps:
80000 bytes from B
80000 bytes from A
80000 bytes from C

testing with 100000 bytes
test took: 804 ms
rsps:
100000 bytes from B
100000 bytes from A
100000 bytes from C

testing with 200000 bytes
test took: 1001 ms
rsps:
200000 bytes from B
200000 bytes from A
200000 bytes from C

testing with 400000 bytes
test took: 1001 ms
rsps:
400000 bytes from B
400000 bytes from A
400000 bytes from C

testing with 800000 bytes
test took: 1793 ms
rsps:
800000 bytes from B
800000 bytes from A
800000 bytes from C

testing with 1000000 bytes
test took: 67 ms
rsps:
1000000 bytes from B
1000000 bytes from A
1000000 bytes from C

testing with 2000000 bytes
test took: 1944 ms
rsps:
2000000 bytes from B
2000000 bytes from A
2000000 bytes from C

testing with 5000000 bytes
test took: 1247 ms
rsps:
5000000 bytes from B
5000000 bytes from A
5000000 bytes from C

testing with 10000000 bytes
test took: 7970 ms
rsps:
10000000 bytes from B
10000000 bytes from A
10000000 bytes from C

testing with 20000000 bytes
test took: 12262 ms
rsps:
20000000 bytes from B
20000000 bytes from A
20000000 bytes from C

testing with 50000000 bytes
test took: 20001 ms
rsps:
50000000 bytes from B
50000000 bytes from A
java.lang.AssertionError
	at org.jgroups.blocks.RpcDispatcherTest._testLargeValue(RpcDispatcherTest.java:548)
	at org.jgroups.blocks.RpcDispatcherTest.testLargeReturnValue(RpcDispatcherTest.java:443)
{noformat}

I can quite easily reproduce this on my machine. The RPC call times out partway through processing and leaves an incomplete result. When I extend the timeout from 20 seconds to 30 seconds, the test passes.

We can probably eliminate these errors by extending the timeout from 20 seconds to 30 seconds to take account of slow machines.
I have also added in count of how many ms each RPC call takes, which helps to see why it may have failed (i.e. tool too long).

Bela, is extending the timeout something you would consider? 
                
> 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: http://www.atlassian.com/software/jira