This discussion is archived
1 Reply Latest reply: Oct 22, 2011 6:13 AM by RenévanWijk RSS

Peer unreachable for 240 seconds

895768 Newbie
Currently Being Moderated
I have a simple J2EE server client application. Its deployed on

weblogic server. Whenever my client is receiving large chunk of data

from server i get error saying "Peer is unreachable for 240 seconds".

I tried configuring heartbeat timeout (IdlePeriodsUntilTimeout) to 10

seconds (default value was 4). And my understanding was even if i

receive error it would say "Peer is unreachable for 600 seconds" (as

in both cases heartbeat PeriodLength is 60). But i still keep getting

error that peer is unreachable for 240 seconds.
I tried to find information about server tuning for this issue. But I

could not find anything else.
Any help or hint would be appreciated.
Thanks.
  • 1. Re: Peer unreachable for 240 seconds
    RenévanWijk Oracle ACE
    Currently Being Moderated
    Some information on the 240 seconds can be found here: http://download.oracle.com/docs/cd/E12840_01/wls/docs103/rmi/rmi_t3.html

    Could be your network is not able to carry large chunks of data. You can check the packet size by using the ping utility, for example,
    ping -c 3 -M do -s 1468 172.31.0.108
    
    PING 172.31.0.108 (172.31.0.108) 1468(1496) bytes of data.
    1476 bytes from 172.31.0.108: icmp_seq=1 ttl=64 time=0.019 ms
    1476 bytes from 172.31.0.108: icmp_seq=2 ttl=64 time=0.024 ms
    1476 bytes from 172.31.0.108: icmp_seq=3 ttl=64 time=0.024 ms
    
    --- 172.31.0.108 ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2000ms
    rtt min/avg/max/mdev = 0.019/0.022/0.024/0.004 ms
    The 1468 is the packet size for which a test is performed. If a message is shown that must be fragmented you know the packaet size is too large.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points