Re: Connection pool and parallel deployment problem

[HeeGu Lee]

Dear Gilles,

I apologize for the delay in reply.

I make simple webapp and upload to github. In project, my test result is
included.

https://github.com/elfhazardwork/dbcp2-test

Tomcat's parallel deploy mechanism is deploy new version before undeploy
old.
So, If your webapp is use JMX, bean name will duplicate and crush.

The connection pool is used where the developer does not explicitly declare
JXM.
So this is a Tomcat bug.
Otherwise, you must set JMX bean name dynamically.

I hope this helps.


2018년 11월 27일 (화) 오전 2:03, Chris Cheshire 님이 작성:

> On Mon, Nov 26, 2018 at 9:58 AM Gilles SCHLIENGER
>  wrote:
> >
> > Hi,
> > I understand your needs, but what is your problem, since you don't use
> parallel deployment ?
> > Your connections are not closed but they will not be recreated when you
> deploy your webapp again, so there should be no problem ?
> >
> > Gilles
> >
>
> I added my 2c because I am seeing what you describe here
>
> > > - I undeploy the first version of the webapp
> > > - I check on my postgresql and mysql database and all connections are
> still opened (even if I wait for a long time)
>
>
> Yes I know you are using parallel deployment and I am not, but that
> doesn't necessarily mean that the problem you see is limited to only
> parallel deployment. Maybe the problem can be simplified to "
> Tomcat considers the connections closed, the database doesn't."
>
> I could well be wrong, I'll leave it up to the gurus to decide :)
>
>
> > -Message d'origine-
> > De : Chris Cheshire [mailto:yahoono...@gmail.com]
> > Envoyé : lundi 26 novembre 2018 15:27
> > À : Tomcat Users List
> > Objet : Re: Connection pool and parallel deployment problem
> >
> > I'm interested in what solution there is for this because I have the
> > exact same problem but without parallel deployment.
> >
> > [snip]
> >
> > On Mon, Nov 26, 2018 at 3:54 AM Gilles SCHLIENGER
> >  wrote:
> > >
> > > Hi Christopher,
> > >
> > > Thanks for your email.
> > >
> > > About connection pools not being closed, maybe the connection pool is
> closed but the connections to the database are not.
> > >
> > > Here are the tests I did:
> > >
> > > + TEST 1:
> > > - I deploy my war
> > > - I login to my webapp
> > > - I check on my postgresql and mysql database that connections have
> been opened (select...)
> > > - I undeploy my webapp through the manager webapp
> > > - I check that the connections are still opened
> > > - Tomcat is still running
> > > - I redeploy the exact samed webapp and login to my application
> > > - No other connection is being opened
> > >
> > > + TEST 2:
> > > - I deploy my war
> > > - I login to my webapp
> > > - I check on my postgresql and mysql database that connections have
> been opened (select...)
> > > - I deploy a new version of my application and login with another
> browser
> > > - I check on my postgresql and mysql database that new connexions have
> been opened (they doubled)
> > > - I undeploy the first version of the webapp
> > > - I check on my postgresql and mysql database and all connections are
> still opened (even if I wait for a long time)
> > >
> > > For tests 1 and 2, I used C3p0, DBCP2 and even HikariCP
> > >
> >
> >
> > My results are the same. Using mysql, connection pools defined in
> > server.xml (for user realm for access control to host manager app) and
> > in my context.xml for my application. When I use the host-manager to
> > reload an app, the connections are closed (no abandoned connection
> > warnings) but not released. It is no until I stop tomcat completely
> > and restart it that the connections are released in mysql. This has
> > been the case for tomcat 7, 8.5 and 9 versions, with constant updates
> > of mysql 5.7 and its driver, using both the apache connection pool and
> > the tomcat connection pool. The driver lives in the tomcat/lib
> > directory (since it is needed for the user realm datasource).
> >
> >
> > > -Message d'origine-
> > > De : Christopher Schultz [mailto:ch...@christopherschultz.net]
> > > Envoyé : samedi 24 novembre 2018 17:19
> > > À : users@tomcat.apache.org
> > > Objet : Re: Connection pool and parallel deployment problem
> > >
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA256
> > >
> > > Gilles,
> > >
> > > On 11/23/18 05:07, Gilles SCHLIENGER wrote:
> >
> > [snip]
> >
> > >
> > > > The warning/error messages are not actually linked to the
> > > > connexions not closed. To ovoid these messages, you can: - move the
> > > > jars (connexion pool, drivers...) into TOMCAT/lib - Have a
> > > > ServletContextListener that calls
> > > > AbandonedConnectionCleanupThread.checkedShutdown();
> > >
> > > The Connector/J devs haven't been able to understand how ClassLoaders
> > > work, and have never really fixed that long-standing bug in a
> > > satisfying way as far as I know. But you should always use a
> > > ServletContextListener to attempt to shut-down the
> > > AbadonedConnectionCleanuopThread.
> > >
> > > BTW that thread does not work 

Re: Translations update

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

André,

On 11/26/18 17:07, André Warnier (tomcat) wrote:
> On 26.11.2018 17:01, Christopher Schultz wrote:
>>> We were super serious, like for Apache Matou:)
>> :)
>> 
>> I like that as a (silly) name (Apache Dead?), but didn't get the 
>> actual joke.:(
> 
> "matou" is the litteral French translation of "tomcat". (Evokes a
> big tough male macho alley cat, the kind which takes no sh.. from
> anyone).

Aw... Google Translate failed me and I didn't notice.

I had it translate "matou" (which I suspected would be "Tomcat",
actually, even though I know that "chat" is "cat"), but GT
auto-detected the language as "Portuguese" and translated it as "killed"
.

It really killed the joke. ;)

- -chris
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlv8thcACgkQHPApP6U8
pFi4eBAAhJrcS5cx7s1et9PP9zVbSP/WzNDpO5o1WOVEwBlt68oPApJ2Yr0u703H
auL4lyg5hW0ubj8gJXTqkXI7X08BueRQuGa1Y2Dv+yaLHY8jn38X4zHKTBFy/tpO
wv46YY+beYW86106WOUOg/uFBu025zh4Dnddru+KK8ACVsj9RB85z9G4xdmJE3kB
BU/KwCMBS2vK/EqLa6cQ/ifgc/pIy9XPxBC1bp+QuCGtbXn8wAEWT0JSophoy4+M
w2099ZOmJMWX1bu55G5TFL5jwkApaWLpWlnCSdIceKvwKmlcNhX6aax1EO8WIb8T
JkuT1KYSya1RwakJVlSvt5iirdj8+NAu4/tDYSPCVwIin/yKXuRv4wVf8BJ3jExL
H2Qs2eo69LxY+km7KUF7GehGS4gT6/601/qZDOeFEQ2VHF72QFOSMQkRlTtkUbMM
5eZIvE9C3sWgRkKL/gkSLUjY/ZM69K9c1ZlE6rBOHeIbUoVprUqjhf3HW9EavlNB
CMkS0wpTXfKupxZHzI7sX5ingl/p5/UCl9gw/8YgaVZXroeGvNKYYcmmLlhuSRAf
l7CKg7PeHVtGjIcHbfVjLbjPG28Fwed5VrABtMceoNceo3RQehOjhukj6WlLLehh
GsphfRPaucSow7HKHngd/H3OUswddQIm7KJtfMVUWXGvdwzlyUI=
=+U7g
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Compression for Resources served through DefaultServlet

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Leon,

On 11/26/18 18:53, Leon Rosenberg wrote:
> On Mon, Nov 26, 2018 at 10:27 PM Mark Thomas 
> wrote:
> 
>> On 26/11/2018 21:19, Leon Rosenberg wrote:
>>> Good time of the day,
>>> 
>>> I am debugging bad page insights reported by google for a
>>> mobile versus desktop version of our site and I'm seeing that
>>> the static resources, served by the DefaultServlet (aka files)
>>> aren't compressed, versus to dynamic resources served by a
>>> servlet. Tomcat version in question 8.5.15 and 8.5.31 (tested
>>> on both)
>> 
>> http://tomcat.apache.org/tomcat-8.5-doc/config/http.html
>> 
>> Search for sendfile.
>> 
>> ?
>> 
> 
> I thought sendfile is NIO only, this was probably the mistake.

It's for NIO/NIO2 and APR, and on by default. Those are the only
connectors available these days, so by default sendFile=true and
therefore compression=false.

- -chris
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlv8lZsACgkQHPApP6U8
pFg7GhAAnYAlwdMTkpe1i995Q1mFKfOV5GTU8IpqFXFadnaiNov/mpWX64IVSGQB
3B2m0CwHgQE1Nv0lh/3AHleqC54S5i8Hiuhw3YiYBQ6xfKVbctrG2m+97WtgXSzG
lwV2pUw1nsJlJ/Wlnc+/Pf1DUN6p5r8IMSIP4NnuhM0KSYwJi60bN2w10ZJsMpDR
6DFkLMT+g3LQ7lvsRsol99AQkpbkeEpUypRr1y5/duvkqz/8A/8WX4kZ7+Ix5oah
y+hLmd31nqjE03wAnacLfiMQ4ziUzh0MNKfjJUnccOvK5eXLSpE6uvAtA6nsMuAK
3HxsGsDTc6wdeF6oEU3MY16AdnG6mGOhfASCv5tMqkDYrzKLnznN7dmYCpzikgjR
S3SzYGoXm+YE5n0ciA/aKat+701YJZX9N9LJak60A9+eJ9Xr0gG81t/4H6FW8uo2
0M5ukNhBy08M5yqFbz3rQmDEZdOsCOCO9Mb+2ABusnjupnadBCfonUSD+JVNezXm
7im0PiiNuXGigrmURS85xAtE3VJIt9mTCylbLxMDMJw3LdZUrMpd0AK/VuBPK5/0
zjn1JvqB6qosdCqnKvERk85EKY4c4mfqVVVDl0Ok0pJcH5x3rgnmyaysjDaUy0sX
ap3plQplGRpJI6J+b9QLrviYEq/4uFYabQIoEJ7p1Lm+Jq8JjhI=
=eiE1
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 9 does not work with Java 11

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Andi,

On 11/26/18 15:08, Andi Meister wrote:
> Tomorrow I will try it on an other machine with no previous Tomcat 
> installed. But my problem is that I have to get it to run on this
> machine. What could I do? First uninstall all jdks and Tomcats and
> then install jdk11 and newest Tomcat?

You might want to:

1. C:...\tomcat-7> bin\service.bat remove  (optional name parameter)

2. C:...\tomcat-9> bin\service.bat install (optional name parameter)

Something might be broken in the service definition, and this should
reset everything. Note that any of the system properties you might
have defined in the existing service will be wiped-out by this
process. So, you might want to take a few screenshots of the various
configuration screens if you are using anything other than the plain
defaults.

Hmm... just realized that the service.bat file might not be included
in the "installer" bundle. You might have to grab the ZIP bundle from
the Tomcat downloads site to get those scripts.

- -chris

> Am Mo., 26. Nov. 2018, 20:59 hat Andi Meister
>  geschrieben:
> 
>> Thank you. Dies this mean that I'm doing anything correctly but
>> it just doesn't work on this machine maybe?
>> 
>> Ralf
>> 
>> 
>> Am Mo., 26. Nov. 2018, 20:32 hat Mark Thomas  
>> geschrieben:
>> 
>>> On 26/11/2018 18:51, Andi Meister wrote:
 I guess the JDK that I used is not OpenJDK but Oracle JDK?
 That's not
>>> the
 same isn't it?
>>> 
>>> They aren't identical but the differences aren't in any areas
>>> that would impact this issue. Tomcat works happily with both.
>>> 
>>> Mark
>>> 
>>> 
 
 There is a pre-story to that. Maybe there is the reason?! On
 this server there was installed: JRE 1.6 and Tomcat 7 -
 running for years. Now there is an update planned to Java 11
 and I have to check if it
>>> runs.
 
 First, I installed the JDK 11 additionally and pointed the
>>> Java-location in
 Tomcat 7 configuration app to the new /bin/server/jvm.dll.
 
 Same error as now.
 
 Then I uninstalled Tomcat 7 and JRE 6. Then installed Tomcat
 9. Error...
 
 Ralf
 
 
 Am Mo., 26. Nov. 2018 um 18:34 Uhr schrieb Mark Thomas <
>>> ma...@apache.org>:
 
> Tomcat 9.0.13 windows installer, Open JDK 11.0.1 and Window
> server 2008 R2 work first time for me on a clean install.
> 
> This doesn't look like a Tomcat issue at this point.
> 
> Mark
> 
> 
> 
> On 26/11/2018 17:04, Andi Meister wrote:
>> more detailled: 9.0.13 Core:
>> 
>> - zip <
> 
>>> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-to
mcat-9.0.13.zip
>>
>>
>>> 
(pgp
>> <
> 
>>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomca
t-9.0.13.zip.asc
>>
>>> 
,
>> sha512 <
> 
>>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomca
t-9.0.13.zip.sha512
>>
>>> 
)
>> 
>> - tar.gz <
> 
>>> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-to
mcat-9.0.13.tar.gz
>>
>>
>>> 
(pgp
>> <
> 
>>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomca
t-9.0.13.tar.gz.asc
>>
>>> 
,
>> sha512 <
> 
>>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomca
t-9.0.13.tar.gz.sha512
>>
>>> 
)
>> 
>> - 32-bit Windows zip <
> 
>>> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-to
mcat-9.0.13-windows-x86.zip
>>
>>
>>> 
(pgp
>> <
> 
>>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomca
t-9.0.13-windows-x86.zip.asc
>>
>>> 
,
>> sha512 <
> 
>>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomca
t-9.0.13-windows-x86.zip.sha512
>>
>>> 
)
>> 
>> - 64-bit Windows zip <
> 
>>> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-to
mcat-9.0.13-windows-x64.zip
>>
>>
>>> 
(pgp
>> <
> 
>>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomca
t-9.0.13-windows-x64.zip.asc
>>
>>> 
,
>> sha512 <
> 
>>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomca
t-9.0.13-windows-x64.zip.sha512
>>
>>> 
)
>> 
>> - 32-bit/64-bit Windows Service Installer <
> 
>>> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-to
mcat-9.0.13.exe
>>
>>
>>> 
(pgp
>> <
> 
>>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomca
t-9.0.13.exe.asc
>>
>>> 
,
>> sha512 <
> 
>>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomca
t-9.0.13.exe.sha512
>>
>>> 
)
>>  this one
>> 
>> 
>> Am Mo., 26. Nov. 2018 um 18:02 Uhr schrieb Andi Meister
>> < blackpum...@googlemail.com>:
>> 
>>> Hi Chris,
>>> 
>>> this one: 32-bit/64-bit Windows Service Installer <
> 
>>> 

Re: Tomcat 9 does not work with Java 11

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

M Manna,

On 11/26/18 17:57, M. Manna wrote:
> if you are moving away from Java 8, I would recommmend you install
> java 11 first. Oracle JDK or openJDK doesn’t matter here.
> 
> Once you do that, confirm that your JAVA_HOME env var is setup
> correctly ( google it if you’re not sure). The go ahead with your
> tomcat installation (service or standalone). See how it works for
> you.

The value of JAVA_HOME is not relevant when running as a Windows Service
.

- -chris

> On Mon, 26 Nov 2018 at 20:08, Andi Meister 
>  wrote:
> 
>> Tomorrow I will try it on an other machine with no previous
>> Tomcat installed. But my problem is that I have to get it to run
>> on this machine. What could I do? First uninstall all jdks and
>> Tomcats and then install jdk11 and newest Tomcat?
>> 
>> Ralf
>> 
>> Am Mo., 26. Nov. 2018, 20:59 hat Andi Meister
>>  geschrieben:
>> 
>>> Thank you. Dies this mean that I'm doing anything correctly but
>>> it just doesn't work on this machine maybe?
>>> 
>>> Ralf
>>> 
>>> 
>>> Am Mo., 26. Nov. 2018, 20:32 hat Mark Thomas
>>>  geschrieben:
>>> 
 On 26/11/2018 18:51, Andi Meister wrote:
> I guess the JDK that I used is not OpenJDK but Oracle JDK?
> That's not
 the
> same isn't it?
 
 They aren't identical but the differences aren't in any areas
 that would impact this issue. Tomcat works happily with
 both.
 
 Mark
 
 
> 
> There is a pre-story to that. Maybe there is the reason?! 
> On this server there was installed: JRE 1.6 and Tomcat 7 -
> running for years. Now there is an update planned to Java
> 11 and I have to check if it
 runs.
> 
> First, I installed the JDK 11 additionally and pointed the
 Java-location in
> Tomcat 7 configuration app to the new /bin/server/jvm.dll.
> 
> Same error as now.
> 
> Then I uninstalled Tomcat 7 and JRE 6. Then installed
> Tomcat 9. Error...
> 
> Ralf
> 
> 
> Am Mo., 26. Nov. 2018 um 18:34 Uhr schrieb Mark Thomas <
 ma...@apache.org>:
> 
>> Tomcat 9.0.13 windows installer, Open JDK 11.0.1 and
>> Window server
>> 2008
>> R2 work first time for me on a clean install.
>> 
>> This doesn't look like a Tomcat issue at this point.
>> 
>> Mark
>> 
>> 
>> 
>> On 26/11/2018 17:04, Andi Meister wrote:
>>> more detailled: 9.0.13 Core:
>>> 
>>> - zip <
>> 
 
>> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tom
cat-9.0.13.zip
>>>
>>>
>> 
(pgp
>>> <
>> 
 
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat
- -9.0.13.zip.asc
>>>
>> 
,
>>> sha512 <
>> 
 
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat
- -9.0.13.zip.sha512
>>>
>> 
)
>>> 
>>> - tar.gz <
>> 
 
>> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tom
cat-9.0.13.tar.gz
>>>
>>>
>> 
(pgp
>>> <
>> 
 
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat
- -9.0.13.tar.gz.asc
>>>
>> 
,
>>> sha512 <
>> 
 
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat
- -9.0.13.tar.gz.sha512
>>>
>> 
)
>>> 
>>> - 32-bit Windows zip <
>> 
 
>> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tom
cat-9.0.13-windows-x86.zip
>>>
>>>
>> 
(pgp
>>> <
>> 
 
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat
- -9.0.13-windows-x86.zip.asc
>>>
>> 
,
>>> sha512 <
>> 
 
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat
- -9.0.13-windows-x86.zip.sha512
>>>
>> 
)
>>> 
>>> - 64-bit Windows zip <
>> 
 
>> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tom
cat-9.0.13-windows-x64.zip
>>>
>>>
>> 
(pgp
>>> <
>> 
 
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat
- -9.0.13-windows-x64.zip.asc
>>>
>> 
,
>>> sha512 <
>> 
 
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat
- -9.0.13-windows-x64.zip.sha512
>>>
>> 
)
>>> 
>>> - 32-bit/64-bit Windows Service Installer <
>> 
 
>> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tom
cat-9.0.13.exe
>>>
>>>
>> 
(pgp
>>> <
>> 
 
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat
- -9.0.13.exe.asc
>>>
>> 
,
>>> sha512 <
>> 
 
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat
- -9.0.13.exe.sha512
>>>
>> 
)
>>>  this one
>>> 
>>> 
>>> Am Mo., 26. Nov. 2018 um 18:02 Uhr schrieb Andi Meister
>>> < blackpum...@googlemail.com>:
>>> 
 Hi Chris,
 
 this one: 32-bit/64-bit Windows Service Installer <
>> 
 
>> 

Re: Compression for Resources served through DefaultServlet

[Leon Rosenberg]

On Mon, Nov 26, 2018 at 10:27 PM Mark Thomas  wrote:

> On 26/11/2018 21:19, Leon Rosenberg wrote:
> > Good time of the day,
> >
> > I am debugging bad page insights reported by google for a mobile versus
> > desktop version of our site and I'm seeing that the static resources,
> > served by the DefaultServlet (aka files) aren't compressed, versus to
> > dynamic resources served by a servlet.
> > Tomcat version in question 8.5.15 and 8.5.31 (tested on both)
>
> http://tomcat.apache.org/tomcat-8.5-doc/config/http.html
>
> Search for sendfile.
>
> ?
>

I thought sendfile is NIO only, this was probably the mistake.

Thank you.
Leon


>
> Mark
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: Tomcat 9 does not work with Java 11

[Johan Compagner]

Do you have a commercial license with Oracle so that you can use oracle's
Java 11?

Because if you just download it from oracle's site, you can't use it at all
in a production system..

But the 2 (open or Oracle) should be quite identical from Java 11 on..

Op ma 26 nov. 2018 19:52 schreef Andi Meister
 I guess the JDK that I used is not OpenJDK but Oracle JDK? That's not the
> same isn't it?
>
> There is a pre-story to that. Maybe there is the reason?!
> On this server there was installed: JRE 1.6 and Tomcat 7 - running for
> years.
> Now there is an update planned to Java 11 and I have to check if it runs.
>
> First, I installed the JDK 11 additionally and pointed the Java-location in
> Tomcat 7 configuration app to the new /bin/server/jvm.dll.
>
> Same error as now.
>
> Then I uninstalled Tomcat 7 and JRE 6. Then installed Tomcat 9.
> Error...
>
> Ralf
>
>
> Am Mo., 26. Nov. 2018 um 18:34 Uhr schrieb Mark Thomas :
>
> > Tomcat 9.0.13 windows installer, Open JDK 11.0.1 and Window server 2008
> > R2 work first time for me on a clean install.
> >
> > This doesn't look like a Tomcat issue at this point.
> >
> > Mark
> >
> >
> >
> > On 26/11/2018 17:04, Andi Meister wrote:
> > > more detailled:
> > > 9.0.13 Core:
> > >
> > >- zip
> > ><
> >
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.zip
> > >
> > >(pgp
> > ><
> >
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.zip.asc
> > >,
> > >sha512
> > ><
> >
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.zip.sha512
> > >)
> > >
> > >- tar.gz
> > ><
> >
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.tar.gz
> > >
> > >(pgp
> > ><
> >
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.tar.gz.asc
> > >,
> > >sha512
> > ><
> >
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.tar.gz.sha512
> > >)
> > >
> > >- 32-bit Windows zip
> > ><
> >
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x86.zip
> > >
> > >(pgp
> > ><
> >
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x86.zip.asc
> > >,
> > >sha512
> > ><
> >
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x86.zip.sha512
> > >)
> > >
> > >- 64-bit Windows zip
> > ><
> >
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x64.zip
> > >
> > >(pgp
> > ><
> >
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x64.zip.asc
> > >,
> > >sha512
> > ><
> >
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x64.zip.sha512
> > >)
> > >
> > >- 32-bit/64-bit Windows Service Installer
> > ><
> >
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe
> > >
> > >(pgp
> > ><
> >
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe.asc
> > >,
> > >sha512
> > ><
> >
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe.sha512
> > >)
> > > this one
> > >
> > >
> > > Am Mo., 26. Nov. 2018 um 18:02 Uhr schrieb Andi Meister <
> > > blackpum...@googlemail.com>:
> > >
> > >> Hi Chris,
> > >>
> > >> this one:
> > >> 32-bit/64-bit Windows Service Installer
> > >> <
> >
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe
> > >
> > >>
> > >> Ralf
> > >>
> > >>
> > >> Am Mo., 26. Nov. 2018 um 16:52 Uhr schrieb Christopher Schultz <
> > >> ch...@christopherschultz.net>:
> > >>
> > > Ralf,
> > >
> > > On 11/26/18 10:39, Andi Meister wrote:
> > > Hi,
> > >
> > >
> > > I downloaded and installed Java 11 from here:
> > >
> > >
> > https://www.oracle.com/technetwork/java/javase/downloads/jdk11-downloa
> > > ds-5066655.html
> > > <
> >
> https://www.oracle.com/technetwork/java/javase/downloads/jdk11-downloads-5066655.html
> > >
> > >
> > >
> > >
> > > Then I downloaded and installed Tomcat 9 Windows service
> > > executable.
> > >
> > >
> > > During installation I was asked for the path to JRE.
> > >
> > > Java 11 does not contain a JRE anymore, so I pointed to the Java 11
> > > root directory.
> > >
> > > The installer was fine with that.
> > >
> > >
> > > But when I finally start Tomcat service, it does NOT run.
> > >
> > > In commons_deamon.log I see this error message:
> > >
> > >
> > > [2018-11-26 13:36:39] [info]  [ 3732] Running 'Tomcat9' Service...
> > >
> > > [2018-11-26 13:36:39] [info]  [ 4776] Starting service...
> > >
> > > [2018-11-26 13:36:39] [error] [ 4776] The specified procedure could
> > > not be found.
> > >
> > > [2018-11-26 13:36:39] 

Re: Tomcat 9 does not work with Java 11

[M. Manna]

if you are moving away from Java 8, I would recommmend you install java 11
first. Oracle JDK or openJDK doesn’t matter here.

Once you do that, confirm that your JAVA_HOME env var is setup correctly (
google it if you’re not sure). The go ahead with your tomcat installation
(service or standalone). See how it works for you.

Thanks,

On Mon, 26 Nov 2018 at 20:08, Andi Meister
 wrote:

> Tomorrow I will try it on an other machine with no previous Tomcat
> installed.
> But my problem is that I have to get it to run on this machine. What could
> I do? First uninstall all jdks and Tomcats and then install jdk11 and
> newest Tomcat?
>
> Ralf
>
> Am Mo., 26. Nov. 2018, 20:59 hat Andi Meister 
> geschrieben:
>
> > Thank you.
> > Dies this mean that I'm doing anything correctly but it just doesn't work
> > on this machine maybe?
> >
> > Ralf
> >
> >
> > Am Mo., 26. Nov. 2018, 20:32 hat Mark Thomas 
> > geschrieben:
> >
> >> On 26/11/2018 18:51, Andi Meister wrote:
> >> > I guess the JDK that I used is not OpenJDK but Oracle JDK? That's not
> >> the
> >> > same isn't it?
> >>
> >> They aren't identical but the differences aren't in any areas that would
> >> impact this issue. Tomcat works happily with both.
> >>
> >> Mark
> >>
> >>
> >> >
> >> > There is a pre-story to that. Maybe there is the reason?!
> >> > On this server there was installed: JRE 1.6 and Tomcat 7 - running for
> >> > years.
> >> > Now there is an update planned to Java 11 and I have to check if it
> >> runs.
> >> >
> >> > First, I installed the JDK 11 additionally and pointed the
> >> Java-location in
> >> > Tomcat 7 configuration app to the new /bin/server/jvm.dll.
> >> >
> >> > Same error as now.
> >> >
> >> > Then I uninstalled Tomcat 7 and JRE 6. Then installed Tomcat 9.
> >> > Error...
> >> >
> >> > Ralf
> >> >
> >> >
> >> > Am Mo., 26. Nov. 2018 um 18:34 Uhr schrieb Mark Thomas <
> >> ma...@apache.org>:
> >> >
> >> >> Tomcat 9.0.13 windows installer, Open JDK 11.0.1 and Window server
> 2008
> >> >> R2 work first time for me on a clean install.
> >> >>
> >> >> This doesn't look like a Tomcat issue at this point.
> >> >>
> >> >> Mark
> >> >>
> >> >>
> >> >>
> >> >> On 26/11/2018 17:04, Andi Meister wrote:
> >> >>> more detailled:
> >> >>> 9.0.13 Core:
> >> >>>
> >> >>>- zip
> >> >>><
> >> >>
> >>
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.zip
> >> >>>
> >> >>>(pgp
> >> >>><
> >> >>
> >>
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.zip.asc
> >> >>> ,
> >> >>>sha512
> >> >>><
> >> >>
> >>
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.zip.sha512
> >> >>> )
> >> >>>
> >> >>>- tar.gz
> >> >>><
> >> >>
> >>
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.tar.gz
> >> >>>
> >> >>>(pgp
> >> >>><
> >> >>
> >>
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.tar.gz.asc
> >> >>> ,
> >> >>>sha512
> >> >>><
> >> >>
> >>
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.tar.gz.sha512
> >> >>> )
> >> >>>
> >> >>>- 32-bit Windows zip
> >> >>><
> >> >>
> >>
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x86.zip
> >> >>>
> >> >>>(pgp
> >> >>><
> >> >>
> >>
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x86.zip.asc
> >> >>> ,
> >> >>>sha512
> >> >>><
> >> >>
> >>
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x86.zip.sha512
> >> >>> )
> >> >>>
> >> >>>- 64-bit Windows zip
> >> >>><
> >> >>
> >>
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x64.zip
> >> >>>
> >> >>>(pgp
> >> >>><
> >> >>
> >>
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x64.zip.asc
> >> >>> ,
> >> >>>sha512
> >> >>><
> >> >>
> >>
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x64.zip.sha512
> >> >>> )
> >> >>>
> >> >>>- 32-bit/64-bit Windows Service Installer
> >> >>><
> >> >>
> >>
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe
> >> >>>
> >> >>>(pgp
> >> >>><
> >> >>
> >>
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe.asc
> >> >>> ,
> >> >>>sha512
> >> >>><
> >> >>
> >>
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe.sha512
> >> >>> )
> >> >>> this one
> >> >>>
> >> >>>
> >> >>> Am Mo., 26. Nov. 2018 um 18:02 Uhr schrieb Andi Meister <
> >> >>> blackpum...@googlemail.com>:
> >> >>>
> >>  Hi Chris,
> >> 
> >>  this one:
> >>  32-bit/64-bit Windows Service Installer
> >>  <
> >> >>
> >>
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe
> >> >>>
> >> 
> >> 

Re: Translations update

[tomcat]

On 26.11.2018 17:01, Christopher Schultz wrote:

We were super serious, like for Apache Matou:)

:)

I like that as a (silly) name (Apache Dead?), but didn't get the
actual joke.:(


"matou" is the litteral French translation of "tomcat".
(Evokes a big tough male macho alley cat, the kind which takes no sh.. from 
anyone).


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Overriding MultiPartConfig

[Mark A. Claassen]

Thanks for the reply!

I have been working this for a while and having been failing.  There is so much 
going on here that I don't understand that I feel like such a newby.

First, when the multi-part config is in my local web.xml, everything works.  
However, if I remove that whole servlet from my web.xml, I see that Jersey 
initializes my servlet on its own first, and then my context listener tries to 
add it again and the registration object I get back from addServlet is null.

I assume that Jersey is doing this auto-configuration based on the annotations 
I use, but if this is true, why does it work when the configuration is in my 
web.xml?  The org.apache.catalina.Wrapper created in the Application has an 
Overridable property, but it is false here.

Any help would be appreciated.  Is this more of a Jersey question?

Mark Claassen
Senior Software Engineer

Donnell Systems, Inc.
130 South Main Street
Leighton Plaza Suite 375
South Bend, IN  46601
E-mail: mailto:mclaas...@ocie.net
Voice: (574)232-3784
Fax: (574)232-4014
  
---
Confidentiality Notice: OCIESERVICE
---
The contents of this e-mail message and any attachments are intended solely for 
the addressee(s) named in this message. This communication is intended to be 
and to remain confidential. If you are not the intended recipient of this 
message, or if this message has been addressed to you in error, please 
immediately alert the sender by reply e-mail and then delete this message and 
its attachments. Do not deliver, distribute, copy, disclose the contents or 
take any action in reliance upon the information contained in the communication 
or any attachments.

-Original Message-
From: Mark Thomas  
Sent: Monday, November 26, 2018 12:42 PM
To: Tomcat Users List 
Subject: Re: Overriding MultiPartConfig

On 26/11/2018 17:11, Mark A. Claassen wrote:
> I am having trouble finding a way to override my MultiPart config.  I have a 
> servlet with a configuration in the web.xml.
>   
> ...
> 
>   ...
> 
>   
> 
> However, I would like to be able to be able to configure this outside of the 
> web.xml file so it can be changed outside of the webapp directory.  Is there 
> a way to do this from the "context" in the conf/Catalina/localhost directory?

No.

> Doing it programmatically would be ok for me as well, but I can't find anyway 
> to access the multi-part config through the standard APIs.

You can only do this if you remove the entry from web.xml.

You'd need to register the servlet in a ServletContextListener and then use 
ServletContext#addServlet() and then ServletRegistration.Dynamic#
setMultipartConfig()

(along with ading any other configuration / mapping required by the servlet)

> I don't think I can use the annotation @MultipartConfig since I am writing 
> something that extends javax.ws.rs.core.Application and I need to be able to 
> configure this at startup time.

@MultipartConfig has to be added to a Servlet class and can only be changed by 
recompilation - which is more work than changing web.xml.

> I am just using Jersey, running inside of Tomcat.
> 
> Thanks!
> 
> Mark Claassen
> Senior Software Engineer
> 
> Donnell Systems, Inc.
> 130 South Main Street
> Leighton Plaza Suite 375
> South Bend, IN  46601
> E-mail: mailto:mclaas...@ocie.net
> Voice: (574)232-3784
> Fax: (574)232-4014
> 
> Disclaimer:
> The opinions provided herein do not necessarily state or reflect those 
> of Donnell Systems, Inc.(DSI). DSI makes no warranty for and assumes 
> no legal liability or responsibility for the posting.
> 
> 


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Compression for Resources served through DefaultServlet

[Mark Thomas]

On 26/11/2018 21:19, Leon Rosenberg wrote:
> Good time of the day,
> 
> I am debugging bad page insights reported by google for a mobile versus
> desktop version of our site and I'm seeing that the static resources,
> served by the DefaultServlet (aka files) aren't compressed, versus to
> dynamic resources served by a servlet.
> Tomcat version in question 8.5.15 and 8.5.31 (tested on both)

http://tomcat.apache.org/tomcat-8.5-doc/config/http.html

Search for sendfile.

?

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Compression for Resources served through DefaultServlet

[Leon Rosenberg]

Good time of the day,

I am debugging bad page insights reported by google for a mobile versus
desktop version of our site and I'm seeing that the static resources,
served by the DefaultServlet (aka files) aren't compressed, versus to
dynamic resources served by a servlet.
Tomcat version in question 8.5.15 and 8.5.31 (tested on both)

Connector setting:

There is a loadbalancer in front of the connector, but its transparent,
doesn't change anything.

Now when I request a resource like this:
https://www.mysite.com/rd/V-2.0.0-SNAPSHOT_2018-11-22T13:39:22,000/static-ext/bootstrap.css
(where rd is mapping to a servlet) the result is shown in inspect tab of
chrome as 18.K (obviously compressed) and the response headers indicate
that the file is gziped:

HTTP/1.1 200 Last-Modified: Tue, 31 Jul 02018 11:42:50 GMT Expires: Tue, 26
Nov 02019 21:15:04 GMT Content-Type: text/css Transfer-Encoding: chunked
Content-Encoding: gzip Vary: Accept-Encoding Date: Mon, 26 Nov 2018
21:15:04 GMT

If I make a request to a static file the file is not gziped:
https://www.mysite.com/static-ext/css/bootstrap.css
HTTP/1.1 200 Accept-Ranges: bytes ETag: W/"131194-1539850288000"
Last-Modified: Thu, 18 Oct 2018 08:11:28 GMT Content-Type: text/css
Content-Length: 131194 Date: Mon, 26 Nov 2018 20:53:37 GMT


Are there any specific settings to the default servlet to enable it to
support compression? Both files are css, hence they should be covered by
default compression types. Are there any other settings to try?

regards
Leon

Re: Tomcat 9 does not work with Java 11

[Andi Meister]

Tomorrow I will try it on an other machine with no previous Tomcat
installed.
But my problem is that I have to get it to run on this machine. What could
I do? First uninstall all jdks and Tomcats and then install jdk11 and
newest Tomcat?

Ralf

Am Mo., 26. Nov. 2018, 20:59 hat Andi Meister 
geschrieben:

> Thank you.
> Dies this mean that I'm doing anything correctly but it just doesn't work
> on this machine maybe?
>
> Ralf
>
>
> Am Mo., 26. Nov. 2018, 20:32 hat Mark Thomas 
> geschrieben:
>
>> On 26/11/2018 18:51, Andi Meister wrote:
>> > I guess the JDK that I used is not OpenJDK but Oracle JDK? That's not
>> the
>> > same isn't it?
>>
>> They aren't identical but the differences aren't in any areas that would
>> impact this issue. Tomcat works happily with both.
>>
>> Mark
>>
>>
>> >
>> > There is a pre-story to that. Maybe there is the reason?!
>> > On this server there was installed: JRE 1.6 and Tomcat 7 - running for
>> > years.
>> > Now there is an update planned to Java 11 and I have to check if it
>> runs.
>> >
>> > First, I installed the JDK 11 additionally and pointed the
>> Java-location in
>> > Tomcat 7 configuration app to the new /bin/server/jvm.dll.
>> >
>> > Same error as now.
>> >
>> > Then I uninstalled Tomcat 7 and JRE 6. Then installed Tomcat 9.
>> > Error...
>> >
>> > Ralf
>> >
>> >
>> > Am Mo., 26. Nov. 2018 um 18:34 Uhr schrieb Mark Thomas <
>> ma...@apache.org>:
>> >
>> >> Tomcat 9.0.13 windows installer, Open JDK 11.0.1 and Window server 2008
>> >> R2 work first time for me on a clean install.
>> >>
>> >> This doesn't look like a Tomcat issue at this point.
>> >>
>> >> Mark
>> >>
>> >>
>> >>
>> >> On 26/11/2018 17:04, Andi Meister wrote:
>> >>> more detailled:
>> >>> 9.0.13 Core:
>> >>>
>> >>>- zip
>> >>><
>> >>
>> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.zip
>> >>>
>> >>>(pgp
>> >>><
>> >>
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.zip.asc
>> >>> ,
>> >>>sha512
>> >>><
>> >>
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.zip.sha512
>> >>> )
>> >>>
>> >>>- tar.gz
>> >>><
>> >>
>> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.tar.gz
>> >>>
>> >>>(pgp
>> >>><
>> >>
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.tar.gz.asc
>> >>> ,
>> >>>sha512
>> >>><
>> >>
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.tar.gz.sha512
>> >>> )
>> >>>
>> >>>- 32-bit Windows zip
>> >>><
>> >>
>> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x86.zip
>> >>>
>> >>>(pgp
>> >>><
>> >>
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x86.zip.asc
>> >>> ,
>> >>>sha512
>> >>><
>> >>
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x86.zip.sha512
>> >>> )
>> >>>
>> >>>- 64-bit Windows zip
>> >>><
>> >>
>> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x64.zip
>> >>>
>> >>>(pgp
>> >>><
>> >>
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x64.zip.asc
>> >>> ,
>> >>>sha512
>> >>><
>> >>
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x64.zip.sha512
>> >>> )
>> >>>
>> >>>- 32-bit/64-bit Windows Service Installer
>> >>><
>> >>
>> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe
>> >>>
>> >>>(pgp
>> >>><
>> >>
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe.asc
>> >>> ,
>> >>>sha512
>> >>><
>> >>
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe.sha512
>> >>> )
>> >>> this one
>> >>>
>> >>>
>> >>> Am Mo., 26. Nov. 2018 um 18:02 Uhr schrieb Andi Meister <
>> >>> blackpum...@googlemail.com>:
>> >>>
>>  Hi Chris,
>> 
>>  this one:
>>  32-bit/64-bit Windows Service Installer
>>  <
>> >>
>> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe
>> >>>
>> 
>>  Ralf
>> 
>> 
>>  Am Mo., 26. Nov. 2018 um 16:52 Uhr schrieb Christopher Schultz <
>>  ch...@christopherschultz.net>:
>> 
>> >>> Ralf,
>> >>>
>> >>> On 11/26/18 10:39, Andi Meister wrote:
>> >>> Hi,
>> >>>
>> >>>
>> >>> I downloaded and installed Java 11 from here:
>> >>>
>> >>>
>> >> https://www.oracle.com/technetwork/java/javase/downloads/jdk11-downloa
>> >>> ds-5066655.html
>> >>> <
>> >>
>> https://www.oracle.com/technetwork/java/javase/downloads/jdk11-downloads-5066655.html
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> Then I downloaded and installed Tomcat 9 Windows service
>> >>> executable.
>> >>>
>> >>>
>> >>> During installation I was asked for the path to 

Re: Tomcat 9 does not work with Java 11

[Andi Meister]

Thank you.
Dies this mean that I'm doing anything correctly but it just doesn't work
on this machine maybe?

Ralf


Am Mo., 26. Nov. 2018, 20:32 hat Mark Thomas  geschrieben:

> On 26/11/2018 18:51, Andi Meister wrote:
> > I guess the JDK that I used is not OpenJDK but Oracle JDK? That's not the
> > same isn't it?
>
> They aren't identical but the differences aren't in any areas that would
> impact this issue. Tomcat works happily with both.
>
> Mark
>
>
> >
> > There is a pre-story to that. Maybe there is the reason?!
> > On this server there was installed: JRE 1.6 and Tomcat 7 - running for
> > years.
> > Now there is an update planned to Java 11 and I have to check if it runs.
> >
> > First, I installed the JDK 11 additionally and pointed the Java-location
> in
> > Tomcat 7 configuration app to the new /bin/server/jvm.dll.
> >
> > Same error as now.
> >
> > Then I uninstalled Tomcat 7 and JRE 6. Then installed Tomcat 9.
> > Error...
> >
> > Ralf
> >
> >
> > Am Mo., 26. Nov. 2018 um 18:34 Uhr schrieb Mark Thomas  >:
> >
> >> Tomcat 9.0.13 windows installer, Open JDK 11.0.1 and Window server 2008
> >> R2 work first time for me on a clean install.
> >>
> >> This doesn't look like a Tomcat issue at this point.
> >>
> >> Mark
> >>
> >>
> >>
> >> On 26/11/2018 17:04, Andi Meister wrote:
> >>> more detailled:
> >>> 9.0.13 Core:
> >>>
> >>>- zip
> >>><
> >>
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.zip
> >>>
> >>>(pgp
> >>><
> >>
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.zip.asc
> >>> ,
> >>>sha512
> >>><
> >>
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.zip.sha512
> >>> )
> >>>
> >>>- tar.gz
> >>><
> >>
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.tar.gz
> >>>
> >>>(pgp
> >>><
> >>
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.tar.gz.asc
> >>> ,
> >>>sha512
> >>><
> >>
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.tar.gz.sha512
> >>> )
> >>>
> >>>- 32-bit Windows zip
> >>><
> >>
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x86.zip
> >>>
> >>>(pgp
> >>><
> >>
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x86.zip.asc
> >>> ,
> >>>sha512
> >>><
> >>
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x86.zip.sha512
> >>> )
> >>>
> >>>- 64-bit Windows zip
> >>><
> >>
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x64.zip
> >>>
> >>>(pgp
> >>><
> >>
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x64.zip.asc
> >>> ,
> >>>sha512
> >>><
> >>
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x64.zip.sha512
> >>> )
> >>>
> >>>- 32-bit/64-bit Windows Service Installer
> >>><
> >>
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe
> >>>
> >>>(pgp
> >>><
> >>
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe.asc
> >>> ,
> >>>sha512
> >>><
> >>
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe.sha512
> >>> )
> >>> this one
> >>>
> >>>
> >>> Am Mo., 26. Nov. 2018 um 18:02 Uhr schrieb Andi Meister <
> >>> blackpum...@googlemail.com>:
> >>>
>  Hi Chris,
> 
>  this one:
>  32-bit/64-bit Windows Service Installer
>  <
> >>
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe
> >>>
> 
>  Ralf
> 
> 
>  Am Mo., 26. Nov. 2018 um 16:52 Uhr schrieb Christopher Schultz <
>  ch...@christopherschultz.net>:
> 
> >>> Ralf,
> >>>
> >>> On 11/26/18 10:39, Andi Meister wrote:
> >>> Hi,
> >>>
> >>>
> >>> I downloaded and installed Java 11 from here:
> >>>
> >>>
> >> https://www.oracle.com/technetwork/java/javase/downloads/jdk11-downloa
> >>> ds-5066655.html
> >>> <
> >>
> https://www.oracle.com/technetwork/java/javase/downloads/jdk11-downloads-5066655.html
> >>>
> >>>
> >>>
> >>>
> >>> Then I downloaded and installed Tomcat 9 Windows service
> >>> executable.
> >>>
> >>>
> >>> During installation I was asked for the path to JRE.
> >>>
> >>> Java 11 does not contain a JRE anymore, so I pointed to the Java 11
> >>> root directory.
> >>>
> >>> The installer was fine with that.
> >>>
> >>>
> >>> But when I finally start Tomcat service, it does NOT run.
> >>>
> >>> In commons_deamon.log I see this error message:
> >>>
> >>>
> >>> [2018-11-26 13:36:39] [info]  [ 3732] Running 'Tomcat9' Service...
> >>>
> >>> [2018-11-26 13:36:39] [info]  [ 4776] Starting service...
> >>>
> 

Re: Tomcat 9 does not work with Java 11

[Mark Thomas]

On 26/11/2018 18:51, Andi Meister wrote:
> I guess the JDK that I used is not OpenJDK but Oracle JDK? That's not the
> same isn't it?

They aren't identical but the differences aren't in any areas that would
impact this issue. Tomcat works happily with both.

Mark


> 
> There is a pre-story to that. Maybe there is the reason?!
> On this server there was installed: JRE 1.6 and Tomcat 7 - running for
> years.
> Now there is an update planned to Java 11 and I have to check if it runs.
> 
> First, I installed the JDK 11 additionally and pointed the Java-location in
> Tomcat 7 configuration app to the new /bin/server/jvm.dll.
> 
> Same error as now.
> 
> Then I uninstalled Tomcat 7 and JRE 6. Then installed Tomcat 9.
> Error...
> 
> Ralf
> 
> 
> Am Mo., 26. Nov. 2018 um 18:34 Uhr schrieb Mark Thomas :
> 
>> Tomcat 9.0.13 windows installer, Open JDK 11.0.1 and Window server 2008
>> R2 work first time for me on a clean install.
>>
>> This doesn't look like a Tomcat issue at this point.
>>
>> Mark
>>
>>
>>
>> On 26/11/2018 17:04, Andi Meister wrote:
>>> more detailled:
>>> 9.0.13 Core:
>>>
>>>- zip
>>><
>> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.zip
>>>
>>>(pgp
>>><
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.zip.asc
>>> ,
>>>sha512
>>><
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.zip.sha512
>>> )
>>>
>>>- tar.gz
>>><
>> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.tar.gz
>>>
>>>(pgp
>>><
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.tar.gz.asc
>>> ,
>>>sha512
>>><
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.tar.gz.sha512
>>> )
>>>
>>>- 32-bit Windows zip
>>><
>> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x86.zip
>>>
>>>(pgp
>>><
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x86.zip.asc
>>> ,
>>>sha512
>>><
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x86.zip.sha512
>>> )
>>>
>>>- 64-bit Windows zip
>>><
>> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x64.zip
>>>
>>>(pgp
>>><
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x64.zip.asc
>>> ,
>>>sha512
>>><
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x64.zip.sha512
>>> )
>>>
>>>- 32-bit/64-bit Windows Service Installer
>>><
>> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe
>>>
>>>(pgp
>>><
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe.asc
>>> ,
>>>sha512
>>><
>> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe.sha512
>>> )
>>> this one
>>>
>>>
>>> Am Mo., 26. Nov. 2018 um 18:02 Uhr schrieb Andi Meister <
>>> blackpum...@googlemail.com>:
>>>
 Hi Chris,

 this one:
 32-bit/64-bit Windows Service Installer
 <
>> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe
>>>

 Ralf


 Am Mo., 26. Nov. 2018 um 16:52 Uhr schrieb Christopher Schultz <
 ch...@christopherschultz.net>:

>>> Ralf,
>>>
>>> On 11/26/18 10:39, Andi Meister wrote:
>>> Hi,
>>>
>>>
>>> I downloaded and installed Java 11 from here:
>>>
>>>
>> https://www.oracle.com/technetwork/java/javase/downloads/jdk11-downloa
>>> ds-5066655.html
>>> <
>> https://www.oracle.com/technetwork/java/javase/downloads/jdk11-downloads-5066655.html
>>>
>>>
>>>
>>>
>>> Then I downloaded and installed Tomcat 9 Windows service
>>> executable.
>>>
>>>
>>> During installation I was asked for the path to JRE.
>>>
>>> Java 11 does not contain a JRE anymore, so I pointed to the Java 11
>>> root directory.
>>>
>>> The installer was fine with that.
>>>
>>>
>>> But when I finally start Tomcat service, it does NOT run.
>>>
>>> In commons_deamon.log I see this error message:
>>>
>>>
>>> [2018-11-26 13:36:39] [info]  [ 3732] Running 'Tomcat9' Service...
>>>
>>> [2018-11-26 13:36:39] [info]  [ 4776] Starting service...
>>>
>>> [2018-11-26 13:36:39] [error] [ 4776] The specified procedure could
>>> not be found.
>>>
>>> [2018-11-26 13:36:39] [error] [ 4776] Failed creating Java
>>> C:\Program Files\Java\jdk-11.0.1\bin\server\jvm.dll
>>>
>>> [2018-11-26 13:36:39] [error] [ 4776] The specified procedure could
>>> not be found.
>>>
>>> [2018-11-26 13:36:39] [error] [ 4776] ServiceStart returned 1
>>>
>>> [2018-11-26 13:36:39] [error] [ 4776] The specified procedure could
>>> not be found.
>>>

Re: Tomcat 9 does not work with Java 11

[Andi Meister]

I guess the JDK that I used is not OpenJDK but Oracle JDK? That's not the
same isn't it?

There is a pre-story to that. Maybe there is the reason?!
On this server there was installed: JRE 1.6 and Tomcat 7 - running for
years.
Now there is an update planned to Java 11 and I have to check if it runs.

First, I installed the JDK 11 additionally and pointed the Java-location in
Tomcat 7 configuration app to the new /bin/server/jvm.dll.

Same error as now.

Then I uninstalled Tomcat 7 and JRE 6. Then installed Tomcat 9.
Error...

Ralf


Am Mo., 26. Nov. 2018 um 18:34 Uhr schrieb Mark Thomas :

> Tomcat 9.0.13 windows installer, Open JDK 11.0.1 and Window server 2008
> R2 work first time for me on a clean install.
>
> This doesn't look like a Tomcat issue at this point.
>
> Mark
>
>
>
> On 26/11/2018 17:04, Andi Meister wrote:
> > more detailled:
> > 9.0.13 Core:
> >
> >- zip
> ><
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.zip
> >
> >(pgp
> ><
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.zip.asc
> >,
> >sha512
> ><
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.zip.sha512
> >)
> >
> >- tar.gz
> ><
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.tar.gz
> >
> >(pgp
> ><
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.tar.gz.asc
> >,
> >sha512
> ><
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.tar.gz.sha512
> >)
> >
> >- 32-bit Windows zip
> ><
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x86.zip
> >
> >(pgp
> ><
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x86.zip.asc
> >,
> >sha512
> ><
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x86.zip.sha512
> >)
> >
> >- 64-bit Windows zip
> ><
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x64.zip
> >
> >(pgp
> ><
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x64.zip.asc
> >,
> >sha512
> ><
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x64.zip.sha512
> >)
> >
> >- 32-bit/64-bit Windows Service Installer
> ><
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe
> >
> >(pgp
> ><
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe.asc
> >,
> >sha512
> ><
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe.sha512
> >)
> > this one
> >
> >
> > Am Mo., 26. Nov. 2018 um 18:02 Uhr schrieb Andi Meister <
> > blackpum...@googlemail.com>:
> >
> >> Hi Chris,
> >>
> >> this one:
> >> 32-bit/64-bit Windows Service Installer
> >> <
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe
> >
> >>
> >> Ralf
> >>
> >>
> >> Am Mo., 26. Nov. 2018 um 16:52 Uhr schrieb Christopher Schultz <
> >> ch...@christopherschultz.net>:
> >>
> > Ralf,
> >
> > On 11/26/18 10:39, Andi Meister wrote:
> > Hi,
> >
> >
> > I downloaded and installed Java 11 from here:
> >
> >
> https://www.oracle.com/technetwork/java/javase/downloads/jdk11-downloa
> > ds-5066655.html
> > <
> https://www.oracle.com/technetwork/java/javase/downloads/jdk11-downloads-5066655.html
> >
> >
> >
> >
> > Then I downloaded and installed Tomcat 9 Windows service
> > executable.
> >
> >
> > During installation I was asked for the path to JRE.
> >
> > Java 11 does not contain a JRE anymore, so I pointed to the Java 11
> > root directory.
> >
> > The installer was fine with that.
> >
> >
> > But when I finally start Tomcat service, it does NOT run.
> >
> > In commons_deamon.log I see this error message:
> >
> >
> > [2018-11-26 13:36:39] [info]  [ 3732] Running 'Tomcat9' Service...
> >
> > [2018-11-26 13:36:39] [info]  [ 4776] Starting service...
> >
> > [2018-11-26 13:36:39] [error] [ 4776] The specified procedure could
> > not be found.
> >
> > [2018-11-26 13:36:39] [error] [ 4776] Failed creating Java
> > C:\Program Files\Java\jdk-11.0.1\bin\server\jvm.dll
> >
> > [2018-11-26 13:36:39] [error] [ 4776] The specified procedure could
> > not be found.
> >
> > [2018-11-26 13:36:39] [error] [ 4776] ServiceStart returned 1
> >
> > [2018-11-26 13:36:39] [error] [ 4776] The specified procedure could
> > not be found.
> >
> > [2018-11-26 13:36:39] [info]  [ 3732] Run service finished.
> >
> >
> >
> > What can I do to get this run?
> >
> >
> > Operating System:
> >
> > Windows Server 2008 R2
> >
> > Which Tomcat installer package did 

Re: Tomcat 9 does not work with Java 11

[M. Manna]

Tomcat 9 doesn’t use any module that’s restricted by OOB openJDK.

It seems like a path issue to me.



On Mon, 26 Nov 2018 at 17:34, Mark Thomas  wrote:

> Tomcat 9.0.13 windows installer, Open JDK 11.0.1 and Window server 2008
> R2 work first time for me on a clean install.
>
> This doesn't look like a Tomcat issue at this point.
>
> Mark
>
>
>
> On 26/11/2018 17:04, Andi Meister wrote:
> > more detailled:
> > 9.0.13 Core:
> >
> >- zip
> ><
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.zip
> >
> >(pgp
> ><
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.zip.asc
> >,
> >sha512
> ><
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.zip.sha512
> >)
> >
> >- tar.gz
> ><
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.tar.gz
> >
> >(pgp
> ><
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.tar.gz.asc
> >,
> >sha512
> ><
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.tar.gz.sha512
> >)
> >
> >- 32-bit Windows zip
> ><
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x86.zip
> >
> >(pgp
> ><
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x86.zip.asc
> >,
> >sha512
> ><
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x86.zip.sha512
> >)
> >
> >- 64-bit Windows zip
> ><
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x64.zip
> >
> >(pgp
> ><
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x64.zip.asc
> >,
> >sha512
> ><
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13-windows-x64.zip.sha512
> >)
> >
> >- 32-bit/64-bit Windows Service Installer
> ><
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe
> >
> >(pgp
> ><
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe.asc
> >,
> >sha512
> ><
> https://www.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe.sha512
> >)
> > this one
> >
> >
> > Am Mo., 26. Nov. 2018 um 18:02 Uhr schrieb Andi Meister <
> > blackpum...@googlemail.com>:
> >
> >> Hi Chris,
> >>
> >> this one:
> >> 32-bit/64-bit Windows Service Installer
> >> <
> https://www-us.apache.org/dist/tomcat/tomcat-9/v9.0.13/bin/apache-tomcat-9.0.13.exe
> >
> >>
> >> Ralf
> >>
> >>
> >> Am Mo., 26. Nov. 2018 um 16:52 Uhr schrieb Christopher Schultz <
> >> ch...@christopherschultz.net>:
> >>
> > Ralf,
> >
> > On 11/26/18 10:39, Andi Meister wrote:
> > Hi,
> >
> >
> > I downloaded and installed Java 11 from here:
> >
> >
> https://www.oracle.com/technetwork/java/javase/downloads/jdk11-downloa
> > ds-5066655.html
> > <
> https://www.oracle.com/technetwork/java/javase/downloads/jdk11-downloads-5066655.html
> >
> >
> >
> >
> > Then I downloaded and installed Tomcat 9 Windows service
> > executable.
> >
> >
> > During installation I was asked for the path to JRE.
> >
> > Java 11 does not contain a JRE anymore, so I pointed to the Java 11
> > root directory.
> >
> > The installer was fine with that.
> >
> >
> > But when I finally start Tomcat service, it does NOT run.
> >
> > In commons_deamon.log I see this error message:
> >
> >
> > [2018-11-26 13:36:39] [info]  [ 3732] Running 'Tomcat9' Service...
> >
> > [2018-11-26 13:36:39] [info]  [ 4776] Starting service...
> >
> > [2018-11-26 13:36:39] [error] [ 4776] The specified procedure could
> > not be found.
> >
> > [2018-11-26 13:36:39] [error] [ 4776] Failed creating Java
> > C:\Program Files\Java\jdk-11.0.1\bin\server\jvm.dll
> >
> > [2018-11-26 13:36:39] [error] [ 4776] The specified procedure could
> > not be found.
> >
> > [2018-11-26 13:36:39] [error] [ 4776] ServiceStart returned 1
> >
> > [2018-11-26 13:36:39] [error] [ 4776] The specified procedure could
> > not be found.
> >
> > [2018-11-26 13:36:39] [info]  [ 3732] Run service finished.
> >
> >
> >
> > What can I do to get this run?
> >
> >
> > Operating System:
> >
> > Windows Server 2008 R2
> >
> > Which Tomcat installer package did you download?
> >
> > -chris
> >>>
> >>> -
> >>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> >>> For additional commands, e-mail: users-h...@tomcat.apache.org
> >>>
> >>>
> >
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: 

Re: Overriding MultiPartConfig

[Mark Thomas]

On 26/11/2018 17:11, Mark A. Claassen wrote:
> I am having trouble finding a way to override my MultiPart config.  I have a 
> servlet with a configuration in the web.xml.
>   
> ...
> 
>   ...
> 
>   
> 
> However, I would like to be able to be able to configure this outside of the 
> web.xml file so it can be changed outside of the webapp directory.  Is there 
> a way to do this from the "context" in the conf/Catalina/localhost directory?

No.

> Doing it programmatically would be ok for me as well, but I can't find anyway 
> to access the multi-part config through the standard APIs.

You can only do this if you remove the entry from web.xml.

You'd need to register the servlet in a ServletContextListener and then
use ServletContext#addServlet() and then ServletRegistration.Dynamic#
setMultipartConfig()

(along with ading any other configuration / mapping required by the servlet)

> I don't think I can use the annotation @MultipartConfig since I am writing 
> something that extends javax.ws.rs.core.Application and I need to be able to 
> configure this at startup time.

@MultipartConfig has to be added to a Servlet class and can only be
changed by recompilation - which is more work than changing web.xml.

> I am just using Jersey, running inside of Tomcat.
> 
> Thanks!
> 
> Mark Claassen
> Senior Software Engineer
> 
> Donnell Systems, Inc.
> 130 South Main Street
> Leighton Plaza Suite 375
> South Bend, IN  46601
> E-mail: mailto:mclaas...@ocie.net
> Voice: (574)232-3784
> Fax: (574)232-4014
> 
> Disclaimer:
> The opinions provided herein do not necessarily state or reflect
> those of Donnell Systems, Inc.(DSI). DSI makes no warranty for and
> assumes no legal liability or responsibility for the posting.
> 
> 


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 9 does not work with Java 11

[Mark Thomas]

Tomcat 9.0.13 windows installer, Open JDK 11.0.1 and Window server 2008
R2 work first time for me on a clean install.

This doesn't look like a Tomcat issue at this point.

Mark



On 26/11/2018 17:04, Andi Meister wrote:
> more detailled:
> 9.0.13 Core:
> 
>- zip
>
> 
>(pgp
>
> ,
>sha512
>
> )
> 
>- tar.gz
>
> 
>(pgp
>
> ,
>sha512
>
> )
> 
>- 32-bit Windows zip
>
> 
>(pgp
>
> ,
>sha512
>
> )
> 
>- 64-bit Windows zip
>
> 
>(pgp
>
> ,
>sha512
>
> )
> 
>- 32-bit/64-bit Windows Service Installer
>
> 
>(pgp
>
> ,
>sha512
>
> )
> this one
> 
> 
> Am Mo., 26. Nov. 2018 um 18:02 Uhr schrieb Andi Meister <
> blackpum...@googlemail.com>:
> 
>> Hi Chris,
>>
>> this one:
>> 32-bit/64-bit Windows Service Installer
>> 
>>
>> Ralf
>>
>>
>> Am Mo., 26. Nov. 2018 um 16:52 Uhr schrieb Christopher Schultz <
>> ch...@christopherschultz.net>:
>>
> Ralf,
> 
> On 11/26/18 10:39, Andi Meister wrote:
> Hi,
>
>
> I downloaded and installed Java 11 from here:
>
> https://www.oracle.com/technetwork/java/javase/downloads/jdk11-downloa
> ds-5066655.html
> 
>
>
>
> Then I downloaded and installed Tomcat 9 Windows service
> executable.
>
>
> During installation I was asked for the path to JRE.
>
> Java 11 does not contain a JRE anymore, so I pointed to the Java 11
> root directory.
>
> The installer was fine with that.
>
>
> But when I finally start Tomcat service, it does NOT run.
>
> In commons_deamon.log I see this error message:
>
>
> [2018-11-26 13:36:39] [info]  [ 3732] Running 'Tomcat9' Service...
>
> [2018-11-26 13:36:39] [info]  [ 4776] Starting service...
>
> [2018-11-26 13:36:39] [error] [ 4776] The specified procedure could
> not be found.
>
> [2018-11-26 13:36:39] [error] [ 4776] Failed creating Java
> C:\Program Files\Java\jdk-11.0.1\bin\server\jvm.dll
>
> [2018-11-26 13:36:39] [error] [ 4776] The specified procedure could
> not be found.
>
> [2018-11-26 13:36:39] [error] [ 4776] ServiceStart returned 1
>
> [2018-11-26 13:36:39] [error] [ 4776] The specified procedure could
> not be found.
>
> [2018-11-26 13:36:39] [info]  [ 3732] Run service finished.
>
>
>
> What can I do to get this run?
>
>
> Operating System:
>
> Windows Server 2008 R2
> 
> Which Tomcat installer package did you download?
> 
> -chris
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>>
>>>
> 


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Overriding MultiPartConfig

[Mark A. Claassen]

I am having trouble finding a way to override my MultiPart config.  I have a 
servlet with a configuration in the web.xml.
  
...

  ...

  

However, I would like to be able to be able to configure this outside of the 
web.xml file so it can be changed outside of the webapp directory.  Is there a 
way to do this from the "context" in the conf/Catalina/localhost directory?
Doing it programmatically would be ok for me as well, but I can't find anyway 
to access the multi-part config through the standard APIs.

I don't think I can use the annotation @MultipartConfig since I am writing 
something that extends javax.ws.rs.core.Application and I need to be able to 
configure this at startup time.

I am just using Jersey, running inside of Tomcat.

Thanks!

Mark Claassen
Senior Software Engineer

Donnell Systems, Inc.
130 South Main Street
Leighton Plaza Suite 375
South Bend, IN  46601
E-mail: mailto:mclaas...@ocie.net
Voice: (574)232-3784
Fax: (574)232-4014

Disclaimer:
The opinions provided herein do not necessarily state or reflect
those of Donnell Systems, Inc.(DSI). DSI makes no warranty for and
assumes no legal liability or responsibility for the posting.

Re: Tomcat 9 does not work with Java 11

[Andi Meister]

more detailled:
9.0.13 Core:

   - zip
   

   (pgp
   
,
   sha512
   
)

   - tar.gz
   

   (pgp
   
,
   sha512
   
)

   - 32-bit Windows zip
   

   (pgp
   
,
   sha512
   
)

   - 64-bit Windows zip
   

   (pgp
   
,
   sha512
   
)

   - 32-bit/64-bit Windows Service Installer
   

   (pgp
   
,
   sha512
   
)
    this one


Am Mo., 26. Nov. 2018 um 18:02 Uhr schrieb Andi Meister <
blackpum...@googlemail.com>:

> Hi Chris,
>
> this one:
> 32-bit/64-bit Windows Service Installer
> 
>
> Ralf
>
>
> Am Mo., 26. Nov. 2018 um 16:52 Uhr schrieb Christopher Schultz <
> ch...@christopherschultz.net>:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> Ralf,
>>
>> On 11/26/18 10:39, Andi Meister wrote:
>> > Hi,
>> >
>> >
>> > I downloaded and installed Java 11 from here:
>> >
>> > https://www.oracle.com/technetwork/java/javase/downloads/jdk11-downloa
>> ds-5066655.html
>> 
>> >
>> >
>> >
>> > Then I downloaded and installed Tomcat 9 Windows service
>> > executable.
>> >
>> >
>> > During installation I was asked for the path to JRE.
>> >
>> > Java 11 does not contain a JRE anymore, so I pointed to the Java 11
>> > root directory.
>> >
>> > The installer was fine with that.
>> >
>> >
>> > But when I finally start Tomcat service, it does NOT run.
>> >
>> > In commons_deamon.log I see this error message:
>> >
>> >
>> > [2018-11-26 13:36:39] [info]  [ 3732] Running 'Tomcat9' Service...
>> >
>> > [2018-11-26 13:36:39] [info]  [ 4776] Starting service...
>> >
>> > [2018-11-26 13:36:39] [error] [ 4776] The specified procedure could
>> > not be found.
>> >
>> > [2018-11-26 13:36:39] [error] [ 4776] Failed creating Java
>> > C:\Program Files\Java\jdk-11.0.1\bin\server\jvm.dll
>> >
>> > [2018-11-26 13:36:39] [error] [ 4776] The specified procedure could
>> > not be found.
>> >
>> > [2018-11-26 13:36:39] [error] [ 4776] ServiceStart returned 1
>> >
>> > [2018-11-26 13:36:39] [error] [ 4776] The specified procedure could
>> > not be found.
>> >
>> > [2018-11-26 13:36:39] [info]  [ 3732] Run service finished.
>> >
>> >
>> >
>> > What can I do to get this run?
>> >
>> >
>> > Operating System:
>> >
>> > Windows Server 2008 R2
>>
>> Which Tomcat installer package did you download?
>>
>> - -chris
>> -BEGIN PGP SIGNATURE-
>> Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
>>
>> iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlv8Fr0ACgkQHPApP6U8
>> pFgYMg/+O3RW95N/U1ZWkk1WCkevcTHLqDQio41+LYUegvidEtzOxFb7uf1bcA8A
>> KhPqghGnM9cp9QEcyutQIsAEt1+YWB/d71DoKwGnewxr+K+1nF3VxCgV3gYLz5vP
>> k+7LtWkaQuen5nzEGkWTWIurdBhO7cgmn+rtcrVuhPFLGizlwf9EN2C4D1aaHBKl
>> WSkdiouBZ3O4XZ1LKiNw0HfO/wNWZ1QekvnKu7YMiucBRBMUMBCUEyy8pkUkFglx
>> nGi/Tx3Jr/rC+zlPNHRtbB/r5wIly6wnaVMkt90EtH727KKuRoeZtrNIc/B7xv9B
>> I3Co6KqxuZGVxhB3m1Zz7ag5ZAmm+11x2dhlPTClUMhMcr0mdpyar7WrYfyCky+p
>> kqpqyLI9YbwY+HZQZRpzTXfN+R0YNBI80/o+6Ys87ydydssu57utH5UWKSLhXU/Z
>> csK1uvTPjqaK10zLUfMvVXu4WScHG8f6Iw10nMrELyLsI8W4MXsHLxsnCwiWPfcH
>> y43+AuscZi+9Sp6dQBDv9BYq2vzxtq6wLM7jdJ4DuU83J0mF7xCktZnOC9rEsGxY
>> ZmejlgizAi8Sb3+fSBAomIjc7KwElvBKop2ItVgvMKbXu+gbOdsA1EUJhzsyCSR0
>> A93dekV3djlfkQ/rn688Bl69Oqw+Qjh87OaZplbgxRDhOjhq0fs=
>> =fDkT
>> -END PGP SIGNATURE-
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>>

Re: Connection pool and parallel deployment problem

[Chris Cheshire]

On Mon, Nov 26, 2018 at 9:58 AM Gilles SCHLIENGER
 wrote:
>
> Hi,
> I understand your needs, but what is your problem, since you don't use 
> parallel deployment ?
> Your connections are not closed but they will not be recreated when you 
> deploy your webapp again, so there should be no problem ?
>
> Gilles
>

I added my 2c because I am seeing what you describe here

> > - I undeploy the first version of the webapp
> > - I check on my postgresql and mysql database and all connections are still 
> > opened (even if I wait for a long time)


Yes I know you are using parallel deployment and I am not, but that
doesn't necessarily mean that the problem you see is limited to only
parallel deployment. Maybe the problem can be simplified to "
Tomcat considers the connections closed, the database doesn't."

I could well be wrong, I'll leave it up to the gurus to decide :)


> -Message d'origine-
> De : Chris Cheshire [mailto:yahoono...@gmail.com]
> Envoyé : lundi 26 novembre 2018 15:27
> À : Tomcat Users List
> Objet : Re: Connection pool and parallel deployment problem
>
> I'm interested in what solution there is for this because I have the
> exact same problem but without parallel deployment.
>
> [snip]
>
> On Mon, Nov 26, 2018 at 3:54 AM Gilles SCHLIENGER
>  wrote:
> >
> > Hi Christopher,
> >
> > Thanks for your email.
> >
> > About connection pools not being closed, maybe the connection pool is 
> > closed but the connections to the database are not.
> >
> > Here are the tests I did:
> >
> > + TEST 1:
> > - I deploy my war
> > - I login to my webapp
> > - I check on my postgresql and mysql database that connections have been 
> > opened (select...)
> > - I undeploy my webapp through the manager webapp
> > - I check that the connections are still opened
> > - Tomcat is still running
> > - I redeploy the exact samed webapp and login to my application
> > - No other connection is being opened
> >
> > + TEST 2:
> > - I deploy my war
> > - I login to my webapp
> > - I check on my postgresql and mysql database that connections have been 
> > opened (select...)
> > - I deploy a new version of my application and login with another browser
> > - I check on my postgresql and mysql database that new connexions have been 
> > opened (they doubled)
> > - I undeploy the first version of the webapp
> > - I check on my postgresql and mysql database and all connections are still 
> > opened (even if I wait for a long time)
> >
> > For tests 1 and 2, I used C3p0, DBCP2 and even HikariCP
> >
>
>
> My results are the same. Using mysql, connection pools defined in
> server.xml (for user realm for access control to host manager app) and
> in my context.xml for my application. When I use the host-manager to
> reload an app, the connections are closed (no abandoned connection
> warnings) but not released. It is no until I stop tomcat completely
> and restart it that the connections are released in mysql. This has
> been the case for tomcat 7, 8.5 and 9 versions, with constant updates
> of mysql 5.7 and its driver, using both the apache connection pool and
> the tomcat connection pool. The driver lives in the tomcat/lib
> directory (since it is needed for the user realm datasource).
>
>
> > -Message d'origine-
> > De : Christopher Schultz [mailto:ch...@christopherschultz.net]
> > Envoyé : samedi 24 novembre 2018 17:19
> > À : users@tomcat.apache.org
> > Objet : Re: Connection pool and parallel deployment problem
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > Gilles,
> >
> > On 11/23/18 05:07, Gilles SCHLIENGER wrote:
>
> [snip]
>
> >
> > > The warning/error messages are not actually linked to the
> > > connexions not closed. To ovoid these messages, you can: - move the
> > > jars (connexion pool, drivers...) into TOMCAT/lib - Have a
> > > ServletContextListener that calls
> > > AbandonedConnectionCleanupThread.checkedShutdown();
> >
> > The Connector/J devs haven't been able to understand how ClassLoaders
> > work, and have never really fixed that long-standing bug in a
> > satisfying way as far as I know. But you should always use a
> > ServletContextListener to attempt to shut-down the
> > AbadonedConnectionCleanuopThread.
> >
> > BTW that thread does not work as documented. It's claimed that it
> > doesn't start unless you issue a query with a timeout, but it always
> > starts whether or not you use queries with timeouts. It's frustrating.
> >
>
> Should we be using checked or unchecked shutdown?
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 9 does not work with Java 11

[Andi Meister]

Hi Chris,

this one:
32-bit/64-bit Windows Service Installer


Ralf


Am Mo., 26. Nov. 2018 um 16:52 Uhr schrieb Christopher Schultz <
ch...@christopherschultz.net>:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Ralf,
>
> On 11/26/18 10:39, Andi Meister wrote:
> > Hi,
> >
> >
> > I downloaded and installed Java 11 from here:
> >
> > https://www.oracle.com/technetwork/java/javase/downloads/jdk11-downloa
> ds-5066655.html
> 
> >
> >
> >
> > Then I downloaded and installed Tomcat 9 Windows service
> > executable.
> >
> >
> > During installation I was asked for the path to JRE.
> >
> > Java 11 does not contain a JRE anymore, so I pointed to the Java 11
> > root directory.
> >
> > The installer was fine with that.
> >
> >
> > But when I finally start Tomcat service, it does NOT run.
> >
> > In commons_deamon.log I see this error message:
> >
> >
> > [2018-11-26 13:36:39] [info]  [ 3732] Running 'Tomcat9' Service...
> >
> > [2018-11-26 13:36:39] [info]  [ 4776] Starting service...
> >
> > [2018-11-26 13:36:39] [error] [ 4776] The specified procedure could
> > not be found.
> >
> > [2018-11-26 13:36:39] [error] [ 4776] Failed creating Java
> > C:\Program Files\Java\jdk-11.0.1\bin\server\jvm.dll
> >
> > [2018-11-26 13:36:39] [error] [ 4776] The specified procedure could
> > not be found.
> >
> > [2018-11-26 13:36:39] [error] [ 4776] ServiceStart returned 1
> >
> > [2018-11-26 13:36:39] [error] [ 4776] The specified procedure could
> > not be found.
> >
> > [2018-11-26 13:36:39] [info]  [ 3732] Run service finished.
> >
> >
> >
> > What can I do to get this run?
> >
> >
> > Operating System:
> >
> > Windows Server 2008 R2
>
> Which Tomcat installer package did you download?
>
> - -chris
> -BEGIN PGP SIGNATURE-
> Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
>
> iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlv8Fr0ACgkQHPApP6U8
> pFgYMg/+O3RW95N/U1ZWkk1WCkevcTHLqDQio41+LYUegvidEtzOxFb7uf1bcA8A
> KhPqghGnM9cp9QEcyutQIsAEt1+YWB/d71DoKwGnewxr+K+1nF3VxCgV3gYLz5vP
> k+7LtWkaQuen5nzEGkWTWIurdBhO7cgmn+rtcrVuhPFLGizlwf9EN2C4D1aaHBKl
> WSkdiouBZ3O4XZ1LKiNw0HfO/wNWZ1QekvnKu7YMiucBRBMUMBCUEyy8pkUkFglx
> nGi/Tx3Jr/rC+zlPNHRtbB/r5wIly6wnaVMkt90EtH727KKuRoeZtrNIc/B7xv9B
> I3Co6KqxuZGVxhB3m1Zz7ag5ZAmm+11x2dhlPTClUMhMcr0mdpyar7WrYfyCky+p
> kqpqyLI9YbwY+HZQZRpzTXfN+R0YNBI80/o+6Ys87ydydssu57utH5UWKSLhXU/Z
> csK1uvTPjqaK10zLUfMvVXu4WScHG8f6Iw10nMrELyLsI8W4MXsHLxsnCwiWPfcH
> y43+AuscZi+9Sp6dQBDv9BYq2vzxtq6wLM7jdJ4DuU83J0mF7xCktZnOC9rEsGxY
> ZmejlgizAi8Sb3+fSBAomIjc7KwElvBKop2ItVgvMKbXu+gbOdsA1EUJhzsyCSR0
> A93dekV3djlfkQ/rn688Bl69Oqw+Qjh87OaZplbgxRDhOjhq0fs=
> =fDkT
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: Translations update

[tomcat]

On 26.11.2018 15:38, Rémy Maucherat wrote:

> >- "dispatch"/"dispatcher" (for the Servlet request dispatcher): ?
> >

>
>dépêcher / dépêcheur ?
>

That "répartiteur" from Emmanuel sounds better in theory, will have to see
in context.




+1 for "répartiteur".



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Translations update

[tomcat]

On 26.11.2018 15:01, Ludovic Pénet wrote:

- "endpoint" (for websockets, and for the Tomcat connectors, so

>possibly

>>two different terms): "point d'entrée" ?

>
>That sounds like exactly the opposite of "endpoint" to me.
>Although I must say that even in English, the vocabulary used in some
>reference documents
>(in particular everything to do with XML-based protocols, such as SOAP,
>SAML, OASIS and
>the like) is sometimes mysterious and counter-intuitive.
>What about "cible" here ?
>Or more literally, "point final" ?

Terminaison ?



>

+1 for "terminaison", else untranslated "endpoint".


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Translations update

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Rémy,

On 11/26/18 10:05, Rémy Maucherat wrote:
> On Mon, Nov 26, 2018 at 3:46 PM Christopher Schultz < 
> ch...@christopherschultz.net> wrote:
> 
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>> 
>> André,
>> 
>> On 11/26/18 08:35, André Warnier (tomcat) wrote:
>>> On 26.11.2018 13:29, Rémy Maucherat wrote:
 On Sat, Nov 24, 2018 at 9:48 AM Ludovic Pénet
  wrote:
 
> Le vendredi 23 novembre 2018 à 23:51 +0100, Rémy Maucherat
> a écrit :
>> On Wed, Nov 21, 2018 at 10:58 AM Mark Thomas 
>>  wrote:
>> 
>>> - French has increased from 18% to 64% coverage
>>> 
>> 
>> Done (well, close enough, a few tribes/ha remain) !
> A single translation remains to be performed.
> 
> Jump to https://poeditor.com/join/project/NUTIjDWzrl and be
> the one to complete the French translation. ;-)
> 
 
 Ok, you could have finished it, I was busy.
 
 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): ? - "endpoint" (for
 websockets, and for the Tomcat connectors, so possibly two
 different terms): "point d'entrée" ?
