[jbosstools-issues] [JBoss JIRA] (JBIDE-13140) remote start of as7.0.1 fails because it is bound to localnost and so web poller does not work

[Rob Stryker (JIRA)]

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

Rob Stryker resolved JBIDE-13140.
---------------------------------

           Labels: affects_documentation  (was: )
    Fix Version/s: 4.0.0.CR1
                       (was: 4.1.x)
       Resolution: Won't Fix


Unfortunately we cannot fix this on a tools level. However the user can fix this by modifying the remote standalone.xml. 

http://stackoverflow.com/questions/6853409/binding-jboss-as7-to-all-interfaces

This should be documented. Support for out-of-the-box as7.0.x on a remote system is limited to this use case. 
                
> remote start of as7.0.1 fails because it is bound to localnost and so web poller does not work
> ----------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-13140
>                 URL: https://issues.jboss.org/browse/JBIDE-13140
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: JBossAS/Servers
>    Affects Versions: 4.0.0.CR1
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>              Labels: affects_documentation
>             Fix For: 4.0.0.CR1
>
>
> JBIDE-13045 fixed the problem that -b was used for remote AS 7.0.1 which doesn't support it. But now the problem is that without -b the server is always deployed to localhost. So the web poller cannot work obviously. So unless you expose management port and use JBoss 7 management start poller you cannot really start the server properly - it starts but doesn't recognize the startup and when timeout is reached it shows an error.
> Now how do we solve this? Is it even worth solving? ;) We could say that the workaround is to always use the as7 management (if that works for 7.0.1 at all).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira