[jbossts-issues] [JBoss JIRA] Closed: (JBTM-412) Socket process id binds to the wrong interface
[
https://jira.jboss.org/jira/browse/JBTM-412?page=com.atlassian.jira.plugi...
]
Michael Musgrove closed JBTM-412.
---------------------------------
Resolution: Done
The SocketProcessId port should be bound to the loopback address (and not the hostname
which fails if there is no network present).
Socket process id binds to the wrong interface
----------------------------------------------
Key: JBTM-412
URL: https://jira.jboss.org/jira/browse/JBTM-412
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Application Server Integration
Affects Versions: 4.4.CR1, 4.4.CR2, 4.4.0.GA, 4.5
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Fix For: 4.5
If working offline, i.e. no eth0/network, and jboss is started on localhost then the
server doesn't boot because SocketProcessId is binding to the wrong interface -
InetAddress getByName(null) should be used instead of InetAddress.getLocalHost()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira