[jboss-jira] [JBoss JIRA] Resolved: (JBAS-6118) EJB3 InvokerLocator server socket binds only to 127.0.0.1 when the hostname is listed in /etc/host as 127.0.0.1

Carlo de Wolf (JIRA) jira-events at lists.jboss.org
Tue May 5 02:29:46 EDT 2009


     [ https://jira.jboss.org/jira/browse/JBAS-6118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carlo de Wolf resolved JBAS-6118.
---------------------------------

    Resolution: Duplicate Issue


> EJB3 InvokerLocator server socket binds only to 127.0.0.1 when the hostname is listed in /etc/host as 127.0.0.1
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-6118
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6118
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.2.GA
>         Environment: RedHat Linux 
> 2.6.9-42.ELsmp Kernel
>            Reporter: Alejandro Isacovich
>            Assignee: Carlo de Wolf
>
> If the host name is listed in an entry of the /etc/hosts file as 127.0.0.1. For example as follows (where vm9-srv01 is the hostname):
> 127.0.0.1       localhost.localdomain localhost  vm9-srv01
> Then the EJB3 InvokerLocator server socket binds only to 127.0.0.0 regardless of what the jboss.bind.address is.
> That means clients from other machines will not be able to make EJB3 calls to the server.
> This issue was also discussed here for JBoss 4.2.1.GA: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098486#4098486

-- 
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

        



More information about the jboss-jira mailing list