Tuxedo ISL Server Can Not Boot If Secure Port (-S option) Is The Same As Nonsecure Listener Port (-n option) (Doc ID 1330293.1)

Last updated on NOVEMBER 04, 2016

Applies to:

Oracle Tuxedo - Version: 10.3.0 and later   [Release: and later ]
Information in this document applies to any platform.

Symptoms

ISL process ALWAYS uses a Listener Port ("-n" option within CLOPT string). By default this Listener Port is not secured.

When configuring ISL parameters with a secure port ("-S" option within CLOPT string) equal to the non-secure port :

ISL SRVID=125 CLOPT="-A -o /home/appdir/log/stdout -e /home/appdir/log/stderr -- -a -z 40 -Z 56 -S 41200 -n //machineA:41200 -m 1 -M 10 -x 5 -T 30 -C warn"

ISL CAN NOT be started up and reports in ULOG file the following error messages :


165018.machineA!ISL.20185260.1.0: 06-14-2011: Tuxedo Version 10.3.0.0, 32-bit
165018.machineA!ISL.20185260.1.0: LIBTUX_CAT:262: INFO: Standard main starting
165018.machineA!ISL.20185260.1.0: ISNAT_CAT:1424: INFO: host = "machineA", port = 41200
165018.machineA!ISL.20185260.1.0: ISNAT_CAT:1542: INFO: SSL port = 41200
165018.machineA!ISL.20185260.1.0: ISNAT_CAT:1658: ERROR: Could not establish listening address on network //machineA:41200
165018.machineA!ISL.20185260.1.0: LIBTUX_CAT:250: ERROR: tpsvrinit() failed





Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms