Bug 284433 - Port configuration problem running web components on Mac
Summary: Port configuration problem running web components on Mac
Status: RESOLVED WORKSFORME
Alias: None
Product: e4
Classification: Eclipse Project
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Simon Kaegi CLA
QA Contact: Boris Bokowski CLA
URL:
Whiteboard: stalebug
Keywords: readme
Depends on:
Blocks:
 
Reported: 2009-07-23 10:56 EDT by John Arthorne CLA
Modified: 2019-06-05 07:43 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Arthorne CLA 2009-07-23 10:56:16 EDT
The Web component editor (site manifest editor), doesn't work out of the box on Mac. It appears to be a port selection problem where Jetty is not getting configured to use an acceptable port.

The workaround is to add "-Dorg.eclipse.equinox.http.jetty.http.port=8080" to the end of the eclipse.ini file.
Comment 1 Boris Bokowski CLA 2009-07-27 15:13:27 EDT
Simon, it looks like a Jetty instance is being started on port 80 (which fails on the Mac) even though I request a separate instance. Apparently, only if the default instance can be started will the other one start too. Any idea why?
Comment 2 Simon Kaegi CLA 2009-07-27 15:28:26 EDT
Can you point me at the code where we start the Jetty bundle. If the bundle is explicitly started "persistently" it will try to register an Http Service on the default port, it should instead be started "transitively". Not sure if that's it but a good place to start.
Comment 3 Boris Bokowski CLA 2009-07-27 18:41:20 EDT
org.eclipse.e4.pde.internal.webui.Activator

in org.eclipse.e4.pde.webui
Comment 4 Simon Kaegi CLA 2009-07-28 00:04:21 EDT
Thanks Boris but looks fine. I'll take this and dig deeper.
Comment 5 Eclipse Genie CLA 2019-01-21 19:27:05 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 6 Lars Vogel CLA 2019-06-05 07:43:02 EDT
This is a mass change to close all e4 bugs marked with "stalebug" whiteboard.

If this bug is still valid, please reopen and remove the "stalebug" keyword.