1 Reply Latest reply on Apr 23, 2005 2:25 PM by Ben Wang

    Picking up the wrong server when getting an InitialContext

    Greg Paul Newbie

      Our environment currently consists of 3 servers. 2 are clustered under the Partition named MyPartitiation. The 3rd server is not clustered and is run as default. A client attempts to get an InitialContext provided by the 3rd server. If it is not there, for some reason it is connecting to the first 2 servers that are clustered. The client code has no knowlege of these other servers, and yet is seems to be finding them. Does anyone have any idea why this is so? Just a note, the client code is not doing new InitialContext(), it is actually specifing the details for server 3.

      Any thoughts would be appreciated.