Closed glassfishrobot closed 14 years ago
@glassfishrobot Commented km said: I agree with the motivation, but these defaults can be overridden, just so you know.
@glassfishrobot Commented takedat said: Yes, the defaults can be customized, but almost users do not. This is a proposal for preventing failure.
@glassfishrobot Commented tmueller said: Hopefully this can be addressed as we put in the new config for clustering.
@glassfishrobot Commented jc129909 said: Changed default ports in default-config to begin with 2 instead of 3.
@glassfishrobot Commented tmueller said: Marking as referenced by the clustering admin one-pager.
@glassfishrobot Commented Was assigned to jc129909
@glassfishrobot Commented This issue was imported from java.net JIRA GLASSFISH-11794
@glassfishrobot Commented Reported by takedat
@glassfishrobot Commented Marked as fixed on Thursday, May 20th 2010, 3:48:38 pm
In v2.1 cluster profile, server instances sometime fail to startup. Because ports used by instances conflict with internal services in other instances(like admin channel) or other applications that using ephemeral ports.
It seems that the conflicts are caused of default port numbers defined in ephemeral port range on Solaris and Linux. The defaults should be changed to out of range of ephemeral port. I think below are suitable.
HTTP_LISTENER_PORT 28080 HTTP_SSL_LISTENER_PORT 28181 IIOP_LISTENER_PORT 23700 IIOP_SSL_LISTENER_PORT 23820 IIOP_SSL_MUTUALAUTH_PORT 23920 JMX_SYSTEM_CONNECTOR_PORT 28686 JMS_PROVIDER_PORT 27676
Ephemeral port range: Windows 1024-5000 Windows Vista 49152-65535 Solaris 32768-65535 Linux kernel 2.2 1024-4999 Linux kernel 2.4 32768-61000 -->Current default may conflict in Solaris and Linux kernel 2.4.
Environment
Operating System: All Platform: All
Affected Versions
[v2.1]