RE: Mod_JK vs Mod_Proxy
I get it and agree, but it does just add unnecessary complexity also. Have a Happy!!! 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: Wednesday, December 7, 2022 4:54 PM > To: Tomcat Users List ; > jonmcalexan...@wellsfargo.com.INVALID > Subject: Re: Mod_JK vs Mod_Proxy > > Jon, > > On 12/6/22 16:22, jonmcalexan...@wellsfargo.com.INVALID wrote: > > What, pray tell, is an encrypted AJP connection? Are you talking AJP > > over an SSH Tunnel (Stunnel)? > Exactly. It's absolutely cheating, but it achieves the goal :) > > -chris > > >> -Original Message- > >> From: Christopher Schultz > >> Sent: Tuesday, December 6, 2022 3:01 PM > >> To: users@tomcat.apache.org > >> Subject: Re: Mod_JK vs Mod_Proxy > >> > >> Jon, > >> > >> On 12/6/22 12:36, jonmcalexan...@wellsfargo.com.INVALID wrote: > >>> IMHO, switching to mod_proxy, and using it over SSL, is by far > >>> better than > >> using mod_jk or mod_ajp, primarily as mod_proxy allows for secure > >> proxy connection, whereas mod_jk and mod_ajp aren't "secure" as they > >> are not encrypted channels. > >> > >> While this is true (and supports my assertion that everyone should > >> migrate), it doesn't preclude the use of encrypted AJP connections. > >> > >> -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: Mod_JK vs Mod_Proxy
Jon, On 12/6/22 16:22, jonmcalexan...@wellsfargo.com.INVALID wrote: What, pray tell, is an encrypted AJP connection? Are you talking AJP over an SSH Tunnel (Stunnel)? Exactly. It's absolutely cheating, but it achieves the goal :) -chris -Original Message- From: Christopher Schultz Sent: Tuesday, December 6, 2022 3:01 PM To: users@tomcat.apache.org Subject: Re: Mod_JK vs Mod_Proxy Jon, On 12/6/22 12:36, jonmcalexan...@wellsfargo.com.INVALID wrote: IMHO, switching to mod_proxy, and using it over SSL, is by far better than using mod_jk or mod_ajp, primarily as mod_proxy allows for secure proxy connection, whereas mod_jk and mod_ajp aren't "secure" as they are not encrypted channels. While this is true (and supports my assertion that everyone should migrate), it doesn't preclude the use of encrypted AJP connections. -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: Error setting socket options
In fact I'm not setting those variables. That's why I'm not sure because I'm getting that error. On Wed, Dec 7, 2022 at 10:36 AM Mark Thomas wrote: > On 07/12/2022 12:15, Gustavo Monti Rocha wrote: > > Hi Mark, > > > > Thanks for helping me. How can I check if my environment has valid values > > for JVM? > > If you are setting those values, the simple solution is don't set them > and the JVM will use appropriate defaults for your environment. > > If you do want to set them (why?), then look at the docs for your JVM / > platform to find acceptable values. > > Mark > > > > > > Thanks in advance. > > > > > > On Wed, Dec 7, 2022 at 6:21 AM Mark Thomas wrote: > > > >> Make sure you have set socket.soLingerOn and socket.soLingerTime to > >> valid values for your JVM and platform. Tomcat does not set these by > >> default so it is something your application or Spring Boot is doing. > >> > >> Mark > >> > >> > >> On 07/12/2022 01:47, Gustavo Monti Rocha wrote: > >>> Hello, > >>> > >>> I'm using spring boot with eureka and openfeign to communicate between > >>> services A and B. > >>> > >>> When a send a request from A to B getting: > >>> > >>> 2022-12-06 22:30:26.634 ERROR 6352 --- [o-8081-Acceptor] > >>> org.apache.tomcat.util.net.NioEndpoint : Error setting socket > options > >>> > >>> java.net.SocketException: Invalid argument > >>> at java.base/sun.nio.ch.Net.setIntOption0(Native Method) ~[na:na] > >>> at java.base/sun.nio.ch.Net.setSocketOption(Net.java:455) ~[na:na] > >>> at java.base/sun.nio.ch.Net.setSocketOption(Net.java:393) ~[na:na] > >>> at > >>> java.base/sun.nio.ch > >> .SocketChannelImpl.setOption(SocketChannelImpl.java:280) > >>> ~[na:na] > >>> at java.base/sun.nio.ch > >> .SocketAdaptor.setIntOption(SocketAdaptor.java:247) > >>> ~[na:na] > >>> at java.base/sun.nio.ch > >> .SocketAdaptor.setSoLinger(SocketAdaptor.java:285) > >>> ~[na:na] > >>> at > >>> org.apache.tomcat.util.net > >> .SocketProperties.setProperties(SocketProperties.java:219) > >>> ~[tomcat-embed-core-9.0.55.jar:9.0.55] > >>> at > >>> org.apache.tomcat.util.net > >> .NioEndpoint.setSocketOptions(NioEndpoint.java:495) > >>> ~[tomcat-embed-core-9.0.55.jar:9.0.55] > >>> at > >>> org.apache.tomcat.util.net > >> .NioEndpoint.setSocketOptions(NioEndpoint.java:78) > >>> ~[tomcat-embed-core-9.0.55.jar:9.0.55] > >>> at org.apache.tomcat.util.net.Acceptor.run(Acceptor.java:149) > >>> ~[tomcat-embed-core-9.0.55.jar:9.0.55] > >>> at java.base/java.lang.Thread.run(Thread.java:833) ~[na:na] > >>> > >>> I'm using Spring boot 2.5.7 and Spring Cloud 2020.0.3. > >>> > >>> java version "17.0.5" 2022-10-18 LTS > >>> Java(TM) SE Runtime Environment (build 17.0.5+9-LTS-191) > >>> Java HotSpot(TM) 64-Bit Server VM (build 17.0.5+9-LTS-191, mixed mode, > >>> sharing) > >>> > >> > >> - > >> 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: Error setting socket options
On 07/12/2022 12:15, Gustavo Monti Rocha wrote: Hi Mark, Thanks for helping me. How can I check if my environment has valid values for JVM? If you are setting those values, the simple solution is don't set them and the JVM will use appropriate defaults for your environment. If you do want to set them (why?), then look at the docs for your JVM / platform to find acceptable values. Mark Thanks in advance. On Wed, Dec 7, 2022 at 6:21 AM Mark Thomas wrote: Make sure you have set socket.soLingerOn and socket.soLingerTime to valid values for your JVM and platform. Tomcat does not set these by default so it is something your application or Spring Boot is doing. Mark On 07/12/2022 01:47, Gustavo Monti Rocha wrote: Hello, I'm using spring boot with eureka and openfeign to communicate between services A and B. When a send a request from A to B getting: 2022-12-06 22:30:26.634 ERROR 6352 --- [o-8081-Acceptor] org.apache.tomcat.util.net.NioEndpoint : Error setting socket options java.net.SocketException: Invalid argument at java.base/sun.nio.ch.Net.setIntOption0(Native Method) ~[na:na] at java.base/sun.nio.ch.Net.setSocketOption(Net.java:455) ~[na:na] at java.base/sun.nio.ch.Net.setSocketOption(Net.java:393) ~[na:na] at java.base/sun.nio.ch .SocketChannelImpl.setOption(SocketChannelImpl.java:280) ~[na:na] at java.base/sun.nio.ch .SocketAdaptor.setIntOption(SocketAdaptor.java:247) ~[na:na] at java.base/sun.nio.ch .SocketAdaptor.setSoLinger(SocketAdaptor.java:285) ~[na:na] at org.apache.tomcat.util.net .SocketProperties.setProperties(SocketProperties.java:219) ~[tomcat-embed-core-9.0.55.jar:9.0.55] at org.apache.tomcat.util.net .NioEndpoint.setSocketOptions(NioEndpoint.java:495) ~[tomcat-embed-core-9.0.55.jar:9.0.55] at org.apache.tomcat.util.net .NioEndpoint.setSocketOptions(NioEndpoint.java:78) ~[tomcat-embed-core-9.0.55.jar:9.0.55] at org.apache.tomcat.util.net.Acceptor.run(Acceptor.java:149) ~[tomcat-embed-core-9.0.55.jar:9.0.55] at java.base/java.lang.Thread.run(Thread.java:833) ~[na:na] I'm using Spring boot 2.5.7 and Spring Cloud 2020.0.3. java version "17.0.5" 2022-10-18 LTS Java(TM) SE Runtime Environment (build 17.0.5+9-LTS-191) Java HotSpot(TM) 64-Bit Server VM (build 17.0.5+9-LTS-191, mixed mode, sharing) - 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: Regarding Compilation Steps for Tomcat version 9 on RHEL8
On 07/12/2022 09:36, Vivek Naruka (EXT-NSB) wrote: Hi, We have downloaded Tomcat version 9 "apache-tomcat-9.0.70.tar.gz" from https://tomcat.apache.org/download-90.cgi. To check the compatibility of Tomcat version 9.0 with OpenSSL 3.0, we need to compile source code of Tomcat version 9 on RHEL-8 with OpenSSL3.0. We require compilation steps to compile Tomcat source code on RHEL8. Tomcat 9.0.x does not require OpenSSL to compile. What makes you think it does? Could you please help to share the compilation steps? Try looking in the BUILDING.txt file in the root of the source tarball. The build should be fully reproducible, providing you follow the additional instructions for reproducible builds. Getting back to the OpenSSL 3.0 question. Tomcat Native, which does have a dependency on OpenSSL, is compatible with OpenSSL in both the 1.2.x and 2.0.x branches. What makes you think that it is not? You can use Tomcat Native 1.2.x or 2.0.x with Tomcat 9.0.x but if you use Tomcat Native 2.0.x, you can't use the APR/native connectors - you must use NIO or NIO2. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Error setting socket options
Hi Mark, Thanks for helping me. How can I check if my environment has valid values for JVM? Thanks in advance. On Wed, Dec 7, 2022 at 6:21 AM Mark Thomas wrote: > Make sure you have set socket.soLingerOn and socket.soLingerTime to > valid values for your JVM and platform. Tomcat does not set these by > default so it is something your application or Spring Boot is doing. > > Mark > > > On 07/12/2022 01:47, Gustavo Monti Rocha wrote: > > Hello, > > > > I'm using spring boot with eureka and openfeign to communicate between > > services A and B. > > > > When a send a request from A to B getting: > > > > 2022-12-06 22:30:26.634 ERROR 6352 --- [o-8081-Acceptor] > > org.apache.tomcat.util.net.NioEndpoint : Error setting socket options > > > > java.net.SocketException: Invalid argument > > at java.base/sun.nio.ch.Net.setIntOption0(Native Method) ~[na:na] > > at java.base/sun.nio.ch.Net.setSocketOption(Net.java:455) ~[na:na] > > at java.base/sun.nio.ch.Net.setSocketOption(Net.java:393) ~[na:na] > > at > > java.base/sun.nio.ch > .SocketChannelImpl.setOption(SocketChannelImpl.java:280) > > ~[na:na] > > at java.base/sun.nio.ch > .SocketAdaptor.setIntOption(SocketAdaptor.java:247) > > ~[na:na] > > at java.base/sun.nio.ch > .SocketAdaptor.setSoLinger(SocketAdaptor.java:285) > > ~[na:na] > > at > > org.apache.tomcat.util.net > .SocketProperties.setProperties(SocketProperties.java:219) > > ~[tomcat-embed-core-9.0.55.jar:9.0.55] > > at > > org.apache.tomcat.util.net > .NioEndpoint.setSocketOptions(NioEndpoint.java:495) > > ~[tomcat-embed-core-9.0.55.jar:9.0.55] > > at > > org.apache.tomcat.util.net > .NioEndpoint.setSocketOptions(NioEndpoint.java:78) > > ~[tomcat-embed-core-9.0.55.jar:9.0.55] > > at org.apache.tomcat.util.net.Acceptor.run(Acceptor.java:149) > > ~[tomcat-embed-core-9.0.55.jar:9.0.55] > > at java.base/java.lang.Thread.run(Thread.java:833) ~[na:na] > > > > I'm using Spring boot 2.5.7 and Spring Cloud 2020.0.3. > > > > java version "17.0.5" 2022-10-18 LTS > > Java(TM) SE Runtime Environment (build 17.0.5+9-LTS-191) > > Java HotSpot(TM) 64-Bit Server VM (build 17.0.5+9-LTS-191, mixed mode, > > sharing) > > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
Regarding Compilation Steps for Tomcat version 9 on RHEL8
Hi, We have downloaded Tomcat version 9 "apache-tomcat-9.0.70.tar.gz" from https://tomcat.apache.org/download-90.cgi. To check the compatibility of Tomcat version 9.0 with OpenSSL 3.0, we need to compile source code of Tomcat version 9 on RHEL-8 with OpenSSL3.0. We require compilation steps to compile Tomcat source code on RHEL8. Could you please help to share the compilation steps? Regards Vivek Singh Naruka
Re: Error setting socket options
Make sure you have set socket.soLingerOn and socket.soLingerTime to valid values for your JVM and platform. Tomcat does not set these by default so it is something your application or Spring Boot is doing. Mark On 07/12/2022 01:47, Gustavo Monti Rocha wrote: Hello, I'm using spring boot with eureka and openfeign to communicate between services A and B. When a send a request from A to B getting: 2022-12-06 22:30:26.634 ERROR 6352 --- [o-8081-Acceptor] org.apache.tomcat.util.net.NioEndpoint : Error setting socket options java.net.SocketException: Invalid argument at java.base/sun.nio.ch.Net.setIntOption0(Native Method) ~[na:na] at java.base/sun.nio.ch.Net.setSocketOption(Net.java:455) ~[na:na] at java.base/sun.nio.ch.Net.setSocketOption(Net.java:393) ~[na:na] at java.base/sun.nio.ch.SocketChannelImpl.setOption(SocketChannelImpl.java:280) ~[na:na] at java.base/sun.nio.ch.SocketAdaptor.setIntOption(SocketAdaptor.java:247) ~[na:na] at java.base/sun.nio.ch.SocketAdaptor.setSoLinger(SocketAdaptor.java:285) ~[na:na] at org.apache.tomcat.util.net.SocketProperties.setProperties(SocketProperties.java:219) ~[tomcat-embed-core-9.0.55.jar:9.0.55] at org.apache.tomcat.util.net.NioEndpoint.setSocketOptions(NioEndpoint.java:495) ~[tomcat-embed-core-9.0.55.jar:9.0.55] at org.apache.tomcat.util.net.NioEndpoint.setSocketOptions(NioEndpoint.java:78) ~[tomcat-embed-core-9.0.55.jar:9.0.55] at org.apache.tomcat.util.net.Acceptor.run(Acceptor.java:149) ~[tomcat-embed-core-9.0.55.jar:9.0.55] at java.base/java.lang.Thread.run(Thread.java:833) ~[na:na] I'm using Spring boot 2.5.7 and Spring Cloud 2020.0.3. java version "17.0.5" 2022-10-18 LTS Java(TM) SE Runtime Environment (build 17.0.5+9-LTS-191) Java HotSpot(TM) 64-Bit Server VM (build 17.0.5+9-LTS-191, mixed mode, sharing) - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
