Re: disable sandbox tomcat9
The README file explains how to override the systemd configuration. You can either add ReadWritePaths directives [1] to grant access to more paths, or set ProtectSystem=false [2] to disable the sandboxing completely. Emmanuel Bourg [1] https://www.freedesktop.org/software/systemd/man/systemd.exec.html#ReadWritePaths= [2] https://www.freedesktop.org/software/systemd/man/systemd.exec.html#ProtectSystem= On 24/09/2020 03:15, Cristiano Albiero Berni wrote: > Hi, > > Tomcat 9 package install on Ubuntu 20.04 lts server. > I need to disable the sandbox. It's a problem when adding a new filesystem. > I need to get it NO sandboxing to all the "/" > including different filesystems. > > How could I do that? > > > Or > https://salsa.debian.org/java-team/tomcat9/blob/master/debian/README.Debian > in this link have how to override. > > How cold I add a wildcard folder. Like /home* (/home, /home02, /home03) > > > thanks a lot. > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: File "catalina.out" not being created/populated when using Tomcat 9.0.31 + Ubuntu 20.04, and content goes to the Ubuntu syslog instead?
Le 24/06/2020 à 03:33, Brian a écrit : > To be honest with you, I'm happy about the catalina.out file finally getting > created and I really appreciate your kind help, I really do. But I'm not > really happy about having to restart rsyslog before every time I need to > restart Tomcat. It is weird, and I guess a lot of users will never imagine > that they have to do that and they will not feel very pleased when they > realize that the catalina.out file doesn't get created after restarting > Tomcat. And probably most of them will not even notice that the Tomcat log is > being added to the syslog, for that matter. This whole new relation between > syslog and Tomcat is really weird and I don't think the users are being > warned about it. I have used Tomcat+Ubuntu for several years and I haven't > seen this complication before. If there is an advantage about this relation > between syslog and Tomcat, I really can't see it. This is weird I fully agree, and I'll try do to something better. There is a way to write to catalina.out without using rsyslogd, it's possible to instruct systemd to write the process output directly to the file by overriding the StandardOutput directive of the service file: StandardOutput=file:/var/log/tomcat9/catalina.out This would go in a /etc/systemd/system/tomcat9.service.d/override.conf file for example. The downside is that you can no longer access the Tomcat output with 'journalctl -t tomcat9', nor see the last lines of the log when displaying the status with 'systemctl status tomcat9'. Ideally systemd should support writing to the journal and to a file simultaneously, with something like StandardOutput=journal+file:... If there is no other way to achieve the same result I'll file an enhancement request on systemd. Emmanuel Bourg - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: File "catalina.out" not being created/populated when using Tomcat 9.0.31 + Ubuntu 20.04, and content goes to the Ubuntu syslog instead?
Le 24/06/2020 à 02:35, Brian a écrit : > Good news: I updated "/etc/tmpfiles.d/tomcat9.conf" (the file I created) with > the new value of 2770. Deleted all the logs inside "/val/log/tomcat9" and > restarted Ubuntu. "catalina.out" got created and populated. > Bad news: Then I deleted all the logs inside "/val/log/tomcat9" and just > restarted Tomcat (which is something I do sometimes, in production). > "catalina.out" didn't get created this time. > > Just to confirm, again I deleted all the logs inside "/val/log/tomcat9" and > restarted Ubuntu. "catalina.out" got created and populated again. > > Any ideas? The catalina.out file is held by rsyslogd and isn't recreated unless you restart rsyslogd. Try this when you clean the logs and restart Tomcat: systemctl restart rsyslog tomcat9 Emmanuel Bourg - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: File "catalina.out" not being created/populated when using Tomcat 9.0.31 + Ubuntu 20.04, and content goes to the Ubuntu syslog instead?
Le 23/06/2020 à 19:48, Brian a écrit : > It seems that rsyslogd is still unable to deal with > "/var/log/tomcat9/catalina.out". > What could be wrong now? Do you have any ideas? I got the permissions wrong, the adm group is now allowed to write to /var/log/tomcat9 but not to enter it. Try 2770 instead of 2760. Emmanuel Bourg - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: File "catalina.out" not being created/populated when using Tomcat 9.0.31 + Ubuntu 20.04, and content goes to the Ubuntu syslog instead?
Le 23/06/2020 à 02:53, Brian a écrit : > Please do! It definitely looks like a bug. > I just reported the bug here: > https://bugs.launchpad.net/ubuntu/+source/tomcat9/+bug/1884591 I've just uploaded tomcat9/9.0.36-1 in Debian and changed the permissions [1] on the log directory. This will propagate to Ubuntu sooner or later. Emmanuel Bourg [1] https://salsa.debian.org/java-team/tomcat9/-/commit/51128fe9 - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: File "catalina.out" not being created/populated when using Tomcat 9.0.31 + Ubuntu 20.04, and content goes to the Ubuntu syslog instead?
Le 22/06/2020 à 18:43, Brian a écrit : > I'm not really an expert with Linux. It would seem to me that the "adm" group > (to which syslog seems to belong) lacks a write permission Indeed, rsyslog in Ubuntu runs as syslog:adm and needs special permissions to write to /var/log/tomcat9. This issue should be reported to Ubuntu. The tomcat9 package in Debian isn't affected by this issue because rsyslogd runs as root. > OK, I did it and the write permission was added to the adm group. I restarted > Tomcat and it worked, the catalina.out file got created! However, after I > restarted the whole Ubuntu, I discovered that the permissions went back to > how there were (not write for adm). Why is that? The permissions on this directory are managed by systemd-tmpfiles. The tomcat9 package defines the expected permissions in /usr/lib/tmpfiles.d/tomcat9.conf and the permissions are enforced when the system starts. It's possible to override the default settings, you have to copy the configuration file to /etc/tmpfiles.d/ and change the permissions on /var/log/tomcat9 from 2750 to 2760: cp /usr/lib/tmpfiles.d/tomcat9.conf /etc/tmpfiles.d/ sed -i s/2750/2760/ /etc/tmpfiles.d/tomcat9.conf The write permissions for the adm group will then be persistent. > In any case, why is this permission required in my new VPS, if the old one > lacks it and catalina.out works perfectly? I guess your older VPS had the tomcat8 package installed. The tomcat9 package is different as it leverages several systemd features to improve the security and the reliability. Emmanuel Bourg - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: File "catalina.out" not being created/populated when using Tomcat 9.0.31 + Ubuntu 20.04, and content goes to the Ubuntu syslog instead?
Le 22/06/2020 à 10:44, calder a écrit : > However, this is one reason we do not use "distro-specific" Tomcat > installations (to include implementations of WebSphere and WebLogic). > . > For example, we grab the plain vanilla Tomcat ZIP and extract it to "/opt/" > (as in "/opt/tomcat/") - we now have complete control over its > configuration and runtime instantiation. This is a valid strategy, but you miss the tight integration with the system that comes out of the box with a distro specific package (proper system service, started on boot, restarted on crashes, run by a non privileged user allowed to bind to ports below 1024, sandboxed, with logs in a consistent location). And you are still able to override some aspects of the default configuration you might not like. Emmanuel Bourg - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: File "catalina.out" not being created/populated when using Tomcat 9.0.31 + Ubuntu 20.04, and content goes to the Ubuntu syslog instead?
Le 22/06/2020 à 20:03, Christopher Schultz a écrit : > It looks like whoever is responsible for packing Tomcat for Ubuntu has > something missing, there. I suggest you file a bug with Ubuntu. That must be me :) I'll get a look. Emmanuel Bourg - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: [OT] Re: Maven Warning. Ubuntu Users
Le 06/01/2020 à 21:24, Zahid Rahman a écrit : > Don't shoot the messenger. You are not sending the message to the right list, there is nothing the Tomcat developers can do to fix this issue. This should be brought to debian-j...@lists.debian.org instead (Debian is the source of Ubuntu Java packages). But you are lucky because beside maintaining Tomcat in Debian, I also maintain Maven, and thanks to your message I've filled the bugs to address this issue [1][2]. Emmanuel Bourg [1] https://bugs.debian.org/948309 [2] https://bugs.debian.org/948310 - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 9 does not allow to read file in /tmp folder with 777 permission?
Le 04/01/2020 à 16:06, Pham Huu Bang a écrit : > Thanks for this link > https://salsa.debian.org/java-team/tomcat9/blob/master/debian/README.Debian. > But I cannot *read* the file from /tmp (not *write* file to /tmp). The > strange thing is, it can read another file from another location, e.g in > /opt/: The tomcat9 service is configured with a private /tmp directory (using the 'PrivateTmp=yes' systemd directive). So Tomcat can't see what other applications write to /tmp, and temporary files written by Tomcat are out of reach from the other applications. This is a security hardening setting that can be overridden as described in the README file Olaf mentioned. Emmanuel Bourg - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat starts very slow
Le 03/07/2019 à 01:23, W a écrit : > Hi,I have Tomcat 9 on Ubuntu 18.04. Tomcat stars very slow, sometimes 15 > minute. > I checked catalina.2019-xxx.log and found some issues below. > What should I do? > Any information would be appreciated. Thanks in advance. Your server lacks entropy, see: https://cwiki.apache.org/confluence/display/TOMCAT/HowTo+FasterStartUp#HowToFasterStartUp-EntropySource Emmanuel Bourg - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: migrate to tomcat 9: application can not write files on system filder
Le 01/07/2019 à 19:55, W a écrit : > Hi,I am migrate from ubuntu 16.04 (server), mysql 5.7 and tomcat 8 to ubuntu > 18.04(server), mysql 8 and tomcat 9. > My application works on old system. Now when my application tries to write a > file on > a directory (permission allowed), there is an > error:java.nio.file.FileSystemException: /photoLogos/PERSON/-_~x: Read-only > file system The tomcat9 package on Debian/Ubuntu uses systemd and leverages its sandboxing feature to limit the write access to the conf, log, work and webapps directories by default. If you look at the package's README file (/usr/share/doc/tomcat9/README.Debian) you'll find the instructions to grant Tomcat write access to other directories: https://salsa.debian.org/java-team/tomcat9/blob/master/debian/README.Debian If write access to other directories is required the service settings have to be overridden. This is done by creating an override.conf file in /etc/systemd/system/tomcat9.service.d/ containing: [Service] ReadWritePaths=/path/to/the/directory/ The service has to be restarted afterward with: systemctl daemon-reload systemctl restart tomcat9 Emmanuel Bourg - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Number of tomcat downloads
Le 05/02/2019 à 00:48, Leon Rosenberg a écrit : > I vaguely remember Marc naming some figures for number of tomcat downloads > sofar, but I couldn't find anything in the state of the cat slides. > I checked on the website, but all I found was this: > > " Tomcat has been downloaded more than 10 million times: assuming even a 1% > production adoption rate results in more than 10 installations. " > But this is from 2014 and I assume there should be a better number by now. > > Anyone? Asking for a friend ;-) Some numbers, from Debian: https://qa.debian.org/popcon-graph.php?packages=tomcat9+tomcat8+tomcat7+tomcat6_installed=on_legend=on_ticks=on_date=_date=_date=_fmt=%25Y-%25m=1 around 2400 installations reported by popcon, rather stable over the years. >From Ubuntu: https://popcon.ubuntu.com/by_inst tomcat6 15785 tomcat72122 tomcat8 117 And from Netcraft: https://news.netcraft.com/archives/2018/12/17/december-2018-web-server-survey.html Netcraft reported ~600000 domains served by Tomcat. Emmanuel Bourg - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 8 runs under Java 7, but not Java 8
Hi James, Le 18/12/2018 à 21:40, James H. H. Lampert a écrit : > I just installed Java 8 (not as the default JRE) on a Google Compute > Debian 8 instance that has been running Tomcat 8 under Java 7. I assume you are using the tomcat8 package from the distribution. Tomcat on Debian 8 Jessie is a bit old (but still receives security fixes), I recommend upgrading to Debian 9 where you'll be able to use the latest 8.5 version from the stretch-backports repository (and soon tomcat9 too). > If I change setenv.sh to add >> JAVA_HOME="/usr/lib/jvm/java-8-openjdk-amd64/" Note that on Debian the JAVA_HOME variable is typically set in the /etc/defaut/tomcat8 file. > and I try to "service tomcat8 start," I get > >> Job for tomcat8.service failed because the control process exited with >> error code. >> See "systemctl status tomcat8.service" and "journalctl -xe" for details. This version of the Tomcat package doesn't have really useful information in the systemd log unfortunately. This changed with the version 8.5.32-2 of the package which now provides a proper systemd service file. So in your case you should look into /var/log/tomcat8/catalina.out instead. > If I leave the JAVA_HOME in there, but change it to refer to the Java 7 > directory, it works fine. > > What am I doing wrong? Tomcat 8 runs just fine on our other Google > Compute instances, and they *only* have Java 8. How did you install Java 8? From the jessie-backports repository? Emmanuel Bourg - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Translations update
Le 26/11/2018 à 13:29, Rémy Maucherat a écrit : > Now we can try to harmonize terms, fixes are then easy to do with the > search feature > > Common ones we have right now: > - "socket" (usually untranslated or cleverly omitted): ? +1 untranslated > - "endpoint" (for websockets, and for the Tomcat connectors, so possibly > two different terms): "point d'entrée" ? +1 for "point d'entrée" > - "thread" (often it is untranslated elsewhere): "fil d'exécution" ? untranslated is more clear. > - "membership" (that's the clustering object): "gestionnaire de membres" ? "appartenance" ? > - "dispatch"/"dispatcher" (for the Servlet request dispatcher): ? "répartiteur" ? Emmanuel Bourg - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Java 10; JAXB; and Tomcat 9
Le 03/05/2018 à 00:42, Jerry Malcolm a écrit : > Thanks for the input. I haven't been keeping up with Java EE for a > while. I tried to download EE instead of SE and got a few gigabytes of > "GlassFish server". Couldn't even find the jaxb jar files in that > package. I haven't researched what GlassFish is... but I know I don't > need to learn another server right now. Did I download the wrong > thing? Is there still just a plain ol' EE version of Java with jar files? Here is the standalone JAXB distribution: https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-ri/2.3.0/jaxb-ri-2.3.0.zip - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Java 10; JAXB; and Tomcat 9
Le 02/05/2018 à 23:14, Jerry Malcolm a écrit : > I just did a clean install of TC 9 on a new system. I downloaded the > latest JDK, (10). My code started getting errors about JAXB Exception > class not found. I had already faced this with the JAMES installation > and found out JAXB was removed in Java 9+, but was still available if > called out. The forums said to include --add-modules java.xml.bind on > the Java command line. This fixed it in JAMES. But I added this to the > java options in the TC configuration app and get an "invalid option" > error. Am I putting this option in the wrong place on the config > panel? Is there another way to call out JAXB in TC? The java.xml.bind module is going to be removed from Java 11 and the --add-modules trick will no longer work. I suggest adding the jaxb jar to your classpath instead for a long term solution. Emmanuel Bourg - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: debian 9 and tomcat 8 error at startup
Hi Roberto, You have to install the libservlet3.1-java package. This is a mistake in the packaging that will be fixed in a future update (Debian bug #867247). Emmanuel Bourg Le 26/09/2017 à 07:56, r.bott...@afterbit.com a écrit : > Hi, > i have installed tomcat 8 on a Debian server using aptitude command. > but when tomcat starts, I get this strange error : > > > 26-Sep-2017 07:47:14.613 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Server version: > Apache Tomcat/8.5.14 (Debian) > 26-Sep-2017 07:47:14.614 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Server built: > Sep 3 2017 17:51:58 UTC > 26-Sep-2017 07:47:14.614 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Server number: > 8.5.14.0 > 26-Sep-2017 07:47:14.614 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log OS Name: > Linux > 26-Sep-2017 07:47:14.614 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log OS Version: > 4.9.0-3-amd64 > 26-Sep-2017 07:47:14.614 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Architecture: > amd64 > 26-Sep-2017 07:47:14.614 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Java Home: > /usr/lib/jvm/java-8-oracle/jre > 26-Sep-2017 07:47:14.614 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log JVM Version: > 1.8.0_144-b01 > 26-Sep-2017 07:47:14.614 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: > Oracle Corporation > 26-Sep-2017 07:47:14.615 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: > /var/lib/tomcat8 > 26-Sep-2017 07:47:14.615 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: > /usr/share/tomcat8 > 26-Sep-2017 07:47:14.615 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: > -Djava.util.logging.config.file=/var/lib/tomcat8/conf/logging.properties > 26-Sep-2017 07:47:14.615 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager > 26-Sep-2017 07:47:14.615 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: -Djava.awt.headless=true > 26-Sep-2017 07:47:14.615 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: -XX:+UseConcMarkSweepGC > 26-Sep-2017 07:47:14.615 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: -Djdk.tls.ephemeralDHKeySize=2048 > 26-Sep-2017 07:47:14.616 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: -Djava.protocol.handler.pkgs=org.apache.catalina.webresources > 26-Sep-2017 07:47:14.616 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: -Dcatalina.base=/var/lib/tomcat8 > 26-Sep-2017 07:47:14.616 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: -Dcatalina.home=/usr/share/tomcat8 > 26-Sep-2017 07:47:14.616 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: -Djava.io.tmpdir=/tmp/tomcat8-tomcat8-tmp > 26-Sep-2017 07:47:14.616 INFO [main] > org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR > based Apache Tomcat Native library which allows optimal performance in > production environments was not found on the java.library.path: > /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib > 26-Sep-2017 07:47:14.764 INFO [main] > org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler > ["http-nio-8080"] > 26-Sep-2017 07:47:14.789 INFO [main] > org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a > shared selector for servlet write/read > 26-Sep-2017 07:47:14.791 INFO [main] > org.apache.catalina.startup.Catalina.load Initialization processed in > 684 ms > 26-Sep-2017 07:47:14.826 INFO [main] > org.apache.catalina.core.StandardService.startInternal Starting service > Catalina > 26-Sep-2017 07:47:14.826 INFO [main] > org.apache.catalina.core.StandardEngine.startInternal Starting Servlet > Engine: Apache Tomcat/8.5.14 (Debian) > 26-Sep-2017 07:47:14.843 INFO [localhost-startStop-1] > org.apache.catalina.startup.HostConfig.deployDirectory Deploying web > application directory /var/lib/tomcat8/webapps/ROOT > 26-Sep-2017 07:47:15.141 WARNING [localhost-startStop-1] > org.apache.tomcat.util.scan.StandardJarScanner.scan Failed to scan > [file:/usr/share/java/el-api-3.0.jar] from classloader
Re: For some reason, the AUTHBIND approach isn't working with 8.5
Le 7/09/2017 à 02:02, James H. H. Lampert a écrit : > Now, I'm attempting to do the same with Tomcat 8.5, and it's not working. > > > I think I did everything the same as before. I uncommented AUTHBIND in > /etc/default/tomcat8, and set it to "AUTHBIND=yes"; an > /etc/authbind/byuid/109 (the uid of the tomcat8 user) was generated with > contents > > and yet still, I get the stack trace given above. Hi James, You didn't change the TOMCAT8_USER variable in /etc/default/tomcat8 and authbind is installed, right? What is the output of (as root): su tomcat8 -s /bin/bash -c "authbind --deep /bin/bash -c 'netcat -v -p 443 -l'" Emmanuel Bourg - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Where Tomcat webapp contexts live on Debian
On 08/16/2017 09:24 AM, Leon Rosenberg wrote: > Debian has a long tradition of doing things in a very special way when it > comes to java. Long enough they shipped GnuJ as standard JVM with a debian > distribution, a piece of garbage that wasn't able to start simplest of java > programs. GCJ has been superseded by OpenJDK a lng time ago as the default Java runtime on Debian. > But there has been an as long tradition to reply to every question about > tomcat behaviour on a specific distribution by suggesting to throw the crap > away and download the vanilla tomcat form the one and only legal source ;-) > (at least in the past, to which debian belongs). FWIW, there is now a Tomcat committer maintaining the Tomcat package in Debian and controlling its quality. If you think there is something crappy about the packaging feel free to send a mail to me or to the debian-j...@lists.debian.org and I'll be happy to help. Emmanuel Bourg - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Reg CVE-2017-5664
Le 22/06/2017 à 17:46, Durga Srinivasu Karuturi a écrit : > We are using tomcat 8.5.14. >From Debian 9? If so this has been patched today: https://www.debian.org/security/2017/dsa-3891 Emmanuel Bourg - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Should Tomcat continue to support SSI?
Le 7/06/2017 à 16:51, Christopher Schultz a écrit : > What about separating SSI out into a separate (sub?) project and > removing it from Tomcat core? +1, I was about to suggest this as well. Emmanuel Bourg - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: TomcatCon @ ApacheCon
Le 1/02/2017 à 20:20, Coty Sutherland a écrit : > I'm still planning to submit for the linux packaging talk (though I > haven't heard anything else form the other distro maintainers), just > haven't done it yet. I suppose I could volunteer for one of the > others, I'll check the list. Hi Coty, If you already have a draft of your presentation you can send it to me and I'll insert a few slides about Debian. Emmanuel Bourg - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat maintainer's ApacheCon NA presentation
Hi Coty, This is an excellent idea. I won't be able to attend ApacheCon NA but I'll be happy to provide some input for your presentation and contribute a few slides to describe the Tomcat packaging in Debian/Ubuntu. Emmanuel Bourg Le 19/01/2017 à 19:26, Coty Sutherland a écrit : > Hi all, > > My name is Coty and I'm the maintainer for RHEL tomcat and a > co-maintainer for Fedora/EPEL tomcat. I'm reaching out to you all in > response to the tomcat users list thread (subject: TomcatCon @ > ApacheCon) to see if you're interested in doing a talk with me about > linux packaging at the upcoming ApacheCon NA conference. Is anyone > interested? Do you know any of the maintainers for other linux > distributions that may be interested? > > As far as the talk goes, I figure it could be a panel discussion; we > can take some topics/slides on how each distro packages tomcat > differently and why we do that, then get the audience engaged to > solicit some feedback on how we can better provide tomcat in our > respective distros. We could also use this as a forum to bring up > tomcat backwards compatibility issues, as I've gotten lots of > complaints about that in the past :( The other tomcat committers seem > to be pretty open to these discussions, so I'd love to include other > distros in the conversation to get all the different perspectives we > can. > > > > Thanks! > Coty > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: [ANN] Apache Tomcat 8.0.9 (stable) available
I'm also pleased to announce that Tomcat 8.0.9 is now available for Debian 7 (Wheezy) through the backport repository [1]. The repository has to be declared in /etc/apt/sources.list by adding this line: deb http://http.debian.net/debian wheezy-backports main The package can then be installed with: apt-get update apt-get install tomcat8 For Ubuntu users the package is also available for Utopic Unicorn [2] (to be released this fall). Emmanuel Bourg [1] http://backports.debian.org [2] http://packages.ubuntu.com/utopic/tomcat8 Le 26/06/2014 09:00, Mark Thomas a écrit : The Apache Tomcat team announces the immediate availability of Apache Tomcat 8.0.9, the first stable release of the 8.0.x series. Apache Tomcat 8 is an open source software implementation of the Java Servlet, JavaServer Pages, Java Unified Expression Language and Java WebSocket technologies. Apache Tomcat 8 is aligned with Java EE 7. In addition to supporting updated versions of the Java EE specifications, Tomcat 8 includes a number of improvements compared to Tomcat 7. The notable changes include: - Support for Java Servlet 3.1, JavaServer Pages 2.3, Java Unified Expression Language 3.0 and Java WebSocket 1.0. - The default connector implementation is now the Java non-blocking implementation (NIO) for both HTTP and AJP. - A new resources implementation that replaces Aliases, VirtualLoader, VirtualDirContext, JAR resources and external repositories with a single, consistent approach for configuring additional web application resources. The new resources implementation can also be used to implement overlays (using a master WAR as the basis for multiple web applications that each have their own customizations). Apache Tomcat 8.0.9 includes numerous fixes for issues identified in 8.0.8 as well as a number of other enhancements and changes. The notable changes since 8.0.8 include: - Start to move towards RFC6265 for cookie handling - Better error handling when the error occurs after the response has been committed - Various Jasper improvements to make it easier for other containers (e.g. Jetty) to consume Please refer to the change log for the complete list of changes: http://tomcat.apache.org/tomcat-8.0-doc/changelog.html Note: This version has 4 zip binaries: a generic one and three bundled with Tomcat native binaries for Windows operating systems running on different CPU architectures. Downloads: http://tomcat.apache.org/download-80.cgi Migration guides from Apache Tomcat 5.5.x, 6.0.x and 7.0.x: http://tomcat.apache.org/migration.html Enjoy! - The Apache Tomcat team - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
