]
Isaac Rooskov updated JBIDE-12650:
----------------------------------
Release Notes Docs Status: Documented as Feature Request
Writer: irooskov
Release Notes Text: A new feature has been added that enhances the server port
configuration for JBoss Enterprise Application Platform 6 and JBoss Application Server
7.1. This enhancement accounts for a configured port-offset and displays this information
to a user through the server configuration display.
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, new_and_noteworthy
Fix For: 4.0.0.CR1
Attachments: JBIDE-12650.png
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.
steps to reproduce:
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.
--
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: