How would a TIBCO iProcess Engine process allocate a port number greater than 65535?
Article ID: KB0093331
Updated On:
| Products | Versions |
|---|---|
| TIBCO iProcess Engine (Oracle) | - |
| TIBCO iProcess Engine (DB2) | - |
| Not Applicable | - |
Description
Resolution:
A TCP Port number has a restriction of 16 bits. Hence, the physical range of a TCP port can be 0-65535. If a port number greater than 65535 is assigned, which is greater than 16 bits, the port would be truncated from the left such that a resultant 16-bit port can be used.
Example: If an SPO Server has been configured with a TCP port number such as 185130 :
The binary format of 185130 is 101101001100101010.
Truncating from the left to form 16 bits - 1101001100101010.
Decimal format of the truncated binary is - 54058.
54058 would be the physical port number being used on the OS.
This truncation is not performed by the TIBCO iProcess Engine. This has been tested on Red Hat Linux / Solaris / AIX. TIBCO recommends assigning a valid physical port, rather than relying on the truncation.
Issue/Introduction
How would a TIBCO iProcess Engine process allocate a port number greater than 65535?
Additional Information
http://en.wikipedia.org/wiki/Transmission_Control_Protocol
http://ravatheodor.blogspot.com/2013/07/tcp-ports-greater-than-65535.html
http://www.unix.com/aix/110931-tcp-port-70000-aix-6-1-surely-higher-than-allowed-maximum.html
Feedback
Yes
No
Powered by
