Bug 419483 - Windows service: Installing as Windows service does always uses port 8080
Summary: Windows service: Installing as Windows service does always uses port 8080
Status: NEW
Alias: None
Product: Hudson
Classification: Technology
Component: Core (show other bugs)
Version: 3.1.0   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Winston Prakash CLA
QA Contact: Geoff Waymark CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-15 12:18 EDT by Latha Amujuri CLA
Modified: 2013-10-15 16:45 EDT (History)
2 users (show)

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 Latha Amujuri CLA 2013-10-15 12:18:31 EDT 
Launch Hudson using a custom port
java -jar <hudson.war> --httpPort=8081
Manage Hudson
Install as Windows Service
Accept all defaults and click Finish.
Click Yes to stop the server and start the service.
Reload Hudson console URL (http://localhost:8081).
Note that the server is not running.
Check Event Viewer on Windows and note the command line used to start the service is using 8080 instead of the port that was used to start the server (8081)

 java -Xrs -Xmx256m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "USER_HOME\.hudson\hudson.war" --httpPort=8080
Comment 1 Bob Foster CLA 2013-10-15 16:45:32 EDT 
Is this a bug or an expectation that not every user might have? Is it reasonable that the service is installed with the same port as Hudson is running with when it does the install, or should the port be explicitly configurable in the install?