Looking further into the problem I found the jboss-service.xml in the conf directory, which has the following bit of code:
<mbean code="org.jboss.services.binding.ServiceBindingManager" name="jboss.system:service=ServiceBindingManager"> <attribute name="ServerName">ports-01</attribute> <attribute name="StoreURL">../docs/examples/binding-manager/sample-bindings.xml</attribute> <attribute name="StoreFactoryClassName"> org.jboss.services.binding.XMLServicesStoreFactory </attribute> </mbean>
looking at the sample-bindings.xml i found this:
<!-- jbossweb-tomcat50.sar --> <service-config name="jboss.web:service=WebServer" delegateClass="org.jboss.services.binding.XSLTFileDelegate" > <delegate-config> <xslt-config configName="ConfigFile"><![CDATA[ <xsl:stylesheet xmlns:xsl='http://www.w3.org/1999/XSL/Transform' version='1.0'> <xsl:output method="xml" /> <xsl:param name="port"/> <xsl:variable name="portAJP" select="$port - 71"/> <xsl:variable name="portHttps" select="$port + 363"/>
Particularly, the last two lines caught my attention as it would seem at first glace it's taking some random port ? and substracting a set number from it and adding a set number to it, to get some random configuration. I'll have to test if I see this number pattern in the port assingments i'm seeing.
Could this be part of the problem?
Unless you have enabled the binding manager service the configuration file that you have found will not be used so is not related to your problem.
The extract that you have found does not assign random ports, it is used to make sure that different instances have different known ports.
Okay. Then I guess that's not it.
I'm basically running the standard default config that comes with the 3.2.6 package, with modifications done to the following files:
The only changes in those files have been to the port numbers from the default ones.