This is an issue of webseal junction not able to come up when there is a restart of backend server.
Usually, where there is a restart of backend server., Junction server state changes to not running when the backend server is down. When the backend is available, the junction still remains down., we need to create the junction again to make it up. This issue can be resolved by enabling dynamic-addresses = {yes|no}to yes in the webseald.conf. The default value is no.
Syntax: dynamic-addresses = {yes|no}
Description
Indicates when the junction server host name is resolved to its corresponding IP address and used in communication with the junction server.
You can customize this configuration item for a particular junction by adding the adjusted configuration item to a [junction:{junction_name}] stanza.
where {junction_name} refers to the junction point for a standard junction (including the leading / character) or the virtual host label for a virtual host junction.
Options
yes
The junction server host name is resolved to its corresponding IP address immediately before any communication with the junction server.
no
The junction server host name is resolved to its corresponding IP address and this address is used for subsequent communication with the junction server.
Usage
This stanza entry is required.
Default value
no
Example
dynamic-addresses = no
Usually, where there is a restart of backend server., Junction server state changes to not running when the backend server is down. When the backend is available, the junction still remains down., we need to create the junction again to make it up. This issue can be resolved by enabling dynamic-addresses = {yes|no}to yes in the webseald.conf. The default value is no.
Syntax: dynamic-addresses = {yes|no}
Description
Indicates when the junction server host name is resolved to its corresponding IP address and used in communication with the junction server.
You can customize this configuration item for a particular junction by adding the adjusted configuration item to a [junction:{junction_name}] stanza.
where {junction_name} refers to the junction point for a standard junction (including the leading / character) or the virtual host label for a virtual host junction.
Options
yes
The junction server host name is resolved to its corresponding IP address immediately before any communication with the junction server.
no
The junction server host name is resolved to its corresponding IP address and this address is used for subsequent communication with the junction server.
Usage
This stanza entry is required.
Default value
no
Example
dynamic-addresses = no
