[jbosstools-issues] [JBoss JIRA] (JBIDE-12650) Detecting server ports from local runtime does not account for configured port-offset
Max Rydahl Andersen (JIRA)
jira-events at lists.jboss.org
Wed Nov 7 08:38:18 EST 2012
[ https://issues.jboss.org/browse/JBIDE-12650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Max Rydahl Andersen updated JBIDE-12650:
----------------------------------------
Issue Type: Feature Request (was: Bug)
Steps to Reproduce: (was: With pristine jboss-as-7.1.1.Final, in standalone.xml, element 'socket-binding-group' attribute 'port-offset': change ${jboss.socket.binding.port-offset:0} to ${jboss.socket.binding.port-offset:400}. Start server.
Server will log successful start ("JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 1676ms"), but ide tools will not detect server as started, message "Starting jboss-as-7.1.1.Final" stays until timeout is reached.)
> Detecting server ports from local runtime does not account for configured port-offset
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-12650
> URL: https://issues.jboss.org/browse/JBIDE-12650
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: JBossAS/Servers
> Environment: eclipse juno, jboss-as-7.1.1.Final, JBossAS Tools 2.3.1.v20120715-0243-H142-Final
> Reporter: Ozan Ayyüce
> Assignee: Rob Stryker
> Priority: Minor
> Labels: f2f2012
>
> When socket-binding in standalone.xml is configured with a port-offset other than 0, the server ports are not detected correctly in the server configuration view.
> The server startup is not detected correctly and times out.
> Opening the server in the web browser uses the wrong port.
--
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
More information about the jbosstools-issues
mailing list