Kbase P76105: Can not add more than 10 webspeed or appserver servers when minSrvrIntance is changed to 20
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
24/03/2009 |
|
Status: Verified
SYMPTOM(s):
Can not add more than 10 webspeed or appserver servers when minSrvrIntance is changed to 20
The ubroker.properties file is not changed when changes are made through progress explorer
Verify from progress explorer that changes are made
changed minSrvInstance from 10 to 20 for webspeed or appserver broker
The broker is down when the change on the broker is made
The timestamp of ubroker.properties file remains the same even after the change made by progress explorer
After the change is made, opening ubroker.properties file to validate the change, the changes is not there
Exceptions exist in ads0.exp which are corresponding to the time the changes are attempted
java.rmi.ConnectException
Trouble accessing remote property in PVS: maxSrvrInstance
Connection refused to host: xx.xx.xxx.xxx; nested exception is:
java.net.ConnectException: Connection refused
Firewall between progress explorer and admin server
FACT(s) (Environment):
WebSpeed 3.x
Progress 9.x
CAUSE:
AdminServer and Progress explorer are never intended to use going through firewalls.
When the user clicks on the save button, the flow of data is as the following when the problem occurred:
1. Progress explorer calls a "remote object" on the server in the form of its stub to save the changes made -- a random port is opened for this connection by the RMI Server. But within this (remote) method call, to limit the message size, Progress explorer only sends to the server the properties that are changed, but not the changed values.
2. The admin server receives the request, does some validations on the properties, then ask for the changed values from the client -- a remote method call on another "remote object" on the client in the form of its stub. And for this connection, another random port is opened, and the traffic direction is now from server to progress explorer. That is what causes exception.
3. If the last step is successful, the server will receive the changed values. In the code we actually ask for each property changed values in a separate remote call. That means while the port in step 1 is open (because the method is not finished yet), several other ports might have been opened to get the values. Once the values are received, then server validates them, then writes them to the properties file. Then the control is returned to the caller (which is Progress Explorer), the port from step 1 is released.
FIX:
Open two way traffic in the firewall between admin server and progress explorer.