>>> 
>>> That sounds like exactly the opposite of "endpoint" to me.
>>> Although I must say that even in English, the vocabulary used
>>> in some reference documents (in particular everything to do
>>> with XML-based protocols, such as SOAP, SAML, OASIS and the
>>> like) is sometimes mysterious and counter-intuitive. What about
>>> "cible" here ? Or more literally, "point final" ?
>> 
>> I disagree.
>> 
>> An "endpoint" is a thing to which clients connect... an "entry
>> point", as Rémy suggests.
>> 
> 
> French and English constructs are the opposite in a lot of cases so
> that's why I though that "point d'entrée" was pretty good, as you
> stay the endpoint for the client is the "startingpoint" for the
> server (but there it sounds really bad).
> 
> 
>> 
>>> For "socket", "soquet" (like the piece in which you insert a
>>> plug, or a lightbulb) sounds ok to me.
>> 
>> This sounds okay to me, thought I don't know French at all. :)
>> 
 - "thread" (often it is untranslated elsewhere): "fil 
 d'exécution" ? - "membership" (that's the clustering
 object): "gestionnaire de membres" ?
>>> 
>>> "Membership" refers to "le fait d'être membre", no ? "adhésion"
>>> ? (like "cluster members" -> "adhérents au cluster" (with the 
>>> appropriate French pronounciation for "cleustère") :-)
>> 
>> What would you call a list of people who belong to a certain
>> fancy club or society? That's the word that should be used,
>> here.
>> 
> 
> So ... In that case it would simply be "liste de membres". Which
> after a quick check actually looks quite good in the context of the
> Tribes strings.
> 
> I have another difficult one for Tribes: that "replicated map"
> which should be ?? "structure répliquée" ? I used various terms for
> that annoying one ...

