LiveCycle – Running an Additional JBoss 4.2 Instance on Same Server

In many customer situations, you might be required to run multiple, non-clustered JBoss instances on the same server. For example, TEST and DEV instances, or LiveCycle ES and BAM (Business Activity Monitor) instances.

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\jboss-web.deployer\server.xml (Tomcat)
Change HTTP Connector port from 8080 to 8090
Change redirectPort from 8443 to 8453
Change SSLConnector from 8443 to 8453
Change AJP Connector from 8009 to 8010

%JBOSS_HOME%\server\all\conf\jboss-service.xml
Change org.jboss.web.WebService port from 8083 to 8084
Change org.jboss.naming.NamingService Port from 1099 to 1200
Change org.jboss.naming.NamingService RmiPort from 1098 to 1201
Change org.jboss.invocation.jrmp.server.JRMPInvoker RMIObjectPort from 4444 to 4544
Change org.jboss.invocation.pooled.server.PooledInvoker ServerBindPort from 4445 to 4545
Change invoker serverBindPort from 4446 to 4546

%JBOSS_HOME%\server\all\conf\jacorb.properties
Change ORBInitRef.NameService=corbaloc::localhost:3528/JBoss/Naming/root from 3528 to 3529
Change OAPort from 3528 to 3529
Change OASSLPort from 3529 to 3530

%JBOSS_HOME%\server\all\deploy-hasingleton\jms\uil2-service.xml
Change org.jboss.mq.il.uil2.UILServerILService ServerBindPort from 8093 to 8094

%JBOSS_HOME%\server\all\deploy\ejb3.deployer\META-INF\jboss-service.xml
Change org.jboss.remoting.transport.Connector InvokerLocator port from 3873 to to 3973

%JBOSS_HOME%\server\all\deploy\snmp-adaptor.sar\META-INF\jboss-service.xml
Change org.jboss.jmx.adaptor.snmp.trapd.TrapdService Port from 1162 to 1164
Change org.jboss.jmx.adaptor.snmp.agent.SnmpAgentService Port from 1161 to 1163

%JBOSS_HOME%\bin\run.bat
Add a line to add a new property:
set JAVA_OPTS=%JAVA_OPTS% -Djboss.partition.name=partitionLCDev

%JBOSS_HOME%\server\all\deploy\cluster-service.xml (JBoss Cluster)
Add attribute ip_mcast=”false”
Change num_initial_members from 3 to 1
Change org.jboss.ha.jndi.HANamingService port from 1100 to 1203
Change org.jboss.ha.jndi.HANamingService RmiPort from 1101 to 1204
Change AutoDiscoveryGroup port from 1102 to 1205
Change org.jboss.invocation.jrmp.server.JRMPInvokerHA RMIObjectPort from 4447 to 4547
Change org.jboss.invocation.pooled.server.PooledInvokerHA ServerBindPort from 4448 to 4548

%JBOSS_HOME%\server\all\deploy\ejb3-clustered-sfsbcache-service.xml (JBoss Stateful Sessions Beans [EJB] Cache)
Add attribute ip_mcast=”false”
Change num_initial_members from 3 to 1

%JBOSS_HOME%\server\all\deploy\ejb3-entity-cache-service.xml (JBoss Entity Beans [EJB] Cache)
Add attribute ip_mcast=”false”
Change num_initial_members from 3 to 1

%JBOSS_HOME%\server\all\deploy\jboss-web-cluster.sar\META-INF\jboss-services.xml (Tomcat Cluster)
Add attribute ip_mcast=”false”
Change num_initial_members from 3 to 1

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 10.0/10 (2 votes cast)
LiveCycle - Running an Additional JBoss 4.2 Instance on Same Server, 10.0 out of 10 based on 2 ratings
This entry was posted in Adobe LiveCycle ES, General Interest and tagged . Bookmark the permalink.

Comments are closed.