Peer reconnection with multiple peers

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Client connects to two peers
2. One peer becomes unavailable

What is the expected output? What do you see instead?
Jdiameter should try to reopen connection to disconnected peer. This is not 
done until all peer becomes unavailable.

What version of the product are you using? On what operating system?
Jdiameter rev:de9b5c011ad8 Aug 25, 2014
Ubuntu 14.04 LTS

Please provide any additional information below.

Jdiameter client network configuration

    <Network>
        <Peers>
             <Peer name="aaa://peer-1:3868" rating="1"/>
             <Peer name="aaa://peer-2:3868" rating="1"/>
        </Peers>
        <Realms>
            <Realm name ="ims.indoona.net" peers="peer-1,peer-2" local_action="LOCAL" dynamic="true" exp_time="1">
                <ApplicationID>
                     <VendorId value="10415"/>
                     <AuthApplId value="4"/>
                     <AcctApplId value="0"/>
                </ApplicationID>
            </Realm>
        </Realms>
    </Network>

Original issue reported on code.google.com by flavioba...@gmail.com on 17 Sep 2014 at 9:17

[GoogleCodeExporter]

Just curious: what caused disconnection? Peer restart or network failure?

Do not know if related but I have a problem with client peer reconnection after 
server peer restart.

Just asked about this in: 
https://code.google.com/p/mobicents/issues/detail?id=2628

Original comment by kulas...@gmail.com on 15 Oct 2014 at 2:32

[GoogleCodeExporter]

Hi, this failure occurs on peer restart, so when Disconnect-Cause AVP is set to 
REBOOT. The bad thing is that it doesn't always happen.

Original comment by flavioba...@gmail.com on 15 Oct 2014 at 3:24

[GoogleCodeExporter]

Hi, so we have the same scenario. I have even only one remote peer defined on 
my Diameter Stack. After it (remote peer) restart Stack remains running but 
does not try to reconnect to remote peer. As pointed out in link attached above 
issue can probably be fixed by changing PeerFSMImpl. In fact it was already 
done on server side but my suspicion is that the same patch should be applied 
on client side but would be good to have confirmation from someone who knows 
jDiameter better first. Or maybe you already tried it?

Original comment by kulas...@gmail.com on 17 Oct 2014 at 6:49

[GoogleCodeExporter]

I'll do more tests next days. This scenario occurs sometimes, and only on 
graceful restarts. Currently, as we have a stable environment this does not 
happens anymore. But if it can be fixed is better for everyone. 

Bye

Original comment by flavioba...@gmail.com on 17 Oct 2014 at 7:22