Re: Fabric creates multiple DB connections
On furthur investigation it seems the serverGroupsExpiration setting was set to 1 second. So it was constantly refreshing the ServerGroup objects. Hence the serverConnections map ended up having multiple entries for same key as the key is based on object reference.
The question is, when refreshState method is called, why the existing connections is not cleared from the serverConnections map. Is this a bug or am i using the api incorrectly?
Subject
Views
Written By
Posted
3415
August 30, 2016 12:20PM
1045
August 30, 2016 12:33PM
Re: Fabric creates multiple DB connections
1078
August 30, 2016 02:33PM
914
August 31, 2016 06:54AM
964
August 31, 2016 01:44PM
1079
September 01, 2016 01:48AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.