Which configuration files need to be modified when two JBoss instances are running on the same machine? Information Source: http://gocom.primeton.com/module
... Cle. php? StoryID = 398.Which configuration files need to be modified when two JBoss instances are running on the same machine?
Note: It is also applicable to running two JBoss instances on one server. [Applicability]
Eos5.0 and later versions for JBoss [Problem description and positioning]
If one machine runs two EOS for JBoss instances and both use the same port, when another instance is started, an exception is reported. [Solution and steps]
You can modify the port configurations of JBoss and Eos to solve the port occupation problem. 1. Modify ports 1098,1099, 4444,4445, 8083 in the jboss-3.2.5 \ Server \ Default \ conf \ jboss-service.xml. The port configuration is located in the configuration file as follows:
...
<Mbean code = "org. JBoss. Web. WebService" name = "JBoss: service = WebService">
<Attribute name = "Port"> 8083 </attribute>
...
<Mbean code = "org. JBoss. Naming. namingservice" name = "JBoss: service = naming">
...
<Attribute name = "Port"> 1099 </attribute>
...
<Attribute name = "rmiport"> 1098 </attribute>
...
<Mbean code = "org. JBoss. Invocation. jrmp. server. jrmpinvoker" name = "JBoss: service = invoker, type = jrmp">
<Attributes name = "rmiobjectport"> 4444 </attribute>
...
<Mbean code = "org. JBoss. Invocation. Pooled. server. pooledinvoker" name = "JBoss: service = invoker, type = pooled">
...
<Attribute name = "serverbindport"> 4445 </attribute>
... 2, jboss-3.2.5 \ Server \ Default \ conf \ port 1099 in the jboss-minimal.xml, be sure to change to the same as the 1099 in the jboss-service.xml. The port configuration is located in the configuration file as follows:
...
<Mbean code = "org. JBoss. Naming. namingservice" name = "JBoss: service = naming">
...
<Attribute name = "Port"> 1099 </attribute>
</Mbean>
... 3. jboss-3.2.5 \ Server \ Default \ deploy \ jbossweb-tomcat50.sar \ Server. xml port 80, 80 81. The port configuration is located in the configuration file as follows:
...
<Service name = "JBoss. Web" classname = "org. JBoss. Web. tomcat. tc5.standardservice">
<! -- A HTTP/1.1 Connector on port 8080 -->
<Connector Port = "8080" address = "$ {JBoss. BIND. address} "maxthreads =" 150 "minsparethreads =" 25 "maxsparethreads =" 75 "combined =" false "redirectport =" 8443 "acceptcount =" 100 "connectiontimeout =" 20000 "disableuploadtimeout = ""True" uriencoding = "GBK"/>
...
<Connector uriencoding = "GBK" enablelookups = "true" keystorefile = "keystore" Port = "8081" redirectport = "8443" Scheme = "HTTPS" secure = "true" sslprotocol =" TLS "/>
... 3. Port 8093 in the jboss-3.2.5 \ Server \ Default \ deploy \ JMS \ uil2-service.xml. The port configuration is located in the configuration file as follows:
...
<Attribute name = "serverbindport"> 8093 </attribute>
... 4. Port 1099,30614 in eosserver \ config \ eosconfig. xml. Note that port 1099 must be the same as port 1099 in the jboss-service.xml. The port configuration is located in the configuration file as follows:
...
<Group name = "dbconnect">
<Configvalue key = "dbtype"> sqlserver2000 </configvalue>
<Configvalue key = "context-Initial-factory"> org. jnp. Interfaces. namingcontextfactory </configvalue>
<Configvalue key = "dbprovider"> jnp: // localhost: 1099 </configvalue>
...
<Module name = "cluster">
<Group name = "Config">
<Configvalue key = "nodelist"> 127.0.0.1 </configvalue>
<Configvalue key = "remotecallerport"> 30614 </configvalue>
</Group>
</Module>
... [Remarks]
1. When performing JBoss load balancing on the same machine, you cannot refer to this document when modifying the configuration file.
2. When the JBoss port 1099 is changed, the port 1099 configured in eosconfig. xml also needs to be changed.
3. If you configure the data source for the component package through the "component package information configuration" on the EOS Console (eosmgr), make sure that port 1099 is modified accordingly. |