I'm a bug fan of naming things what they *mean*, not what they are.

For example, seeing this in code:

   Map> mapOfStringToClass = ...;

Is totally worthless from a self-documenting code perspective. This is
much better:

  Map> beanImplementationClasses = ...;

I think we should do the same thing with our descriptions, here.

So, for example, the fact that it's called "replicatedMap" in English
probably doesn't matter. The "replicated" part is important. The "map"
probably isn't. It could be any collection of objects. So, "replicated
structure" seems reasonable, here.

On the other hand, when saying "something is wrong with the
MacGuffin[1]", translating the word "MacGuffin" may make things worse.
If you want to know how to look it up in the documentation and/or
code, it needs to agree with what's there. Since the code is
(nominally) in English, the term might need to be in English.

A corollary of this is that the error messages and the documentation
should agree with each other. Do we have French-language documentation
for this stuff?

>>> (Sorry for the missing c cédille, can't type it here) (PTHT = 
>>> Protocol de Transport Hyper-Texte)
>> 
>> HTTP should always be spelled HTTP and never PTHT, just like UTC
>> is always spelled UTC, even in English (where the acronym makes
>> no sense to Englist speakers).
>> 
>> I think maybe you were kidding, but ... just in case :)
>> 
> 
> We were super serious, like for Apache Matou :)

:)

I like that as a (silly) name (Apache Dead?), but didn't get the
actual joke. :(

- -chris

[1] https://tvtropes.org/pmwiki/pmwiki.php/Main/MacGuffin
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlv8GNcACgkQHPApP6U8
pFj4pQ//QTq8mPf7kuyNIzflzjylSTlcHoAhnjusGhNOlG4pyqIazc8JVllPAHo1
dZUbj9gMcJOBYks7n4sUNBibz4bpmWTWsd2jnu8g4MxvKAXZ40/KRRkqWcyNOQZ/

Re: Translations update

[Woonsan Ko]

On Mon, Nov 26, 2018 at 10:05 AM Rémy Maucherat  wrote:
>
> On Mon, Nov 26, 2018 at 3:46 PM Christopher Schultz <
> ch...@christopherschultz.net> wrote:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > André,
> >
> > On 11/26/18 08:35, André Warnier (tomcat) wrote:
> > > On 26.11.2018 13:29, Rémy Maucherat wrote:
> > >> On Sat, Nov 24, 2018 at 9:48 AM Ludovic Pénet 
> > >> wrote:
> > >>
> > >>> Le vendredi 23 novembre 2018 à 23:51 +0100, Rémy Maucherat a
> > >>> écrit :
> >  On Wed, Nov 21, 2018 at 10:58 AM Mark Thomas
> >   wrote:
> > 
> > > - French has increased from 18% to 64% coverage
> > >
> > 
> >  Done (well, close enough, a few tribes/ha remain) !
> > >>> A single translation remains to be performed.
> > >>>
> > >>> Jump to https://poeditor.com/join/project/NUTIjDWzrl and be the
> > >>> one to complete the French translation. ;-)
> > >>>
> > >>
> > >> Ok, you could have finished it, I was busy.
> > >>
> > >> 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): ? - "endpoint" (for websockets, and for the
> > >> Tomcat connectors, so possibly two different terms): "point
> > >> d'entrée" ?
> > >
> > > That sounds like exactly the opposite of "endpoint" to me. Although
> > > I must say that even in English, the vocabulary used in some
> > > reference documents (in particular everything to do with XML-based
> > > protocols, such as SOAP, SAML, OASIS and the like) is sometimes
> > > mysterious and counter-intuitive. What about "cible" here ? Or more
> > > literally, "point final" ?
> >
> > I disagree.
> >
> > An "endpoint" is a thing to which clients connect... an "entry point",
> > as Rémy suggests.
> >
>
> French and English constructs are the opposite in a lot of cases so that's
> why I though that "point d'entrée" was pretty good, as you stay the
> endpoint for the client is the "startingpoint" for the server (but there it
> sounds really bad).
>
>
> >
> > > For "socket", "soquet" (like the piece in which you insert a plug,
> > > or a lightbulb) sounds ok to me.
> >
> > This sounds okay to me, thought I don't know French at all. :)
> >
> > >> - "thread" (often it is untranslated elsewhere): "fil
> > >> d'exécution" ? - "membership" (that's the clustering object):
> > >> "gestionnaire de membres" ?
> > >
> > > "Membership" refers to "le fait d'être membre", no ? "adhésion" ?
> > > (like "cluster members" -> "adhérents au cluster" (with the
> > > appropriate French pronounciation for "cleustère") :-)
> >
> > What would you call a list of people who belong to a certain fancy
> > club or society? That's the word that should be used, here.
> >
>
> So ... In that case it would simply be "liste de membres". Which after a
> quick check actually looks quite good in the context of the Tribes strings.
>
> I have another difficult one for Tribes: that "replicated map" which should
> be ?? "structure répliquée" ?
> I used various terms for that annoying one ...
>
>
> >
> > >> - "dispatch"/"dispatcher" (for the Servlet request dispatcher):
> > >> ?
> > >>
> > >
> > > dépêcher / dépêcheur ?
> > >
> > >> And I just saw it is really "connexion" and not "connection".
> > >> Oooops, I thought both were ok. I guess it's the same kind of
> > >> mistake with English-UK vs English-US, where I usually hate the
> > >> UK style (except in HarryP and Discworld, it's part of the charm
> > >> I suppose).
> > >>
> > >
> > > Maybe a note : the target audience of most of these messages is not
> > > the members of the Académie or the jury of the Prix Goncourt. Its
> > > is programmers, sysadmins and qualified tomcat/webservers users.
> > > The translations should be helpful to them, to get a first idea of
> > > the issue and be able to search later in the on-line documentation.
> > > Which happens to be only available/up-to-date/searchable in
> > > English, no ?
> > >
> > > So I believe that a translation such as "La requête PTHT recue sur
> > > le soquet du connecteur de toile a été dépêchée au conducteur du
> > > groupe d'adhérents" may be stylistically correct, but ultimately
> > > quite counter-productive.
> > >
> > > (Sorry for the missing c cédille, can't type it here) (PTHT =
> > > Protocol de Transport Hyper-Texte)
> >
> > HTTP should always be spelled HTTP and never PTHT, just like UTC is
> > always spelled UTC, even in English (where the acronym makes no sense
> > to Englist speakers).
> >
> > I think maybe you were kidding, but ... just in case :)
> >
>
> We were super serious, like for Apache Matou :)

:-)
I found this sentence from google and used their translation service,
just out of curiosity and out of context:
"Le matou n'est probablement pas devenu plus exigeant en termes
gustatifs." [Le Monde, 2002]
The matou won't be too demanding in The World! ;-)

Woonsan

>
> Rémy

Re: Tomcat 9 does not work with Java 11

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Ralf,

