Icegrid and Client/Server Communication Routing/Availability
We have a service that is loaded into IceGrid and started by IceGridNode on a machine with activation set to always. Sometimes, the service is unable to service requests due to reliance on a external resource but has state which needs to be held and deliver once the external resource is avaiable so our developers wrote something like the following:
Ice::PropertiesPtr properties = communicator()->getProperties();
properties = communicator->getProperties();
adapter = communicator()->createObjectAdapter(iceAdapter);
id = communicator()->stringToIdentity(properties->getProperty("Identity"));
They also claimed that it worked in Ice 3.2 but it fails to work in Ice 3.5.
1) Would upgrading to Ice 3.7 help?
2) Is the claim valid?
3) Is there a way to route a service request to a specific server from the client? I don't see this in the documentation.
4) Is there a way to tell Icegrid that a service is temporarily unavailable and not route new requests to a server instance? I see something about holding requests from the server in the docs but nothing about temporarily making the server instance unavailable.
Let me know if you have any questions or comments.