Arto Huusko commented on JBTM-253:
These days practically every single software that listens on a network port can be
configured fully as to where it listens on. It simply is a good thing to give
administrators the freedom to configure their systems. JBoss is no exception to this rule,
and as far as I know the listen address of every service except JBossTS in JBoss can be
configured -- and by default the listen address is configured to jboss.listen.address
I don't feel there is much need to discuss why administrators want configuration
options, and why it is bad for local services to listen on global addresses (as a data
point on this, some SMTP servers configured for local mail relay by default don't
listen on *any* network addresses, but use for example unix domain sockets).
More interesting discussion would be why this configuration option would not be needed or
why it would be bad.
Listen address of JBossTS ports not configurable
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Transaction Core
Affects Versions: 4.2.3.SP3
Environment: JBoss AS 4.2.0 GA
Reporter: Arto Huusko
Assigned To: Mark Little
JBossTS integrated in JBoss AS 4.2.0 GA always binds some tcp ports to listen on all
addresses. jboss.bind.address has no effect on the listen address, nor is it otherwise
Looking at source code (for example
jbossts-jta-4.2.3.SP3-src.zip) confirms that there is no kind of support for binding the
listen address, only the port can be freely selected.
The listen address should be configurable, so that it can be limited to localhost, for
In addition, if possible, it would be nice to be able to disable listening on any ports.
I'm not sure if the TransactionStatusManager really needs to listen on any port in a
simple JBoss AS installation.
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see: http://www.atlassian.com/software/jira