Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 367774

Summary:	Transition from Winstone to Jetty
Product:	Community	Reporter:	Eclipse Webmaster <webmaster>
Component:	CI-Jenkins	Assignee:	Eclipse Webmaster <webmaster>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	glyn.normington, kim.moir, matthias.sohn, mheitz, mrrussell, nicolas.bros, pwebster, sbouchet
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:
Bug Depends on:
Bug Blocks:	367238

Description Eclipse Webmaster

2012-01-03 11:11:22 EST

It seems that active development of Winstone stopped some time ago.  Since Jetty can do even more I'm going to investigate switching.  Based on my brief conversation with Jesse I'm going to hold off for 7.6.0 since I know they're working to fix a couple of HTTPs issues.

I'll start the deployment on the sandbox and if that goes well we can push it out to the main instance.

-M.

Comment 1 Bouchet Stéphane

2012-01-04 09:38:03 EST

+1 

IMO Winstone is used by Husdon only for local needs, no for real production environment..

Comment 2 Matt Heitz

2012-01-04 09:39:31 EST

+1

My team has been using Jetty.  I asked for opinions and got feedback like "lightweight and snappy", "works well", etc.

Comment 3 Matthias Sohn

2012-01-04 17:18:48 EST

+1 we have good experience running Hudson and Jenkins on Jetty

Comment 4 Glyn Normington

2012-01-05 03:27:12 EST

This sounds like a reasonable change, but one beauty of a stable/defunct project is that it does not encourage regular "upgrades" which can result in regressions etc. Therefore, I would suggest picking a tried and trusted level of Jetty and sticking with it as long as possible rather than upgrading regularly as Jetty evolves. Perhaps that's what was intended anyway?

Comment 5 Eclipse Webmaster

2012-01-05 10:33:04 EST

Well I'm looking at Jetty because it's becoming clear that Winstone just can't handle this.  

We don't tend to rush any updates aside from security patches(if it isn't broke don't fix it).

-M.

Comment 6 Eclipse Webmaster

2012-02-06 15:41:22 EST

I'm having some difficulties getting Jetty 7.6 and Hudson to play together nicely.  I've touched base with the Jetty folks to see if they have any insight into what's happening.

-M.

Comment 7 Eclipse Webmaster

2012-02-13 11:23:24 EST

Thanks to the advice of both the Jetty and Hudson teams I've managed to get the sandbox up and running on Jetty.  I'll leave it cook for a little while, and maybe after the 17th(SR2) we can look at deploying this to the main instance.

-M.

Comment 8 Denis Roy

2012-02-16 15:14:16 EST

(In reply to comment #7)
> sandbox up and running on Jetty.  I'll leave it cook for a little while, and

I'll write a script that will pummel it with http get and head requests.  We can then see if it handles http load better than Winstone.

Comment 9 Eclipse Webmaster

2012-02-28 14:44:59 EST

Ok, I've archived and 'redeployed' the sandbox Jetty instance and things went much better.  I've copied the Jetty config to the main Hudson instance and I"m just finishing making sure everything is ok.  At 4pm I plan to shutdown our current Hudson instance and bring up the jetty instance.

-M.

Comment 10 Eclipse Webmaster

2012-02-28 16:17:46 EST

Ok, we're now Jetty powered(TM?).  We may need to do some tuning with the IO threads and so on, but lets see how things go.

-M.