On 11/26/18 10:39, Andi Meister wrote:
> Hi,
> 
> 
> I downloaded and installed Java 11 from here:
> 
> https://www.oracle.com/technetwork/java/javase/downloads/jdk11-downloa
ds-5066655.html
>
> 
> 
> Then I downloaded and installed Tomcat 9 Windows service
> executable.
> 
> 
> During installation I was asked for the path to JRE.
> 
> Java 11 does not contain a JRE anymore, so I pointed to the Java 11
> root directory.
> 
> The installer was fine with that.
> 
> 
> But when I finally start Tomcat service, it does NOT run.
> 
> In commons_deamon.log I see this error message:
> 
> 
> [2018-11-26 13:36:39] [info]  [ 3732] Running 'Tomcat9' Service...
> 
> [2018-11-26 13:36:39] [info]  [ 4776] Starting service...
> 
> [2018-11-26 13:36:39] [error] [ 4776] The specified procedure could
> not be found.
> 
> [2018-11-26 13:36:39] [error] [ 4776] Failed creating Java
> C:\Program Files\Java\jdk-11.0.1\bin\server\jvm.dll
> 
> [2018-11-26 13:36:39] [error] [ 4776] The specified procedure could
> not be found.
> 
> [2018-11-26 13:36:39] [error] [ 4776] ServiceStart returned 1
> 
> [2018-11-26 13:36:39] [error] [ 4776] The specified procedure could
> not be found.
> 
> [2018-11-26 13:36:39] [info]  [ 3732] Run service finished.
> 
> 
> 
> What can I do to get this run?
> 
> 
> Operating System:
> 
> Windows Server 2008 R2

Which Tomcat installer package did you download?

- -chris
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlv8Fr0ACgkQHPApP6U8
pFgYMg/+O3RW95N/U1ZWkk1WCkevcTHLqDQio41+LYUegvidEtzOxFb7uf1bcA8A
KhPqghGnM9cp9QEcyutQIsAEt1+YWB/d71DoKwGnewxr+K+1nF3VxCgV3gYLz5vP
k+7LtWkaQuen5nzEGkWTWIurdBhO7cgmn+rtcrVuhPFLGizlwf9EN2C4D1aaHBKl
WSkdiouBZ3O4XZ1LKiNw0HfO/wNWZ1QekvnKu7YMiucBRBMUMBCUEyy8pkUkFglx
nGi/Tx3Jr/rC+zlPNHRtbB/r5wIly6wnaVMkt90EtH727KKuRoeZtrNIc/B7xv9B
I3Co6KqxuZGVxhB3m1Zz7ag5ZAmm+11x2dhlPTClUMhMcr0mdpyar7WrYfyCky+p
kqpqyLI9YbwY+HZQZRpzTXfN+R0YNBI80/o+6Ys87ydydssu57utH5UWKSLhXU/Z
csK1uvTPjqaK10zLUfMvVXu4WScHG8f6Iw10nMrELyLsI8W4MXsHLxsnCwiWPfcH
y43+AuscZi+9Sp6dQBDv9BYq2vzxtq6wLM7jdJ4DuU83J0mF7xCktZnOC9rEsGxY
ZmejlgizAi8Sb3+fSBAomIjc7KwElvBKop2ItVgvMKbXu+gbOdsA1EUJhzsyCSR0
A93dekV3djlfkQ/rn688Bl69Oqw+Qjh87OaZplbgxRDhOjhq0fs=
=fDkT
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Tomcat 9 does not work with Java 11

[Andi Meister]

Hi,


I downloaded and installed Java 11 from here:

https://www.oracle.com/technetwork/java/javase/downloads/jdk11-downloads-5066655.html


Then I downloaded and installed Tomcat 9 Windows service executable.


During installation I was asked for the path to JRE.

Java 11 does not contain a JRE anymore, so I pointed to the Java 11 root
directory.

The installer was fine with that.


But when I finally start Tomcat service, it does NOT run.

In commons_deamon.log I see this error message:


[2018-11-26 13:36:39] [info]  [ 3732] Running 'Tomcat9' Service...

[2018-11-26 13:36:39] [info]  [ 4776] Starting service...

[2018-11-26 13:36:39] [error] [ 4776] The specified procedure could not be
found.

[2018-11-26 13:36:39] [error] [ 4776] Failed creating Java C:\Program
Files\Java\jdk-11.0.1\bin\server\jvm.dll

[2018-11-26 13:36:39] [error] [ 4776] The specified procedure could not be
found.

[2018-11-26 13:36:39] [error] [ 4776] ServiceStart returned 1

[2018-11-26 13:36:39] [error] [ 4776] The specified procedure could not be
found.

[2018-11-26 13:36:39] [info]  [ 3732] Run service finished.



What can I do to get this run?


Operating System:

Windows Server 2008 R2


Ralf

Re: [OT] help installing mod_jk on Centos 7 on a Google Cloud server

[Lou Wallace]

Hi Chris,

For the most party those were there when the Google Cloud instance created
the Apache web server. But you are right once working I need to eval all of
them.

Lou

On Mon, Nov 26, 2018 at 9:38 AM Christopher Schultz <
ch...@christopherschultz.net> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Lou,
>
> On 11/24/18 17:01, Lou Wallace wrote:
> > Here is what I see
> >
> > Loaded Modules: core_module (static) so_module (static) http_module
> > (static) access_compat_module (shared) actions_module (shared)
> > alias_module (shared) allowmethods_module (shared)
> > auth_basic_module (shared) auth_digest_module (shared)
> > authn_anon_module (shared) authn_core_module (shared)
> > authn_dbd_module (shared) authn_dbm_module (shared)
> > authn_file_module (shared) authn_socache_module (shared)
> > authz_core_module (shared) authz_dbd_module (shared)
> > authz_dbm_module (shared) authz_groupfile_module (shared)
> > authz_host_module (shared) authz_owner_module (shared)
> > authz_user_module (shared) autoindex_module (shared) cache_module
> > (shared) cache_disk_module (shared) data_module (shared) dbd_module
> > (shared) deflate_module (shared) dir_module (shared) dumpio_module
> > (shared) echo_module (shared) env_module (shared) expires_module
> > (shared) ext_filter_module (shared) filter_module (shared)
> > headers_module (shared) include_module (shared) info_module
> > (shared) log_config_module (shared) logio_module (shared)
> > mime_magic_module (shared) mime_module (shared) negotiation_module
> > (shared) remoteip_module (shared) reqtimeout_module (shared)
> > rewrite_module (shared) setenvif_module (shared)
> > slotmem_plain_module (shared) slotmem_shm_module (shared)
> > socache_dbm_module (shared) socache_memcache_module (shared)
> > socache_shmcb_module (shared) status_module (shared)
> > substitute_module (shared) suexec_module (shared) unique_id_module
> > (shared) unixd_module (shared) userdir_module (shared)
> > version_module (shared) vhost_alias_module (shared) dav_module
> > (shared) dav_fs_module (shared) dav_lock_module (shared) lua_module
> > (shared) mpm_prefork_module (shared) proxy_module (shared)
> > lbmethod_bybusyness_module (shared) lbmethod_byrequests_module
> > (shared) lbmethod_bytraffic_module (shared)
> > lbmethod_heartbeat_module (shared) proxy_ajp_module (shared)
> > proxy_balancer_module (shared) proxy_connect_module (shared)
> > proxy_express_module (shared) proxy_fcgi_module (shared)
> > proxy_fdpass_module (shared) proxy_ftp_module (shared)
> > proxy_http_module (shared) proxy_scgi_module (shared)
> > proxy_wstunnel_module (shared) ssl_module (shared) systemd_module
> > (shared) cgi_module (shared)
>
> That's like ... every single module available. Are you sure you want
> all those modules? After you get mod_jk working, you might want to
> review your configuration. Lots of stuff in there you almost certainly
> don't need.
>
> - -chris
> -BEGIN PGP SIGNATURE-
> Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
>
> iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlv8BX0ACgkQHPApP6U8
> pFgv9g//S4yxRRcCIo7bRxz4vZZim+Oun7Dg0Qpao5w/MhMHDwry2P512ozds2z4
> ZPpnWKKFuWzu4S45oCaDAYnAzkhEJlcn7mbXzR7TbLGWwSrkM/TWGMiMNbAAwOm4
> uvmkKJf6XOHZH4NexhAlDb3b+u/1g/kusLrsmZ58lt2GhOqVBJEaoWsBQ+xTW+Q6
> XVY/tEJIIBJsv5PD9qXf6MZi6vafYkOd1tv7n8VE+nCbG1wRKzF+sDcsGnxNUlZl
> 2F3qSplfYEVCZZRJCSNCgk8ZxWv2j2iB754jHDUzYR0iqxyzzgx4SCuH117LIo+U
> cGa116omE945IuLrhzcjM5fe1N0KdKvR4zrmTQTCRumaAzvEoFTRzB2TddStf/50
> FX/TQ7ULSmgNXRNnq3e/DjqmyrTRHoOrJnNn6AaL/Vftk6bN9p83oPCqtyvR9L0h
> kxGa6pvOAJ9qbQaixscRypSSHUmWkAz8MS6vIQyBqNyl9VtAKEcJ+nqUzhu8Y9aL
> UdQS+iMVwUjYEh1RlIuT6SETlOUoa0VXrRt/DG7P5HY+S0DQmgnBduZG/PZO3LLM
> E88mDXYFCMTCLfsawAU3slODt0DchcpVHt3dc8xuspsHbGLG0yxCZCCEFzgDZWij
> 6NfMHpGtAI4U7FJc3pMjB7IKVOS8aTyltPOevAtUGOF8Mv6pAQE=
> =8n4C
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: Character encoding problems using jsp:include with jsp:param in Tomcat 8.5 only.

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Thorsten,

On 11/26/18 08:45, Thorsten Schöning wrote:
> Hi all,
> 
> I'm currently testing migration of a legacy web app from Tomcat 7
> to 8 to 8.5 and ran into problems regarding character encoding in
> 8.5 only. That app uses JSP pages and declares all of those to be
> stored in UTF-8, does really do so :-), and declares a HTTP-Content
> type of "text/html; charset=UTF-8" as well. Textual content at
> HTML-level is properly encoded using UTF-8 and looks properly in
> the browser etc.
> 
> In Tomcat 8.5 the following is introducing encoding problems,
> though:
> 
>>  > name="chooseSearchInputTitle" value="Benutzer wählen" /> 
>> 
> 
> "search.jsp" simply outputs the value of the param as the "title" 
> attribute of some HTML-link and the character "ä" is replaced 
> somewhere with the Unicode character REPLACEMENT CHARACTER 0xFFFD.
> But really only in Tomcat 8.5, not in 8 and not in 7.

Have you been able to determine if the problem is on input or output?

> I can fix that problem using either "SetCharacterEncodingFilter"
> or the following line, which simply results in the same I guess:
> 
>> <% request.setCharacterEncoding("UTF-8"); %>

FYI the SetCharacterEncodingFilter only modifies request encoding and
not response encoding. Also, it only changes the encoding of the
request *body* (e.g. PUT/POST), and not the encoding used to decode
the URI. That's configured in 's URIEncoding. There is also
useBodyEncodingForURI which inherits the request body's encoding if
it's present. I recommend using useBodyEncodingForURI="true".

I recommend *always* using SetCharacterEncodingFilter, since web
browsers both habitually refuse to send a correct content/type and
often use UTF-8 in URLs in violation of the HTTP spec. The result is
essentially that everything works the way you *want* it to work,
except that you just have to "hope" it works instead of being able to
prove that it will.

> Looking at the generated Java code for the JSP I get the
> following:
> 
>> org.apache.jasper.runtime.JspRuntimeLibrary.include(request,
>> response, "/WEB-INF/jsp/includes/search.jsp" + "?" +
>> org.apache.jasper.runtime.JspRuntimeLibrary.URLEncode("chooseSearchIn
putTitle",
>> request.getCharacterEncoding())+ "=" +
>> org.apache.jasper.runtime.JspRuntimeLibrary.URLEncode("Benutzer
>> wählen", request.getCharacterEncoding()), out, false);
> 
> The "ä" is properly encoded using UTF-8 in all versions of Tomcat
> and the generated code seems to be the same in all versions as
> well, especially regarding "request.getCharacterEncoding()".
> 
> "getCharacterEncoding" in Tomcat 8.8 has changed, the former 
> implementation didn't take the context into account:
> 
>> @Override public String getCharacterEncoding() { String
>> characterEncoding = coyoteRequest.getCharacterEncoding(); if
>> (characterEncoding != null) { return characterEncoding; }
>> 
>> Context context = getContext(); if (context != null) { return
>> context.getRequestCharacterEncoding(); }
>> 
>> return null; }

This is just a fall-back for when there is no character encoding
defined in the request (because the browser didn't send one).

> My connector in server.xml is configured to use "URIEncoding" as
> UTF-8 in all versions of Tomcat, but that doesn't make a difference
> to 8.5. So I understand that using "setCharacterEncoding", I set
> the value actually used in the generated Java now, even though the
> following is documented for character encoding filter:
> 
>> Note that the encoding for GET requests is not set here, but on a
>> Connector
> 
> https://tomcat.apache.org/tomcat-8.5-doc/config/filter.html#Set_Charac
ter_Encoding_Filter/Introduction
>
>  Now I'm wondering about multiple things...
> 
> 1. Doesn't "getCharacterEncoding" provide the encoding of the 
> HTTP-body?

Yes, but it comes directly from the browser, who often doesn't provide
it. There is no encoding-detection going on, so it's often "null" or
ISO-8859-1, which is the spec-defined default.

> My JSP is called using GET and the Java quoted above seems to build
> a query string as well. So why does it depend on some body encoding
> instead of e.g. URIEncoding of the connector?

Good question. Might be  a bug, here.

> 2. Is my former approach wrong or did changes in Tomcat 8.5
> introduce some regression? There is some conversion somewhere which
> was not present in the past.

Tomcat 8.5 follows the servlet spec, which in v4.0 added the
 to make things even more fun.
Actually, this can replace the use of the SetCharacterEncodingFilter.
Thanks for pointing this out; I wasn't aware of this feature of the
4.0 spec.

> 3. What is the correct fix I need now? The character encoding
> filter, even though it only applies to bodies per documentation?

Try setting  in your  like this:

web.xml
- ---

  UTF-8


- -chris
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

Re: Translations update

[Rémy Maucherat]

On Mon, Nov 26, 2018 at 3:46 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> André,
>
> On 11/26/18 08:35, André Warnier (tomcat) wrote:
> > On 26.11.2018 13:29, Rémy Maucherat wrote:
> >> On Sat, Nov 24, 2018 at 9:48 AM Ludovic Pénet 
> >> wrote:
> >>
> >>> Le vendredi 23 novembre 2018 à 23:51 +0100, Rémy Maucherat a
> >>> écrit :
>  On Wed, Nov 21, 2018 at 10:58 AM Mark Thomas
>   wrote:
> 
> > - French has increased from 18% to 64% coverage
> >
> 
>  Done (well, close enough, a few tribes/ha remain) !
> >>> A single translation remains to be performed.
> >>>
> >>> Jump to https://poeditor.com/join/project/NUTIjDWzrl and be the
> >>> one to complete the French translation. ;-)
> >>>
> >>
> >> Ok, you could have finished it, I was busy.
> >>
> >> 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): ? - "endpoint" (for websockets, and for the
> >> Tomcat connectors, so possibly two different terms): "point
> >> d'entrée" ?
> >
> > That sounds like exactly the opposite of "endpoint" to me. Although
> > I must say that even in English, the vocabulary used in some
> > reference documents (in particular everything to do with XML-based
> > protocols, such as SOAP, SAML, OASIS and the like) is sometimes
> > mysterious and counter-intuitive. What about "cible" here ? Or more
> > literally, "point final" ?
>
> I disagree.
>
> An "endpoint" is a thing to which clients connect... an "entry point",
> as Rémy suggests.
>

French and English constructs are the opposite in a lot of cases so that's
why I though that "point d'entrée" was pretty good, as you stay the
endpoint for the client is the "startingpoint" for the server (but there it
sounds really bad).


>
> > For "socket", "soquet" (like the piece in which you insert a plug,
> > or a lightbulb) sounds ok to me.
>
> This sounds okay to me, thought I don't know French at all. :)
>
> >> - "thread" (often it is untranslated elsewhere): "fil
> >> d'exécution" ? - "membership" (that's the clustering object):
> >> "gestionnaire de membres" ?
> >
> > "Membership" refers to "le fait d'être membre", no ? "adhésion" ?
> > (like "cluster members" -> "adhérents au cluster" (with the
> > appropriate French pronounciation for "cleustère") :-)
>
> What would you call a list of people who belong to a certain fancy
> club or society? That's the word that should be used, here.
>

So ... In that case it would simply be "liste de membres". Which after a
quick check actually looks quite good in the context of the Tribes strings.

I have another difficult one for Tribes: that "replicated map" which should
be ?? "structure répliquée" ?
I used various terms for that annoying one ...


>
> >> - "dispatch"/"dispatcher" (for the Servlet request dispatcher):
> >> ?
> >>
> >
> > dépêcher / dépêcheur ?
> >
> >> And I just saw it is really "connexion" and not "connection".
> >> Oooops, I thought both were ok. I guess it's the same kind of
> >> mistake with English-UK vs English-US, where I usually hate the
> >> UK style (except in HarryP and Discworld, it's part of the charm
> >> I suppose).
> >>
> >
> > Maybe a note : the target audience of most of these messages is not
> > the members of the Académie or the jury of the Prix Goncourt. Its
> > is programmers, sysadmins and qualified tomcat/webservers users.
> > The translations should be helpful to them, to get a first idea of
> > the issue and be able to search later in the on-line documentation.
> > Which happens to be only available/up-to-date/searchable in
> > English, no ?
> >
> > So I believe that a translation such as "La requête PTHT recue sur
> > le soquet du connecteur de toile a été dépêchée au conducteur du
> > groupe d'adhérents" may be stylistically correct, but ultimately
> > quite counter-productive.
> >
> > (Sorry for the missing c cédille, can't type it here) (PTHT =
> > Protocol de Transport Hyper-Texte)
>
> HTTP should always be spelled HTTP and never PTHT, just like UTC is
> always spelled UTC, even in English (where the acronym makes no sense
> to Englist speakers).
>
> I think maybe you were kidding, but ... just in case :)
>

