Bug 157651 - JBoss 4.0 not recognizing server is started when using non-standard ports
Summary: JBoss 4.0 not recognizing server is started when using non-standard ports
Status: NEW
Alias: None
Product: WTP ServerTools
Classification: WebTools
Component: jst.server (show other bugs)
Version: 1.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Naci Dai CLA
QA Contact: Tim deBoer CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-18 12:21 EDT by Calvin Robol CLA
Modified: 2006-09-23 11:26 EDT (History)
0 users

See Also:

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 Calvin Robol CLA 2006-09-18 12:21:37 EDT 
My Configuration:

eclipse 3.2 - callisto release
JBoss 4.0.2

In my JBoss configuration for the tomcat.sar in server.xml, I had defined the http port to 8081.  This normally defaults to 8080.  After I had made this change I created a new JBoss server in the webtools console.  The wizard asked me for a port, however it appears this is being ignored, or overridden by the server.xml config in <jboss_home>/server/default/deploy/jbossweb-tomcat55.sar.
This was causing the server console to not recognize the server was started, and after a few minutes, eclipse shut down the JBoss server.

When I switched the port back to 8080 in the server.xml,  everything ran fine, and the server startup was recognized.  My problem is I have other services on my pc that need port 8080, so not being able to change this is a burden.