We have our production JBoss servers behind a firewall so we knew we had to open up 1099 and 4444. What we didn't realize is there is a third port spun off that the client connects back to that appeared to be random. This created a big problem for us because we couldn't just open up a big range of ports on our firewall to accommodate this behavior. After some digging we found we could statically define that port by adding the following attribute name tag to the jboss.jcml file.
<mbean code="org.jboss.naming.NamingService" name="DefaultDomain:service=Naming">
My question is whether this will limit the number of concurrent client requests JBoss can handle. We are occasionally seeing 'connection refused' exceptions.
Does this solution change the requirement for Port 4444 in conf/*/standardjboss.xml?