See JBTM-253. JBossTS opens a bunch of network ports (three, I think, but debug output only mentions two) it listens on, but JBossTS does not give me the option to specify at which address it listens for connections. As such, this is not a bug or error. However, standard practice in practically every single network listening software is to give the option for the administrator to specify at which address the software listens on. JBoss AS also gives this option, it even has a global system property jboss.bind.address, and every single service except JBossTS can be separately configured to listen on a particular address, and by default the services usually are configured to listen on ${jboss.bind.address}. I want to see JBossTS also support this. My ultimate reason for this is simply the fact that I hate to have services listening globally on ports they have no business or need listening on. Of course my servers are firewalled, so there's no problem of getting rogue connections, but even so, if I'm running a simple single JBoss AS instance, nothing will ever need to connect to JBossTS services from outside of the localhost, then I want to configure JBossTS so that it listens only on localhost. But really, for complex installations there may be even real reasons why this needs to be configured. The server could have multiple IP addresses, run several JBoss instances, and would need to configure JBossTS in each instance to listen on different IP. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063814#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...