23 Jun, 2009

1 commit


19 Jun, 2009

2 commits


16 Jun, 2009

2 commits


13 Jun, 2009

2 commits


12 Jun, 2009

1 commit


11 Jun, 2009

1 commit


10 Jun, 2009

1 commit


05 Jun, 2009

1 commit


15 May, 2009

1 commit


14 May, 2009

1 commit


12 May, 2009

4 commits


07 May, 2009

2 commits


06 May, 2009

1 commit


05 May, 2009

1 commit


04 May, 2009

5 commits


01 May, 2009

1 commit


30 Apr, 2009

1 commit


29 Apr, 2009

2 commits


28 Apr, 2009

1 commit


25 Apr, 2009

1 commit


24 Apr, 2009

2 commits


23 Apr, 2009

2 commits


22 Apr, 2009

2 commits

  • git-svn-id: https://svn.forgerock.org/opendj/trunk@5266 41b1ffd8-f28e-4786-ab96-9950f0a78031
    sin
     
  • When cn=monitor is searched, the replication therefore asks informations
    about the replication state to all Replication Servers. This should always be
    fast unless a server is hanged. In such case the replication waits for
    5 seconds then issue an error message and goes on with the
    information it has received at this time.
    
    In some cases however it looks like that some server do not send back the
    responses fast enough thus provoking errors in the logs.
    I was not able to produce this problem but discovered some inefficiency in the
    replication monitoring code that can lead to query several time the other servers
    and therefore maybe producing the problem.
    
    This change therefore improve the monitoring code so that we only wait once if
    a server is very slow to answer.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5260 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     

17 Apr, 2009

1 commit


16 Apr, 2009

1 commit