| Summary | When server port range is set the client hangs. |
|---|---|
| Article Number | 18325 |
| Environment | All Supported Operating Systems Orbix 6.3.4 |
| Question/Problem Description | When server port range is set the client hangs. When using policies:iiop:server_address_mode_policy:port_range the client cannot communicate with the server. There's a firewall problem when policies:iiop:server_address_mode_policy:port_range is used. |
| Clarifying Information | |
| Error Message | |
| Defect/Enhancement Number | |
| Cause | For the server port range to work, Orbix needs to possibly try different ports and rely on 'port is busy' indication from the OS to know to try the next one. However, if a port is lingering in a busy status, for example, when a process crashes without closing the listener it is associated with, then this causes a conflict. |
| Resolution | Set the plugins:iiop:ip:reuse_addr flag to "false". That is, place the following line: plugins:iiop:ip:reuse_addr flag = "false"; in the outermost scope of the configuration file. What the plugins:iiop:ip:reuse_addr flag does, if set to true (default), is to essentially disable detection of busy ports. When set to "true" Orbix is saying to the OS to just create a socket without checking if the port is busy. By setting the plugins:iiop:ip:reuse_addr flag to "false" if a port is deemed busy by the OS it will not be allocated for Orbix use and the above problem should not occur. |
| Workaround | |
| Notes | |
| Attachment |
| Created date: | 06 September 2011 |
|---|---|
| Last Modified: | 13 February 2013 |
| Last Published: | 23 June 2012 |
| First Published date: | 09 September 2011 |
#Orbix
#KnowledgeDocs
