[JBoss JIRA] (JBIDE-12650) Detecting server ports from local runtime does not account for configured port-offset
4:59 a.m.
Ozan Ayyüce created JBIDE-12650:
-----------------------------------
Summary: 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: Bug
Environment: eclipse juno, jboss-as-7.1.1.Final, jboss as tools
Reporter: Ozan Ayyüce
Priority: Minor
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 also.
--
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
5:05 a.m.
[
https://issues.jboss.org/browse/JBIDE-12650?page=com.atlassian.jira.plugi...
]
Ozan Ayyüce updated JBIDE-12650:
--------------------------------
Environment: eclipse juno, jboss-as-7.1.1.Final, JBossAS
Tools 2.3.1.v20120715-0243-H142-Final (was: eclipse juno, jboss-as-7.1.1.Final, jboss as
tools )
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: Bug
Environment: eclipse juno, jboss-as-7.1.1.Final, JBossAS
Tools 2.3.1.v20120715-0243-H142-Final
Reporter: Ozan Ayyüce
Priority: Minor
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 also.
--
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
9:04 a.m.
[
https://issues.jboss.org/browse/JBIDE-12650?page=com.atlassian.jira.plugi...
]
Ozan Ayyüce updated JBIDE-12650:
--------------------------------
Description:
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.
was:
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 also.
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: Bug
Environment: eclipse juno, jboss-as-7.1.1.Final, JBossAS
Tools 2.3.1.v20120715-0243-H142-Final
Reporter: Ozan Ayyüce
Priority: Minor
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
12:05 p.m.
[
https://issues.jboss.org/browse/JBIDE-12650?page=com.atlassian.jira.plugi...
]
Alexey Kazakov updated JBIDE-12650:
-----------------------------------
Assignee: Rob Stryker
Component/s: JBossAS/Servers
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: Bug
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
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
7:38 a.m.
[
https://issues.jboss.org/browse/JBIDE-12650?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-12650:
----------------------------------------
Fix Version/s: 4.1.0.Alpha1
Description:
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.
was:
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.
Labels: f2f2012 (was: )
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
Fix For: 4.1.0.Alpha1
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: http://www.atlassian.com/software/jira
7:38 a.m.
[
https://issues.jboss.org/browse/JBIDE-12650?page=com.atlassian.jira.plugi...
]
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
3:33 a.m.
[
https://issues.jboss.org/browse/JBIDE-12650?page=com.atlassian.jira.plugi...
]
Rob Stryker updated JBIDE-12650:
--------------------------------
Attachment: JBIDE-12650.png
The new feature looks as attached in the png file. I've also fixed some small issues
with changes to the underlying file not being shown immediately (bad caching).
You cannot see this in the screenshot, but if you uncheck the 'detect
automatically', and change the values, the text fields for the other ports
(management, web, etc) adjust themselves.
This feature is only available for as7.1 / eap6
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.1.0.Alpha1
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: http://www.atlassian.com/software/jira
3:33 a.m.
[
https://issues.jboss.org/browse/JBIDE-12650?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-12650.
---------------------------------
Labels: f2f2012 new_and_noteworthy (was: f2f2012)
Fix Version/s: 4.0.0.CR1
(was: 4.1.0.Alpha1)
Resolution: Done
This has been pushed to origin/master.
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: http://www.atlassian.com/software/jira
5:19 p.m.
[
https://issues.jboss.org/browse/JBIDE-12650?page=com.atlassian.jira.plugi...
]
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: http://www.atlassian.com/software/jira
7:50 a.m.
[
https://issues.jboss.org/browse/JBIDE-12650?page=com.atlassian.jira.plugi...
]
Martin Malina closed JBIDE-12650.
---------------------------------
Verified in JBDS 6.0.0.CR1 B111
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: http://www.atlassian.com/software/jira
4880
days inactive
4944
days old
jbosstools-issues@lists.jboss.org
9 comments
6 participants
participants (6)
-
Alexey Kazakov (JIRA) -
Isaac Rooskov (JIRA)
-
Martin Malina (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Ozan Ayyüce (JIRA)
-
Rob Stryker (JIRA)