Apache Tomcat 9. Preview. Mark Thomas, August Pivotal Software, Inc. All rights reserved.

Transcription

1

2 2 Apache Tomcat 9 Preview Mark Thomas, August 2015

3 Introduction Apache Tomcat committer since December 2003 Tomcat 8 release manager Member of the Servlet, WebSocket and EL expert groups Consultant Software Pivotal Currently focused on Apache Tomcat 9 3

4 Agenda Specification mandated new features Tomcat specific new features Tomcat features removed Internal changes 4

5 Tomcat versions Tomcat JavaEE Minimum Java SE Servlet JSP EL WebSocket JASPIC 1 st Stable Release EOL 5.x N/A N/A N/A x N/A N/A x N/A TBD 8.x N/A TBD 9.x ? 3.1? 2.0? 1.1? Q4 2016? TBD 5

6 Specification changes 6

7 Specifications JavaEE 8 Key elements HTML 5.0 HTTP/2 Simplification Better integration for managed beans Better infrastructure for the cloud 7

8 Specifications Servlet 4.0 Work started, stalled and is now starting again HTTP/2 HTTP/2 close to SPDY v4 Tomcat had an initial SPDY v2 implementation Browsers no longer support SPDY v2 so it has been removed Tomcat 9.0.x has HTTP/2 support h2 and h2c 8

9 Specifications Servlet 4.0 HTTP/2 progress Work in progress: not yet considered stable h2c available with all connectors h2 requires APR/native due to ALPN requirements Haven t tested h2 with NIO/NIO2 and OpenSSL engine (see later) Basic HTTP requests work Async support not yet implemented Non-blocking I/O support not yet implemented Server push has not been implemented yet 9

10 Specifications Servlet 4.0 HTTP/2 on Java 8 JSSE APIs don t, and won t, support ALPN ALPN is two-way so SNI trick (see later) won t work Java 9 should support ALPN TBD if ALPN API is sufficient 10

11 Specifications WebSocket 2.0 Work has not started Assuming 2.0 Could be 1.2 Standardize extension support Compression Multiplexing 11

12 Specifications EL 3.1 Work has not started Nothing obvious to do here Java 8 lambda alignment? Most issues opened against UEL are implementation bugs Expect minor changes and clarifications 12

13 Specifications JSP 2.4 There is no JSP expert group Just an other maintenance release Issues to resolve with EL 3.0 and JSPs Imports (definition and resolution) 13

14 Specifications JASPIC 1.1 Java Authentication Service Provider Interface for Containers Not much demand There are benefits (e.g. drop-in support for OAuth) Unsuccessful GSoC 2015 project to implement I intend to complete the JASPIC work for Tomcat 9 14

15 Specifications Other Tomcat 9 isn t going to implement the web profile Lack of demand TomEE JACC Java Authorization Contract for Containers Zero demand Might be useful On the have a look if there is time list 15

16 Tomcat New Features 16

17 Tomcat 9 New Features Major overhaul of TLS support Tomcat 8 supports one TLS virtual host per connector one certificate per virtual host Tomcat 9 supports multiple virtual hosts per connector (SNI) multiple certificates per virtual host TLS configuration has changed to support this 17

18 Tomcat 9 New Features SNI and multiple certificates supported by all connectors APR/native support via the OpenSSL API JSSE support via parsing the initial handshake ALPN support for APR/native JSSE support is currently TBD Common (where possible) configuration for all connectors Some JSSE / OpenSSL differences remain OpenSSL engine option for NIO and NIO2 18

19 Tomcat 9 New Features Other possibilities HTTP upgrade support for AJP Needs help with the C code Suggestions welcome Suggestions with patches are even better ;) 19

20 Tomcat 9 New Features With OpenSSL engine support for NIO and NIO2 why bother with the APR/native connector? NIO and NIO2 are very similar in performance NIO is more stable NIO2 API is (arguably) better suited to WebSocket and HTTP2 Do we need both NIO and NIO2? Is a single connector implementation viable? Maybe 20

21 Removed Features 21

22 Removed Features BIO HTTP and BIO AJP connectors Both WebSocket and Servlet 3.1 require non-blocking IO BIO connectors currently pretend to be non-blocking Creates complexity No scalability benefits Opportunity for things to break Therefore decided to remove them 22

23 Removed Features BIO HTTP and BIO AJP connectors NIO implementation remains the default HTTP and AJP NIO2 introduced in Tomcat 8 APR/native still available Requires native library 23

24 Removed Features Comet Proprietary interface for asynchronous I/O Users are moving (have moved) to WebSocket Adds complexity to all the connectors Therefore decided to remove it 24

25 Internal Changes 25

26 Internal Changes Connectors HTTP 2.0 support adds complexity Connectors were already complex Connector code was fragile in some areas Cleaned up the code up before starting on HTTP

27 Internal Changes Connectors Removed BIO Comet Implementation specific per connector code Move to Endpoint Implementation specific per connection code Move to SocketWrapper 27

28 Internal Changes Connectors Used to have connector specific HTTP, AJP and upgrade implementations Reduce duplication HTTP upgrade reduced to 3 classes from 12 Removed ~400 loc (of ~120,000) HTTP 1.1 removed ~50% / 2500 loc AJP 1.3 removed ~30% / 400 loc No connector specific HTTP/2 code 28

29 Internal Changes WebSocket Refactored I/O implementation Direct to Tomcat s I/O layer Not via Servlet 3.1 non-blocking API Simpler Faster Extension support likely to require further refactoring 29

30 Internal Changes Other Remove use of system properties for configuration Move to per Context / Host / Server / Connector May keep the system property for one version as a default Made RFC 6265 CookieProcessor the default Note UTF-8 extension 30

31 Get Involved 31

32 Get Involved Ask questions Report bugs Provide patches GitHub pull request 32

33 Get Involved Development (9.0.x) Update the wiki You don t need to be an expert Documentation needs patches too 33

34 Questions 34

35