[tomcat] branch master updated: Update with the release of Graal 19.3

[re...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

remm pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomcat.git


The following commit(s) were added to refs/heads/master by this push:
     new ab95586  Update with the release of Graal 19.3
ab95586 is described below

commit ab955860e6e92dc272911a67feee5706add62098
Author: remm <re...@apache.org>
AuthorDate: Thu Nov 28 10:39:11 2019 +0100

    Update with the release of Graal 19.3
    
    Java 9+ support in native images will need updates because at the moment
    it sets the jre9Available flag to false. Of course since this is Graal
    the Java 9 support has a small footprint: "oh, there's no module support
    with native images".
---
 webapps/docs/graal.xml | 15 +++++----------
 1 file changed, 5 insertions(+), 10 deletions(-)

diff --git a/webapps/docs/graal.xml b/webapps/docs/graal.xml
index 852de70..cb73078 100644
--- a/webapps/docs/graal.xml
+++ b/webapps/docs/graal.xml
@@ -57,7 +57,7 @@
   <p>
     Download and install GraalVM. The first step is then to add the
     native-image tool.
-    <source>export JAVA_HOME=/absolute...path...to/graalvm-ce-x.y.z
+    <source>export JAVA_HOME=/absolute...path...to/graalvm-ce-javaX-x.y.z
 cd $JAVA_HOME/bin
 ./gu install native-image</source>
     Download the Tomcat Maven packaging from
@@ -103,7 +103,7 @@ ant -Dwebapp.name=somewebapp -f graal-webapp.ant.xml</source>
   <p>
     Run the GraalVM substrate VM using the trace agent:
     <source>$JAVA_HOME/bin/java\
-        -agentlib:native-image-agent=trace-output=$TOMCAT_MAVEN/target/trace-file.json\
+        -agentlib:native-image-agent=config-output-dir=$TOMCAT_MAVEN/target/\
         -Dcatalina.base=. -Djava.util.logging.config.file=conf/logging.properties\
         -jar target/tomcat-maven-1.0.jar</source>
   </p>
@@ -117,11 +117,7 @@ ant -Dwebapp.name=somewebapp -f graal-webapp.ant.xml</source>
   </p>
 
   <p>
-    Once that is done, the VM may be shut down. The descriptors can now be
-    generated from the trace file.
-    <source>$JAVA_HOME/bin/native-image-configure generate\
-        --trace-input=$TOMCAT_MAVEN/target/trace-file.json\
-        --output-dir=$TOMCAT_MAVEN/target</source>
+    The descriptors have now been generated in the agent output directory.
     At this point, further configuration must be made to add items that are
     not traced, including: base interfaces, resource bundles, BeanInfo based
     reflection, etc. Please refer to the Graal documentation for more
@@ -179,12 +175,11 @@ ant -Dwebapp.name=somewebapp -f graal-webapp.ant.xml</source>
   <p>
     Missing items for better Tomcat functionality:
     <ul>
-      <li>Java 11: ALPN for TLS, TLS 1.3, etc</li>
       <li>BeanInfo support: BeanInfo use in JSP taglibs must be configured
         manually in descriptors</li>
       <li>Java serialization: Clustering, session persistence</li>
-      <li>Static linking configuration: JSSE elliptic curve support,
-        tomcat-native support when creating an image with static linking</li>
+      <li>Static linking configuration: tomcat-native support when creating
+        an image with static linking</li>
       <li>JMX: Tomcat monitoring and management</li>
     </ul>
   </p>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org

Re: [tomcat] branch master updated: Update with the release of Graal 19.3

[Rémy Maucherat <re...@apache.org>]

On Thu, Nov 28, 2019 at 10:39 AM <re...@apache.org> wrote:

>      Missing items for better Tomcat functionality:
>      <ul>
> -      <li>Java 11: ALPN for TLS, TLS 1.3, etc</li>
>        <li>BeanInfo support: BeanInfo use in JSP taglibs must be configured
>          manually in descriptors</li>
>        <li>Java serialization: Clustering, session persistence</li>
> -      <li>Static linking configuration: JSSE elliptic curve support,
> -        tomcat-native support when creating an image with static
> linking</li>
> +      <li>Static linking configuration: tomcat-native support when
> creating
> +        an image with static linking</li>
>        <li>JMX: Tomcat monitoring and management</li>
>      </ul>
>

As you can see here, this is a rather huge Graal update for Tomcat as JSSE
TLS is now functional and TLS is also usable in a container environment
thanks to static linking of the needed libraries.
I did some TLS Tomcat benchmarks with the "EE" version since it is rather
"feature complete" now and I am quite disappointed though. Better luck next
time I guess.

Rémy