This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 62797 - Server port should be detected
Summary: Server port should be detected
Status: VERIFIED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: JBoss (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: Pavel Buzek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-22 17:09 UTC by zikmund
Modified: 2005-09-14 09:16 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description zikmund 2005-08-22 17:09:29 UTC 
Build 200508181800

1) Change JBoss port to port 8089:
edit file $JBOSS_INSTALLDIR\server\default\deploy\jbossweb-tomcat55.sar\server.xml
element's attribute <Connector port="8080"

2) Add JBoss in IDE (Add Server)
3) ERROR:
port 8080 is default. It should be detected from server.xml as it is in other
servers.

Note: Current solution confuses users because they expect that their typed port
in IDE will be used for JBoss start (as it is for Tomcat). Although the typed
port is currently used ony for IDE server detection.
Comment 1 Pavel Buzek 2005-08-24 05:44:17 UTC 
not sure this qualifies as a P2, but would be nice to fix for 4.2
Comment 2 zikmund 2005-08-24 09:51:22 UTC 
Since it confuses users a lot, it is IMHO P2 - other solution could be add a
explanation text or warning under port edit box. Then I could agree with
downgrading to P3.
Comment 3 Alexander Kouznetsov 2005-08-29 16:02:04 UTC 
In Buzz, plugin correctly works with server 8089 while 8080 is set in the Add
Server Wizard. It correctly starts/stops server and determines its status. But
it uses entered port number when constructing URL for Run Project action.
Therefore, the wrong page is shown. Is the same behavior experienced in 4.2?
Comment 4 Anna Bolotova 2005-08-30 15:15:29 UTC 
Described behavior don't reproduce on 4.1 version.
Comment 5 zikmund 2005-09-08 17:08:50 UTC 
In 5.0 starting JBoss with wrong port entered in Add Server dialog starts JBoss,
but its status stays as 'stopped'. Therefore each web application run tries to
start new server instance :(.
Comment 6 Pavel Buzek 2005-09-08 18:02:09 UTC 
I am working on it in trunk, you can then merge the fix.
Comment 7 Anna Bolotova 2005-09-09 10:03:04 UTC 
I fixed this problem in 4.1 version
Comment 8 zikmund 2005-09-09 11:09:43 UTC 
To abolotova: If it is fixed in release41, it should be marked as Fixed, added
fix_41only Status Whiteboard and Version/TM should be set to 4.1. Commit log
should be attached as well.
Comment 11 zikmund 2005-09-14 09:16:15 UTC 
Verified in 200509131800 build.