The edit made to the G3.0 wiki is not correct at this time (GERONIMO-5987).
The etc/blueprint-activemq-placeholder.cfg is not used to change the PortOffset in current trunk nor in 3.0-M1. I just tested this morning's snapshot to verify it is still broken. David Jencks is working to replace Blueprint with Spring DS. After which hopefully this issue will be resolved, and the etc/blueprint-activemq-placeholder.cfg config file will be removed. That etc/blueprint-activemq-placeholder.cfg config file was a work-around to a blueprint issue, and the work-around is also broken. So currently it is not possible to change the ActiveMQ Port. And when it is fixed, we should be able to use the config-substitution file once again. You can refer to our previous conversation about this matter. See this thread: ActiveMQ config-substitution change G2.2 vs G3.0, http://markmail.org/message/bf6uta2o3fuesiki -RG
--- Begin Message ---
Changing the default port numbers
Page edited by Runhua Chi
Changes (1)
...
There are a number of reasons why you might want to use other port numbers than those provided by default. Most common startup problems are in fact associated with port conflicts. You can use monitoring utilities like Active Ports that will quickly tell you what application or process is using what port so you can customize Geronimo's ports accordingly. On Unix-like platforms, you can always use something like {{netstat -nao | grep -i list}} to get the ports in use along with what application is holding that port. Alternatively, you can use {{netstat -nab}} on a Windows platform.
Note that *ActiveMQPort* setting in the {{config-substitution.properties}} file does not work. If you want to change the port number for ActiveMQ server, update the value of *portOffset* in {{etc/blueprint-activemq-placeholder.cfg}} file.Full Content
Changing the default port numbers
The config-substitutions.properties file lets you specify a totally new set of ports and define an automatic port offset for when you run multiple servers (or instances of the same server). Other than that, you can define different variables and their substitution values in this file, which will be used when processing the corresponding config.xml. These substitution values can be overridden by environment variables and system properties by prefixing the property name with org.apache.geronimo.config.substitution.
For example, an entry such as hostName=localhost can be overridden by an environment variable or system property org.apache.geronimo.config.substitution.hostName=foo.
Although this section is focusing on changing these settings by updating a properties file, there is an alternative way by using the Geronimo administrative console which is explained in more detail under the Configuring the Web Container section. However, if you have port conflicts at start up time the Geronimo administrative console will not be available, so we have to focus on configuring the config-substitutions.properties file by choosing a new PortOffset value (the default is 0).
The following example shows the config-substitutions.properties file for the Tomcat distribution of Geronimo. The file provided with the Jetty distribution is nearly identical. Changes to the file should be made when the server is stopped.
config-substitutions.properties#Tue Dec 16 15:44:41 EST 2008 ORBPort=6882 AJPPort=8009 clusterNodeName=NODE MaxThreadPoolSize=500 ResourceBindingsNamePattern= Capacity=1000 SMTPHost=localhost StatelessPoolSize=10 StatelessTimeout=0 ResourceBindingsQuery=?\#org.apache.geronimo.naming.ResourceSource DerbyPort=1527 BMPPoolSize=10 COSNamingPort=1050 StatefulTimeout=20 webcontainer=TomcatWebContainer OpenEJBPort=4201 ORBSSLPort=2001 PortOffset=0 ORBHost=localhost JMXPort=9999 EndPointURI=http\://localhost\:8080 NamingPort=1099 DefaultWadiSweepInterval=36000 WebConnectorConTimeout=20000 BulkPassivate=100 MulticastDiscoveryPort=6142 HTTPSPort=8443 COSNamingHost=localhost MinThreadPoolSize=200 MulticastDiscoveryAddress=239.255.3.2 ReplicaCount=2 ServerHostname=0.0.0.0 ActiveMQPort=61616 ORBSSLHost=localhost SMTPPort=25 webcontainerName=tomcat6 ResourceBindingsNameInNamespace=jca\: StrictPooling=true JMXSecurePort=9998 DefaultWadiNumPartitions=24 AccessTimeout=30 HTTPPort=8080 clusterName=CLUSTER_NAME ClusterName=cluster1 ResourceBindingsFormat={groupId}/{artifactId}/{j2eeType}/{name} RemoteDeployHostname=localhost TmId=71,84,77,73,68There are a number of reasons why you might want to use other port numbers than those provided by default. Most common startup problems are in fact associated with port conflicts. You can use monitoring utilities like Active Ports that will quickly tell you what application or process is using what port so you can customize Geronimo's ports accordingly. On Unix-like platforms, you can always use something like netstat -nao | grep -i list to get the ports in use along with what application is holding that port. Alternatively, you can use netstat -nab on a Windows platform.
Note that ActiveMQPort setting in the config-substitution.properties file does not work. If you want to change the port number for ActiveMQ server, update the value of portOffset in etc/blueprint-activemq-placeholder.cfg file.
Change Notification PreferencesView Online | View Changes | Add Comment
--- End Message ---
