Re: Tomcat 9 release plan
Am Dienstag, dem 30.01.2024 um 16:29 +0530 schrieb Kambhapati, Sindhuri: > Can we get a confirmation as to how long tomcat 9 releases would be > happening or there would be support for the existing one's. Please look / search in the archives, this was already discussed a few days ago, topic was: EOL - Tomcat versions No need to do another thread with the same topic. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: [OT] Migrating Subversion to a new hostname
Just use svn relocate: https://svnbook.red-bean.com/en/1.7/svn.ref.svn.c.relocate.html Torsten Christopher Schultz schrieb am Di., 3. Okt. 2023, 19:35: > All, > > Does anyone have any experience re-locating a Subversion repo? We are > looking at breaking-up some currently co-hosted services, and we'd like > to *move* our existing Subversion repo to a new hostname. No other > changes, but that means anywhere we have code checked-out will have to > be dealt with. > > Is it possible to "update/switch" those working-copies to the new > server, or do we basically have to delete all working copies and > re-check-out from the new host? > > -chris > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
Re: Did something JSP related change between 9.0.71 and 9.0.73
Am Freitag, dem 01.09.2023 um 15:18 +1000 schrieb Tim N: > We're seeing this too, but not in all our environments. We also use > NewRelic. Does it happen without NewRelic too? If not, better ask NewRelic about that problem. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Re-Cannot upload an image file from a deployed JSP page in Tomcat 10
Am Donnerstag, dem 01.06.2023 um 08:52 + schrieb Lauri: > > You mention a servlet part, but I do not use a servlet. > > All the code is contained in the JSP page. You need to divide that code in a JSP and in your upload servlet as you need to provide the @MultipartConfig on that servlet which handles your upload. Without that you will get: Unable to process parts as no multi-part configuration has been provided as an exception when accessing the request.getParts() API. The whole thing is all written there btw: https://docs.oracle.com/javaee/6/tutorial/doc/glrbb.html I don't know - maybe Mark does - if you can annotate a JSP page, had never seen it or read about that so my best guess is, you can't do that and you need to use a servlet + jsp unless you want to overwrite the JspServlet from Tomcat with a custom one which does have that annotation and handles the Jsp stuff. kind regards Torsten -- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Re-Cannot upload an image file from a deployed JSP page in Tomcat 10
Am Mittwoch, dem 31.05.2023 um 09:42 + schrieb Lauri: > But my initial question remains, what should have to modify on my > posted JSP page ? We already posted you with the docs where you can read about the necessary changes you need to make to your page, it is all written there (just call getParts() or getPart(..) on the servlet request object). You can ask about specific failures again if you have errors etc. but at least I don't fix your code to make it work - you can do that yourself and ask again if something isn't working like expected, after reading the docs we pointed you to and adapting your page. That's my 2 cents about it. kind regards Torsten -- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Re-Cannot upload an image file from a deployed JSP page in Tomcat 10
Am Mittwoch, dem 31.05.2023 um 09:14 + schrieb Lauri: > So, I guess I need to re-write my JSP page as if it was for Java EE > for Tomcat 9 (or earlier versions) for instance, correct? Why would you want to do that? Just rewrite it to work with the jakarta api and it will work with tomcat 10. kind regards Torsten -- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Re-Cannot upload an image file from a deployed JSP page in Tomcat 10
Am Mittwoch, dem 31.05.2023 um 09:18 + schrieb Thomas Hoffmann (Speed4Trade GmbH): > http://www.java2s.com/example/java-api/javax/servlet/http/httpservletrequest/getparts-0-0.html There is also a whole example app on the link you already provided Thomas: https://docs.oracle.com/javaee/6/tutorial/doc/glraq.html You just need to read though ;-). kind regards Torsten -- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Re-Cannot upload an image file from a deployed JSP page in Tomcat 10
Am Mittwoch, dem 31.05.2023 um 09:04 + schrieb Lauri: > What modules should I use if these are wrong ? None, it is already included in the servlet api. Like already written, please read e.g.: https://docs.oracle.com/javaee/6/tutorial/doc/gmhba.html kind regards Torsten -- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: OT: Tomcat and TLS
AddOn, if you use the native TLS implementation with openssl you can't
configure the TLS 1.3 ciphers which should be used with the ciphers
attribute, you will get all the ones which are enabled by default for TLS
1.3 in openssl.
Tomcat does still not support to configure them, you can look through the
archives, I made a question / thread about that, last year afaik, maybe
older.
schrieb am Do., 20. Apr. 2023,
19:03:
> Thank You!!!
>
>
> Dream * Excel * Explore * Inspire
> Jon McAlexander
> Senior Infrastructure Engineer
> Asst. Vice President
> He/His
>
> Middleware Product Engineering
> Enterprise CIO | EAS | Middleware | Infrastructure Solutions
>
> 8080 Cobblestone Rd | Urbandale, IA 50322
> MAC: F4469-010
> Tel 515-988-2508 | Cell 515-988-2508
>
> jonmcalexan...@wellsfargo.com
> This message may contain confidential and/or privileged information. If
> you are not the addressee or authorized to receive this for the addressee,
> you must not use, copy, disclose, or take any action based on this message
> or any information herein. If you have received this message in error,
> please advise the sender immediately by reply e-mail and delete this
> message. Thank you for your cooperation.
>
>
> > -Original Message-
> > From: Kevin Huntly
> > Sent: Thursday, April 20, 2023 11:25 AM
> > To: Tomcat Users List
> > Subject: Re: OT: Tomcat and TLS
> >
> > This is what I have:
> >
> > > address="0.0.0.0" port="8443" maxHttpHeaderSize="8192"
> > maxThreads="150"
> > minSpareThreads="25" enableLookups="false" acceptCount="100"
> > connectionTimeout="2" disableUploadTimeout="true"
> > compression="on" compressionMinSize="2048"
> > noCompressionUserAgents="gozilla, traviata" scheme="https"
> > secure="true"
> > SSLEnabled="true"
> > defaultSSLHostConfigName="appsrv.lan" server="Tomcat"
> > proxyName="esolutions.caspersbox.com" proxyPort="443">
> > > className="org.apache.coyote.http2.Http2Protocol" />
> > > protocols="TLSv1.2,TLSv1.3">
> > > certificateKeystoreFile="/home/appsrv/etc/kdb/tomcat.p12" type="RSA"
> > certificateKeystorePassword="Sj45gvHBgdoJerbptVZV" />
> >
> >
> >
> >
> > Kevin Huntly
> > Email: kmhun...@gmail.com
> > Cell: 716/424-3311
> >
> >
> > -BEGIN GEEK CODE BLOCK-
> > Version: 1.0
> > GCS/IT d+ s a C++ UL+++$ P+(++) L+++ E---
> > W+++ N+ o K(+) w--- O- M-- V-- PS+ PE Y(+)
> > PGP++(+++) t+ 5-- X-- R+ tv+ b++ DI++ D++
> > G++ e(+) h--- r+++ y+++*
> > --END GEEK CODE BLOCK--
> >
> >
> > On Thu, Apr 20, 2023 at 12:17 PM
> > wrote:
> >
> > > Is this actually Kosher?
> > >
> > > Open your Tomcat server
> > > Open your server.xml file in tomcat
> > > Add the connector with TLS protocol as below
> > > > >
> > > protocol="org.apache.coyote.http11.Http11NioProtocol"
> > > maxThreads="150"
> > > maxHttpHeaderSize="16384"
> > > compression="on"
> > > scheme="https"
> > > SSLEnabled="true"
> > > secure="true"
> > > defaultSSLHostConfigName="test.test">
> > > > > className="org.apache.coyote.http2.Http2Protocol" />
> > > > > hostName="test.test"
> > > protocols="TLSv1.2"
> > >
> > >
> > >
> > ciphers="TLS_DHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WI
> > TH_AES_25
> > > 6_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
> > >
> > >
> > TLS_DHE_DSS_WITH_AES_256_GCM_SHA384,TLS_DHE_RSA_WITH_AES_256
> > _CCM,TLS_E
> > >
> > CDHE_ECDSA_WITH_AES_256_CCM,TLS_DHE_RSA_WITH_AES_256_CCM_8,
> > >
> > >
> > TLS_ECDHE_ECDSA_WITH_AES_256_CCM_8,TLS_DHE_RSA_WITH_AES_128_
> > GCM_SHA256
> > > ,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
> > >
> > >
> > TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_DHE_DSS_WITH_AES
> > _128_GCM_S
> > > HA256,TLS_DHE_RSA_WITH_AES_128_CCM,
> > >
> > >
> > TLS_ECDHE_ECDSA_WITH_AES_128_CCM,TLS_DHE_RSA_WITH_AES_128_CC
> > M_8,TLS_EC
> > > DHE_ECDSA_WITH_AES_128_CCM_8,
> > >
> > >
> > TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256,TLS_ECDHE_RSA_WITH
> > _CHACHA20_
> > > POLY1305_SHA256,
> > >
> > > TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256">
> > > > > certificateKeystoreFile=" > > (JKS)>"
> > > certificateKeystorePassword ="${keystore.pass}"
> > > certificateKeyPassword="${keystore.pass}"
> > > certificateKeyAlias=""
> > > />
> > >
> > > Now, restart your Tomcat.
> > >
> > > If so, do we just add the TLS 1.3 ciphers to the list?
> > >
> > > Dream * Excel * Explore * Inspire
> > > Jon McAlexander
> > > Senior Infrastructure Engineer
> > >
Re: Tips on identifying the DB connection leaks leading to the "Pool empty" error
Use logAbandoned as a boolean parameter, you will get stacktraces in the log. From those you can narrow down where you are leaking connections. Akshay Mishra schrieb am Di., 18. Apr. 2023, 01:07: > Hello Tomcat Community! > > > Tomcat Version: 9.0.70 > > Our Tomcat web service started exhausting the max connections allowed to > the backend datastore (Postgres). > > From the logs, we don’t see any 1 thread requesting lot of connections. > Nor do we see too many threads requesting a new connection. > We collected thread dumps (at a fixed interval of 5 mins) and they do not > point to too many threads requesting connections. > > We suspect someone could be leaking connections but we are unclear on how > to narrow that down especially since the thread dump was inconclusive > > We added parameters like “removeAbandoned”, “removeAbandonedTimeout” and > “ResetAbandonedTimer” to our datasource config and the results were > encouraging - we don't see the pool getting exhausted but are concerned > this might mask a larger problem in case there are connection leaks in our > service. > > It would be great if the community has any thoughts on these new > parameters. Or on way to narrow down the problem to isolate connection > leaks. > > Any help is appreciated. Thanks > > Akshay >
Re: ClassNotFound after upgrade to tomcat 10
The whole thing is also well answered there btw: https://stackoverflow.com/questions/4928271/how-to-install-jstl-the-absolute-uri-http-java-sun-com-jstl-core-cannot-be-r#4928309 Kevin Huntly schrieb am Di., 18. Apr. 2023, 00:52: > I am now seeing this: > > 17-Apr-2023 18:50:44.450 SEVERE [catalina-exec-1] > org.apache.catalina.core.ApplicationDispatcher.invoke Servlet.service() for > servlet [jsp] threw exception > org.apache.jasper.JasperException: > /com.cws.esolutions.web.login/jsp/html/en/Login.jsp (line: [1], column: > [1]) Unable to find taglib [c] for URI: [jakarta.tags.core] > > After updating the taglib imports on my jsp files > > > Kevin Huntly > Email: kmhun...@gmail.com > Cell: 716/424-3311 > > > -BEGIN GEEK CODE BLOCK- > Version: 1.0 > GCS/IT d+ s a C++ UL+++$ P+(++) L+++ E--- > W+++ N+ o K(+) w--- O- M-- V-- PS+ PE Y(+) > PGP++(+++) t+ 5-- X-- R+ tv+ b++ DI++ D++ > G++ e(+) h--- r+++ y+++* > --END GEEK CODE BLOCK-- > > > On Mon, Apr 17, 2023 at 6:47 PM Torsten Krah wrote: > > > And update your taglib definitions, see here: > > > > https://jakarta.ee/specifications/tags/3.0/ > > > > The old ones are deprecated/ removed: > > > > Quote: > > > > Rename java.sun.com taglib URIs to new jakarta.tags.* URNs. > > > > > > > > Kevin Huntly schrieb am Di., 18. Apr. 2023, 00:34: > > > > > Now i'm getting these: > > > > > > 17-Apr-2023 18:32:03.236 INFO [main] > > > org.apache.catalina.core.ApplicationContext.log No Spring > > > WebApplicationInitializer types detected on classpath > > > 17-Apr-2023 18:32:04.904 INFO [main] > > > org.apache.catalina.core.ApplicationContext.log Initializing Spring > > > DispatcherServlet 'eSolutions' > > > 17-Apr-2023 18:32:16.844 SEVERE [catalina-exec-1] > > > org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() > > for > > > servlet [eSolutions] in context with path [/esolutions] threw exception > > > [Handler processing failed: java.lang.NoClassDefFoundError: > > > jakarta/servlet/jsp/jstl/core/Config] with root cause > > > java.lang.ClassNotFoundException: > > > jakarta.servlet.jsp.jstl.core.Config > > > > > > 17-Apr-2023 18:32:16.986 SEVERE [catalina-exec-1] > > > org.apache.catalina.core.ApplicationDispatcher.invoke Servlet.service() > > for > > > servlet [jsp] threw exception > > > org.apache.jasper.JasperException: > > > /theme/cws/html/en/jsp/errHandler.jsp (line: [1], column: [1]) The > > absolute > > > uri: [http://java.sun.com/jsp/jstl/core] cannot be resolved in either > > > web.xml or the jar files deployed with this application > > > > > > I removed the apache taglibs dependency, clearly that was a mistake. > > > > > > > > > Kevin Huntly > > > Email: kmhun...@gmail.com > > > Cell: 716/424-3311 > > > > > > > > > -BEGIN GEEK CODE BLOCK- > > > Version: 1.0 > > > GCS/IT d+ s a C++ UL+++$ P+(++) L+++ E--- > > > W+++ N+ o K(+) w--- O- M-- V-- PS+ PE Y(+) > > > PGP++(+++) t+ 5-- X-- R+ tv+ b++ DI++ D++ > > > G++ e(+) h--- r+++ y+++* > > > --END GEEK CODE BLOCK-- > > > > > > > > > On Mon, Apr 17, 2023 at 6:26 PM Torsten Krah > wrote: > > > > > > > You should only use https://jakarta.ee/specifications/tags/3.0/ and > > not > > > > the > > > > old 1.2.5 one, remove that old one. > > > > Why do you have both included? > > > > > > > > Kevin Huntly schrieb am Di., 18. Apr. 2023, > > 00:19: > > > > > > > > > 6.0.0 > > > > > > > > > > 1.2.5 > > > > > > > > > > 3.0.0 > > > > > > > > > > 3.1.1 > > > > > > > > > > > > > > > Kevin Huntly > > > > > Email: kmhun...@gmail.com > > > > > Cell: 716/424-3311 > > > > > > > > > > > > > > > -BEGIN GEEK CODE BLOCK- > > > > > Version: 1.0 > > > > > GCS/IT d+ s a C++ UL+++$ P+(++) L+++ E--- > > > > > W+++ N+ o K(+) w--- O-
Re: ClassNotFound after upgrade to tomcat 10
https://stackoverflow.com/questions/74585710/migration-to-jakarta-ee-unable-to-find-taglib-c-for-uri-jakarta-tags-core Does that help? Kevin Huntly schrieb am Di., 18. Apr. 2023, 00:52: > I am now seeing this: > > 17-Apr-2023 18:50:44.450 SEVERE [catalina-exec-1] > org.apache.catalina.core.ApplicationDispatcher.invoke Servlet.service() for > servlet [jsp] threw exception > org.apache.jasper.JasperException: > /com.cws.esolutions.web.login/jsp/html/en/Login.jsp (line: [1], column: > [1]) Unable to find taglib [c] for URI: [jakarta.tags.core] > > After updating the taglib imports on my jsp files > > > Kevin Huntly > Email: kmhun...@gmail.com > Cell: 716/424-3311 > > > -BEGIN GEEK CODE BLOCK- > Version: 1.0 > GCS/IT d+ s a C++ UL+++$ P+(++) L+++ E--- > W+++ N+ o K(+) w--- O- M-- V-- PS+ PE Y(+) > PGP++(+++) t+ 5-- X-- R+ tv+ b++ DI++ D++ > G++ e(+) h--- r+++ y+++* > --END GEEK CODE BLOCK-- > > > On Mon, Apr 17, 2023 at 6:47 PM Torsten Krah wrote: > > > And update your taglib definitions, see here: > > > > https://jakarta.ee/specifications/tags/3.0/ > > > > The old ones are deprecated/ removed: > > > > Quote: > > > > Rename java.sun.com taglib URIs to new jakarta.tags.* URNs. > > > > > > > > Kevin Huntly schrieb am Di., 18. Apr. 2023, 00:34: > > > > > Now i'm getting these: > > > > > > 17-Apr-2023 18:32:03.236 INFO [main] > > > org.apache.catalina.core.ApplicationContext.log No Spring > > > WebApplicationInitializer types detected on classpath > > > 17-Apr-2023 18:32:04.904 INFO [main] > > > org.apache.catalina.core.ApplicationContext.log Initializing Spring > > > DispatcherServlet 'eSolutions' > > > 17-Apr-2023 18:32:16.844 SEVERE [catalina-exec-1] > > > org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() > > for > > > servlet [eSolutions] in context with path [/esolutions] threw exception > > > [Handler processing failed: java.lang.NoClassDefFoundError: > > > jakarta/servlet/jsp/jstl/core/Config] with root cause > > > java.lang.ClassNotFoundException: > > > jakarta.servlet.jsp.jstl.core.Config > > > > > > 17-Apr-2023 18:32:16.986 SEVERE [catalina-exec-1] > > > org.apache.catalina.core.ApplicationDispatcher.invoke Servlet.service() > > for > > > servlet [jsp] threw exception > > > org.apache.jasper.JasperException: > > > /theme/cws/html/en/jsp/errHandler.jsp (line: [1], column: [1]) The > > absolute > > > uri: [http://java.sun.com/jsp/jstl/core] cannot be resolved in either > > > web.xml or the jar files deployed with this application > > > > > > I removed the apache taglibs dependency, clearly that was a mistake. > > > > > > > > > Kevin Huntly > > > Email: kmhun...@gmail.com > > > Cell: 716/424-3311 > > > > > > > > > -BEGIN GEEK CODE BLOCK- > > > Version: 1.0 > > > GCS/IT d+ s a C++ UL+++$ P+(++) L+++ E--- > > > W+++ N+ o K(+) w--- O- M-- V-- PS+ PE Y(+) > > > PGP++(+++) t+ 5-- X-- R+ tv+ b++ DI++ D++ > > > G++ e(+) h--- r+++ y+++* > > > --END GEEK CODE BLOCK-- > > > > > > > > > On Mon, Apr 17, 2023 at 6:26 PM Torsten Krah > wrote: > > > > > > > You should only use https://jakarta.ee/specifications/tags/3.0/ and > > not > > > > the > > > > old 1.2.5 one, remove that old one. > > > > Why do you have both included? > > > > > > > > Kevin Huntly schrieb am Di., 18. Apr. 2023, > > 00:19: > > > > > > > > > 6.0.0 > > > > > > > > > > 1.2.5 > > > > > > > > > > 3.0.0 > > > > > > > > > > 3.1.1 > > > > > > > > > > > > > > > Kevin Huntly > > > > > Email: kmhun...@gmail.com > > > > > Cell: 716/424-3311 > > > > > > > > > > > > > > > -BEGIN GEEK CODE BLOCK- > > > > > Version: 1.0 > > > > > GCS/IT d+ s a C++ UL+++$ P+(++) L+++ E--- > > > > > W+++ N+ o K(+) w--- O-
Re: ClassNotFound after upgrade to tomcat 10
And update your taglib definitions, see here:
https://jakarta.ee/specifications/tags/3.0/
The old ones are deprecated/ removed:
Quote:
Rename java.sun.com taglib URIs to new jakarta.tags.* URNs.
Kevin Huntly schrieb am Di., 18. Apr. 2023, 00:34:
> Now i'm getting these:
>
> 17-Apr-2023 18:32:03.236 INFO [main]
> org.apache.catalina.core.ApplicationContext.log No Spring
> WebApplicationInitializer types detected on classpath
> 17-Apr-2023 18:32:04.904 INFO [main]
> org.apache.catalina.core.ApplicationContext.log Initializing Spring
> DispatcherServlet 'eSolutions'
> 17-Apr-2023 18:32:16.844 SEVERE [catalina-exec-1]
> org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for
> servlet [eSolutions] in context with path [/esolutions] threw exception
> [Handler processing failed: java.lang.NoClassDefFoundError:
> jakarta/servlet/jsp/jstl/core/Config] with root cause
> java.lang.ClassNotFoundException:
> jakarta.servlet.jsp.jstl.core.Config
>
> 17-Apr-2023 18:32:16.986 SEVERE [catalina-exec-1]
> org.apache.catalina.core.ApplicationDispatcher.invoke Servlet.service() for
> servlet [jsp] threw exception
> org.apache.jasper.JasperException:
> /theme/cws/html/en/jsp/errHandler.jsp (line: [1], column: [1]) The absolute
> uri: [http://java.sun.com/jsp/jstl/core] cannot be resolved in either
> web.xml or the jar files deployed with this application
>
> I removed the apache taglibs dependency, clearly that was a mistake.
>
>
> Kevin Huntly
> Email: kmhun...@gmail.com
> Cell: 716/424-3311
>
>
> -BEGIN GEEK CODE BLOCK-
> Version: 1.0
> GCS/IT d+ s a C++ UL+++$ P+(++) L+++ E---
> W+++ N+ o K(+) w--- O- M-- V-- PS+ PE Y(+)
> PGP++(+++) t+ 5-- X-- R+ tv+ b++ DI++ D++
> G++ e(+) h--- r+++ y+++*
> --END GEEK CODE BLOCK--
>
>
> On Mon, Apr 17, 2023 at 6:26 PM Torsten Krah wrote:
>
> > You should only use https://jakarta.ee/specifications/tags/3.0/ and not
> > the
> > old 1.2.5 one, remove that old one.
> > Why do you have both included?
> >
> > Kevin Huntly schrieb am Di., 18. Apr. 2023, 00:19:
> >
> > > 6.0.0
> > >
> > > 1.2.5
> > >
> > > 3.0.0
> > >
> > > 3.1.1
> > >
> > >
> > > Kevin Huntly
> > > Email: kmhun...@gmail.com
> > > Cell: 716/424-3311
> > >
> > >
> > > -BEGIN GEEK CODE BLOCK-
> > > Version: 1.0
> > > GCS/IT d+ s a C++ UL+++$ P+(++) L+++ E---
> > > W+++ N+ o K(+) w--- O- M-- V-- PS+ PE Y(+)
> > > PGP++(+++) t+ 5-- X-- R+ tv+ b++ DI++ D++
> > > G++ e(+) h--- r+++ y+++*
> > > --END GEEK CODE BLOCK--
> > >
> > >
> > > On Mon, Apr 17, 2023 at 6:17 PM Torsten Krah
> wrote:
> > >
> > > > All the api ones have to be provided, not compile scope imho. Tomcat
> > does
> > > > provide them, don't package them in your war file and double check
> the
> > > > versions from the guide, there is still a class referencing the old
> API
> > > and
> > > > is causing the exception.
> > > >
> > > > You missed to add the versions you used, add them here please, the
> > > > information you provided is lacking those crucial detail.
> > > >
> > > > Kevin Huntly schrieb am Di., 18. Apr. 2023,
> > 00:12:
> > > >
> > > > > Thank you for that... I have the right (I think) dependencies in my
> > > pom:
> > > > >
> > > > >
> > > > >
> > > > > org.apache.taglibs
> > > > >
> > > > > taglibs-standard-impl
> > > > >
> > > > > ${taglibs.version}
> > > > >
> > > > > jar
> > > > >
> > > > > compile
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > jakarta.servlet.jsp.jstl
> > > > >
> > > > > jakarta.servlet.jsp.jstl-api
> > > > >
> > > > > ${jstl.version}
> > > > >
> > > > > jar
> > > > >
> > > > > compile
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > jakarta.servlet.jsp
> > > > >
> > > > &g
Re: ClassNotFound after upgrade to tomcat 10
The Jakarta jstl ones have to be compile scope, they are not included in
tomcat, do you have that?
See the migration guide, spec section, only those APIs listed there should
be provided scope.
Kevin Huntly schrieb am Di., 18. Apr. 2023, 00:34:
> Now i'm getting these:
>
> 17-Apr-2023 18:32:03.236 INFO [main]
> org.apache.catalina.core.ApplicationContext.log No Spring
> WebApplicationInitializer types detected on classpath
> 17-Apr-2023 18:32:04.904 INFO [main]
> org.apache.catalina.core.ApplicationContext.log Initializing Spring
> DispatcherServlet 'eSolutions'
> 17-Apr-2023 18:32:16.844 SEVERE [catalina-exec-1]
> org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for
> servlet [eSolutions] in context with path [/esolutions] threw exception
> [Handler processing failed: java.lang.NoClassDefFoundError:
> jakarta/servlet/jsp/jstl/core/Config] with root cause
> java.lang.ClassNotFoundException:
> jakarta.servlet.jsp.jstl.core.Config
>
> 17-Apr-2023 18:32:16.986 SEVERE [catalina-exec-1]
> org.apache.catalina.core.ApplicationDispatcher.invoke Servlet.service() for
> servlet [jsp] threw exception
> org.apache.jasper.JasperException:
> /theme/cws/html/en/jsp/errHandler.jsp (line: [1], column: [1]) The absolute
> uri: [http://java.sun.com/jsp/jstl/core] cannot be resolved in either
> web.xml or the jar files deployed with this application
>
> I removed the apache taglibs dependency, clearly that was a mistake.
>
>
> Kevin Huntly
> Email: kmhun...@gmail.com
> Cell: 716/424-3311
>
>
> -BEGIN GEEK CODE BLOCK-
> Version: 1.0
> GCS/IT d+ s a C++ UL+++$ P+(++) L+++ E---
> W+++ N+ o K(+) w--- O- M-- V-- PS+ PE Y(+)
> PGP++(+++) t+ 5-- X-- R+ tv+ b++ DI++ D++
> G++ e(+) h--- r+++ y+++*
> --END GEEK CODE BLOCK--
>
>
> On Mon, Apr 17, 2023 at 6:26 PM Torsten Krah wrote:
>
> > You should only use https://jakarta.ee/specifications/tags/3.0/ and not
> > the
> > old 1.2.5 one, remove that old one.
> > Why do you have both included?
> >
> > Kevin Huntly schrieb am Di., 18. Apr. 2023, 00:19:
> >
> > > 6.0.0
> > >
> > > 1.2.5
> > >
> > > 3.0.0
> > >
> > > 3.1.1
> > >
> > >
> > > Kevin Huntly
> > > Email: kmhun...@gmail.com
> > > Cell: 716/424-3311
> > >
> > >
> > > -BEGIN GEEK CODE BLOCK-
> > > Version: 1.0
> > > GCS/IT d+ s a C++ UL+++$ P+(++) L+++ E---
> > > W+++ N+ o K(+) w--- O- M-- V-- PS+ PE Y(+)
> > > PGP++(+++) t+ 5-- X-- R+ tv+ b++ DI++ D++
> > > G++ e(+) h--- r+++ y+++*
> > > --END GEEK CODE BLOCK--
> > >
> > >
> > > On Mon, Apr 17, 2023 at 6:17 PM Torsten Krah
> wrote:
> > >
> > > > All the api ones have to be provided, not compile scope imho. Tomcat
> > does
> > > > provide them, don't package them in your war file and double check
> the
> > > > versions from the guide, there is still a class referencing the old
> API
> > > and
> > > > is causing the exception.
> > > >
> > > > You missed to add the versions you used, add them here please, the
> > > > information you provided is lacking those crucial detail.
> > > >
> > > > Kevin Huntly schrieb am Di., 18. Apr. 2023,
> > 00:12:
> > > >
> > > > > Thank you for that... I have the right (I think) dependencies in my
> > > pom:
> > > > >
> > > > >
> > > > >
> > > > > org.apache.taglibs
> > > > >
> > > > > taglibs-standard-impl
> > > > >
> > > > > ${taglibs.version}
> > > > >
> > > > > jar
> > > > >
> > > > > compile
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > jakarta.servlet.jsp.jstl
> > > > >
> > > > > jakarta.servlet.jsp.jstl-api
> > > > >
> > > > > ${jstl.version}
> > > > >
> > > > > jar
> > > > >
> > > > > compile
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > jakarta.servlet.jsp
> > > > >
> > > > &g
Re: ClassNotFound after upgrade to tomcat 10
You should only use https://jakarta.ee/specifications/tags/3.0/ and not the
old 1.2.5 one, remove that old one.
Why do you have both included?
Kevin Huntly schrieb am Di., 18. Apr. 2023, 00:19:
> 6.0.0
>
> 1.2.5
>
> 3.0.0
>
> 3.1.1
>
>
> Kevin Huntly
> Email: kmhun...@gmail.com
> Cell: 716/424-3311
>
>
> -BEGIN GEEK CODE BLOCK-
> Version: 1.0
> GCS/IT d+ s a C++ UL+++$ P+(++) L+++ E---
> W+++ N+ o K(+) w--- O- M-- V-- PS+ PE Y(+)
> PGP++(+++) t+ 5-- X-- R+ tv+ b++ DI++ D++
> G++ e(+) h--- r+++ y+++*
> --END GEEK CODE BLOCK--
>
>
> On Mon, Apr 17, 2023 at 6:17 PM Torsten Krah wrote:
>
> > All the api ones have to be provided, not compile scope imho. Tomcat does
> > provide them, don't package them in your war file and double check the
> > versions from the guide, there is still a class referencing the old API
> and
> > is causing the exception.
> >
> > You missed to add the versions you used, add them here please, the
> > information you provided is lacking those crucial detail.
> >
> > Kevin Huntly schrieb am Di., 18. Apr. 2023, 00:12:
> >
> > > Thank you for that... I have the right (I think) dependencies in my
> pom:
> > >
> > >
> > >
> > > org.apache.taglibs
> > >
> > > taglibs-standard-impl
> > >
> > > ${taglibs.version}
> > >
> > > jar
> > >
> > > compile
> > >
> > >
> > >
> > >
> > >
> > > jakarta.servlet.jsp.jstl
> > >
> > > jakarta.servlet.jsp.jstl-api
> > >
> > > ${jstl.version}
> > >
> > > jar
> > >
> > > compile
> > >
> > >
> > >
> > >
> > >
> > > jakarta.servlet.jsp
> > >
> > > jakarta.servlet.jsp-api
> > >
> > > ${jsp-api.version}
> > >
> > > jar
> > >
> > > compile
> > >
> > >
> > >
> > >
> > >
> > > jakarta.servlet
> > >
> > > jakarta.servlet-api
> > >
> > > ${jakarta.servlet.version}
> > >
> > > jar
> > >
> > > provided
> > >
> > >
> > >
> > >
> > > I just want to use the jstl tag libraries =(
> > >
> > >
> > > Kevin Huntly
> > > Email: kmhun...@gmail.com
> > > Cell: 716/424-3311
> > >
> > >
> > > -BEGIN GEEK CODE BLOCK-
> > > Version: 1.0
> > > GCS/IT d+ s a C++ UL+++$ P+(++) L+++ E---
> > > W+++ N+ o K(+) w--- O- M-- V-- PS+ PE Y(+)
> > > PGP++(+++) t+ 5-- X-- R+ tv+ b++ DI++ D++
> > > G++ e(+) h--- r+++ y+++*
> > > --END GEEK CODE BLOCK--
> > >
> > >
> > > On Mon, Apr 17, 2023 at 6:07 PM Torsten Krah
> wrote:
> > >
> > > > Please read
> > https://tomcat.apache.org/migration-10.html#Server_Pages_3.0
> > > > and while you are there, read the whole guide ;-).
> > > >
> > > > Kevin Huntly schrieb am Mo., 17. Apr. 2023,
> > 23:57:
> > > >
> > > > > Hello,
> > > > >
> > > > > I'm getting the following exception when I try to access my webapp:
> > > > >
> > > > > 17-Apr-2023 17:52:55.982 SEVERE [catalina-exec-1]
> > > > > org.apache.catalina.core.ApplicationDispatcher.invoke
> > Servlet.service()
> > > > for
> > > > > servlet [jsp] threw exception
> > > > > java.lang.ClassNotFoundException:
> > > > > javax.servlet.jsp.tagext.TagLibraryValidator
> > > > > at
> > > > >
> > > > >
> > > >
> > >
> >
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1437)
> > > > > at
> > > > >
> > > > >
> > > >
> > >
> >
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1245)
> > > > > at
> > java.base/java.lang.ClassLoader.defineClass1(Native
> > > > > Method)
> > > > > at
> > > > > java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1013)
> > > >
Re: ClassNotFound after upgrade to tomcat 10
All the api ones have to be provided, not compile scope imho. Tomcat does
provide them, don't package them in your war file and double check the
versions from the guide, there is still a class referencing the old API and
is causing the exception.
You missed to add the versions you used, add them here please, the
information you provided is lacking those crucial detail.
Kevin Huntly schrieb am Di., 18. Apr. 2023, 00:12:
> Thank you for that... I have the right (I think) dependencies in my pom:
>
>
>
> org.apache.taglibs
>
> taglibs-standard-impl
>
> ${taglibs.version}
>
> jar
>
> compile
>
>
>
>
>
> jakarta.servlet.jsp.jstl
>
> jakarta.servlet.jsp.jstl-api
>
> ${jstl.version}
>
> jar
>
> compile
>
>
>
>
>
> jakarta.servlet.jsp
>
> jakarta.servlet.jsp-api
>
> ${jsp-api.version}
>
> jar
>
> compile
>
>
>
>
>
> jakarta.servlet
>
> jakarta.servlet-api
>
> ${jakarta.servlet.version}
>
> jar
>
> provided
>
>
>
>
> I just want to use the jstl tag libraries =(
>
>
> Kevin Huntly
> Email: kmhun...@gmail.com
> Cell: 716/424-3311
>
>
> -BEGIN GEEK CODE BLOCK-
> Version: 1.0
> GCS/IT d+ s a C++ UL+++$ P+(++) L+++ E---
> W+++ N+ o K(+) w--- O- M-- V-- PS+ PE Y(+)
> PGP++(+++) t+ 5-- X-- R+ tv+ b++ DI++ D++
> G++ e(+) h--- r+++ y+++*
> --END GEEK CODE BLOCK--
>
>
> On Mon, Apr 17, 2023 at 6:07 PM Torsten Krah wrote:
>
> > Please read https://tomcat.apache.org/migration-10.html#Server_Pages_3.0
> > and while you are there, read the whole guide ;-).
> >
> > Kevin Huntly schrieb am Mo., 17. Apr. 2023, 23:57:
> >
> > > Hello,
> > >
> > > I'm getting the following exception when I try to access my webapp:
> > >
> > > 17-Apr-2023 17:52:55.982 SEVERE [catalina-exec-1]
> > > org.apache.catalina.core.ApplicationDispatcher.invoke Servlet.service()
> > for
> > > servlet [jsp] threw exception
> > > java.lang.ClassNotFoundException:
> > > javax.servlet.jsp.tagext.TagLibraryValidator
> > > at
> > >
> > >
> >
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1437)
> > > at
> > >
> > >
> >
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1245)
> > > at java.base/java.lang.ClassLoader.defineClass1(Native
> > > Method)
> > > at
> > > java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1013)
> > > at
> > >
> > >
> >
> java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:150)
> > > at
> > >
> > >
> >
> org.apache.catalina.loader.WebappClassLoaderBase.findClassInternal(WebappClassLoaderBase.java:2487)
> > > at
> > >
> > >
> >
> org.apache.catalina.loader.WebappClassLoaderBase.findClass(WebappClassLoaderBase.java:865)
> > > at
> > >
> > >
> >
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1401)
> > > at
> > >
> > >
> >
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1245)
> > >
> > > it's running on AlmaLinux and tomcat 10.1.7. If I do a grep for
> > > "TagLibraryValidator" I can find it in my app under WEB-INF/lib, so I'm
> > not
> > > sure what's going on
> > >
> > >
> > > Kevin Huntly
> > > Email: kmhun...@gmail.com
> > > Cell: 716/424-3311
> > >
> > >
> > > -BEGIN GEEK CODE BLOCK-
> > > Version: 1.0
> > > GCS/IT d+ s a C++ UL+++$ P+(++) L+++ E---
> > > W+++ N+ o K(+) w--- O- M-- V-- PS+ PE Y(+)
> > > PGP++(+++) t+ 5-- X-- R+ tv+ b++ DI++ D++
> > > G++ e(+) h--- r+++ y+++*
> > > --END GEEK CODE BLOCK--
> > >
> >
>
Re: ClassNotFound after upgrade to tomcat 10
Please read https://tomcat.apache.org/migration-10.html#Server_Pages_3.0 and while you are there, read the whole guide ;-). Kevin Huntly schrieb am Mo., 17. Apr. 2023, 23:57: > Hello, > > I'm getting the following exception when I try to access my webapp: > > 17-Apr-2023 17:52:55.982 SEVERE [catalina-exec-1] > org.apache.catalina.core.ApplicationDispatcher.invoke Servlet.service() for > servlet [jsp] threw exception > java.lang.ClassNotFoundException: > javax.servlet.jsp.tagext.TagLibraryValidator > at > > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1437) > at > > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1245) > at java.base/java.lang.ClassLoader.defineClass1(Native > Method) > at > java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1013) > at > > java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:150) > at > > org.apache.catalina.loader.WebappClassLoaderBase.findClassInternal(WebappClassLoaderBase.java:2487) > at > > org.apache.catalina.loader.WebappClassLoaderBase.findClass(WebappClassLoaderBase.java:865) > at > > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1401) > at > > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1245) > > it's running on AlmaLinux and tomcat 10.1.7. If I do a grep for > "TagLibraryValidator" I can find it in my app under WEB-INF/lib, so I'm not > sure what's going on > > > Kevin Huntly > Email: kmhun...@gmail.com > Cell: 716/424-3311 > > > -BEGIN GEEK CODE BLOCK- > Version: 1.0 > GCS/IT d+ s a C++ UL+++$ P+(++) L+++ E--- > W+++ N+ o K(+) w--- O- M-- V-- PS+ PE Y(+) > PGP++(+++) t+ 5-- X-- R+ tv+ b++ DI++ D++ > G++ e(+) h--- r+++ y+++* > --END GEEK CODE BLOCK-- >
Re: Multiple entries
That has nothing to do with Tomcat, just autowire them by name and not by type like the exception is telling you. Kevin Huntly schrieb am Fr., 14. Apr. 2023, 13:47: > Hi Everyone, > > I can't remember if I posted this already or not (and I don't know how to > check)... I'm getting the following message when I have more than one > value to obtain: > > tomcat config in context.xml > override="false" /> > override="false" /> > override="false" /> > > And my Spring config: > > jndi-name="java:comp/env/isTestSystem" /> > > "java:comp/env/webURL" /> > > jndi-name="java:comp/env/isResetAvailable" /> > > > I'm getting the following exception: > > > Caused by: > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name 'appConfig': Unsatisfied dependency expressed > through field 'homePage'; nested exception is > org.springframework.beans.factory.NoUniqueBeanDefinitionException: No > qualifying bean of type 'java.lang.String' available: expected single > matching bean but found 2: isTestSystem,webURL Anyone have any ideas? > > > Kevin Huntly > Email: kmhun...@gmail.com > Cell: 716/424-3311 > > > -BEGIN GEEK CODE BLOCK- > Version: 1.0 > GCS/IT d+ s a C++ UL+++$ P+(++) L+++ E--- > W+++ N+ o K(+) w--- O- M-- V-- PS+ PE Y(+) > PGP++(+++) t+ 5-- X-- R+ tv+ b++ DI++ D++ > G++ e(+) h--- r+++ y+++* > --END GEEK CODE BLOCK--
Re: Quick Question with Tomcat 10.1x
schrieb am Do., 16. März 2023, 19:32: > Hi, > I have a really simple war file I created to "test" that Tomcat is coming > up and running. It works fine on Tomcat 8.5x, 9.0x, AND 10.0x, however on > 10.1.7 I am getting this strange stack trace. I'm not able to determine > just what is being called out. > > SEVERE: Servlet.service() for servlet [jsp] in context with path [/pouat] > threw exception [java.lang.NoClassDefFoundError: > javax/servlet/ServletResponse] with root cause > java.lang.ClassNotFoundException: javax.servlet.ServletResponse > at > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1437) > at > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1245) > at > org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader.java:122) > at > org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader.java:58) > at > java.base/java.lang.Class.getDeclaredConstructors0(Native Method) > at > java.base/java.lang.Class.privateGetDeclaredConstructors(Class.java:3137) > at > java.base/java.lang.Class.getConstructor0(Class.java:3342) > at > java.base/java.lang.Class.getConstructor(Class.java:2151) > at > org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:160) > at > org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:189) > at > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:410) > at > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:380) > at > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:328) > at > jakarta.servlet.http.HttpServlet.service(HttpServlet.java:814) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:223) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:158) > at > org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:185) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:158) > at > org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter(HttpHeaderSecurityFilter.java:126) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:185) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:158) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:177) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97) > at > org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:542) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:119) > at > org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:690) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78) > at > org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:690) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:357) > at > org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:400) > at > org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) > at > org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:859) > at org.apache.tomcat.util.net > .NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1734) > at org.apache.tomcat.util.net > .SocketProcessorBase.run(SocketProcessorBase.java:52) > at > org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191) > at > org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659) > at > org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) > at java.base/java.lang.Thread.run(Thread.java:834) > > Any hints on what I should look at? > > The test site does have SSL enabled. > > Thank you, > > Dream * Excel * Explore * Inspire > Jon McAlexander > Senior Infrastructure Engineer > Asst. Vice President > He/His > > Middleware Product Engineering > Enterprise CIO | EAS | Middleware |
Re: tomcat-embedded 9.x -> 10.1.x - how to set ssl honor cipher order option now
> Now there is a single method. This should
> do what you need:
>
> SSLHostConfig[] sslHostConfigs = httpHandler.findSslHostConfigs();
>
> for (SSLHostConfig sslHostConfig : sslHostConfigs) {
> sslHostConfig.setHonorCipherOrder(true);
> }
That is even better now, thanks.
>
>
> Mark
Torsten
--
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
tomcat-embedded 9.x -> 10.1.x - how to set ssl honor cipher order option now
Hi, using tomcat-embed 9.x I was able to customize my protocol handler like this: AbstractHttp11Protocol httpHandler = ((AbstractHttp11Protocol) connector.getProtocolHandler()); httpHandler.setSSLHonorCipherOrder(true); httpHandler.setUseServerCipherSuitesOrder(true); Switched to 10.1.1 now and those 2 methods are gone and I am wondering where they are now and how to access them when coming from the connector. Any help appreciated. kind regards Torsten -- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Variables in server.xml leads to error when stopping Tomcat
Am Donnerstag, dem 05.05.2022 um 06:42 + schrieb Boesch, Henning (G-GPPD): > export CATALINA_OPTS="-Dport.shutdown=12345 $CATALINA_OPTS" The docs have this: # CATALINA_OPTS (Optional) Java runtime options used when the "start", # "run" or "debug" command is executed. # Include here and not in JAVA_OPTS all options, that should # only be used by Tomcat itself, not by the stop process, # the version command etc. # Examples are heap size, GC logging, JMX ports etc You need to put "-Dport.shutdown=12345" to the JAVA_OPTS because the stop process needs that port. Torsten - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 9.0.59 - TLS 1.3 cipher configuration ignored (TLS 1.2 ok)
Am Dienstag, dem 15.03.2022 um 15:29 +0100 schrieb Rémy Maucherat: > I used Panama for prototyping, SSL_CTX_set_ciphersuites works but is > > not so trivial to use. If you try using the ciphersuite for more than > > 1.3, there will be warnings (which I improved), and the default > Tomcat > > uses also does not make sense for 1.3. I wonder if it should revert > to > > not setting anything in that case (which would need some more > > changes). > > > > Rémy Should I open a bug / feature request in bugzilla to track that feature? Torsten -- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 9.0.59 - TLS 1.3 cipher configuration ignored (TLS 1.2 ok)
> It seems to me you are listing a cipher that might be correct > according to the OpenSSL documentation, but then whether that is > available to your JVM may be different. That is for sure not the problem - just use the "ciphers.sh" from the binary directory of tomcat which will list you all possible ciphers you can use - and those match the ones I want to use. > > Maybe you can run some small java application on the very same JVM to > simply list the supported ciphers? At least that would give you an > authorative list of ciphers you can put into the configuration file. No need for that, tomcat already has that - use ciphers.sh . As Thomas found, it is a known bug / missing feature of tomcat - you can't configure TLS 1.3 ciphers in tomcat yet if you want to use the OpenSSL native implementation and Mark Thomas confirmed that here: https://lists.apache.org/thread/q8lmp40xkn0b4k4o6n05n9fyttlvmd22 That was 08/2019 - but it still is unsupported in 03/2022 - maybe I'll do a patch for that one ;). kind regards Torsten - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 9.0.59 - TLS 1.3 cipher configuration ignored (TLS 1.2 ok)
Am Freitag, dem 11.03.2022 um 09:17 + schrieb Thomas Hoffmann (Speed4Trade GmbH): > The configuration which works for me is: > > protocol="org.apache.coyote.http11.Http11NioProtocol" > > > sslImplementationName="org.apache.tomcat.util.net.openssl.OpenSSLImpl > ementation" > >maxThreads="150" minSpareThreads="25" > >URIEncoding="UTF-8" useBodyEncodingForURI="false" > >enableLookups="false" disableUploadTimeout="true" > >acceptCount="100" scheme="https" secure="true" > >SSLEnabled="true"> > > > disab > leSessionTickets="true" > > honor > CipherOrder="false" > > proto > cols="+TLSv1.2,+TLSv1.3"> I am using: protocol="org.apache.coyote.http11.Http11Nio2Protocol" and in combination with the native APR in place it does the correct thing, using OpenSSL - and the error shows that this is in place. The list of protocols can be either of those - see the https://tomcat.apache.org/tomcat-9.0-doc/config/http.html ciphers docs: The ciphers to enable using the OpenSSL syntax. (See the OpenSSL documentation for the list of ciphers supported and the syntax). Alternatively, a comma separated list of ciphers using the standard OpenSSL cipher names or the standard JSSE cipher names may be used. Your example does not have any TLS 1.3 cipher listet - so you just get the 3 defaults (which I want / need to change) - and as seen in the code it won't work anyway, because it does not call: SSL_CTX_set_ciphersuites() to set the 1.3 suites. kind regards Torsten - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 9.0.59 - TLS 1.3 cipher configuration ignored (TLS 1.2 ok)
Am Freitag, dem 11.03.2022 um 10:09 +0100 schrieb Torsten Krah:
> So it seems like a bug to me, right?
I had a quick look on the JNI SSLContext code + the native
implementation:
TCN_IMPLEMENT_CALL(jboolean, SSL, setCipherSuites)(TCN_STDARGS, jlong ssl,
jstring ciphers)
{
jboolean rv = JNI_TRUE;
SSL *ssl_ = J2P(ssl, SSL *);
TCN_ALLOC_CSTRING(ciphers);
UNREFERENCED_STDARGS;
if (ssl_ == NULL) {
TCN_FREE_CSTRING(ciphers);
tcn_ThrowException(e, "ssl is null");
return JNI_FALSE;
}
UNREFERENCED(o);
if (!J2S(ciphers)) {
TCN_FREE_CSTRING(ciphers);
return JNI_FALSE;
}
if (!SSL_set_cipher_list(ssl_, J2S(ciphers))) {
char err[256];
ERR_error_string(SSL_ERR_get(), err);
tcn_Throw(e, "Unable to configure permitted SSL ciphers (%s)", err);
rv = JNI_FALSE;
}
TCN_FREE_CSTRING(ciphers);
return rv;
}
and this one does really use SSL_set_cipher_list even for TLS 1.3 -
that won't work.
Can anyone confirm that? Should I open a bug here:
https://bz.apache.org/bugzilla/enter_bug.cgi
about that?
kind regards
Torsten
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 9.0.59 - TLS 1.3 cipher configuration ignored (TLS 1.2 ok)
Am Freitag, dem 11.03.2022 um 09:50 +0100 schrieb Torsten Krah: > (error:1410D0B9:SSL routines:SSL_CTX_set_cipher_list:no cipher match) Reading that message and looking at: https://wiki.openssl.org/index.php/TLS1.3#Ciphersuites there it is written that with TLS 1.3: Applications should use the SSL_CTX_set_ciphersuites() or SSL_set_ciphersuites() functions to configure TLSv1.3 ciphersuites. Seems tomcat is using *SSL_CTX_set_cipher_list* instead of *SSL_CTX_set_ciphersuites* - maybe someone with knowledge here can confirm that theory. Reading: https://www.openssl.org/docs/manmaster/man3/SSL_CTX_set_cipher_list.html there is this: SSL_CTX_set_cipher_list() sets the list of available ciphers (TLSv1.2 and below) for ctx using the control string str. The format of the string is described in openssl-ciphers(1). The list of ciphers is inherited by all ssl objects created from ctx. This function does not impact TLSv1.3 ciphersuites. Use SSL_CTX_set_ciphersuites() to configure those. So it seems like a bug to me, right? kind regards Torsten - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 9.0.59 - TLS 1.3 cipher configuration ignored (TLS 1.2 ok)
Am Freitag, dem 11.03.2022 um 08:52 + schrieb Thomas Hoffmann (Speed4Trade GmbH): > Hello, > > the protocol attribute looks a bit strange. > > I think it should be: > > protocols="+TLSv1.2,+TLSv1.3"> I tried standalone TLS 1.3 like you suggested: protocols="+TLSv1.3" still the same exception: 11-Mar-2022 09:57:41.996 WARNUNG [main] org.apache.tomcat.util.net.openssl.OpenSSLContext.init Fehler beim initialisieren des SSL Contexts java.lang.Exception: Unable to configure permitted SSL ciphers (error:1410D0B9:SSL routines:SSL_CTX_set_cipher_list:no cipher match) kind regards Torsten - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 9.0.59 - TLS 1.3 cipher configuration ignored (TLS 1.2 ok)
Interesting exception on startup when using TLS 1.3 only - configured the connector like this: using only TLS 1.3 and the configured ciphers but now I get this on startup: 11-Mar-2022 09:43:42.753 WARNUNG [main] org.apache.tomcat.util.net.openssl.OpenSSLContext.init Fehler beim initialisieren des SSL Contexts java.lang.Exception: Unable to configure permitted SSL ciphers (error:1410D0B9:SSL routines:SSL_CTX_set_cipher_list:no cipher match) at org.apache.tomcat.jni.SSLContext.setCipherSuite(Native Method) at org.apache.tomcat.util.net.openssl.OpenSSLContext.init(OpenSSLContext.java:329) at org.apache.tomcat.util.net.SSLUtilBase.createSSLContext(SSLUtilBase.java:245) at org.apache.tomcat.util.net.AbstractJsseEndpoint.createSSLContext(AbstractJsseEndpoint.java:97) at org.apache.tomcat.util.net.AbstractJsseEndpoint.initialiseSsl(AbstractJsseEndpoint.java:71) at org.apache.tomcat.util.net.Nio2Endpoint.bind(Nio2Endpoint.java:144) at org.apache.tomcat.util.net.AbstractEndpoint.bindWithCleanup(AbstractEndpoint.java:1227) at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:1240) at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:603) at org.apache.coyote.http11.AbstractHttp11Protocol.init(AbstractHttp11Protocol.java:80) at org.apache.catalina.connector.Connector.initInternal(Connector.java:1046) at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136) at org.apache.catalina.core.StandardService.initInternal(StandardService.java:556) at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136) at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:1042) at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136) at org.apache.catalina.startup.Catalina.load(Catalina.java:724) at org.apache.catalina.startup.Catalina.load(Catalina.java:746) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:305) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:475) The cipher names does match: https://wiki.openssl.org/index.php/TLS1.3#Ciphersuites and https://datatracker.ietf.org/doc/html/rfc8446#appendix-B.4 I am lost at that point, maybe someone has an idea. kind regards Torsten - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat 9.0.59 - TLS 1.3 cipher configuration ignored (TLS 1.2 ok)
Hi, I am using Tomcat 9.0.59 and configured it like that: ... Output is: [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded Apache Tomcat Native library [1.2.31] using APR version [1.7.0]. [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true], UDS [true]. [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR/OpenSSL configuration: useAprConnector [false], useOpenSSL [true] [main] org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL successfully initialized [OpenSSL 1.1.1k 25 Mar 2021] Using testssl I had a look on the ciphers configured and they match my expectations for TLS 1.2 but the TLS 1.3 ones are ignored - the standard ciphers activated in openssl are still used according to: https://wiki.openssl.org/index.php/TLS1.3#Ciphersuites Output of testssl: Cipher order TLSv1.2: ECDHE-RSA-AES256-GCM-SHA384 ECDHE-RSA-AES128-GCM-SHA256 DHE-RSA-AES256-GCM-SHA384 DHE-RSA-AES128-GCM-SHA256 TLSv1.3: TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 Hexcode Cipher Suite Name (OpenSSL) KeyExch. Encryption Bits Cipher Suite Name (IANA/RFC) - x1302 TLS_AES_256_GCM_SHA384ECDH 253 AESGCM 256 TLS_AES_256_GCM_SHA384 x1303 TLS_CHACHA20_POLY1305_SHA256 ECDH 253 ChaCha20256 TLS_CHACHA20_POLY1305_SHA256 xc030 ECDHE-RSA-AES256-GCM-SHA384 ECDH 253 AESGCM 256 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 x9f DHE-RSA-AES256-GCM-SHA384 DH 4096AESGCM 256 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 x1301 TLS_AES_128_GCM_SHA256ECDH 253 AESGCM 128 TLS_AES_128_GCM_SHA256 xc02f ECDHE-RSA-AES128-GCM-SHA256 ECDH 253 AESGCM 128 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 x9e DHE-RSA-AES128-GCM-SHA256 DH 4096AESGCM 128 TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 How to configure the TLS 1.3 ciphers? kind regards Torsten - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Number of Web Applications in one Tomcat
Am Dienstag, den 30.10.2018, 15:13 + schrieb Jäkel, Guido: > I'm pretty sure that this problem is just caused by malformed > applications that include some XML stuff inside the application that > MUST NOT include, but have to be provided instead by the platform -- > e.g. as JVM endorsed libs. A common case is that application A > provide and register some implementation of an API at JVM level and > application B provide this also, but with another version. Then, one > of the application will use at runtime another lib as at compile > time. > > Without parallel start, this might seem to work (or not) in a stable > way. But with parallel start, you get race conditions. The whole xml stack used is from the JVM (no custom xerces, xalan etc added to WEB-INF/lib) - so i don't know where to look for something which should not be in "my" local libs. And there is no ClasscastException or LinkageError here - its the parser itself who does fail: Caused by: org.xml.sax.SAXParseException; lineNumber: 476; columnNumber: 97; src-resolve: Name 'ehcache:resource-unit' kann nicht als 'type definition'-Komponente aufgelöst werden. But i am happy to continue that discussion in the original thread because i am still interested in getting the root cause because at the moment parallel startup is disabled because of that error. Cheers Torsten smime.p7s Description: S/MIME cryptographic signature
Re: Number of Web Applications in one Tomcat
Am Dienstag, den 30.10.2018, 14:39 +0100 schrieb Ahmed, Tarek: > "With Tomcat 7.0.23+ you can configure it to start several web > applications in parallel. This is disabled by default but can be > enabled > by setting the startStopThreads attribute of a *Host* to a value > greater > than one." But be aware that you may run into problem with this one - look e.g. here: https://www.mail-archive.com/users@tomcat.apache.org/msg127141.html Cheers Torsten smime.p7s Description: S/MIME cryptographic signature
Re: org.apache.tomcat.jdbc.pool casting to original connection class
Am Dienstag, den 28.08.2018, 09:21 -0400 schrieb Christopher Schultz: > Interesting. I wonder why Postgres decided not to support that > through > the standard JDBC API. > > Have you tried setting the "compatible" flag on the connection just > to > see if it works for you? I am curious - afaik the standard JDBC API does not support e.g. to use seek() or truncate() on the BLOB to fast forward to some position in the file - how would you do that with the standard API Christopher - maybe i've missed that feature? The LargeObject API does support this. kind regards Torsten smime.p7s Description: S/MIME cryptographic signature
Re: org.apache.tomcat.jdbc.pool casting to original connection class
The isWrapperFor(..) and unwrap(..) methods on the connection API should work for this.
mindIdle does not inherit default value from initalSize - tomcat 8.5.x
Tomcat docs for minIdle reads this: https://tomcat.apache.org/tomcat-8.5-doc/jdbc-pool.html minIdle (int) The minimum number of established connections that should be kept in the pool at all times. The connection pool can shrink below this number if validation queries fail. Default value is derived from initialSize:10 (also see testWhileIdle) Setting this to a DS an starting the pool: ds.setInitialSize(1); ds.setMaxIdle(1) ds.setMaxActive(10); results in: WARN org.apache.tomcat.jdbc.pool.ConnectionPool [JuliLog.java:137] - maxIdle is smaller than minIdle, setting maxIdle to: 10 If minIdle would be retrieved from initialSize it is not smaller - seems like a Bug. Do you agree? Should i open a bug report for that? smime.p7s Description: S/MIME cryptographic signature
embedded tomcat (8.5.28) classloading issues when adding another war file and classes can be resolved via that webapp classloader and the bootstrap classloader
Hi, i am using an embedded tomcat to e.g. start my wicket application in my IDE. This works fine so far - the whole classpath used and provided by IntelliJ is used. But adding e.g. a war file via setWebapp to start some additional webapps i am running into some issues with that war files. The intellij classpath does provide e.g. hibernate and this is going to resolve classes when loading entities via associations. Hibernate was loaded using classloader A (bootstrap one) and it does even resolve that association class with A where it should have used the ParallelWebappClassloader from my war file first when getting a request for that war file. So this is going havoc because bootstrap classloader is asked first here where it does find that class (embedded tomcat - no extra classloader stuff done). https://tomcat.apache.org/tomcat-8.5-doc/class-loader-howto.html So how is this supposed to work in case i want to load additional war files in an embedded tomcat - any best practices, docs known how to "reproduce" such an isolated environment for an embedded tomcat? So minimal example would be: 1. The bootstrap class with "new Tomcat()" is in my test classpath of my webapp in the IDE and can run the webapp from "src/main/webapp" as usual - which works so far (one big fat classpath ...). 2. I want to add a webapp from a war file in the same Tomcat() instance - but here it gets messy with the classes. Suggestions welcome :) kind regards Torsten PS: In the "real" tomcat this is going to work because the bootstrap classloader does not know that class at all there - where in the webapp one this is "mixed". smime.p7s Description: S/MIME cryptographic signature
startStopThreads="0" and thread safety issues with SAXParser / Xerces
Hi, i've enabled startStopThreads="0" to increase bootstrap time of my servlet container using tomcat 8.5.15 and jdk 1.8.0_131-b11. Sometimes - not every time - i've got something like that when the entity manager factory is created from the context initialized callback: ## javax.persistence.PersistenceException: [PersistenceUnit: welcome] Unable to build Hibernate SessionFactory at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.persistenceException(EntityManagerFactoryBuilderImpl.java:967) at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:892) at org.hibernate.jpa.HibernatePersistenceProvider.createEntityManagerFactory(HibernatePersistenceProvider.java:58) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:55) at com.google.inject.persist.jpa.JpaPersistService.start(JpaPersistService.java:107) at my.custom.Listener.contextInitialized(BootstrapListener.java:82) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4745) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5207) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:752) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:952) at org.apache.catalina.startup.HostConfig $DeployWar.run(HostConfig.java:1823) at java.util.concurrent.Executors $RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor $Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) Caused by: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.spi.CacheImplementor] at org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:271) at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:233) at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:210) at org.hibernate.service.internal.SessionFactoryServiceRegistryImpl.getService(SessionFactoryServiceRegistryImpl.java:77) at org.hibernate.internal.SessionFactoryImpl.(SessionFactoryImpl.java:240) at org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:445) at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:889) ... 18 more Caused by: javax.cache.CacheException: org.ehcache.xml.exceptions.XmlConfigurationException: Error parsing XML configuration at classpath:hibernate-ehcache.xml at org.ehcache.jsr107.EhcacheCachingProvider $ConfigSupplier.getConfiguration(EhcacheCachingProvider.java:330) at org.ehcache.jsr107.EhcacheCachingProvider.getCacheManager(EhcacheCachingProvider.java:127) at org.ehcache.jsr107.EhcacheCachingProvider.getCacheManager(EhcacheCachingProvider.java:78) at org.ehcache.jsr107.EhcacheCachingProvider.getCacheManager(EhcacheCachingProvider.java:186) at org.hibernate.cache.jcache.JCacheRegionFactory.getCacheManager(JCacheRegionFactory.java:177) at org.hibernate.cache.jcache.JCacheRegionFactory.start(JCacheRegionFactory.java:68) at org.hibernate.cache.spi.RegionFactory.start(RegionFactory.java:63) at org.hibernate.internal.CacheImpl.(CacheImpl.java:71) at org.hibernate.engine.spi.CacheInitiator.initiateService(CacheInitiator.java:28) at org.hibernate.engine.spi.CacheInitiator.initiateService(CacheInitiator.java:20) at org.hibernate.service.internal.SessionFactoryServiceRegistryImpl.initiateService(SessionFactoryServiceRegistryImpl.java:58) at org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:259) ... 24 more Caused by: org.ehcache.xml.exceptions.XmlConfigurationException: Error parsing XML configuration at classpath:hibernate-ehcache.xml at org.ehcache.xml.XmlConfiguration.(XmlConfiguration.java:167) at org.ehcache.xml.XmlConfiguration.(XmlConfiguration.java:131) at org.ehcache.jsr107.EhcacheCachingProvider $ConfigSupplier.getConfiguration(EhcacheCachingProvider.java:327) ... 35 more Caused by: org.xml.sax.SAXParseException; lineNumber: 476;
Re: trimSpaces removing whitespace from html
Am Donnerstag, den 11.05.2017, 09:23 -0400 schrieb Christopher Schultz: > So, removing the trailing space in the "class" attribute's value? That too - but have a look at: mrf-mmrf-image it was before / should be: mrf-m mrf-image there are missing whitespaces in the actual class attributes content. Torsten - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Error 404 - The requested resource is not available
Am Donnerstag, den 12.01.2017, 13:38 -0600 schrieb fonsin2008 .: > Here are the log files. What about fixing those NPE and enable debug/trace logs of struts2 to get more information about how struts is going to map the request and where the 404 is written to the response. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Issues with accessing Apache Httpd Modules
> https://modules.apache.org/ Maybe you're looking for that URL: http://httpd.apache.org/modules/ ... but its nothing you would not have found via the links i'll already wrote. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Issues with accessing Apache Httpd Modules
If you insist to use that non working url (don't know where you've taken that url from nor for which reason you want to reach that url. You did not write what are you searching there) -> just ask the correct mailing list ... If you want to look for the docs you are searching this http://httpd.apache.org/docs/2.4/mod/ is imho the url to go. Look here: http://httpd.apache.org/docs/2.4/mod/mod_dav_fs.html http://httpd.apache.org/docs/2.4/mod/mod_dav.html My last 2 cents about that Cheers Torsten Am Dienstag, den 29.11.2016, 07:51 + schrieb kruthika.krish...@accenture.com: > Hi Torsten, > > This has been tried from various networks , and its still not > accessible. > > https://modules.apache.org/ > > The above is the correct url used. > > Thanks and Regards, > Kruthika Krishnan - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Issues with accessing Apache Httpd Modules
This is the tomcat list, not the httpd one ... but your favorite search engine would easily have answered your question: http://httpd.apache.org/docs/2.4/mod/ Cheers Torsten Am Montag, den 28.11.2016, 07:18 + schrieb kruthika.krish...@accenture.com: > Hi , > I am trying to access the apache HTTPD modules for Apache version 2.4, > through the URL > http://modules.apache.org/ > It shows an error: > Service Unavailable > The server is temporarily unable to service your request due to maintenance > downtime or capacity problems. Please try again later. > Is there any other way to access the Apache modlues the modules I want to > access are : mod_dav and mod_dav_fs. > > Thanks and Regards, > Kruthika Krishnan > > > > This message is for the designated recipient only and may contain privileged, > proprietary, or otherwise confidential information. If you have received it > in error, please notify the sender immediately and delete the original. Any > other use of the e-mail by you is prohibited. Where allowed by local law, > electronic communications with Accenture and its affiliates, including e-mail > and instant messaging (including content), may be scanned by our systems for > the purposes of information security and assessment of internal compliance > with Accenture policy. > __ > > www.accenture.com - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Question about suspectTimeout property of pool configuration - possible Bug - does only work with removeAbandoned = true which seems odd
https://bz.apache.org/bugzilla/show_bug.cgi?id=60043 Am Dienstag, den 23.08.2016, 16:32 +0900 schrieb Keiichi Fujino: > Please open the bugzilla. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Question about suspectTimeout property of pool configuration - possible Bug - does only work with removeAbandoned = true which seems odd
Hi,
looking at the doc:
https://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html
there is:
suspectTimeout
(int) Timeout value in seconds. Default value is 0.
Similar to to the removeAbandonedTimeout value but instead of treating
the connection as abandoned, and potentially closing the connection,
this simply logs the warning if logAbandoned is set to true. If this
value is equal or less than 0, no suspect checking will be performed.
Suspect checking only takes place if the timeout value is larger than 0
and the connection was not abandoned or if abandon check is disabled. If
a connection is suspect a WARN message gets logged and a JMX
notification gets sent once.
To me this sounds like i should get a warning if i configure the pool
like this:
logAbandoned="true"
suspectTimeout="120"
after 2 minutes.
I don't want to remove the connections, i just want to get them logged.
However i don't see such messages - looking at the code it seems that
suspect() from the connection is called from the pool in:
pool.checkAbandoned();
but this is only called from the PoolCleaner in its run method when the
check:
if (pool.getPoolProperties().isRemoveAbandoned())
pool.checkAbandoned();
is true.
But i don't want to get them removed - i just want them logged like
suspect is promising - at least it sounds to me like that.
Any thoughts about that? Shouldn't it read like:
if (pool.getPoolProperties().isRemoveAbandoned() ||
pool.getPoolProperties().getSuspectTimeout() > 0)
pool.checkAbandoned();
JavaDoc of setSuspectTimeout:
/**
* Similar to {@link #setRemoveAbandonedTimeout(int)} but instead of
treating the connection
* as abandoned, and potentially closing the connection, this simply
logs the warning if
* {@link #isLogAbandoned()} returns true. If this value is equal or
less than 0, no suspect
* checking will be performed. Suspect checking only takes place if
the timeout value is larger than 0 and
* the connection was not abandoned or if abandon check is disabled.
If a connection is suspect a WARN message gets
* logged and a JMX notification gets sent once.
* @param seconds - the amount of time in seconds that has to pass
before a connection is marked suspect.
*/
public void setSuspectTimeout(int seconds);
does also imply this behaviour i would expect.
It seems you need to remove them (even with a large timeout set to get
suspect working) - javadoc reads i can have suspect without remove.
If this should be the case checkAbandoned() needs some work so that
shouldAbandon() does check the property - removeAbandoned - to make sure
it should really remove it, not just got to suspect in the else case -
or just have to methods ... don't mind which solution, something like
this ;).
Should i open some ticket about that possible Bug or is it working as
intended?
kind regards
Torsten
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: jdbc driver location in TC 7
Am Montag, den 26.03.2012, 05:30 -0600 schrieb Terence M. Bandoian: Apparently, Tomcat (6.0.29) takes care of that if the driver is located in the Tomcat lib directory but not if it is located in web application's lib directory. Tomcat does not take care afaik - the classloader is not the webapps classloader, so there is no leak to report. smime.p7s Description: S/MIME cryptographic signature
Tomcat 7 - servlet 2.5 app and removed Context disableURLRewriting parameter
Hi, i am using tomcat 7 to run my servlet 2.5 webapps. Im Tomcat 6 it was possible to tell the Context via disableURLRewriting that i want to track session only via Cookie. This parameter is removed and doc tells me to use tracking-modeCOOKIEtracking-mode at session-config element in web.xml. But this is not a valid attribute there in a 2.5 webapp. I am unable to switch to 3.0 yet. So how to disable URL rewriting in tomcat 7 with a 2.5 webapp? regards Torsten smime.p7s Description: S/MIME cryptographic signature
Re: Tomcat 7 - servlet 2.5 app and removed Context disableURLRewriting parameter
Am Donnerstag, den 22.03.2012, 17:43 +0400 schrieb Konstantin Kolinko: 2012/3/22 Torsten Krah tk...@fachschaft.imn.htwk-leipzig.de: Hi, i am using tomcat 7 to run my servlet 2.5 webapps. Im Tomcat 6 it was possible to tell the Context via disableURLRewriting that i want to track session only via Cookie. This parameter is removed and doc tells me to use It was not removed. It was never present in 7.0. Ok, than it was never ported ;-). It is a recent addition that was done to 6.0 only (issue 49811). tracking-modeCOOKIEtracking-mode at session-config element in web.xml. But this is not a valid attribute there in a 2.5 webapp. I am unable to switch to 3.0 yet. So how to disable URL rewriting in tomcat 7 with a 2.5 webapp? You can edit site-wide defaults (conf/web.xml). I am unable to control this site-wide default. I am not allowed and even if i am to do, i may break other apps. Im Tomcat 6 you can control it via parameter, in tomcat 7 you can't control it for apps which are not Servlet 3.0, right? So i am going to open a new feature request, correct? Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org smime.p7s Description: S/MIME cryptographic signature
Re: Tomcat 7 - servlet 2.5 app and removed Context disableURLRewriting parameter
Am Donnerstag, den 22.03.2012, 14:25 + schrieb Mark Thomas: You can, but it will be closed as WONTFIX. The reason it was only added to 6.0.x was that that in 7.0.x there are other ways of achieving the same result and supporting this additional option as well would result in some unnecessarily messy, hard to maintain code. What other ways are there for a 2.5 webapp in a mixed environment (3.0 webapps and 2.5 ones) where i want to disable url rewriting for the 2.5 one but leave the default untouched? If the 7.0.x options don't work for you, why not use 6.0.x? Because i want to use the thread vanishing features tobe able to let the gc collect my class loader in case a thread local is left over by a webapp and 6.0.x does not have this feature. And 7.0.x does support 2.5 webapps, does it? Torsten smime.p7s Description: S/MIME cryptographic signature
tomcat 5.5 - what happens if an OOM has occured in an application and an exception is thrown in thread main later
Does tomcat reinitialisize themself or not? What is the lifecycle if this is happening? Clean restart of coyote engine, nothing or whats happening? If yes - are finally methods of still running threads and applications executed or is it like signal 9 - all gets killed? kind regards Torsten - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fork a new JVM from a project out of a running tomcat instance
Hello. Is there any possibility to fork a new instance of a jvm from a running one? For example, every project tomcat is running, should fork its own jvm. Its appreciated that it use the same start parameters as the original one. thx for help. kind regards Torsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Bootstrap class - Interface bind - Problem there again.
Some additions: Before i call some webapp the container is running, i get this output from netstat: tcp6 0 0 :::127.0.0.1:8005 :::* LISTEN 3495/java tcp6 0 0 :::127.0.0.1:8009 :::* LISTEN 3495/java tcp6 0 0 :::127.0.0.1:8080 :::* LISTEN 3495/java That what i am exspected. After the call i get additionally this: tcp6 0 0 :::54109:::* LISTEN 3495/java The same process id is now waiting for requests at port 54109. I've set development and fork paramteter to false, didnt help. Any tipps what the reason maybe for that? Any specific debug options i can set to log something which let me find some information for this problem? kind regards Torsten Am Mittwoch, den 01.03.2006, 19:02 +0100 schrieb Torsten Krah: Tomcat version 4.1.31-LE-jdk14. OS: Linux 2.6.8 java version 1.4.2-02 Java(TM) 2 Runtime Environment, Standard Edition (build Blackdown-1.4.2-02) Java HotSpot(TM) 64-Bit Server VM (build Blackdown-1.4.2-02, mixed mode) No, i didnt make a LD_ASSUME_KERNEL setting. No, the apps dont spawn another jvm. Theres no cron job or similiar, i have to start it manually. The fork parameter isnt set, so its left at its default. kind regards Torsten Am Mittwoch, den 01.03.2006, 11:46 -0600 schrieb Caldarale, Charles R: From: Torsten Krah [mailto:[EMAIL PROTECTED] Subject: RE: Bootstrap class - Interface bind - Problem there again. Problem is there again - after few minutes in working state, a new process shows up with following call: What Tomcat level? What OS? If Linux, do you have an LD_ASSUME_KERNEL setting? What's the value of the fork parameter for the jsp servlet (in conf/web.xml)? Do any of your apps spawn another JVM? Do you have any cron or similar jobs automatically starting another Tomcat instance? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Bootstrap class - Interface bind
Hello, tomcats connectors are configured to listen on localhost only, which works fine. But the bootstrap class listens still on all interfaces. How can i tell tomcat to behave like the connectors and only listen on addresses i want ( address and port would be nice ). kind regards Torsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Bootstrap class - Interface bind
Like i said, i configured the connectors to listen on address=127.0.0.1, so its not the default one. But i got the problem. I've stopped and started tomcat after changing the connectors - but not all java instances were closed when stopping tomcat. After Stopping Tomcat again, killing all remaining java Bootstrap classes and starting tomcat again, its fine. I will look at this, stopping tomcat should kill all instances in my opinion, strange. kind regards Torsten Am Mittwoch, den 01.03.2006, 10:46 -0600 schrieb Caldarale, Charles R: From: Torsten Krah [mailto:[EMAIL PROTECTED] Subject: Bootstrap class - Interface bind tomcats connectors are configured to listen on localhost only, which works fine. If you're talking about the default Tomcat configuration, that's not true. In the absence of an IP address specification, the connectors listen on 0.0.0.0 - any IP address. The bootstrap class doesn't listen on anything not specified in the server.xml config. If you're having trouble, post your Connector settings, and tell us what Tomcat level you're referring to. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Bootstrap class - Interface bind - Problem there again.
Problem is there again - after few minutes in working state, a new process shows up with following call: /opt/java/bin/java -server -showversion -Xms640M -Xmx640M -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintHeapAtGC -Xloggc:/var/logs/gc.log -Djava.awt.headless=true -Djava.endorsed.dirs=/opt/tomcat/common/endorsed -classpath /opt/java/lib/tools.jar:/opt/tomcat/bin/bootstrap.jar -Dcatalina.base=/var/tomcat -Dcatalina.home=/opt/tomcat -Djava.io.tmpdir=/var/tomcat/temp org.apache.catalina.startup.Bootstrap start tcp6 0 0 :::41276:::* LISTEN 12320/java I guess the number of them will grow with time. The server.xml is defined so: Server port=8005 shutdown=SHUTDOWN debug=0 Listener className=org.apache.catalina.mbeans.ServerLifecycleListener debug=0/ Listener className=org.apache.catalina.mbeans.GlobalResourcesLifecycleListener debug=0/ GlobalNamingResources Environment name=simpleValue type=java.lang.Integer value=30/ Resource name=UserDatabase auth=Container type=org.apache.catalina.UserDatabase description=User database that can be updated and saved /Resource ResourceParams name=UserDatabase parameter namefactory/name valueorg.apache.catalina.users.MemoryUserDatabaseFactory/value /parameter parameter namepathname/name valueconf/tomcat-users.xml/value /parameter /ResourceParams /GlobalNamingResources Service name=Tomcat-Standalone Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8080 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=2 useURIValidationHack=false address=127.0.0.1 / Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=2 useURIValidationHack=false address=127.0.0.1 protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ Engine name=Standalone defaultHost=localhost debug=0 Logger className=org.apache.catalina.logger.FileLogger prefix=catalina_log. suffix=.txt timestamp=true/ Realm className=org.apache.catalina.realm.UserDatabaseRealm debug=0 resourceName=UserDatabase/ Host name=localhost debug=0 appBase=/var/apps unpackWARs=true autoDeploy=true Logger className=org.apache.catalina.logger.FileLogger directory=logs prefix=localhost_log. suffix=.txt timestamp=true/ /Host /Engine /Service /Server The connectors got both the address option. So whats that for a process and how do i stop tomcat from doing that, something wrong with server.xml? thx for any suggestions. kind regards Torsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Bootstrap class - Interface bind - Problem there again.
Tomcat version 4.1.31-LE-jdk14. OS: Linux 2.6.8 java version 1.4.2-02 Java(TM) 2 Runtime Environment, Standard Edition (build Blackdown-1.4.2-02) Java HotSpot(TM) 64-Bit Server VM (build Blackdown-1.4.2-02, mixed mode) No, i didnt make a LD_ASSUME_KERNEL setting. No, the apps dont spawn another jvm. Theres no cron job or similiar, i have to start it manually. The fork parameter isnt set, so its left at its default. kind regards Torsten Am Mittwoch, den 01.03.2006, 11:46 -0600 schrieb Caldarale, Charles R: From: Torsten Krah [mailto:[EMAIL PROTECTED] Subject: RE: Bootstrap class - Interface bind - Problem there again. Problem is there again - after few minutes in working state, a new process shows up with following call: What Tomcat level? What OS? If Linux, do you have an LD_ASSUME_KERNEL setting? What's the value of the fork parameter for the jsp servlet (in conf/web.xml)? Do any of your apps spawn another JVM? Do you have any cron or similar jobs automatically starting another Tomcat instance? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mod_jk Connector
Just guessing: They got legacy stuff and want to use it and doesnt have the man power to upgrade it or development is discarded but their still users who want to work with it - just a thought. Afaik 4.1.31 is the latest 4.1.x Tomcat, so its not old. Its like FreeBSD 4.X vs 6.X which was released a few days ago, many users still want to use 4.X because they trust in it. best regards Torsten Am Donnerstag, den 10.11.2005, 13:12 +0100 schrieb Seak, Teng-Fong: A curious question: I've lots of mails here in which people are using old versions of stuffs. Real old stuffs! For example, Tomcat reaches already 5.5.12. Why don't you get the latest ones to see it works first? Kaushal Shriyan wrote: I have downloaded the following application httpd-2.0.49.tar.gz jakarta-tomcat-4.1.31.tar.gz jakarta-tomcat-connectors-1.2.15-src.tar.gz I am able to check http://localhost:8080/index.jsp and http://localhost But when I do http://localhost/examples it says Not Found The requested URL /examples was not found on this server. Apache/2.0.49 (Unix) mod_jk/1.2.15 Server at localhost Port 80 Please help me to resolve this issue Thanks and regards Kaushal Shriyan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
