In many customer situations, you might be required to run multiple JBoss instances on the same server. For example, LiveCycle Workflow on JBoss 3.2.5 and BAM (Business Activity Monitor) on JBoss 3.2.6
To avoid port conflicts, you will have to change the ports for one of the JBosss instances. Here is a list of what you'd have to do if you are using the "all" configuration:
Please note : some of these recommended ports might conflict in your particular environment. In such cases, you might have to experiment until you get one that does not conflict. The JBoss server.log will tell you if there are any port conflicts. In Windows, you can use TCPView from Microsoft to inventory currently used ports. On Linux, you can use the netstat -an command.
%JBOSS_HOME%\server\all\deploy\jbossweb-tomcat50.sar\server.xml
Change HTTP/1.1 Connector port from 8080 to 8888
Change AJP 1.3 Connector port from 8009 to 8099
Change SSL/TLS Connector port from 8443 to 8493
%JBOSS_HOME%\server\all\conf\jboss-service.xml
Change WebService port from 8083 to 8899
Change NamingService Port from 1099 to 9999
Change RMIport from 1098 to 9998
Change RMIObjectPort from 4444 to 9444
Change PooledInvoker ServerBindPort from 4445 to 9445
%JBOSS_HOME%\server\all\deploy\cluster-service.xml
Change ha.jndi.HANamingService port from 1100 to 1190 and correspondingly in...
%JBOSS_HOME%\server\all\deploy\jms\hajndi-jms-ds.xml
Change java.naming.provider.url from 1100 to 1190
%JBOSS_HOME%\server\all\conf\jacorb.properties
Change OAPort from 3528 to 9528
Change OASSLPort from 3529 to 9529
%JBOSS_HOME%\server\all\deploy-hasingleton\jms\oilservice.xml
Change ServerBindPort from 8090 to 8099
%JBOSS_HOME%\server\all\deploy-hasingleton\jms\oil2-service.xml
Change serverBindPoa from from 8092 to 8199
%JBOSS_HOME%\server\all\deploy-hasingleton\jms\uil2-service.xml
Change ServerBindPort from 8093 to 8993. For the "default" configuration (BAM), the uil2service.xml is in /default/deploy/jms/
%JBOSS_HOME%\server\all\deploy\snmp-adaptor.sar\META-INF\jboss-service.xml
Change from port 1162 to 1182 and correspondingly in...
%JBOSS_HOME%\server\all\deploy\snmp-adaptor.sar\managers.xml
Change from port 1162 to 1182
For JBoss 4.0.3, this article might help.
Hi
This no longer works in LC7.2. We think it may be a hard-coded reference to port 1099 somewhere in Form Manager.
Another tip is to change all port numbers by adding a 1 in front of them - this way, it's easy to remember the old vs new port numbers.
Howard
I have the same feeling, at least in the LCM port 1099 seems to be hardcoded. When LCM tries to initialize the db, it calls the bootstrapper servlet with this URL http://[host]:[port]/LCMBootstrapper/bootstrap?bootstrapper=UM. Without specifing the naming sercice URL. That's why the BootstrapServlet uses the default URL for JBoss: jnp://localhost:1099.
If you use for example port 1199 instead of 1099 the call should be http://[host]:[port]/LCMBootstrapper/bootstrap?bootstrapper=UM&providerURL=jnp://localhost:1099. For this reason you can specify the URL in the config.properties file, but this setting is ignored.
Mike
PS: See also thread in Adobe forums: http://www.adobeforums.com/cgi-bin/webx?14@@.3bc2076c/0