Modifying Properties for Named Configurations and Instances

The properties in a named configuration define port numbers for unclustered instances that reference the configuration or clustered instances that inherit the configuration. An instance initially obtains port numbers from the configuration that the instance references or inherits. To avoid port conflicts, edit the properties of named configurations and instances.

The following topics are addressed here:

Properties for Port Numbers in a Named Configuration
To Modify a Named Configuration's Properties
To Modify Port Numbers of an Instance

Properties for Port Numbers in a Named Configuration

The default configuration default-config contains properties that define the initial values of port numbers in a configuration that is copied from default-config. When an instance or a cluster that references the configuration is created, these properties are set for the instance.

You can create additional system properties for a configuration either by specifying the --systemproperties option of the copy-config(1) subcommand or by using the create-system-properties(1) subcommand. To reference a system property from the configuration, use the ${prop-name} notation, where prop-name is the name of the system property.

For example, if a configuration defines additional HTTP listeners, use system properties to define the ports for those listeners. However, these properties are not set automatically when an instance or a cluster that references the configuration is created. You must set these properties explicitly when you create the instance or cluster.

The properties in a named configuration that define port numbers are as follows:

ASADMIN_LISTENER_PORT: This property specifies the port number of the HTTP port or HTTPS port through which the DAS connects to the instance to manage the instance. Valid values are 1–65535. On UNIX, creating sockets that listen on ports 1–1024 requires superuser privileges.
HTTP_LISTENER_PORT: This property specifies the port number of the port that is used to listen for HTTP requests. Valid values are 1–65535. On UNIX, creating sockets that listen on ports 1–1024 requires superuser privileges.
HTTP_SSL_LISTENER_PORT: This property specifies the port number of the port that is used to listen for HTTPS requests. Valid values are 1–65535. On UNIX, creating sockets that listen on ports 1–1024 requires superuser privileges.
IIOP_LISTENER_PORT: This property specifies the port number of the port that is used for IIOP connections. Valid values are 1–65535. On UNIX, creating sockets that listen on ports 1–1024 requires superuser privileges.
IIOP_SSL_LISTENER_PORT: This property specifies the port number of the port that is used for secure IIOP connections. Valid values are 1–65535. On UNIX, creating sockets that listen on ports 1–1024 requires superuser privileges.
IIOP_SSL_MUTUALAUTH_PORT: This property specifies the port number of the port that is used for secure IIOP connections with client authentication. Valid values are 1–65535. On UNIX, creating sockets that listen on ports 1–1024 requires superuser privileges.
JAVA_DEBUGGER_PORT: This property specifies the port number of the port that is used for connections to the Java Platform Debugger Architecture (JPDA) debugger. Valid values are 1–65535. On UNIX, creating sockets that listen on ports 1–1024 requires superuser privileges.
JMS_PROVIDER_PORT: This property specifies the port number for the Java Message Service provider. Valid values are 1–65535. On UNIX, creating sockets that listen on ports 1–1024 requires superuser privileges.
JMX_SYSTEM_CONNECTOR_PORT: This property specifies the port number on which the JMX connector listens. Valid values are 1–65535. On UNIX, creating sockets that listen on ports 1–1024 requires superuser privileges.
OSGI_SHELL_TELNET_PORT: This property specifies the port number of the port that is used for connections to the Apache Felix Remote Shell. This shell uses the Felix shell service to interact with the OSGi module management subsystem. Valid values are 1–65535. On UNIX, creating sockets that listen on ports 1–1024 requires superuser privileges.

To Modify a Named Configuration’s Properties

Use the get subcommand and the set subcommand in remote mode to modify a named configuration’s properties.

You might copy a configuration for use by instances that reside on the same host as instances that refer to the original configuration. In this situation, edit the properties of one of the configurations to ensure that instances that will refer to the configuration have the correct initial settings.

If you change the port number in a configuration, the port number is changed for any instance that references or inherits the configuration.

Ensure that the DAS is running.
Remote subcommands require a running server.
For each property that you are modifying, determine the current value and set the new value.
1. Determine the current value of the property.
```
asadmin> get configs.config.config-name.system-property.property-name.value
```
  config-name
  
  The name of the configuration whose properties you are modifying.
  
  property-name
  
  The name of the property that you are modifying. For a list of available properties, see Properties for Port Numbers in a Named Configuration.
2. Set the property to its new value.
```
asadmin> set 
configs.config.config-name.system-property.property-name.value=new-value
```
  config-name
  
  The name of the configuration whose properties you are modifying.
  
  property-name
  
  The name of the property that you are modifying. For a list of available properties, see Properties for Port Numbers in a Named Configuration.
  
  new-value
  
  The value to which you are setting the property.

Example 6-5 Modifying a Property of a Named Configuration

This example changes the value of the JMS_PROVIDER_PORT property in the clusterpresets-config configuration from 27676 to 27678.

asadmin> get 
configs.config.clusterpresets-config.system-property.JMS_PROVIDER_PORT.value
configs.config.clusterpresets-config.system-property.JMS_PROVIDER_PORT.value=27676
Command get executed successfully.
asadmin> set 
configs.config.clusterpresets-config.system-property.JMS_PROVIDER_PORT.value=27678
configs.config.clusterpresets-config.system-property.JMS_PROVIDER_PORT.value=27678
Command set executed successfully.

To Modify Port Numbers of an Instance

Use the get subcommand and the set subcommand in remote mode to modify the port numbers of an instance.

The port numbers of a instance are initially set in the configuration that the instance references or inherits from its parent cluster. Multiple instances that reside on the same host must each listen on a unique port number. Therefore, if multiple instances that reference or inherit the same configuration reside on the same host, a port conflict prevents all except one of the instances from starting. To avoid port conflicts, modify the port numbers on which individual instances listen.

If you modify an instance’s port number and later modify the port number in the instance's configuration, the instance’s port number remains unchanged.

The port numbers of an instance are stored as Java system properties. When GlassFish Server is started, it treats these properties in the same way as properties that are passed through the -D option of the Java application launcher.

Ensure that the DAS is running.
Remote subcommands require a running server.
For each port number that you are modifying, determine the current value and set the new value.
1. Determine the current value of the port number.
```
asadmin> get 
servers.server.instance-name.system-property.port-property.value
```
  instance-name
  
  The name of the instance whose port numbers you are modifying.
  
  port-property
  
  The name of the property that corresponds to the port number that you are modifying. For a list of available properties, see Properties for Port Numbers in a Named Configuration.
2. Set the port number to its new value.
```
asadmin> get 
servers.server.instance-name.system-property.port-property.value=new-value
```
  instance-name
  
  The name of the instance whose port numbers you are modifying.
  
  port-property
  
  The name of the property that corresponds to the port number that you are modifying. For a list of available properties, see Properties for Port Numbers in a Named Configuration.
  
  new-value
  
  The value to which you are setting the port number.

Example 6-6 Modifying a Port Number for an Instance

This example changes the port number of the HTTP port or the HTTPS port for administration of the pmdsainst instance from 24849 to 24859.

asadmin> get 
servers.server.pmdsainst.system-property.ASADMIN_LISTENER_PORT.value
servers.server.pmdsainst.system-property.ASADMIN_LISTENER_PORT.value=24849
Command get executed successfully.
asadmin> set 
servers.server.pmdsainst.system-property.ASADMIN_LISTENER_PORT.value=24859
servers.server.pmdsainst.system-property.ASADMIN_LISTENER_PORT.value=24859
Command set executed successfully.

Skip Navigation Links
Exit Print View
	Oracle GlassFish Server 3.1-3.1.1 High Availability Administration Guide