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.
| Summary: | JBoss always run on port 8080,no matter of what set in wizard | ||
|---|---|---|---|
| Product: | serverplugins | Reporter: | Jaroslav Pospisil <jpospisil> |
| Component: | JBoss | Assignee: | issues@serverplugins <issues> |
| Status: | VERIFIED FIXED | ||
| Severity: | blocker | CC: | geertjan |
| Priority: | P2 | ||
| Version: | 5.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
| Bug Depends on: | 62657 | ||
| Bug Blocks: | |||
|
Description
Jaroslav Pospisil
2005-08-19 10:47:38 UTC
It blocks our automated tests. Please fix it ASAP. Thanks. In fact, it's not a bug. You have possibility to change port number just in case if it was determine wrong value you have chance to change it. At the beginning we decided that we cant change JBoss config files, so we cant change port number. What are the reasons for "if it is wrongly determined"? We can determine it in Tomcat, AppServer. Why is it in JBoss harder? because it third party product But then why is there possibility to change port in the wizard,if it do nothing? I just manually changed http port by editing "jboss-4.0.2\server\default\deploy\jbossweb-tomcat55.sar\server.xml" file and jboss normally started on my port 8089. Do we really couldn't do the same in Netbeans? 1) Tomcat is third party too
2) See $JBOSS_INSTALLDIR\server\default\deploy\jbossweb-tomcat55.sar\server.xml
<!-- A HTTP/1.1 Connector on port 8080 -->
<Connector port="8080" address="${jboss.bind.address}"
maxThreads="250" strategy="ms" maxHttpHeaderSize="8192"
emptySessionPath="true"
enableLookups="false" redirectPort="8443" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true"/>
we cant change it in config files, because of our decision but we can read it from config each time we run application For tests it is sufficient to fix at least issue 62657. We can workaround this issue then. I'd recommend only *detect* the port from server.xml and change port number in Add JBoss panel to readonly field. BTW - see how Tomcat works: 1) read port number from server.xml 2) get server.xml timestamp 3) every getPort() checks server.xml and if it has been changed, reparses server.xml Detecting correct server port and using the server port entered by the user (or detected) is described sufficiently in issue 62657. Server wizard is not the right place to change the server port. Support for changing server port in jboss config files is a new feature request (I am changing the issue to FEATURE). OK, then please fix issue 62657 for test purposes, thanks. Removing TEST keyword. "Server wizard is not the right place to change the server port." This is news to me. I think any user would assume that that's why the "Port" field is there -- so that you can SET the port. If you aren't meant to set the port there, then that field shouldn't be there or it should be readonly. "Server wizard is not the right place to change the server port." This is news to me. I think any user would assume that that's why the "Port" field is there -- so that you can SET the port. If you aren't meant to set the port there, then that field shouldn't be there or it should be readonly. I am having this same problem except the port is readonly for me. I have even changed the port manually for the server and the wizard will not even pick up the change correctly. Please see <a href="http://www.netbeans.org/issues/show_bug.cgi?id=64837">Issue 64837</a>. This is a really annoying problem because of <a href="http://www.netbeans.org/issues/show_bug.cgi?id=64833">Issue 64833</a>. Please fix this..It worked in the plugin for 4.1 why can't it work in 5.0. It would be better to file a new issue ... next time ;-) Please, provide NetBeans build, OS and JDK information. Thanks. Fixed in 5.5 by new UI. Verified |