Re: Determining My Own IP address?
On 4/1/21 7:05 PM, Jerry Malcolm wrote: I am running several clustered Tomcat EC2 instances in an Amazon autoscaling group. These instances come and go based on load and failure/restart. IP addresses are assigned dynamically. As far I can figure, the only determinable difference between the instances is the IP address that is assigned to each EC2 when it spins up. I'm seeing some really weird symptoms at times that seem to indicate that the load balancer is not always honoring session affinity. It appears that another server periodically gets sent a request for a session that is being handled by a different EC2. The load balancer problem, if it exists, is definitely not a tomcat problem. However, in order to figure out what is really happening, I need to be able to track and differentiate which server is handling each request. Inside my TC webapp, if I could determine programatically some unique identifier for the EC2 running that http request, I could include that in my logs. My question is, is there a way to determine "my own" IP address from within a webapp servlet? Or is there some other way that I can log some string or some value that will guarantee to be unique within each instance of Tomcat? I guess another option would be to somehow get the tomcat bootup timestamp (from within a servlet) assuming two EC2s won't boot at precisely the same instant. But I don't know a way to access the boot timestamp. Am I missing something more obvious? You can get this from the getLocalAddr method of the ServletRequest object passed to your servlet's doPost/doGet. See [1]. Phil https://javaee.github.io/javaee-spec/javadocs/javax/servlet/ServletRequest.html#getLocalAddr Thx Jerry - 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
Determining My Own IP address?
I am running several clustered Tomcat EC2 instances in an Amazon autoscaling group. These instances come and go based on load and failure/restart. IP addresses are assigned dynamically. As far I can figure, the only determinable difference between the instances is the IP address that is assigned to each EC2 when it spins up. I'm seeing some really weird symptoms at times that seem to indicate that the load balancer is not always honoring session affinity. It appears that another server periodically gets sent a request for a session that is being handled by a different EC2. The load balancer problem, if it exists, is definitely not a tomcat problem. However, in order to figure out what is really happening, I need to be able to track and differentiate which server is handling each request. Inside my TC webapp, if I could determine programatically some unique identifier for the EC2 running that http request, I could include that in my logs. My question is, is there a way to determine "my own" IP address from within a webapp servlet? Or is there some other way that I can log some string or some value that will guarantee to be unique within each instance of Tomcat? I guess another option would be to somehow get the tomcat bootup timestamp (from within a servlet) assuming two EC2s won't boot at precisely the same instant. But I don't know a way to access the boot timestamp. Am I missing something more obvious? Thx Jerry - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
ApacheCon @Home 2021 Call for Presentations is open!
All, ApacheCon @Home is coming to your city/town/village/hamlet/countryside this September 21 - 23. Like last year's event, this one will be virtual, so there is no need to book travel/accommodations or potentially arrange for time-off from work. You don't even need to wear pants if you don't want to. The Call for Presentations is open NOW. Please submit your Tomcat (or other!) related presentation on this site: https://acah2021.jamhosted.net/ Feel free to browse the Presentations Page[1] on the Tomcat web site for some idea of what presentations have been given in the past. Anything related to Tomcat, servlet (etc.) specs, Java web application development, etc. would be considered in-scope for the Tomcat track. There are many other tracks planned as well. Yous presentation does /not need to be completed/ when you submit your idea. So if you have an idea, go ahead and submit it. You will have a few months to build your idea into a presentation. If you have any questions, please send a message to the users@ list with "ApacheCon" in the subject. Please don't email me individually unless you have a question that cannot be answered by anyone but me. My reply would go to the users@ list anyway, so you may as well post the question to the list in the first place :) Thanks, -chris [1] https://tomcat.apache.org/presentations.html - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Enable only TLSv1.3 for IBM SDK8 and Tomcat 7.0.108 on AIX 7.1
Arun, On 4/1/21 12:41, Arun Shankar wrote: Hello, We have a requirement to enable TLS traffic to only use TLS 1.3. We are currently on Tomcat version 7.0.53, which I learned does not support TLSv1.3 (I need to be atleast on Tomcat version 7.0.92 to have TLS 1.3 support from Tomcat (assuming the underlying Java supports it as well)). So I upgraded to the latest version of Tomcat 7 - Tomcat 7.0.108. Now when I enable TLSv1.3 by setting sslEnabledProtocols="TLSv1.3" in server.xml of Tomcat, I get the below error: SEVERE: javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate) at com.ibm.jsse2.Z.(Z.java:287) at com.ibm.jsse2.ac.(ac.java:9) at com.ibm.jsse2.ba.a(ba.java:52) at com.ibm.jsse2.bf.beginHandshake(bf.java:84) at org.apache.tomcat.util.net.SecureNioChannel.reset(SecureNioChannel.java:91) at org.apache.tomcat.util.net.SecureNioChannel.(SecureNioChannel.java:73) at org.apache.tomcat.util.net.NioEndpoint.setSocketOptions(NioEndpoint.java:677) at org.apache.tomcat.util.net.NioEndpoint$Acceptor.run(NioEndpoint.java:844) at java.lang.Thread.run(Thread.java:822) This happens when you try to make a connection, right? Or does it give you that error on startup? What client are you using to connect? In order to verify that your JVM is doing what you expect, try using this utility: https://github.com/ChristopherSchultz/ssltest Build it then run it like this: $ java -jar ssltest.jar -client-info You should see the list of TLS protocols supported at the top of the output. You can also use that to test your server once it's running: $ java -jar ssltest.jar localhost:8443 (or whatever your host:port is) If I set sslEnabledProtocols="TLSv1.2,TLSv1.3" in server.xml of Tomcat, I do not see the error but the client browser (Chrome) connects on TLSv1.2 and not on TLSv1.3. Try the above utility to see what TLSv1.2,TLSv1.3 gets you in your configuration. (Run it against the running server to see the effective protocols.) I then tried the same operations as above on Tomcat 8.5.35 and Tomcat 9.0.13 and I do not see this error. That does suggest that (a) your JVM does indeed support TLSv1.3 and (b) your configuration is correct. Last bit of missing information: when you use Tomcat 8.5/9.0 and don't see this error... does your client connect with TLSv1.3? But we have a requirement to stay on Tomcat 7 because of vendor support licensing. :( Can you please post your current from your Tomcat 7.0.108 conf/server.xml file? Remember to remove any secrets which may be in there. -chris - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Enable only TLSv1.3 for IBM SDK8 and Tomcat 7.0.108 on AIX 7.1
Hello, We have a requirement to enable TLS traffic to only use TLS 1.3. We are currently on Tomcat version 7.0.53, which I learned does not support TLSv1.3 (I need to be atleast on Tomcat version 7.0.92 to have TLS 1.3 support from Tomcat (assuming the underlying Java supports it as well)). So I upgraded to the latest version of Tomcat 7 - Tomcat 7.0.108. Now when I enable TLSv1.3 by setting sslEnabledProtocols="TLSv1.3" in server.xml of Tomcat, I get the below error: SEVERE: javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate) at com.ibm.jsse2.Z.(Z.java:287) at com.ibm.jsse2.ac.(ac.java:9) at com.ibm.jsse2.ba.a(ba.java:52) at com.ibm.jsse2.bf.beginHandshake(bf.java:84) at org.apache.tomcat.util.net.SecureNioChannel.reset(SecureNioChannel.java:91) at org.apache.tomcat.util.net.SecureNioChannel.(SecureNioChannel.java:73) at org.apache.tomcat.util.net.NioEndpoint.setSocketOptions(NioEndpoint.java:677) at org.apache.tomcat.util.net.NioEndpoint$Acceptor.run(NioEndpoint.java:844) at java.lang.Thread.run(Thread.java:822) If I set sslEnabledProtocols="TLSv1.2,TLSv1.3" in server.xml of Tomcat, I do not see the error but the client browser (Chrome) connects on TLSv1.2 and not on TLSv1.3. I then tried the same operations as above on Tomcat 8.5.35 and Tomcat 9.0.13 and I do not see this error. But we have a requirement to stay on Tomcat 7 because of vendor support licensing. Please help.
Re: Tomcat Error: VersionLoggerListener
Kishor,
On 4/1/21 11:31, KISHOR S.JADHAV wrote:
Hi Chris,
Please check the required details below,
1. Your OS vendors and full version: Windows 10 Enterprise
2. Your JVM vendor and full version: jre1.8.0_281
java version "1.8.0_281"
Java(TM) SE Runtime Environment (build 1.8.0_281-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.281-b09, mixed mode)
That's not what the startup logger says:
INFO: JVM Version: 15.0.2+7-27
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: JVM Vendor:Oracle Corporation
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
It also says you aren't running Tomcat 8.5 but 8.0:
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Server version:Apache Tomcat/8.0.36
If you think you are running 8.5 then you are not and something is very
wrong.
3. Your server.xml configuration, in particular the
Please check the details if anything require then please let me know
You are getting the error:
SEVERE: Failed to initialize end point associated with ProtocolHandler
["ajp-nio-8009"]
java.lang.IllegalArgumentException: timeout < 0
This means you have a negative sotimeout setting somewhere. I do not see
it in your configuration above.
Support for Tomcat 8.0 ended in June 2018, nearly 3 years ago.
https://tomcat.apache.org/tomcat-80-eol.html
Please upgrade to a supported version.
-chris
On Thu, 1 Apr 2021 at 20:09, Christopher Schultz <
ch...@christopherschultz.net> wrote:
Kishor,
On 4/1/21 08:57, KISHOR S.JADHAV wrote:
Hi Team,
I am trying to run my war file in tomcat version 8.5 is not working so
I
have decreased the tomcat version and using the Tomcat8 but in this, I
am
getting the below error,
Apr 01, 2021 6:25:11 PM org.apache.tomcat.util.digester.SetPropertiesRule
begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting
property 'source' to 'org.eclipse.jst.jee.server:GovernanceMetrics_P' did
not find a matching property.
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Server version:Apache Tomcat/8.0.36
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Server built: Jun 9 2016 13:55:50 UTC
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Server number: 8.0.36.0
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: OS Name: Windows 10
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: OS Version:10.0
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Architecture: amd64
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Java Home:
C:\Users\kishor.s.jadhav\Downloads\eclipse-jee-2021-03-R-win32-x86_64\eclipse\plugins\org.eclipse.justj.openjdk.hotspot.jre.full.win32.x86_64_15.0.2.v20210201-0955\jre
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: JVM Version: 15.0.2+7-27
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: JVM Vendor:Oracle Corporation
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: CATALINA_BASE:
C:\Users\kishor.s.jadhav\eclipse-workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp1
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: CATALINA_HOME: C:\Softwares\Tomcat\apache-tomcat-8.0.36
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Command line argument:
-Dcatalina.base=C:\Users\kishor.s.jadhav\eclipse-workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp1
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Command line argument:
-Dcatalina.home=C:\Softwares\Tomcat\apache-tomcat-8.0.36
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Command line argument:
-Dwtp.deploy=C:\Users\kishor.s.jadhav\eclipse-workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp1\wtpwebapps
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Command line argument: -Dfile.encoding=Cp1252
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Command line argument: -XX:+ShowCodeDetailsInExceptionMessages
Apr 01, 2021 6:25:11 PM org.apache.catalina.core.AprLifecycleListener
lifecycleEvent
INFO: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found on the
java.library.path:
Re: Tomcat Error: VersionLoggerListener
Hi Chris,
Please check the required details below,
1. Your OS vendors and full version: Windows 10 Enterprise
2. Your JVM vendor and full version: jre1.8.0_281
java version "1.8.0_281"
Java(TM) SE Runtime Environment (build 1.8.0_281-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.281-b09, mixed mode)
3. Your server.xml configuration, in particular the
Please check the details if anything require then please let me know
Thanks and Regards,
Kishor Jadhav
On Thu, 1 Apr 2021 at 20:09, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> Kishor,
>
> On 4/1/21 08:57, KISHOR S.JADHAV wrote:
> > Hi Team,
> > I am trying to run my war file in tomcat version 8.5 is not working so
> I
> > have decreased the tomcat version and using the Tomcat8 but in this, I
> am
> > getting the below error,
> >
> >
> > Apr 01, 2021 6:25:11 PM org.apache.tomcat.util.digester.SetPropertiesRule
> > begin
> > WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting
> > property 'source' to 'org.eclipse.jst.jee.server:GovernanceMetrics_P' did
> > not find a matching property.
> > Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
> > log
> > INFO: Server version:Apache Tomcat/8.0.36
> > Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
> > log
> > INFO: Server built: Jun 9 2016 13:55:50 UTC
> > Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
> > log
> > INFO: Server number: 8.0.36.0
> > Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
> > log
> > INFO: OS Name: Windows 10
> > Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
> > log
> > INFO: OS Version:10.0
> > Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
> > log
> > INFO: Architecture: amd64
> > Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
> > log
> > INFO: Java Home:
> >
> C:\Users\kishor.s.jadhav\Downloads\eclipse-jee-2021-03-R-win32-x86_64\eclipse\plugins\org.eclipse.justj.openjdk.hotspot.jre.full.win32.x86_64_15.0.2.v20210201-0955\jre
> > Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
> > log
> > INFO: JVM Version: 15.0.2+7-27
> > Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
> > log
> > INFO: JVM Vendor:Oracle Corporation
> > Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
> > log
> > INFO: CATALINA_BASE:
> >
> C:\Users\kishor.s.jadhav\eclipse-workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp1
> > Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
> > log
> > INFO: CATALINA_HOME: C:\Softwares\Tomcat\apache-tomcat-8.0.36
> > Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
> > log
> > INFO: Command line argument:
> >
> -Dcatalina.base=C:\Users\kishor.s.jadhav\eclipse-workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp1
> > Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
> > log
> > INFO: Command line argument:
> > -Dcatalina.home=C:\Softwares\Tomcat\apache-tomcat-8.0.36
> > Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
> > log
> > INFO: Command line argument:
> >
> -Dwtp.deploy=C:\Users\kishor.s.jadhav\eclipse-workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp1\wtpwebapps
> > Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
> > log
> > INFO: Command line argument: -Dfile.encoding=Cp1252
> > Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
> > log
> > INFO: Command line argument: -XX:+ShowCodeDetailsInExceptionMessages
> > Apr 01, 2021 6:25:11 PM org.apache.catalina.core.AprLifecycleListener
> > lifecycleEvent
> > INFO: The APR based Apache Tomcat Native library which allows optimal
> > performance in production environments was not found on the
> > java.library.path:
> >
> C:\Users\kishor.s.jadhav\Downloads\eclipse-jee-2021-03-R-win32-x86_64\eclipse\plugins\org.eclipse.justj.openjdk.hotspot.jre.full.win32.x86_64_15.0.2.v20210201-0955\jre\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:/Users/kishor.s.jadhav/Downloads/eclipse-jee-2021-03-R-win32-x86_64/eclipse//plugins/org.eclipse.justj.openjdk.hotspot.jre.full.win32.x86_64_15.0.2.v20210201-0955/jre/bin/server;C:/Users/kishor.s.jadhav/Downloads/eclipse-jee-2021-03-R-win32-x86_64/eclipse//plugins/org.eclipse.justj.openjdk.hotspot.jre.full.win32.x86_64_15.0.2.v20210201-0955/jre/bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program
> > Files\PuTTY\;C:\Program Files\OpenVPN\bin;C:\Program
> > Files\nodejs\;C:\ProgramData\chocolatey\bin;C:\Program Files
> > (x86)\Symantec\VIP Access Client\;C:\Program Files\dotnet\;C:\Program
> > Files\Microsoft SQL
Re: Tomcat Error: VersionLoggerListener
Kishor,
On 4/1/21 08:57, KISHOR S.JADHAV wrote:
Hi Team,
I am trying to run my war file in tomcat version 8.5 is not working so I
have decreased the tomcat version and using the Tomcat8 but in this, I am
getting the below error,
Apr 01, 2021 6:25:11 PM org.apache.tomcat.util.digester.SetPropertiesRule
begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting
property 'source' to 'org.eclipse.jst.jee.server:GovernanceMetrics_P' did
not find a matching property.
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Server version:Apache Tomcat/8.0.36
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Server built: Jun 9 2016 13:55:50 UTC
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Server number: 8.0.36.0
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: OS Name: Windows 10
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: OS Version:10.0
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Architecture: amd64
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Java Home:
C:\Users\kishor.s.jadhav\Downloads\eclipse-jee-2021-03-R-win32-x86_64\eclipse\plugins\org.eclipse.justj.openjdk.hotspot.jre.full.win32.x86_64_15.0.2.v20210201-0955\jre
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: JVM Version: 15.0.2+7-27
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: JVM Vendor:Oracle Corporation
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: CATALINA_BASE:
C:\Users\kishor.s.jadhav\eclipse-workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp1
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: CATALINA_HOME: C:\Softwares\Tomcat\apache-tomcat-8.0.36
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Command line argument:
-Dcatalina.base=C:\Users\kishor.s.jadhav\eclipse-workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp1
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Command line argument:
-Dcatalina.home=C:\Softwares\Tomcat\apache-tomcat-8.0.36
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Command line argument:
-Dwtp.deploy=C:\Users\kishor.s.jadhav\eclipse-workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp1\wtpwebapps
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Command line argument: -Dfile.encoding=Cp1252
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Command line argument: -XX:+ShowCodeDetailsInExceptionMessages
Apr 01, 2021 6:25:11 PM org.apache.catalina.core.AprLifecycleListener
lifecycleEvent
INFO: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found on the
java.library.path:
C:\Users\kishor.s.jadhav\Downloads\eclipse-jee-2021-03-R-win32-x86_64\eclipse\plugins\org.eclipse.justj.openjdk.hotspot.jre.full.win32.x86_64_15.0.2.v20210201-0955\jre\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:/Users/kishor.s.jadhav/Downloads/eclipse-jee-2021-03-R-win32-x86_64/eclipse//plugins/org.eclipse.justj.openjdk.hotspot.jre.full.win32.x86_64_15.0.2.v20210201-0955/jre/bin/server;C:/Users/kishor.s.jadhav/Downloads/eclipse-jee-2021-03-R-win32-x86_64/eclipse//plugins/org.eclipse.justj.openjdk.hotspot.jre.full.win32.x86_64_15.0.2.v20210201-0955/jre/bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program
Files\PuTTY\;C:\Program Files\OpenVPN\bin;C:\Program
Files\nodejs\;C:\ProgramData\chocolatey\bin;C:\Program Files
(x86)\Symantec\VIP Access Client\;C:\Program Files\dotnet\;C:\Program
Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Microsoft SQL
Server\Client
SDK\ODBC\170\Tools\Binn\;C:\Users\kishor.s.jadhav\AppData\Local\Microsoft\WindowsApps;C:\Users\kishor.s.jadhav\AppData\Local\Programs\Git\cmd;C:\Users\kishor.s.jadhav\AppData\Roaming\npm;C:\Users\kishor.s.jadhav\AppData\Local\Programs\Microsoft
VS
Code\bin;C:\Users\kishor.s.jadhav\.dotnet\tools;C:\Users\kishor.s.jadhav\Downloads\eclipse-jee-2021-03-R-win32-x86_64\eclipse;;.
Apr 01, 2021 6:25:11 PM
org.apache.catalina.core.JreMemoryLeakPreventionListener lifecycleEvent
SEVERE: Failed to trigger creation of the GC Daemon thread during Tomcat
start to prevent possible memory leaks. This is expected on non-Sun JVMs.
java.lang.ClassNotFoundException: sun.misc.GC
at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:435)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:589)
at
Re: Recent charset breakage
Konstantin,
On 4/1/21 05:06, Konstantin Kolinko wrote:
чт, 1 апр. 2021 г. в 00:55, Christopher Schultz :
[...]
I've written a tiny JSP to demonstrate the problem.
charecho.jsp
CUT
<%
response.setContentType("text/html");
response.setCharacterEncoding("UTF-8");
%>
The value above is misspelled. You are missing "charset=" before "UTF-8".
Personally, I usually echo the actual contentType header value when
writing a meta tag. I think that would be
Thanks for pointing that out. I have modified the charecho.jsp file, so
it is now:
<%@page contentType="text/html; charset=UTF-8" %>
<%= (null != request.getParameter("text") ?
request.getParameter("text") : "")%>
The behavior is the same.
If I instead insert the following after the @page directive (to act as a
filter, to keep the example completely self-contained), then this works
as desired:
<%
if(null == request.getCharacterEncoding()) {
application.log("Character encoding is unset; setting to UTF-8");
request.setCharacterEncoding("UTF-8");
}
%>
[...]
So, somewhat "mystery solved" although I'd like to understand why
didn't work.
Does validating your web.xml file against an xsd schema complete successfully?
request-character-encoding is defined in
(javax|jakarta)/serv/et/resources/web-app_4_0.xsd, which means Tomcat
9 or later. You wrote that you are running Tomcat 8.5.
Ooh, that would do it.
Confirmed: Using with Tomcat *9* behaves as
desired, even without the filter/hack to correct a missing charset.
Thanks,
-chris
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat Error: VersionLoggerListener
Hi Team,
I am trying to run my war file in tomcat version 8.5 is not working so I
have decreased the tomcat version and using the Tomcat8 but in this, I am
getting the below error,
Apr 01, 2021 6:25:11 PM org.apache.tomcat.util.digester.SetPropertiesRule
begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting
property 'source' to 'org.eclipse.jst.jee.server:GovernanceMetrics_P' did
not find a matching property.
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Server version:Apache Tomcat/8.0.36
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Server built: Jun 9 2016 13:55:50 UTC
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Server number: 8.0.36.0
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: OS Name: Windows 10
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: OS Version:10.0
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Architecture: amd64
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Java Home:
C:\Users\kishor.s.jadhav\Downloads\eclipse-jee-2021-03-R-win32-x86_64\eclipse\plugins\org.eclipse.justj.openjdk.hotspot.jre.full.win32.x86_64_15.0.2.v20210201-0955\jre
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: JVM Version: 15.0.2+7-27
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: JVM Vendor:Oracle Corporation
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: CATALINA_BASE:
C:\Users\kishor.s.jadhav\eclipse-workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp1
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: CATALINA_HOME: C:\Softwares\Tomcat\apache-tomcat-8.0.36
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Command line argument:
-Dcatalina.base=C:\Users\kishor.s.jadhav\eclipse-workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp1
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Command line argument:
-Dcatalina.home=C:\Softwares\Tomcat\apache-tomcat-8.0.36
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Command line argument:
-Dwtp.deploy=C:\Users\kishor.s.jadhav\eclipse-workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp1\wtpwebapps
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Command line argument: -Dfile.encoding=Cp1252
Apr 01, 2021 6:25:11 PM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Command line argument: -XX:+ShowCodeDetailsInExceptionMessages
Apr 01, 2021 6:25:11 PM org.apache.catalina.core.AprLifecycleListener
lifecycleEvent
INFO: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found on the
java.library.path:
C:\Users\kishor.s.jadhav\Downloads\eclipse-jee-2021-03-R-win32-x86_64\eclipse\plugins\org.eclipse.justj.openjdk.hotspot.jre.full.win32.x86_64_15.0.2.v20210201-0955\jre\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:/Users/kishor.s.jadhav/Downloads/eclipse-jee-2021-03-R-win32-x86_64/eclipse//plugins/org.eclipse.justj.openjdk.hotspot.jre.full.win32.x86_64_15.0.2.v20210201-0955/jre/bin/server;C:/Users/kishor.s.jadhav/Downloads/eclipse-jee-2021-03-R-win32-x86_64/eclipse//plugins/org.eclipse.justj.openjdk.hotspot.jre.full.win32.x86_64_15.0.2.v20210201-0955/jre/bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program
Files\PuTTY\;C:\Program Files\OpenVPN\bin;C:\Program
Files\nodejs\;C:\ProgramData\chocolatey\bin;C:\Program Files
(x86)\Symantec\VIP Access Client\;C:\Program Files\dotnet\;C:\Program
Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Microsoft SQL
Server\Client
SDK\ODBC\170\Tools\Binn\;C:\Users\kishor.s.jadhav\AppData\Local\Microsoft\WindowsApps;C:\Users\kishor.s.jadhav\AppData\Local\Programs\Git\cmd;C:\Users\kishor.s.jadhav\AppData\Roaming\npm;C:\Users\kishor.s.jadhav\AppData\Local\Programs\Microsoft
VS
Code\bin;C:\Users\kishor.s.jadhav\.dotnet\tools;C:\Users\kishor.s.jadhav\Downloads\eclipse-jee-2021-03-R-win32-x86_64\eclipse;;.
Apr 01, 2021 6:25:11 PM
org.apache.catalina.core.JreMemoryLeakPreventionListener lifecycleEvent
SEVERE: Failed to trigger creation of the GC Daemon thread during Tomcat
start to prevent possible memory leaks. This is expected on non-Sun JVMs.
java.lang.ClassNotFoundException: sun.misc.GC
at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:435)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:589)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
at
Re: Tomcat Error: VersionLoggerListener
Hi, On Thu, Apr 1, 2021 at 1:42 PM KISHOR S.JADHAV wrote: > Hi Team, > I am trying to run my war file in tomcat version 8.5 is not working so I > have decrease the tomcat version and using the Tomcat8 but in this, I am > getting the below error, > > [image: image.png] > > > [image: image.png] > Please copy/paste the text instead of creating screenshots. Attachments are not allowed in the mailing lists. > > Getting this error *org.apache.catalina.startup.VersionLoggerListener > log* > I am not able to find the correct solution for this issue, Request you > to can you please help me to solve this issue > > Thanks and Regards, > Kishor Jadhav > >
Tomcat Error: VersionLoggerListener
Hi Team, I am trying to run my war file in tomcat version 8.5 is not working so I have decrease the tomcat version and using the Tomcat8 but in this, I am getting the below error, [image: image.png] [image: image.png] Getting this error *org.apache.catalina.startup.VersionLoggerListener log* I am not able to find the correct solution for this issue, Request you to can you please help me to solve this issue Thanks and Regards, Kishor Jadhav
Re: Recent charset breakage
чт, 1 апр. 2021 г. в 00:55, Christopher Schultz :
>
> [...]
>
> I've written a tiny JSP to demonstrate the problem.
>
> charecho.jsp
> CUT
> <%
>response.setContentType("text/html");
>response.setCharacterEncoding("UTF-8");
> %>
>
>
The value above is misspelled. You are missing "charset=" before "UTF-8".
Personally, I usually echo the actual contentType header value when
writing a meta tag. I think that would be
[...]
>
> So, somewhat "mystery solved" although I'd like to understand why
> didn't work.
Does validating your web.xml file against an xsd schema complete successfully?
request-character-encoding is defined in
(javax|jakarta)/serv/et/resources/web-app_4_0.xsd, which means Tomcat
9 or later. You wrote that you are running Tomcat 8.5.
Best regards,
Konstantin Kolinko
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