We were super serious, like for Apache Matou :)

Rémy

RE: Connection pool and parallel deployment problem

[Gilles SCHLIENGER]

Hi,
I understand your needs, but what is your problem, since you don't use parallel 
deployment ?
Your connections are not closed but they will not be recreated when you deploy 
your webapp again, so there should be no problem ?

Gilles

-Message d'origine-
De : Chris Cheshire [mailto:yahoono...@gmail.com] 
Envoyé : lundi 26 novembre 2018 15:27
À : Tomcat Users List
Objet : Re: Connection pool and parallel deployment problem

I'm interested in what solution there is for this because I have the
exact same problem but without parallel deployment.

[snip]

On Mon, Nov 26, 2018 at 3:54 AM Gilles SCHLIENGER
 wrote:
>
> Hi Christopher,
>
> Thanks for your email.
>
> About connection pools not being closed, maybe the connection pool is closed 
> but the connections to the database are not.
>
> Here are the tests I did:
>
> + TEST 1:
> - I deploy my war
> - I login to my webapp
> - I check on my postgresql and mysql database that connections have been 
> opened (select...)
> - I undeploy my webapp through the manager webapp
> - I check that the connections are still opened
> - Tomcat is still running
> - I redeploy the exact samed webapp and login to my application
> - No other connection is being opened
>
> + TEST 2:
> - I deploy my war
> - I login to my webapp
> - I check on my postgresql and mysql database that connections have been 
> opened (select...)
> - I deploy a new version of my application and login with another browser
> - I check on my postgresql and mysql database that new connexions have been 
> opened (they doubled)
> - I undeploy the first version of the webapp
> - I check on my postgresql and mysql database and all connections are still 
> opened (even if I wait for a long time)
>
> For tests 1 and 2, I used C3p0, DBCP2 and even HikariCP
>


My results are the same. Using mysql, connection pools defined in
server.xml (for user realm for access control to host manager app) and
in my context.xml for my application. When I use the host-manager to
reload an app, the connections are closed (no abandoned connection
warnings) but not released. It is no until I stop tomcat completely
and restart it that the connections are released in mysql. This has
been the case for tomcat 7, 8.5 and 9 versions, with constant updates
of mysql 5.7 and its driver, using both the apache connection pool and
the tomcat connection pool. The driver lives in the tomcat/lib
directory (since it is needed for the user realm datasource).


> -Message d'origine-
> De : Christopher Schultz [mailto:ch...@christopherschultz.net]
> Envoyé : samedi 24 novembre 2018 17:19
> À : users@tomcat.apache.org
> Objet : Re: Connection pool and parallel deployment problem
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Gilles,
>
> On 11/23/18 05:07, Gilles SCHLIENGER wrote:

[snip]

>
> > The warning/error messages are not actually linked to the
> > connexions not closed. To ovoid these messages, you can: - move the
> > jars (connexion pool, drivers...) into TOMCAT/lib - Have a
> > ServletContextListener that calls
> > AbandonedConnectionCleanupThread.checkedShutdown();
>
> The Connector/J devs haven't been able to understand how ClassLoaders
> work, and have never really fixed that long-standing bug in a
> satisfying way as far as I know. But you should always use a
> ServletContextListener to attempt to shut-down the
> AbadonedConnectionCleanuopThread.
>
> BTW that thread does not work as documented. It's claimed that it
> doesn't start unless you issue a query with a timeout, but it always
> starts whether or not you use queries with timeouts. It's frustrating.
>

Should we be using checked or unchecked shutdown?

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Translations update

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

André,

On 11/26/18 08:35, André Warnier (tomcat) wrote:
> On 26.11.2018 13:29, Rémy Maucherat wrote:
>> On Sat, Nov 24, 2018 at 9:48 AM Ludovic Pénet 
>> wrote:
>> 
>>> Le vendredi 23 novembre 2018 à 23:51 +0100, Rémy Maucherat a
>>> écrit :
 On Wed, Nov 21, 2018 at 10:58 AM Mark Thomas
  wrote:
 
> - French has increased from 18% to 64% coverage
> 
 
 Done (well, close enough, a few tribes/ha remain) !
>>> A single translation remains to be performed.
>>> 
>>> Jump to https://poeditor.com/join/project/NUTIjDWzrl and be the
>>> one to complete the French translation. ;-)
>>> 
>> 
>> Ok, you could have finished it, I was busy.
>> 
>> 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): ? - "endpoint" (for websockets, and for the
>> Tomcat connectors, so possibly two different terms): "point
>> d'entrée" ?
> 
> That sounds like exactly the opposite of "endpoint" to me. Although
> I must say that even in English, the vocabulary used in some 
> reference documents (in particular everything to do with XML-based 
> protocols, such as SOAP, SAML, OASIS and the like) is sometimes 
> mysterious and counter-intuitive. What about "cible" here ? Or more
> literally, "point final" ?

I disagree.

An "endpoint" is a thing to which clients connect... an "entry point",
as Rémy suggests.

> For "socket", "soquet" (like the piece in which you insert a plug,
> or a lightbulb) sounds ok to me.

This sounds okay to me, thought I don't know French at all. :)

>> - "thread" (often it is untranslated elsewhere): "fil
>> d'exécution" ? - "membership" (that's the clustering object):
>> "gestionnaire de membres" ?
> 
> "Membership" refers to "le fait d'être membre", no ? "adhésion" ? 
> (like "cluster members" -> "adhérents au cluster" (with the
> appropriate French pronounciation for "cleustère") :-)

What would you call a list of people who belong to a certain fancy
club or society? That's the word that should be used, here.

>> - "dispatch"/"dispatcher" (for the Servlet request dispatcher):
>> ?
>> 
> 
> dépêcher / dépêcheur ?
> 
>> And I just saw it is really "connexion" and not "connection".
>> Oooops, I thought both were ok. I guess it's the same kind of
>> mistake with English-UK vs English-US, where I usually hate the
>> UK style (except in HarryP and Discworld, it's part of the charm
>> I suppose).
>> 
> 
> Maybe a note : the target audience of most of these messages is not
> the members of the Académie or the jury of the Prix Goncourt. Its
> is programmers, sysadmins and qualified tomcat/webservers users.
> The translations should be helpful to them, to get a first idea of
> the issue and be able to search later in the on-line documentation.
> Which happens to be only available/up-to-date/searchable in
> English, no ?
> 
> So I believe that a translation such as "La requête PTHT recue sur
> le soquet du connecteur de toile a été dépêchée au conducteur du
> groupe d'adhérents" may be stylistically correct, but ultimately
> quite counter-productive.
> 
> (Sorry for the missing c cédille, can't type it here) (PTHT =
> Protocol de Transport Hyper-Texte)

HTTP should always be spelled HTTP and never PTHT, just like UTC is
always spelled UTC, even in English (where the acronym makes no sense
to Englist speakers).

I think maybe you were kidding, but ... just in case :)

- -chris
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlv8B0AACgkQHPApP6U8
pFi9BBAAqLoE5EpSJjWjwJSXdT1jaKffY9dWB5o+HVEJ+8jb0uxxkIsgSyHTsvEs
D8k+WcUHpREiY2h4Xd0VOOn3w3hwJ1mV6Cs8Qv9p4sdQcFZonIvBr/5KlRNCS/Hy
YWVze0SmREr2uWjSIX3s2FyXp+RTCHZ+poDsvI5MYTxrUGIeb3dYROyjbIuDu4//
uCTUrobF8bB6eHwdu5zu2DUof7iZhfTo582mG4AN03OHy8g5g9YD6LGW4IT9ZrFD
YxQL3KMM8CXarDFpnvX1fvq4MYpo04znOmidK+VlsfBInJaUofGXiWMews8Kkiri
kb6gKdLkCkjTq7g/3DJs6hiwOe/8BP5j7KmvCGfGpl24efIwT7XlJHzFLCenTop1
9IWKCxFuMwY8Oqict7kg/aNmWhTBy/Sm3sUhJtBm9Mri7fR7u6es/b0I76UiojCC
U45ywmGHZLngJTCcTUzcQ/ow6ziHDcLWC3bk05PDOnG6rkMfckBVrCRLeIuRCvCf
/QXBj87zKbdUCkfotN5lH+lZ1ZYt3NtJoxzGCI0wJIMhQm2OVT98AMr402vwcqPd
I8DHC34S+Vi+wrMCmszjH7x427cMw6K9WsBgwmLxcyrzYHAV5IWww5e6aWjDjc5a
1+rrR/qiFaf2VrhcuQmE6RaToo2vm43u4nKjvb0jRA1TFTAk87A=
=b/QY
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: [OT] help installing mod_jk on Centos 7 on a Google Cloud server

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Lou,

On 11/24/18 17:01, Lou Wallace wrote:
> Here is what I see
> 
> Loaded Modules: core_module (static) so_module (static) http_module
> (static) access_compat_module (shared) actions_module (shared) 
> alias_module (shared) allowmethods_module (shared) 
> auth_basic_module (shared) auth_digest_module (shared) 
> authn_anon_module (shared) authn_core_module (shared) 
> authn_dbd_module (shared) authn_dbm_module (shared) 
> authn_file_module (shared) authn_socache_module (shared) 
> authz_core_module (shared) authz_dbd_module (shared) 
> authz_dbm_module (shared) authz_groupfile_module (shared) 
> authz_host_module (shared) authz_owner_module (shared) 
> authz_user_module (shared) autoindex_module (shared) cache_module
> (shared) cache_disk_module (shared) data_module (shared) dbd_module
> (shared) deflate_module (shared) dir_module (shared) dumpio_module
> (shared) echo_module (shared) env_module (shared) expires_module
> (shared) ext_filter_module (shared) filter_module (shared) 
> headers_module (shared) include_module (shared) info_module
> (shared) log_config_module (shared) logio_module (shared) 
> mime_magic_module (shared) mime_module (shared) negotiation_module
> (shared) remoteip_module (shared) reqtimeout_module (shared) 
> rewrite_module (shared) setenvif_module (shared) 
> slotmem_plain_module (shared) slotmem_shm_module (shared) 
> socache_dbm_module (shared) socache_memcache_module (shared) 
> socache_shmcb_module (shared) status_module (shared) 
> substitute_module (shared) suexec_module (shared) unique_id_module
> (shared) unixd_module (shared) userdir_module (shared) 
> version_module (shared) vhost_alias_module (shared) dav_module
> (shared) dav_fs_module (shared) dav_lock_module (shared) lua_module
> (shared) mpm_prefork_module (shared) proxy_module (shared) 
> lbmethod_bybusyness_module (shared) lbmethod_byrequests_module
> (shared) lbmethod_bytraffic_module (shared) 
> lbmethod_heartbeat_module (shared) proxy_ajp_module (shared) 
> proxy_balancer_module (shared) proxy_connect_module (shared) 
> proxy_express_module (shared) proxy_fcgi_module (shared) 
> proxy_fdpass_module (shared) proxy_ftp_module (shared) 
> proxy_http_module (shared) proxy_scgi_module (shared) 
> proxy_wstunnel_module (shared) ssl_module (shared) systemd_module
> (shared) cgi_module (shared)

That's like ... every single module available. Are you sure you want
all those modules? After you get mod_jk working, you might want to
review your configuration. Lots of stuff in there you almost certainly
don't need.

- -chris
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlv8BX0ACgkQHPApP6U8
pFgv9g//S4yxRRcCIo7bRxz4vZZim+Oun7Dg0Qpao5w/MhMHDwry2P512ozds2z4
ZPpnWKKFuWzu4S45oCaDAYnAzkhEJlcn7mbXzR7TbLGWwSrkM/TWGMiMNbAAwOm4
uvmkKJf6XOHZH4NexhAlDb3b+u/1g/kusLrsmZ58lt2GhOqVBJEaoWsBQ+xTW+Q6
XVY/tEJIIBJsv5PD9qXf6MZi6vafYkOd1tv7n8VE+nCbG1wRKzF+sDcsGnxNUlZl
2F3qSplfYEVCZZRJCSNCgk8ZxWv2j2iB754jHDUzYR0iqxyzzgx4SCuH117LIo+U
cGa116omE945IuLrhzcjM5fe1N0KdKvR4zrmTQTCRumaAzvEoFTRzB2TddStf/50
FX/TQ7ULSmgNXRNnq3e/DjqmyrTRHoOrJnNn6AaL/Vftk6bN9p83oPCqtyvR9L0h
kxGa6pvOAJ9qbQaixscRypSSHUmWkAz8MS6vIQyBqNyl9VtAKEcJ+nqUzhu8Y9aL
UdQS+iMVwUjYEh1RlIuT6SETlOUoa0VXrRt/DG7P5HY+S0DQmgnBduZG/PZO3LLM
E88mDXYFCMTCLfsawAU3slODt0DchcpVHt3dc8xuspsHbGLG0yxCZCCEFzgDZWij
6NfMHpGtAI4U7FJc3pMjB7IKVOS8aTyltPOevAtUGOF8Mv6pAQE=
=8n4C
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Translations update

[Rémy Maucherat]

On Mon, Nov 26, 2018 at 2:35 PM André Warnier (tomcat) 
wrote:

> On 26.11.2018 13:29, Rémy Maucherat wrote:
> > On Sat, Nov 24, 2018 at 9:48 AM Ludovic Pénet  wrote:
> >
> >> Le vendredi 23 novembre 2018 à 23:51 +0100, Rémy Maucherat a écrit :
> >>> On Wed, Nov 21, 2018 at 10:58 AM Mark Thomas 
> >>> wrote:
> >>>
>  - French has increased from 18% to 64% coverage
> 
> >>>
> >>> Done (well, close enough, a few tribes/ha remain) !
> >> A single translation remains to be performed.
> >>
> >> Jump to https://poeditor.com/join/project/NUTIjDWzrl and be the one to
> >> complete the French translation. ;-)
> >>
> >
> > Ok, you could have finished it, I was busy.
> >
> > 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): ?
> > - "endpoint" (for websockets, and for the Tomcat connectors, so possibly
> > two different terms): "point d'entrée" ?
>
> That sounds like exactly the opposite of "endpoint" to me.
> Although I must say that even in English, the vocabulary used in some
> reference documents
> (in particular everything to do with XML-based protocols, such as SOAP,
> SAML, OASIS and
> the like) is sometimes mysterious and counter-intuitive.
> What about "cible" here ?
> Or more literally, "point final" ?
>

There are two contexts for it:
- The "NIO Endpoint" (or APR, etc) that is the backend of the Tomcat
connector, it accepts the sockets and deals with the low level stuff from
there
- The WebSocket endpoint javax.websocket.RemoteEndpoint
They can have a different word, actually.


>
> For "socket", "soquet" (like the piece in which you insert a plug, or a
> lightbulb) sounds
> ok to me.
>

Hum, ok, let's forget about this one.


