Keycloak integration with tomcat10
Hi, We wanted to integrate keycloak with tomcat 10. I saw that keycloak does not provide any client adapter compatible with tomcat10. Could you please suggest if there is any other way to integrate keycloak with tomcat10? Thanks, Aniket
Re: Sharing catalina home among tomcat machines in a load balanced environment gives problems with log files
Jon, On 10/10/23 14:26, Mcalexander, Jon J. wrote: Could you have separate work folders but have the appbase be the in the shared folder space? You could do this with some symlinking, but I wouldn't recommend it. If you start to do things like dynamic deployment, etc. you will find that both servers will be affected and that may not be what you want. Automation is very flexible and disk space is cheap. Do yourself a favor and just separate things so you don't have unforeseen problems. -chris -Original Message- From: Christopher Schultz Sent: Tuesday, October 10, 2023 5:59 AM To: users@tomcat.apache.org Subject: Re: Sharing catalina home among tomcat machines in a load balanced environment gives problems with log files Mark, On 10/10/23 06:38, Mark Thomas wrote: Running multiple instances of Tomcat from the same CATALINA_BASE is totally unsupported. This isn't one of those "We don't technically support that but you should be OK situations". This is one of the rare "You do that and it *will* break and you will be on your own when it does." situations. +1 Both the logs/ and the work/ directories will overwrite each other, probably to the point of not only corruption (e.g. log files) but also instability -- because of the work/ directory. Files will appear and disappear surprisingly to one or the other running Tomcat and you WILL have errors, etc. On 10/10/2023 06:51, Giuseppe Sacco wrote: >> I did not use different CATALINA_BASE and CATALINA_HOME since this would have required to deploy all applications on two different tomcats In this case, *you have two different Tomcats*, so it is appropriate to use different CATALINA_BASE paths. and my pipeline only allows to deploy to one tomcat putting an XML file in $CATALINA_BASE/conf/Catalina/localhost directory. Maybe you can use a symlink from both directories? -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 - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
getting 404 after migrating app to rpm based tomcat install
Can some please help me out with this?. recently we have started migrating our application from Tomcat 8.5.49 (tar file) to the RPM-installed Tomcat 8.5.89. We encountered a 404 error after the migration tomcat 8.5.49 tar file installation: TOMCAT_HOME: /deploy/software/tomcat TOMCAT_BASE: /deploy/software/tomcat webapps: ROOT -> the above config is the current one where we have running apps in dev ,stg and prod. tomcat 8.5.89 rpm installation TOMCAT_HOME: /usr/share/tomcat8 ( maintaining same conf dir/files including web.xml what we have with ver 8.5.49) TOMCAT_BASE: /usr/share/tomcat8 webapps: ROOT -> no errors in catalina.out and app is coming up fine and able to connect both ports 8080 and 8443, but I do get 404 when I hit the page *Description* The origin server did not find a current representation for the target resource or is not willing to disclose that one exists. -- *Thanks* *Niranjan*
RE: Sharing catalina home among tomcat machines in a load balanced environment gives problems with log files
👍👍👍 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: Christopher Schultz > Sent: Thursday, October 12, 2023 8:31 AM > To: users@tomcat.apache.org > Subject: Re: Sharing catalina home among tomcat machines in a load > balanced environment gives problems with log files > > Jon, > > On 10/10/23 14:26, Mcalexander, Jon J. wrote: > > Could you have separate work folders but have the appbase be the in > > the shared folder space? > You could do this with some symlinking, but I wouldn't recommend it. If you > start to do things like dynamic deployment, etc. you will find that both > servers will be affected and that may not be what you want. > > Automation is very flexible and disk space is cheap. Do yourself a favor and > just separate things so you don't have unforeseen problems. > > -chris > > >> -Original Message- > >> From: Christopher Schultz > >> Sent: Tuesday, October 10, 2023 5:59 AM > >> To: users@tomcat.apache.org > >> Subject: Re: Sharing catalina home among tomcat machines in a load > >> balanced environment gives problems with log files > >> > >> Mark, > >> > >> On 10/10/23 06:38, Mark Thomas wrote: > >>> Running multiple instances of Tomcat from the same CATALINA_BASE is > >>> totally unsupported. This isn't one of those "We don't technically > >>> support that but you should be OK situations". This is one of the > >>> rare "You do that and it *will* break and you will be on your own > >>> when it does." situations. > >> > >> +1 > >> > >> Both the logs/ and the work/ directories will overwrite each other, > >> probably to the point of not only corruption (e.g. log files) but > >> also instability -- because of the work/ directory. Files will appear > >> and disappear surprisingly to one or the other running Tomcat and you > WILL have errors, etc. > >> > >>> On 10/10/2023 06:51, Giuseppe Sacco wrote: > >> >> > I did not use different CATALINA_BASE and CATALINA_HOME since this > would have required to deploy all applications on two different > tomcats > >> > >> In this case, *you have two different Tomcats*, so it is appropriate > >> to use different CATALINA_BASE paths. > >> > and my > pipeline only allows to deploy to one tomcat putting an XML file in > $CATALINA_BASE/conf/Catalina/localhost directory. > >> > >> Maybe you can use a symlink from both directories? > >> > >> -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 > > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Keycloak integration with tomcat10
Hi Aniket, Am 12.10.23 um 15:19 schrieb Aniket Pachpute: We wanted to integrate keycloak with tomcat 10. I saw that keycloak does not provide any client adapter compatible with tomcat10. Could you please suggest if there is any other way to integrate keycloak with tomcat10? For oidc integration you can use libraries like nimbusd: https://connect2id.com/products/nimbus-oauth-openid-connect-sdk Or, if you use an apache webserver in front of your tomcat, you can also use an oidc-module for apache, e.g.: https://github.com/OpenIDC/mod_auth_openidc -- Greets Bernd Schatz - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat upgrade from 9.0.80 to 9.0.81
All, On 10/11/23 08:06, i...@flyingfischer.ch wrote: Am 11.10.23 um 14:02 schrieb Alexander Veit: Caused by: org.apache.http.ConnectionClosedException: Premature end of Content-Length delimited message body (expected: 4,999; received: 3,040) at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) at io.restassured.internal.util.IOUtils.toByteArray(IOUtils.java:30) at io.restassured.internal.http.GZIPEncoding$GZIPDecompressingEntity.getContent(GZIPEncoding.java:69) at org.apache.http.conn.BasicManagedEntity.getContent(BasicManagedEntity.java:85) at io.restassured.internal.http.HTTPBuilder.parseResponse(HTTPBuilder.java:546) at io.restassured.internal.RequestSpecificationImpl$RestAssuredHttpBuilder.super$2$parseResponse(RequestSpecificationImpl.groovy) at sun.reflect.GeneratedMethodAccessor129.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:107) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:323) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1268) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeMethodOnSuperN(ScriptBytecodeAdapter.java:144) Has anyone seen this? I will keep everyone posted after debugging more. We have experienced the same problem with Tomcat 8.5.94. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org Seems to be reported multiple times as this is blocking bug for upgrading to the last Tomcat version: https://bz.apache.org/bugzilla/show_bug.cgi?id=67670 We understand that it is blocking, but if you re using h2, especially exposed directly to the internet, you should upgrade to the broken release and use Konstantin's recommended workarounds. Both the h2 Rapid Reset and HTTP Trailer / possible request smuggling CVEs are both very important. We apologize for the regressions. Release votes appear to be going well; we will have a new set of releases for everyone very shortly. Although they are not "official" releases, you are welcome to deploy the release-candidates themselves. Assuming they are voted stable, they will be identical to the upcoming "official" releases. See the dev@ list [VOTE] emails for where to get those release-candidate artifacts. -chris - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
JSF errors when upgrading Tomcat and Eclipse: com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation Unknow type constant pool XX at position XX
Hello, First of all, I apologize if maybe my issue is not exclusively related to Tomcat, but I think it is. I started my website many years ago, using Struts 1.2.4 and since then I have been using it. Some years after that I had the intention to migrate to JSF (version 2.2.X) and combine both frameworks for a while until I migrated everything to JSF and Struts was gone. I started learning it, created a few pages on my site but then I realized that it was not the ideal framework for me, so I stopped creating more pages with JSF and continued developing my site with Struts, letting those few JSF pages that work coexist with the rest of the site running using Struts. Since then, I haven't touched JSF. I haven't created even one page with it, never upgraded its version but the JSF JAR and pages are still there. Years passed and nothing made me think about JSF. Now I'm using: - Mac with the M2 chip - Eclipse (ARM version) - Tomcat, when developing with Eclipse - Tomcat 9.0.58 at my production server (which runs Ubuntu 22.04, x86/64) - Azul's Java 11.0.19+7-LTS aarch64, when developing with Eclipse - Java 11.0.20.1+1-post-Ubuntu-0ubuntu122.04, at the production server Well, a few days ago I upgraded Eclipse to Version: 2023-09 (4.29.0) and at the same time upgraded to Azul's Java 11.0.19+7-LTS aarch64 and to Tomcat 9.0.71 when developing. And since then, I get these "SEVERE" JSF error messages (many of them) when I start Tomcat: SEVERE [main] com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation Unknow type constant pool NN at position XX Why is that? Could someone please give me a clue? I just upgraded Eclipse and Tomcat, didn't do anything else relevant and now I get these messages. And when I create the WAR file and deploy it on my production server, I get the same error messages as well over there. It seems like the class files that gets generated are now different, since I didn't upgrade anything on my production server, so it is the WAR file that gets generated with something problematic now. Thanks in advance! Here is the complete stuff that Tomcat shows, as a reference: 12-Oct-2023 14:47:18.676 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version name: Apache Tomcat/9.0.71 12-Oct-2023 14:47:18.678 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Jan 9 2023 22:33:01 UTC 12-Oct-2023 14:47:18.678 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version number: 9.0.71.0 12-Oct-2023 14:47:18.678 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: Mac OS X 12-Oct-2023 14:47:18.678 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 14.0 12-Oct-2023 14:47:18.678 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: aarch64 12-Oct-2023 14:47:18.678 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: /Library/Java/JavaVirtualMachines/zulu-11.jdk/Contents/Home 12-Oct-2023 14:47:18.678 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 11.0.19+7-LTS 12-Oct-2023 14:47:18.678 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Azul Systems, Inc. 12-Oct-2023 14:47:18.678 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: /Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71 12-Oct-2023 14:47:18.678 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: /Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71 12-Oct-2023 14:47:18.719 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71 12-Oct-2023 14:47:18.719 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71 12-Oct-2023 14:47:18.719 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dwtp.deploy=/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71/webapps 12-Oct-2023 14:47:18.719 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71/conf/logging.properties 12-Oct-2023 14:47:18.720 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager 12-Oct-2023 14:47:18.720 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: --add-opens=java.base/java.lang=ALL-UNNAMED 12-Oct-2023 14:47:18.720 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: --add-opens=java.base/java.io=ALL-UNNAMED 12-Oct-2023 14:47:18.720 INFO
Re: JSF errors when upgrading Tomcat and Eclipse: com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation Unknow type constant pool XX at position XX
Brian, On 10/12/23 16:55, Brian Braun wrote: Hello, First of all, I apologize if maybe my issue is not exclusively related to Tomcat, but I think it is. I started my website many years ago, using Struts 1.2.4 and since then I have been using it. Some years after that I had the intention to migrate to JSF (version 2.2.X) and combine both frameworks for a while until I migrated everything to JSF and Struts was gone. I started learning it, created a few pages on my site but then I realized that it was not the ideal framework for me, so I stopped creating more pages with JSF and continued developing my site with Struts, letting those few JSF pages that work coexist with the rest of the site running using Struts. Since then, I haven't touched JSF. I haven't created even one page with it, never upgraded its version but the JSF JAR and pages are still there. Years passed and nothing made me think about JSF. Now I'm using: - Mac with the M2 chip - Eclipse (ARM version) - Tomcat, when developing with Eclipse - Tomcat 9.0.58 at my production server (which runs Ubuntu 22.04, x86/64) - Azul's Java 11.0.19+7-LTS aarch64, when developing with Eclipse - Java 11.0.20.1+1-post-Ubuntu-0ubuntu122.04, at the production server Well, a few days ago I upgraded Eclipse to Version: 2023-09 (4.29.0) and at the same time upgraded to Azul's Java 11.0.19+7-LTS aarch64 and to Tomcat 9.0.71 when developing. And since then, I get these "SEVERE" JSF error messages (many of them) when I start Tomcat: SEVERE [main] com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation Unknow type constant pool NN at position XX Why is that? Could someone please give me a clue? I just upgraded Eclipse and Tomcat, didn't do anything else relevant and now I get these messages. And when I create the WAR file and deploy it on my production server, I get the same error messages as well over there. It seems like the class files that gets generated are now different, since I didn't upgrade anything on my production server, so it is the WAR file that gets generated with something problematic now. Thanks in advance! Here is the complete stuff that Tomcat shows, as a reference: 12-Oct-2023 14:47:18.676 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version name: Apache Tomcat/9.0.71 12-Oct-2023 14:47:18.678 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Jan 9 2023 22:33:01 UTC 12-Oct-2023 14:47:18.678 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version number: 9.0.71.0 12-Oct-2023 14:47:18.678 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: Mac OS X 12-Oct-2023 14:47:18.678 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 14.0 12-Oct-2023 14:47:18.678 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: aarch64 12-Oct-2023 14:47:18.678 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: /Library/Java/JavaVirtualMachines/zulu-11.jdk/Contents/Home 12-Oct-2023 14:47:18.678 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 11.0.19+7-LTS 12-Oct-2023 14:47:18.678 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Azul Systems, Inc. 12-Oct-2023 14:47:18.678 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: /Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71 12-Oct-2023 14:47:18.678 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: /Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71 12-Oct-2023 14:47:18.719 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71 12-Oct-2023 14:47:18.719 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71 12-Oct-2023 14:47:18.719 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dwtp.deploy=/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71/webapps 12-Oct-2023 14:47:18.719 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71/conf/logging.properties 12-Oct-2023 14:47:18.720 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager 12-Oct-2023 14:47:18.720 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: --add-opens=java.base/java.lang=ALL-UNNAMED 12-Oct-2023 14:47:18.720 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: --add-opens=java.base/j
Update to 10.1.14 breaks our application
Hi,
We have a spring boot application (v3.1.4) It currently uses
org.apache.tomcat
tomcat-jdbc
10.1.13
A renovate bot updated this package to 10.1.14 and now our app fails
on startup, with the following exception..
2023-10-11T22:27:16.981Z WARN 7 — [ main]
o.h.e.j.e.i.JdbcEnvironmentInitiator : HHH000342: Could not obtain
connection to query metadata
java.sql.SQLException: null
at
org.apache.tomcat.jdbc.pool.ConnectionPool.setupConnection(ConnectionPool.java:351)
~[tomcat-jdbc-10.1.14.jar!/:na]
at
org.apache.tomcat.jdbc.pool.ConnectionPool.getConnection(ConnectionPool.java:200)
~[tomcat-jdbc-10.1.14.jar!/:na]
at
org.apache.tomcat.jdbc.pool.DataSourceProxy.getConnection(DataSourceProxy.java:133)
~[tomcat-jdbc-10.1.14.jar!/:na]
at
org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.getConnection(DatasourceConnectionProviderImpl.j
Caused by: java.lang.IllegalArgumentException:
org.apache.tomcat.jdbc.pool.PooledConnection is not an interface
at
java.base/java.lang.reflect.Proxy$ProxyBuilder.validateProxyInterfaces(Proxy.java:706)
~[na:na]
at java.base/java.lang.reflect.Proxy$ProxyBuilder.(Proxy.java:648)
~[na:na]
at
java.base/java.lang.reflect.Proxy.lambda$getProxyConstructor$1(Proxy.java:440)
~[na:na]
at
java.base/jdk.internal.loader.AbstractClassLoaderValue$Memoizer.get(AbstractClassLoaderValue.java:329)
~[na:na]
at
java.base/jdk.internal.loader.AbstractClassLoaderValue.computeIfAbsent(AbstractClassLoaderValue.java:205)
~[na:na]
at java.base/java.lang.reflect.Proxy.getProxyConstructor(Proxy.java:438)
~[na:na]
at java.base/java.lang.reflect.Proxy.getProxyClass(Proxy.java:398) ~[na:na]
at
org.apache.tomcat.jdbc.pool.ConnectionPool.getProxyConstructor(ConnectionPool.java:377)
~[tomcat-jdbc-10.1.14.jar:na]
at
org.apache.tomcat.jdbc.pool.ConnectionPool.setupConnection(ConnectionPool.java:339)
~[tomcat-jdbc-10.1.14.jar:na]
The code throws the exceptino when lef.afterPropertiesSet() is called.
@Bean(name = "fsEntityManagerFactory")
public EntityManagerFactory entityManagerFactory(DataSource fsDataSource) {
LocalContainerEntityManagerFactoryBean lef = new
LocalContainerEntityManagerFactoryBean();
HibernateJpaVendorAdapter vendorAdapter = new HibernateJpaVendorAdapter();
lef.setDataSource(fsDataSource);
lef.setJpaVendorAdapter(vendorAdapter);
lef.setPackagesToScan("xx");
lef.setPersistenceUnitName("fsPersistenceUnit");
HashMap properties = new HashMap<>();
properties.put("hibernate.dialect", "org.hibernate.dialect.DB2Dialect");
properties.put(AvailableSettings.ENHANCER_ENABLE_ASSOCIATION_MANAGEMENT,
"false");
properties.put(AvailableSettings.ENHANCER_ENABLE_DIRTY_TRACKING, "false");
properties.put(AvailableSettings.ENHANCER_ENABLE_LAZY_INITIALIZATION, "false");
properties.put("hibernate.jdbc.fetch_size", hibernateFetchSize);
properties.put("hibernate.show_sql", hibernateShowSQL);
properties.put("hibernate.default_schema", hibernateDefaultSchema);
lef.setJpaPropertyMap(properties);
lef.afterPropertiesSet();
return lef.getObject();
}
Right now I've reverted back to 10.1.13 and it works.
What is the best way to fix this?
I saw the release notes, updates were changed to the connection
pooling classes, but I'm unsure on how to proceed.
Thank you,
Rich
CONFIDENTIALITY NOTICE:
This is a transmission from Kohl's, Inc. and may contain information which is
confidential and proprietary.
If you are not the addressee, any disclosure, copying or distribution or use of
the contents of this message is expressly prohibited.
If you have received this transmission in error, please destroy it and notify
us immediately at 262-703-7000.
CAUTION:
Internet and e-mail communications are Kohl's property and Kohl's reserves the
right to retrieve and read any message created, sent and received. Kohl's
reserves the right to monitor messages by authorized Kohl's Associates at any
time without any further consent.
Re: JSF errors when upgrading Tomcat and Eclipse: com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation Unknow type constant pool XX at position XX
Hi Chris, Its JSF version 2.2.1 What is a bytecode scanner? I will google that, I don't have any idea. And why did I start getting this problem a few days ago? The only thing that changed is Eclipse (I upgraded it to the latest) and the Tomcat that Eclipse uses to run the website everytime I run it when I'm developing. I could upgrade JSF to some other version, but would that solve the issue? I don't know. And what if the few pages that I created using JSF will not work anymore because of the upgrade? I really totally forgot about how to use JSF, so I would not like having to learn it again now just because of this obstacle! Who is doing the class scanning? Is it JSF? Is it Tomcat? I have no clue right now. The interesting thing is that in my production server i didn't change anything in the software stack, but the WAR that now arrives there causes this problems. It is like if Eclipse is creating a new type of class/JAR files with some new characteristic, in my opinion. Thanks for your help!!! On Thu, Oct 12, 2023 at 4:35 PM Christopher Schultz < ch...@christopherschultz.net> wrote: > Brian, > > On 10/12/23 16:55, Brian Braun wrote: > > Hello, > > > > First of all, I apologize if maybe my issue is not exclusively related to > > Tomcat, but I think it is. > > > > I started my website many years ago, using Struts 1.2.4 and since then I > > have been using it. Some years after that I had the intention to migrate > to > > JSF (version 2.2.X) and combine both frameworks for a while until I > > migrated everything to JSF and Struts was gone. I started learning it, > > created a few pages on my site but then I realized that it was not the > > ideal framework for me, so I stopped creating more pages with JSF and > > continued developing my site with Struts, letting those few JSF pages > that > > work coexist with the rest of the site running using Struts. Since then, > I > > haven't touched JSF. I haven't created even one page with it, never > > upgraded its version but the JSF JAR and pages are still there. Years > > passed and nothing made me think about JSF. > > > > Now I'm using: > > - Mac with the M2 chip > > - Eclipse (ARM version) > > - Tomcat, when developing with Eclipse > > - Tomcat 9.0.58 at my production server (which runs Ubuntu 22.04, x86/64) > > - Azul's Java 11.0.19+7-LTS aarch64, when developing with Eclipse > > - Java 11.0.20.1+1-post-Ubuntu-0ubuntu122.04, at the production server > > > > Well, a few days ago I upgraded Eclipse to Version: 2023-09 (4.29.0) and > at > > the same time upgraded to Azul's Java 11.0.19+7-LTS aarch64 and to Tomcat > > 9.0.71 when developing. And since then, I get these "SEVERE" JSF error > > messages (many of them) when I start Tomcat: > > > > SEVERE [main] > > > com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation > > Unknow type constant pool NN at position XX > > > > Why is that? Could someone please give me a clue? I just upgraded Eclipse > > and Tomcat, didn't do anything else relevant and now I get these > messages. > > And when I create the WAR file and deploy it on my production server, I > get > > the same error messages as well over there. It seems like the class files > > that gets generated are now different, since I didn't upgrade anything on > > my production server, so it is the WAR file that gets generated with > > something problematic now. > > > > Thanks in advance! > > > > Here is the complete stuff that Tomcat shows, as a reference: > > > > 12-Oct-2023 14:47:18.676 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Server version > name: > > Apache Tomcat/9.0.71 > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Server built: Jan 9 > > 2023 22:33:01 UTC > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Server version > > number: 9.0.71.0 > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log OS Name: Mac OS X > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log OS Version: 14.0 > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Architecture: > aarch64 > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Java Home: > > /Library/Java/JavaVirtualMachines/zulu-11.jdk/Contents/Home > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log JVM Version: > > 11.0.19+7-LTS > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Azul > > Systems, Inc. > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: > > /Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71 > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerList
Re: JSF errors when upgrading Tomcat and Eclipse: com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation Unknow type constant pool XX at position XX
Hi, I replaced JSF 2.2.1 with 2.2.20 and the problem is gone! It seems that the old 2.2.1 JAR had some kind of old format that crushed with the way the latest Eclipse works. And since 2.2.1 to 2.2.20 is not a huge upgrade, my old JSF pages still work. Nice! Thanks! On Thu, Oct 12, 2023 at 4:35 PM Christopher Schultz < ch...@christopherschultz.net> wrote: > Brian, > > On 10/12/23 16:55, Brian Braun wrote: > > Hello, > > > > First of all, I apologize if maybe my issue is not exclusively related to > > Tomcat, but I think it is. > > > > I started my website many years ago, using Struts 1.2.4 and since then I > > have been using it. Some years after that I had the intention to migrate > to > > JSF (version 2.2.X) and combine both frameworks for a while until I > > migrated everything to JSF and Struts was gone. I started learning it, > > created a few pages on my site but then I realized that it was not the > > ideal framework for me, so I stopped creating more pages with JSF and > > continued developing my site with Struts, letting those few JSF pages > that > > work coexist with the rest of the site running using Struts. Since then, > I > > haven't touched JSF. I haven't created even one page with it, never > > upgraded its version but the JSF JAR and pages are still there. Years > > passed and nothing made me think about JSF. > > > > Now I'm using: > > - Mac with the M2 chip > > - Eclipse (ARM version) > > - Tomcat, when developing with Eclipse > > - Tomcat 9.0.58 at my production server (which runs Ubuntu 22.04, x86/64) > > - Azul's Java 11.0.19+7-LTS aarch64, when developing with Eclipse > > - Java 11.0.20.1+1-post-Ubuntu-0ubuntu122.04, at the production server > > > > Well, a few days ago I upgraded Eclipse to Version: 2023-09 (4.29.0) and > at > > the same time upgraded to Azul's Java 11.0.19+7-LTS aarch64 and to Tomcat > > 9.0.71 when developing. And since then, I get these "SEVERE" JSF error > > messages (many of them) when I start Tomcat: > > > > SEVERE [main] > > > com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation > > Unknow type constant pool NN at position XX > > > > Why is that? Could someone please give me a clue? I just upgraded Eclipse > > and Tomcat, didn't do anything else relevant and now I get these > messages. > > And when I create the WAR file and deploy it on my production server, I > get > > the same error messages as well over there. It seems like the class files > > that gets generated are now different, since I didn't upgrade anything on > > my production server, so it is the WAR file that gets generated with > > something problematic now. > > > > Thanks in advance! > > > > Here is the complete stuff that Tomcat shows, as a reference: > > > > 12-Oct-2023 14:47:18.676 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Server version > name: > > Apache Tomcat/9.0.71 > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Server built: Jan 9 > > 2023 22:33:01 UTC > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Server version > > number: 9.0.71.0 > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log OS Name: Mac OS X > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log OS Version: 14.0 > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Architecture: > aarch64 > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Java Home: > > /Library/Java/JavaVirtualMachines/zulu-11.jdk/Contents/Home > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log JVM Version: > > 11.0.19+7-LTS > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Azul > > Systems, Inc. > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: > > /Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71 > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: > > /Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71 > > 12-Oct-2023 14:47:18.719 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: > > > -Dcatalina.base=/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71 > > 12-Oct-2023 14:47:18.719 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: > > > -Dcatalina.home=/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71 > > 12-Oct-2023 14:47:18.719 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: > > > -Dwtp.deploy=/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat
Re: Update to 10.1.14 breaks our application
https://bz.apache.org/bugzilla/show_bug.cgi?id=67664
> On Oct 13, 2023, at 05:45, Richard Cook
> wrote:
>
> Hi,
>
> We have a spring boot application (v3.1.4) It currently uses
>
>
> org.apache.tomcat
> tomcat-jdbc
> 10.1.13
>
>
> A renovate bot updated this package to 10.1.14 and now our app fails
> on startup, with the following exception..
>
> 2023-10-11T22:27:16.981Z WARN 7 — [ main]
> o.h.e.j.e.i.JdbcEnvironmentInitiator : HHH000342: Could not obtain
> connection to query metadata
> java.sql.SQLException: null
> at
> org.apache.tomcat.jdbc.pool.ConnectionPool.setupConnection(ConnectionPool.java:351)
> ~[tomcat-jdbc-10.1.14.jar!/:na]
> at
> org.apache.tomcat.jdbc.pool.ConnectionPool.getConnection(ConnectionPool.java:200)
> ~[tomcat-jdbc-10.1.14.jar!/:na]
> at
> org.apache.tomcat.jdbc.pool.DataSourceProxy.getConnection(DataSourceProxy.java:133)
> ~[tomcat-jdbc-10.1.14.jar!/:na]
> at
> org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.getConnection(DatasourceConnectionProviderImpl.j
>
>
>
>
> Caused by: java.lang.IllegalArgumentException:
> org.apache.tomcat.jdbc.pool.PooledConnection is not an interface
>at
> java.base/java.lang.reflect.Proxy$ProxyBuilder.validateProxyInterfaces(Proxy.java:706)
> ~[na:na]
>at java.base/java.lang.reflect.Proxy$ProxyBuilder.(Proxy.java:648)
> ~[na:na]
>at
> java.base/java.lang.reflect.Proxy.lambda$getProxyConstructor$1(Proxy.java:440)
> ~[na:na]
>at
> java.base/jdk.internal.loader.AbstractClassLoaderValue$Memoizer.get(AbstractClassLoaderValue.java:329)
> ~[na:na]
>at
> java.base/jdk.internal.loader.AbstractClassLoaderValue.computeIfAbsent(AbstractClassLoaderValue.java:205)
> ~[na:na]
>at java.base/java.lang.reflect.Proxy.getProxyConstructor(Proxy.java:438)
> ~[na:na]
>at java.base/java.lang.reflect.Proxy.getProxyClass(Proxy.java:398) ~[na:na]
>at
> org.apache.tomcat.jdbc.pool.ConnectionPool.getProxyConstructor(ConnectionPool.java:377)
> ~[tomcat-jdbc-10.1.14.jar:na]
>at
> org.apache.tomcat.jdbc.pool.ConnectionPool.setupConnection(ConnectionPool.java:339)
> ~[tomcat-jdbc-10.1.14.jar:na]
>
>
> The code throws the exceptino when lef.afterPropertiesSet() is called.
>
>
> @Bean(name = "fsEntityManagerFactory")
> public EntityManagerFactory entityManagerFactory(DataSource fsDataSource) {
> LocalContainerEntityManagerFactoryBean lef = new
> LocalContainerEntityManagerFactoryBean();
> HibernateJpaVendorAdapter vendorAdapter = new HibernateJpaVendorAdapter();
> lef.setDataSource(fsDataSource);
> lef.setJpaVendorAdapter(vendorAdapter);
> lef.setPackagesToScan("xx");
> lef.setPersistenceUnitName("fsPersistenceUnit");
> HashMap properties = new HashMap<>();
> properties.put("hibernate.dialect", "org.hibernate.dialect.DB2Dialect");
> properties.put(AvailableSettings.ENHANCER_ENABLE_ASSOCIATION_MANAGEMENT,
> "false");
> properties.put(AvailableSettings.ENHANCER_ENABLE_DIRTY_TRACKING, "false");
> properties.put(AvailableSettings.ENHANCER_ENABLE_LAZY_INITIALIZATION,
> "false");
> properties.put("hibernate.jdbc.fetch_size", hibernateFetchSize);
> properties.put("hibernate.show_sql", hibernateShowSQL);
> properties.put("hibernate.default_schema", hibernateDefaultSchema);
>
> lef.setJpaPropertyMap(properties);
> lef.afterPropertiesSet();
> return lef.getObject();
> }
>
>
> Right now I've reverted back to 10.1.13 and it works.
>
> What is the best way to fix this?
>
> I saw the release notes, updates were changed to the connection
> pooling classes, but I'm unsure on how to proceed.
>
> Thank you,
>
> Rich
> CONFIDENTIALITY NOTICE:
> This is a transmission from Kohl's, Inc. and may contain information which is
> confidential and proprietary.
> If you are not the addressee, any disclosure, copying or distribution or use
> of the contents of this message is expressly prohibited.
> If you have received this transmission in error, please destroy it and notify
> us immediately at 262-703-7000.
>
> CAUTION:
> Internet and e-mail communications are Kohl's property and Kohl's reserves
> the right to retrieve and read any message created, sent and received. Kohl's
> reserves the right to monitor messages by authorized Kohl's Associates at any
> time without any further consent.
>
> -
> 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
Keycloak-adapter compatible version
Hi, I am trying to upgrade the tomcat 9 to 10 version, May I know which version of the keycloak adapter is compatible with tomcat10? Thanks, Navya
tomcat10 compatible keycloak-adapter version
Hi, I am trying to upgrade the tomcat 9 to 10 version, May I know which version of the keycloak adapter is compatible with tomcat10? Thanks, Navya
Re: Keycloak-adapter compatible version
Hi Navya, Am 13.10.23 um 07:49 schrieb Navya: I am trying to upgrade the tomcat 9 to 10 version, May I know which version of the keycloak adapter is compatible with tomcat10? Which or what kind of ,,keycloak adapter'' do you use with your current tomcat9 version ? -- Greets Bernd Schatz - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Keycloak-adapter compatible version
Thanks for the reply Currently in tomcat 9 I am using Keycloak Adapter version of 21.1.2 KEYCLOAKSUBDIR = 21.1.2 KEYCLOAKVERSION = keycloak-oidc-tomcat-adapter-$(KEYCLOAKSUBDIR) On Fri, Oct 13, 2023 at 11:47 AM Bernd Schatz wrote: > Hi Navya, > > > Am 13.10.23 um 07:49 schrieb Navya: > > I am trying to upgrade the tomcat 9 to 10 version, May I know which > version > > of the keycloak adapter is compatible with tomcat10? > > > Which or what kind of ,,keycloak adapter'' do you use with your > current tomcat9 version ? > > > -- > Greets > Bernd Schatz > > > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
