Ticket #584 (closed Task: fixed)

Opened 7 years ago

Last modified 7 years ago

Update Felix HTTP Jetty

Reported by: jri Owned by: jri
Priority: Major Milestone: Release 4.2
Component: DeepaMehta Standard Distribution Version: 4.1.3
Keywords: Cc: dgf, Malte, JuergeN
Complexity: 2 Area: Runtime Environment
Module:

Description

Since Jan 2011 Apache did no update to the Felix HTTP Jetty component. Until recently the latest version was 2.2.0. This is what we use in DM, including in the current DM 4.1.3 stable. This means DM runs with an old Jetty 6.1.2 web server since several years. Jetty 6 e.g. does not support web sockets. The Jetty 6 line is not maintained anymore since 2010.

Recently, new movement has appeared in Felix HTTP Jetty. In Sep 2013 Apache released version 2.2.1 (bundling Jetty 7.6.12), and in Dec 2013 version 2.2.2 followed (bundling Jetty 7.6.13). That means DM can now have a Jetty 7. Version 7.6.13 is almost the latest in the Jetty 7 line. Jetty 7 supports WebSocket? (RFC 6455) -- the basis for server push.

So, besides switching to Pax Web (#448) we might have an additional option now when it comes to server push in DM.

So far the experience with Pax Web is very bad (see comments in #448). Various ugly workarounds were necessary to bring DM up and running at all.

Just a side note: the bad Pax Web feeling is further nourished by a 3-fold binary footprint (920K for Felix HTTP Jetty 2.2.0 vs. 2.7MB for Pax Web). In contrast updating to Felix HTTP Jetty 2.2.2 means 920K -> 1.3MB.

Besides updating the DM main line to Felix HTTP Jetty 2.2.2 the objective of this ticket is the investigation weather we can utilize web sockets with Felix HTTP Jetty as well (and are not necessarily forced to Pax Web).

Change History

comment:1 Changed 7 years ago by jri

  • Status changed from new to accepted

comment:2 Changed 7 years ago by Jörg Richter

Update Felix Jetty HTTP 2.2.0 -> 2.2.2 (#584).

This updates DM's Jetty 6.1.2 -> 7.6.13

Applies to both: DM Standard Distribution and DM Karaf Distribution.

See #584.

comment:3 Changed 7 years ago by jri

  • Status changed from accepted to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.