>
> > - "thread" (often it is untranslated elsewhere): "fil d'exécution" ?
> > - "membership" (that's the clustering object): "gestionnaire de membres"
> ?
>
> "Membership" refers to "le fait d'être membre", no ? "adhésion" ?
> (like "cluster members" -> "adhérents au cluster" (with the appropriate
> French
> pronounciation for "cleustère") :-)
>

"adhérents" sounds good good and fits some most likely, "appartenance"
likely fits some others. I'll need to look in context.


>
> > - "dispatch"/"dispatcher" (for the Servlet request dispatcher): ?
> >
>
> dépêcher / dépêcheur ?
>

That "répartiteur" from Emmanuel sounds better in theory, will have to see
in context.


>
> > And I just saw it is really "connexion" and not "connection". Oooops, I
> > thought both were ok. I guess it's the same kind of mistake with
> English-UK
> > vs English-US, where I usually hate the UK style (except in HarryP and
> > Discworld, it's part of the charm I suppose).
> >
>
> Maybe a note : the target audience of most of these messages is not the
> members of the
> Académie or the jury of the Prix Goncourt. Its is programmers, sysadmins
> and qualified
> tomcat/webservers users.  The translations should be helpful to them, to
> get a first idea
> of the issue and be able to search later in the on-line documentation.
> Which happens to
> be only available/up-to-date/searchable in English, no ?
>
> So I believe that a translation such as "La requête PTHT recue sur le
> soquet du connecteur
> de toile a été dépêchée au conducteur du groupe d'adhérents" may be
> stylistically correct,
> but ultimately quite counter-productive.
>
> (Sorry for the missing c cédille, can't type it here)
> (PTHT = Protocol de Transport Hyper-Texte)
>

PTHT :D

So I was fine with "fil d'exécution" but it's more complex too than
untranslated. So "thread/socket" it is.


>
> This being said, all these translations leave out what is really the main
> theme here :
> tomcat. So what about a new name too ? what about "matou" ?
> Or does this require a fourchette ?
>

+1 for "Apache Matou" since it's so funny :) We need to apply for a
trademark asap.

Rémy

Re: Connection pool and parallel deployment problem

[Chris Cheshire]

I'm interested in what solution there is for this because I have the
exact same problem but without parallel deployment.

[snip]

On Mon, Nov 26, 2018 at 3:54 AM Gilles SCHLIENGER
 wrote:
>
> Hi Christopher,
>
> Thanks for your email.
>
> About connection pools not being closed, maybe the connection pool is closed 
> but the connections to the database are not.
>
> Here are the tests I did:
>
> + TEST 1:
> - I deploy my war
> - I login to my webapp
> - I check on my postgresql and mysql database that connections have been 
> opened (select...)
> - I undeploy my webapp through the manager webapp
> - I check that the connections are still opened
> - Tomcat is still running
> - I redeploy the exact samed webapp and login to my application
> - No other connection is being opened
>
> + TEST 2:
> - I deploy my war
> - I login to my webapp
> - I check on my postgresql and mysql database that connections have been 
> opened (select...)
> - I deploy a new version of my application and login with another browser
> - I check on my postgresql and mysql database that new connexions have been 
> opened (they doubled)
> - I undeploy the first version of the webapp
> - I check on my postgresql and mysql database and all connections are still 
> opened (even if I wait for a long time)
>
> For tests 1 and 2, I used C3p0, DBCP2 and even HikariCP
>


My results are the same. Using mysql, connection pools defined in
server.xml (for user realm for access control to host manager app) and
in my context.xml for my application. When I use the host-manager to
reload an app, the connections are closed (no abandoned connection
warnings) but not released. It is no until I stop tomcat completely
and restart it that the connections are released in mysql. This has
been the case for tomcat 7, 8.5 and 9 versions, with constant updates
of mysql 5.7 and its driver, using both the apache connection pool and
the tomcat connection pool. The driver lives in the tomcat/lib
directory (since it is needed for the user realm datasource).


> -Message d'origine-
> De : Christopher Schultz [mailto:ch...@christopherschultz.net]
> Envoyé : samedi 24 novembre 2018 17:19
> À : users@tomcat.apache.org
> Objet : Re: Connection pool and parallel deployment problem
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Gilles,
>
> On 11/23/18 05:07, Gilles SCHLIENGER wrote:

[snip]

>
> > The warning/error messages are not actually linked to the
> > connexions not closed. To ovoid these messages, you can: - move the
> > jars (connexion pool, drivers...) into TOMCAT/lib - Have a
> > ServletContextListener that calls
> > AbandonedConnectionCleanupThread.checkedShutdown();
>
> The Connector/J devs haven't been able to understand how ClassLoaders
> work, and have never really fixed that long-standing bug in a
> satisfying way as far as I know. But you should always use a
> ServletContextListener to attempt to shut-down the
> AbadonedConnectionCleanuopThread.
>
> BTW that thread does not work as documented. It's claimed that it
> doesn't start unless you issue a query with a timeout, but it always
> starts whether or not you use queries with timeouts. It's frustrating.
>

Should we be using checked or unchecked shutdown?

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Translations update

[Ludovic Pénet]

Le 26 novembre 2018 14:35:10 GMT+01:00, "André Warnier (tomcat)" 
 a écrit :
>On 26.11.2018 13:29, Rémy Maucherat wrote:
>> On Sat, Nov 24, 2018 at 9:48 AM Ludovic Pénet 
>wrote:
>>
>>> Le vendredi 23 novembre 2018 à 23:51 +0100, Rémy Maucherat a écrit :
 On Wed, Nov 21, 2018 at 10:58 AM Mark Thomas 
 wrote:

> - French has increased from 18% to 64% coverage
>

 Done (well, close enough, a few tribes/ha remain) !
>>> A single translation remains to be performed.
>>>
>>> Jump to https://poeditor.com/join/project/NUTIjDWzrl and be the one
>to
>>> complete the French translation. ;-)
>>>
>>
>> Ok, you could have finished it, I was busy.
I did not feel capable of translating this last one, lacking context.

>>
>> 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): ?
Well, IMHO, I never see this one translated
 So, we would be better sticking with "socket".  If you prefer a translation, I 
suggest also including ("socket") next to it.


>> - "endpoint" (for websockets, and for the Tomcat connectors, so
>possibly
>> two different terms): "point d'entrée" ?
>
>That sounds like exactly the opposite of "endpoint" to me.
>Although I must say that even in English, the vocabulary used in some
>reference documents 
>(in particular everything to do with XML-based protocols, such as SOAP,
>SAML, OASIS and 
>the like) is sometimes mysterious and counter-intuitive.
>What about "cible" here ?
>Or more literally, "point final" ?
Terminaison ?


>
>For "socket", "soquet" (like the piece in which you insert a plug, or a
>lightbulb) sounds 
>ok to me.
>
>> - "thread" (often it is untranslated elsewhere): "fil d'exécution" ?
Same remark.


>> - "membership" (that's the clustering object): "gestionnaire de
>membres" ?
>
>"Membership" refers to "le fait d'être membre", no ? "adhésion" ?
>(like "cluster members" -> "adhérents au cluster" (with the appropriate
>French 
>pronounciation for "cleustère") :-)
Appartenance, for me.

>> - "dispatch"/"dispatcher" (for the Servlet request dispatcher): ?
>>
>
>dépêcher / dépêcheur ?
Répartition / Répartiteur. Same remark on the original word inclusion 


>
>> And I just saw it is really "connexion" and not "connection". Oooops,
>I
>> thought both were ok. I guess it's the same kind of mistake with
>English-UK
>> vs English-US, where I usually hate the UK style (except in HarryP
>and
>> Discworld, it's part of the charm I suppose).
>>
>
>Maybe a note : the target audience of most of these messages is not the
>members of the 
>Académie or the jury of the Prix Goncourt. Its is programmers,
>sysadmins and qualified 
>tomcat/webservers users.  The translations should be helpful to them,
>to get a first idea 
>of the issue and be able to search later in the on-line documentation. 
>Which happens to 
>be only available/up-to-date/searchable in English, no ?
>
>So I believe that a translation such as "La requête PTHT recue sur le
>soquet du connecteur 
>de toile a été dépêchée au conducteur du groupe d'adhérents" may be
>stylistically correct, 
>but ultimately quite counter-productive.

+1000

>
>(Sorry for the missing c cédille, can't type it here)
>(PTHT = Protocol de Transport Hyper-Texte)
>
>This being said, all these translations leave out what is really the
>main theme here : 
>tomcat. So what about a new name too ? what about "matou" ?
>Or does this require a fourchette ?

;-)

Ludovic

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Translations update

[Emmanuel Bourg]

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

Character encoding problems using jsp:include with jsp:param in Tomcat 8.5 only.

[Thorsten Schöning]

Hi all,

I'm currently testing migration of a legacy web app from Tomcat 7 to 8
to 8.5 and ran into problems regarding character encoding in 8.5 only.
That app uses JSP pages and declares all of those to be stored in
UTF-8, does really do so :-), and declares a HTTP-Content type of
"text/html; charset=UTF-8" as well. Textual content at HTML-level is
properly encoded using UTF-8 and looks properly in the browser etc.

In Tomcat 8.5 the following is introducing encoding problems, though:

> 
>  value="Benutzer wählen"
>   />
> 

"search.jsp" simply outputs the value of the param as the "title"
attribute of some HTML-link and the character "ä" is replaced
somewhere with the Unicode character REPLACEMENT CHARACTER 0xFFFD. But
really only in Tomcat 8.5, not in 8 and not in 7.

I can fix that problem using either "SetCharacterEncodingFilter" or
the following line, which simply results in the same I guess:

> <% request.setCharacterEncoding("UTF-8"); %>

Looking at the generated Java code for the JSP I get the following:

> org.apache.jasper.runtime.JspRuntimeLibrary.include(request, response, 
> "/WEB-INF/jsp/includes/search.jsp" + "?" + 
> org.apache.jasper.runtime.JspRuntimeLibrary.URLEncode("chooseSearchInputTitle",
>  request.getCharacterEncoding())+ "=" + 
> org.apache.jasper.runtime.JspRuntimeLibrary.URLEncode("Benutzer wählen", 
> request.getCharacterEncoding()), out, false);

The "ä" is properly encoded using UTF-8 in all versions of Tomcat and
the generated code seems to be the same in all versions as well,
especially regarding "request.getCharacterEncoding()".

"getCharacterEncoding" in Tomcat 8.8 has changed, the former
implementation didn't take the context into account:

>@Override
>public String getCharacterEncoding() {
>String characterEncoding = coyoteRequest.getCharacterEncoding();
>if (characterEncoding != null) {
>return characterEncoding;
>}
>
>Context context = getContext();
>if (context != null) {
>return context.getRequestCharacterEncoding();
>}
>
>return null;
>}

My connector in server.xml is configured to use "URIEncoding" as UTF-8
in all versions of Tomcat, but that doesn't make a difference to 8.5.
So I understand that using "setCharacterEncoding", I set the value
actually used in the generated Java now, even though the following is
documented for character encoding filter:

> Note that the encoding for GET requests is not set here, but on a Connector

https://tomcat.apache.org/tomcat-8.5-doc/config/filter.html#Set_Character_Encoding_Filter/Introduction

Now I'm wondering about multiple things...

1. Doesn't "getCharacterEncoding" provide the encoding of the
   HTTP-body? My JSP is called using GET and the Java quoted above
   seems to build a query string as well. So why does it depend on
   some body encoding instead of e.g. URIEncoding of the connector?

2. Is my former approach wrong or did changes in Tomcat 8.5 introduce
   some regression? There is some conversion somewhere which was not
   present in the past.

3. What is the correct fix I need now? The character encoding filter,
   even though it only applies to bodies per documentation?

Thanks!

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning   E-Mail: thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme  http://www.AM-SoFT.de/

Telefon...05151-  9468- 55
Fax...05151-  9468- 88
Mobil..0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Translations update

[tomcat]

On 26.11.2018 13:29, Rémy Maucherat wrote:

On Sat, Nov 24, 2018 at 9:48 AM Ludovic Pénet  wrote:


Le vendredi 23 novembre 2018 à 23:51 +0100, Rémy Maucherat a écrit :

On Wed, Nov 21, 2018 at 10:58 AM Mark Thomas 
wrote:


- French has increased from 18% to 64% coverage



Done (well, close enough, a few tribes/ha remain) !

A single translation remains to be performed.

Jump to https://poeditor.com/join/project/NUTIjDWzrl and be the one to
complete the French translation. ;-)



Ok, you could have finished it, I was busy.

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): ?
- "endpoint" (for websockets, and for the Tomcat connectors, so possibly
two different terms): "point d'entrée" ?


That sounds like exactly the opposite of "endpoint" to me.
Although I must say that even in English, the vocabulary used in some reference documents 
(in particular everything to do with XML-based protocols, such as SOAP, SAML, OASIS and 
the like) is sometimes mysterious and counter-intuitive.

What about "cible" here ?
Or more literally, "point final" ?

For "socket", "soquet" (like the piece in which you insert a plug, or a lightbulb) sounds 
ok to me.



- "thread" (often it is untranslated elsewhere): "fil d'exécution" ?
- "membership" (that's the clustering object): "gestionnaire de membres" ?


"Membership" refers to "le fait d'être membre", no ? "adhésion" ?
(like "cluster members" -> "adhérents au cluster" (with the appropriate French 
pronounciation for "cleustère") :-)



- "dispatch"/"dispatcher" (for the Servlet request dispatcher): ?



dépêcher / dépêcheur ?


And I just saw it is really "connexion" and not "connection". Oooops, I
thought both were ok. I guess it's the same kind of mistake with English-UK
vs English-US, where I usually hate the UK style (except in HarryP and
Discworld, it's part of the charm I suppose).



Maybe a note : the target audience of most of these messages is not the members of the 
Académie or the jury of the Prix Goncourt. Its is programmers, sysadmins and qualified 
tomcat/webservers users.  The translations should be helpful to them, to get a first idea 
of the issue and be able to search later in the on-line documentation.  Which happens to 
be only available/up-to-date/searchable in English, no ?


So I believe that a translation such as "La requête PTHT recue sur le soquet du connecteur 
de toile a été dépêchée au conducteur du groupe d'adhérents" may be stylistically correct, 
but ultimately quite counter-productive.


(Sorry for the missing c cédille, can't type it here)
(PTHT = Protocol de Transport Hyper-Texte)

This being said, all these translations leave out what is really the main theme here : 
tomcat. So what about a new name too ? what about "matou" ?

Or does this require a fourchette ?




Rémy




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Translations update

[Rémy Maucherat]

On Sat, Nov 24, 2018 at 9:48 AM Ludovic Pénet  wrote:

> Le vendredi 23 novembre 2018 à 23:51 +0100, Rémy Maucherat a écrit :
> > On Wed, Nov 21, 2018 at 10:58 AM Mark Thomas 
> > wrote:
> >
> > > - French has increased from 18% to 64% coverage
> > >
> >
> > Done (well, close enough, a few tribes/ha remain) !
> A single translation remains to be performed.
>
> Jump to https://poeditor.com/join/project/NUTIjDWzrl and be the one to
> complete the French translation. ;-)
>

Ok, you could have finished it, I was busy.

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): ?
- "endpoint" (for websockets, and for the Tomcat connectors, so possibly
two different terms): "point d'entrée" ?
- "thread" (often it is untranslated elsewhere): "fil d'exécution" ?
- "membership" (that's the clustering object): "gestionnaire de membres" ?
- "dispatch"/"dispatcher" (for the Servlet request dispatcher): ?

And I just saw it is really "connexion" and not "connection". Oooops, I
thought both were ok. I guess it's the same kind of mistake with English-UK
vs English-US, where I usually hate the UK style (except in HarryP and
Discworld, it's part of the charm I suppose).

Rémy

RE: Connection pool and parallel deployment problem

[Gilles SCHLIENGER]

Hi Christopher,

Thanks for your email.

About connection pools not being closed, maybe the connection pool is closed 
but the connections to the database are not.

Here are the tests I did:

+ TEST 1:
- I deploy my war
- I login to my webapp
- I check on my postgresql and mysql database that connections have been opened 
(select...)
- I undeploy my webapp through the manager webapp
- I check that the connections are still opened
- Tomcat is still running
- I redeploy the exact samed webapp and login to my application
- No other connection is being opened

+ TEST 2:
- I deploy my war
- I login to my webapp
- I check on my postgresql and mysql database that connections have been opened 
(select...)
- I deploy a new version of my application and login with another browser
- I check on my postgresql and mysql database that new connexions have been 
opened (they doubled)
- I undeploy the first version of the webapp
- I check on my postgresql and mysql database and all connections are still 
opened (even if I wait for a long time)
 
For tests 1 and 2, I used C3p0, DBCP2 and even HikariCP

+ TEST 3:
- I configure my connection pools directly in my Spring application with an 
external configuration file
- I do the same as TEST 2
-> this time, I can see the number of database connections going down when I 
undeploy the first version of the webapp

Thanks again Chris if you have any advice

Regards
Gilles

-Message d'origine-
De : Christopher Schultz [mailto:ch...@christopherschultz.net] 
Envoyé : samedi 24 novembre 2018 17:19
À : users@tomcat.apache.org
Objet : Re: Connection pool and parallel deployment problem

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Gilles,

On 11/23/18 05:07, Gilles SCHLIENGER wrote:
> Thanks Mark for your answer
> 
> Here is what I found in case someone has the same problem.
> 
> When you use parallel deployment, you should not use a connexion
> pool in the context.xml file

Why not?

> Once the connexions are opened, they stay opened until Tomcat
> shuts down, whatever configuration you try.

I would expect that any connection pool created for a context (or
instance of a context, when parallel deployments are being done) would
be shut-down when the application is undeployed. Are you actually
undeploying the old context? It doesn't happen automatically IIRC.

> So everytime you deploy a new version of your webapp, new
> connexions are being opened.

This is expected. How could it work, otherwise?

> So we will configure our connexion pools directly in our Spring 
> webapp. This way, the connexions are closed when the webapp is 
> undeployed.

That's one way to solve the issue, but not the only way.

> The warning/error messages are not actually linked to the
> connexions not closed. To ovoid these messages, you can: - move the
> jars (connexion pool, drivers...) into TOMCAT/lib - Have a
> ServletContextListener that calls
> AbandonedConnectionCleanupThread.checkedShutdown();

The Connector/J devs haven't been able to understand how ClassLoaders
work, and have never really fixed that long-standing bug in a
satisfying way as far as I know. But you should always use a
ServletContextListener to attempt to shut-down the
AbadonedConnectionCleanuopThread.

BTW that thread does not work as documented. It's claimed that it
doesn't start unless you issue a query with a timeout, but it always
starts whether or not you use queries with timeouts. It's frustrating.

- -chris
> -Message d'origine- De : Mark Thomas
> [mailto:ma...@apache.org] Envoyé : mercredi 21 novembre 2018 14:18 
> À : Tomcat Users List; Gilles SCHLIENGER Objet : Re: Connection
> pool and parallel deployment problem
> 
> On 21/11/2018 11:00, Gilles SCHLIENGER wrote:
>> Hi all,
>> 
>> We are using Tomcat 9 and parallel deployment.
>> 
>> I use a connection pool defined in the xml context (myApp##1.xml,
>> myApp##2.xml in my exemple)
>> 
>> I have the following problem : - I have myApp##1.war deployed
>> using a connection pool (configured in myApp##1.xml) - I deploy
>> myApp##2.war (using a connection pool defined in myApp##2.xml) -
>> when the last session in myApp##1 expires, myApp##1 is
>> automatically undeployed (I have undeployOldVersions="true" in
>> server.xml for the Host) but the connections opened by myApp##1
>> are not closed.
>> 
>> I used the Tomcat configuration from the example in : 
>> https://tomcat.apache.org/tomcat-9.0-doc/jndi-datasource-examples-how
to.html#Database_Connection_Pool_(DBCP_2)_Configurations
>>
>>
>> 
> maxTotal="100" maxIdle="30" maxWaitMillis="1"
>> destroy-method="close" username="postgres" password="password"
>> driverClassName="org.postgresql.Driver" 
>> url="jdbc:postgresql://localhost:5432/postgres?stringtype=unspecified
"/>
>>
>>
>> 
During undeploy, I get the following messages :
>> 
>> 21-Nov-2018 11:42:54.795 AVERTISSEMENT
>> [ContainerBackgroundProcessor[StandardEngine[Catalina]]]
>> org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc
>> The web