Kbase P145705: Can an AppServer Server process detect changes to the ubroker.properties file when the AppServer Ser
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/08/2010 |
|
Status: Verified
GOAL:
Can an AppServer Server process detect changes to the ubroker.properties file when the AppServer Server/Agent has been trimmed?
GOAL:
Can changes made to the ubroker.properties file be detected automatically by AppServer Server processes?
GOAL:
Can changes made to the ubroker.properties file be dynamically detected by AppServer or WebSpeed processes?
GOAL:
Will AppServer Server processes once trimmed detect new changes made to the ubroker.properties file?
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.x
Progress 9.x
FIX:
Prior to 10.2B, the ubroker.properties file is accessed once upon process initialization and is cached internally. Because the property file is never referenced again, any subsequent changes made to the ubroker.properties file are not recognized by the AppServer or WebSpeed Transaction Server processes. The AppServer or WebSpeed Transaction Server processes must be restarted in order to recognize any modified property values.
In 10.2B, there is the ability to have the AppServer and WebSpeed Transaction Server as well as other servers to recognize changes made to the ubroker.properties fie without being restarted. This is done by making use of the allowRuntimeUpdates property. The default value for this property is 0 which means Runtime property changes will not be allowed for this server. A value of 1 means that runtime property changes will be allowed for this server.