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 07ebf68 Remove LogManager from the command line since it is useless
there
07ebf68 is described below
commit 07ebf688c038ce28cb37e1b78468dbc45d6e64d4
Author: remm <r...@apache.org>
AuthorDate: Tue Jul 16 09:29:22 2019 +0200
Remove LogManager from the command line since it is useless there
It seems the log manager has to be set during image compilation (it
would be
-J-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager),
unfortunately what the JULI log manager does seems to be a problem with
Graal and I haven't got it to work.
---
res/tomcat-maven/README.md | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/res/tomcat-maven/README.md b/res/tomcat-maven/README.md
index d2592cd..aed08d7 100644
--- a/res/tomcat-maven/README.md
+++ b/res/tomcat-maven/README.md
@@ -91,7 +91,8 @@ As Graal does not support dynamic class loading, all Servlets
and support classe
in `/WEB-INF/classes` and `/WEB-INF/lib`, must be included as part of the
tomcat-maven build process, so they are packaged into the
`target/tomcat-maven-1.0.jar`.
-Run Tomcat with the agent in full trace mode.
+Run Tomcat with the agent in full trace mode. The arguments are identical to
regular Tomcat with the addition of the trace agent which attempts to
+intercept all relevant reflection calls.
```
cd $TOMCAT_MAVEN
$JAVA_HOME/bin/java
-agentlib:native-image-agent=trace-output=$TOMCAT_MAVEN/target/trace-file.json
-Dcatalina.base=. -Djava.util.logging.config.file=conf/logging.properties
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -jar
target/tomcat-maven-1.0.jar
@@ -103,7 +104,7 @@ Generate the final json files using
native-image-configuration then use native i
```
$JAVA_HOME/bin/native-image-configure generate
--trace-input=$TOMCAT_MAVEN/target/trace-file.json
--output-dir=$TOMCAT_MAVEN/target
$JAVA_HOME/bin/native-image --no-server --allow-incomplete-classpath
--enable-https
--initialize-at-build-time=org.eclipse.jdt,org.apache.el.parser.SimpleNode,javax.servlet.jsp.JspFactory,org.apache.jasper.servlet.JasperInitializer,org.apache.jasper.runtime.JspFactoryImpl
-H:+JNI -H:+ReportUnsupportedElementsAtRuntime -H:+ReportExceptionStackTraces
-H:EnableURLProtocols=http,https,jar
-H:ConfigurationFileDirectories=$TOMCAT_MAVEN/target/
-H:ReflectionConfigurationFiles=$TOMCAT_MAVEN/tomc [...]
-./tomcat-maven-1.0 -Djava.library.path=$JAVA_HOME/jre/lib/amd64
-Dcatalina.base=. -Djava.util.logging.config.file=conf/logging.properties
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
+./tomcat-maven-1.0 -Djava.library.path=$JAVA_HOME/jre/lib/amd64
-Dcatalina.base=. -Djava.util.logging.config.file=conf/logging.properties
```
Running in a container is possible, an example `DockerfileGraal` is given. To
use a native image in a container that is not identical to the build platform,
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
