Re: Tomcat not releasing connector port at shutdown

On 3/20/25 9:00 AM, Christopher Schultz wrote: Is the process still running? My guess is that the old process is never actually stopping. FWIW: I've experienced that situation (i.e., the Tomcat server jobs lingering after being told to shut down) on IBM Midrange boxes enough times that I wro

Re: Tomcat not releasing connector port at shutdown

_BASE setups, when getting the shutdown command from the shutdown port, appears to shut down normally. Unfortunately, it never appears to release the connector port for which it's configured. When it's restarted, it fails as it's unable to bind to the port. I've checked using

Tomcat not releasing connector port at shutdown

m the shutdown port, appears to shut down normally. Unfortunately, it never appears to release the connector port for which it's configured. When it's restarted, it fails as it's unable to bind to the port. I've checked using netstat, lsof, ss, ps to see if there's anythi

Re: Secure connection - only ipv6 listener at port 8443

gt;> > proxyName="other.de <http://other.de/> <http://other.de >> <http://other.de/>>" maxThreads="150" enableLookups="false" >> redirectPort="8443" acceptCount="100" connectionTimeout=&qu

Re: Secure connection - only ipv6 listener at port 8443

 disableUploadTimeout="true" />      proxyName="other.de <http://other.de>" maxThreads="150" enableLookups="false"  redirectPort="8443" acceptCount="100" connectionTimeout="2"      disableUploadTimeout="true&qu

Secure connection - only ipv6 listener at port 8443

Hi, I'm trying to connect to a tomcat9 server for which I made an entry in server.xml: and the following entries are also present, FWIW: Connection to the server through port 8443 seems to work (filtered by ufw) but I'm

Re: Tomcat9 not listening to ipv4 port 8080, only ipv6

Hi, > Christoph, > > On 11/28/23 09:53, Christoph Kukulies wrote: >> That was my connector: >> >>  >                connectionTimeout="2" >>                redirectPort="8443" /> >> >> I triednetstat -tulpn as well

Re: Tomcat9 not listening to ipv4 port 8080, only ipv6

Christoph, On 11/28/23 09:53, Christoph Kukulies wrote: That was my connector:   I triednetstat -tulpn as well and it could be seen there was  no listener under ip4 and port 8080. If you use the "address" attribute, you can pick the interface you will listen to: "

Re: Tomcat9 not listening to ipv4 port 8080, only ipv6

On 11/28/23 05:24, Christoph Kukulies wrote: root@mail:/var/lib/tomcat9/logs# lsof -i :8080 COMMAND   PID   USER   FD   TYPE DEVICE SIZE/OFF NODE NAME java    58986 tomcat   37u  IPv6 571175      0t0  TCP *:http-alt (LISTEN) root@mail:/var/lib/tomcat9/logs# On my local desktop (running Ubuntu 2

Re: Tomcat9 not listening to ipv4 port 8080, only ipv6

Hi Christopher, That was my connector: I tried netstat -tulpn as well and it could be seen there was no listener under ip4 and port 8080. Thanks, -- Christoph > Am 28.11.2023 um 15:15 schrieb Christopher Schultz > : > > Christoph, > > On 11/28/23 08:26, Christ

Re: Tomcat9 not listening to ipv4 port 8080, only ipv6

figuration look like? Try using netstat instead of lsof. It will show you the network interface being used as well as the port number and IP stack type. -chris Am 28.11.2023 um 13:58 schrieb Suvendu Sekhar Mondal mailto:suv3...@gmail.com>>: Hello Christoph, On Tue, Nov 28, 2023, 5

Re: Tomcat9 not listening to ipv4 port 8080, only ipv6

Hi Suvendu, not that I kew of (changes in JVM arguments). I will try your suggestion: -Djava.net.preferIPv4Stack=true and thanks, it helped: I put it into /etc/defaults/tomcat9 (under Ubuntu 22.04) JAVA_OPTS="-Djava.awt.headless=true -Djava.net.preferIPv4Stack=true" and now I have: root@mail

Re: Tomcat9 not listening to ipv4 port 8080, only ipv6

Hello Christoph, On Tue, Nov 28, 2023, 5:55 PM Christoph Kukulies wrote: > I'm pulling my hairs on a suddenly occured - possibly - misconfiguration. > But I can't find it out: > > catalina.2023-11-28.log: > > > 28-Nov-2023 13:15:43.742 INFO [main] > org.apache.catalina.startup.VersionLoggerListe

Tomcat9 not listening to ipv4 port 8080, only ipv6

I'm pulling my hairs on a suddenly occured - possibly - misconfiguration. But I can't find it out: catalina.2023-11-28.log: 28-Nov-2023 13:15:43.742 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version name: Apache Tomcat/9.0.58 (Ubuntu) 28-Nov-2023 13:15:43.743

Re: Logging format (port %p)

Sorry, a bit searching revealed: /var/lib/tomcat9/server.xml: > Am 18.11.2023 um 14:48 schrieb Christoph Kukulies : > > I'm running tomcat9 as a backend server and I have configured different > ports. For debugging purposes I would like to log the port > a request i

Logging format (port %p)

I'm running tomcat9 as a backend server and I have configured different ports. For debugging purposes I would like to log the port a request is being sent through. Where is the logging format "wired" into the config? At the moment I'm seeing this (in root@mail:/var/lib/t

Re: Redirect appends port number?

er Schultz < ch...@christopherschultz.net> wrote: > Kevin, > > On 4/12/23 19:35, Kevin Huntly wrote: > > I'm seeing some odd behavior - my servlet filter is redirecting with port > > 10943 attached to the redirect > > Are you the author of the filter? If so, can you po

Re: Redirect appends port number?

Kevin, On 4/12/23 19:35, Kevin Huntly wrote: I'm seeing some odd behavior - my servlet filter is redirecting with port 10943 attached to the redirect Are you the author of the filter? If so, can you post the code that is determining what URL to use for the redirect? > - that por

Redirect appends port number?

Hello everyone, I'm sorry for spamming the list =( I'm seeing some odd behavior - my servlet filter is redirecting with port 10943 attached to the redirect - that port is the port httpd is listening on, but there's a redirect under the covers for TCP 443 to TCP 10943. I'm not

Re: AW: TLS configuration TLS for JMX port

Markus, On 11/4/22 06:04, Bärtschi, Markus-MGB wrote: On 04/11/2022 08:06, Bärtschi, Markus-MGB wrote: How can I configure TSL for my JMX port without the keystore information showing up on the command line ? Don't use passwords. Rely on operating system file permissions to limit a

AW: TLS configuration TLS for JMX port

On 04/11/2022 08:06, Bärtschi, Markus-MGB wrote: >> How can I configure TSL for my JMX port without the keystore information >> showing up on the command line ? > Don't use passwords. Rely on operating system file permissions to limit > access to the file to the Tomcat

Re: TLS configuration TLS for JMX port

work. How can I configure TSL for my JMX port without the keystore information showing up on the command line ? Don't use passwords. Rely on operating system file permissions to limit access to the file to the Tomcat process (and root). Keep in mind that JMX has various security issue

TLS configuration TLS for JMX port

I configured TLS for my JMX post, this is working alright. But the keystore information, especially the passwords end up on the java/tomcat command line. I did attempt to move the configuration items into catalina.properties, but this did not work. How can I configure TSL for my JMX port

Re: Tomcat Redirect Port 80 to 443 and Block OPTIONS HTTP Method

standing is that TRACE got its poor reputation due to a > >>> misbehaving browser. Rather than pressure the browser vendor to fix > >>> their broken browser, the security community decided to pressure the > >>> server community to disable the functionality th

Re: Tomcat Redirect Port 80 to 443 and Block OPTIONS HTTP Method

Thanks, Bhavesh On Fri, Oct 7, 2022 at 10:59 AM Mark Thomas wrote: On 07/10/2022 18:09, Bhavesh Mistry wrote: Hi Tomcat Team, We have a unique situation. We wanted to block ALL *OPTIONALS* HTTP method on port 80 and 443. We have connector definitions as follows:

Re: Tomcat Redirect Port 80 to 443 and Block OPTIONS HTTP Method

have been at the time and how reluctant to >> change the vendor was. >> >> CONNECT returns 405 by default in a Servlet container and none of TRACE, >> OPTIONS or HEAD are inherently unsafe. >> >> Mark >> >> >> > >

Re: Tomcat Redirect Port 80 to 443 and Block OPTIONS HTTP Method

gt; Mark > > > > > > Thanks, > > > > Bhavesh > > > > On Fri, Oct 7, 2022 at 10:59 AM Mark Thomas wrote: > > > >> On 07/10/2022 18:09, Bhavesh Mistry wrote: > >>> Hi Tomcat Team, > >>&g

Re: Tomcat Redirect Port 80 to 443 and Block OPTIONS HTTP Method

n a Servlet container and none of TRACE, OPTIONS or HEAD are inherently unsafe. Mark Thanks, Bhavesh On Fri, Oct 7, 2022 at 10:59 AM Mark Thomas wrote: On 07/10/2022 18:09, Bhavesh Mistry wrote: Hi Tomcat Team, We have a unique situation. We wanted to block ALL *OPTIONALS* HTTP m

Re: Tomcat Redirect Port 80 to 443 and Block OPTIONS HTTP Method

> We have a unique situation. We wanted to block ALL *OPTIONALS* HTTP > method > > on port 80 and 443. > > > > We have connector definitions as follows: > > > > > > > port="8080" protocol="HTTP/1.1" &

Re: Tomcat Redirect Port 80 to 443 and Block OPTIONS HTTP Method

On 07/10/2022 18:09, Bhavesh Mistry wrote: Hi Tomcat Team, We have a unique situation. We wanted to block ALL *OPTIONALS* HTTP method on port 80 and 443. We have connector definitions as follows: --> --> and we have an application filter to blo

Tomcat Redirect Port 80 to 443 and Block OPTIONS HTTP Method

Hi Tomcat Team, We have a unique situation. We wanted to block ALL *OPTIONALS* HTTP method on port 80 and 443. We have connector definitions as follows: --> --> and we have an application filter to block and return 405. This works for HTTPS port 443

Re: too many "CLOSE_WAIT" states on Tomcat 80 port and Tomcat does not responding requests to port 80 anymore

> Mark > > > > > > Thank you > > > > On Sun, Jul 10, 2022 at 4:49 AM Mark Thomas wrote: > > > >> On 10/07/2022 05:40, Jason Zhang wrote: > >>> Hello Tomcat Support team, > >>> > >>> The Tomcat is not responding to

Re: too many "CLOSE_WAIT" states on Tomcat 80 port and Tomcat does not responding requests to port 80 anymore

t how Alfresco works or the root cause of the problem you are seeing, anything is possible. Mark Thank you On Sun, Jul 10, 2022 at 4:49 AM Mark Thomas wrote: On 10/07/2022 05:40, Jason Zhang wrote: Hello Tomcat Support team, The Tomcat is not responding to requests to port 80 in our sy

Re: too many "CLOSE_WAIT" states on Tomcat 80 port and Tomcat does not responding requests to port 80 anymore

> On 10/07/2022 05:40, Jason Zhang wrote: > > Hello Tomcat Support team, > > > > The Tomcat is not responding to requests to port 80 in our system, I > would > > like to know: > > 1. If this is an issue with Tomcat or outside the Tomcat > > 2. If it is an issu

Re: too many "CLOSE_WAIT" states on Tomcat 80 port and Tomcat does not responding requests to port 80 anymore

On 10/07/2022 05:40, Jason Zhang wrote: Hello Tomcat Support team, The Tomcat is not responding to requests to port 80 in our system, I would like to know: 1. If this is an issue with Tomcat or outside the Tomcat 2. If it is an issue with Tomcat, how to fix it 3. If it is outside the Tomcat

Re: correct usage of properties to supply database port

> On Mar 12, 2022, at 9:59 AM, Christopher Schultz > wrote: > > Rob, > Chris, Yes I see that. Wasn’t really worried about context at the time of that post. I would argue though that the message is a tad obtuse. I’ll clean up the code generating that context.xml. Luckily it only breaks

Re: correct usage of properties to supply database port

Rob, On 3/11/22 9:13 AM, Rob Sargent wrote: On Mar 11, 2022, at 6:50 AM, Mark H. Wood wrote: On Thu, Mar 10, 2022 at 09:40:48AM -0700, Rob Sargent wrote: About context/context/value: I have this context.xml. Is the value correctly inside the outer Context?

correct usage of properties to supply database port

port On Mar 11, 2022, at 6:50 AM, Mark H. Wood wrote: On Thu, Mar 10, 2022 at 09:40:48AM -0700, Rob Sargent wrote: About context/context/value: I have this context.xml. Is the value correctly inside the outer Context? I don't think yo

Re: correct usage of properties to supply database port

> On Mar 11, 2022, at 8:17 AM, Thomas Hoffmann (Speed4Trade GmbH) > wrote: > >  > >> -Ursprüngliche Nachricht- >> Von: Rob Sargent >> Gesendet: Freitag, 11. März 2022 15:14 >> An: Tomcat Users List >> Betreff: Re: correc

AW: correct usage of properties to supply database port

> -Ursprüngliche Nachricht- > Von: Rob Sargent > Gesendet: Freitag, 11. März 2022 15:14 > An: Tomcat Users List > Betreff: Re: correct usage of properties to supply database port > > > > > On Mar 11, 2022, at 6:50 AM, Mark H. Wood wrote: > > >

Re: correct usage of properties to supply database port

> On Mar 11, 2022, at 6:50 AM, Mark H. Wood wrote: > > On Thu, Mar 10, 2022 at 09:40:48AM -0700, Rob Sargent wrote: >> About context/context/value: I have this context.xml. Is the value >> correctly inside the outer Context? >> >> >> >> > name="jdbc/sgsdb/tbar" >>

Re: correct usage of properties to supply database port

On Thu, Mar 10, 2022 at 09:40:48AM -0700, Rob Sargent wrote: > About context/context/value:  I have this context.xml. Is the value > correctly inside the outer Context? > > > >     name="jdbc/sgsdb/tbar" >   url="jdbc:postgresql://localhost:5432:/tbar" >   d

Re: correct usage of properties to supply database port

I think I see the problem:  and extra colon has snuck in to the url - localhost:5432*":"*/tbar Sorry for the noise. On 3/10/22 09:40, Rob Sargent wrote: Using tomcat 9.0.58 I have a propertiesfile supplied to my embedded tomcat which includes SGSSRVR_databasePort     = 5432 SGSSRVR_d

correct usage of properties to supply database port

/Context] Mar 10, 2022 8:34:32 AM org.apache.catalina.startup.ContextConfig getDefaultWebXmlFragment INFO: No global web.xml found Mar 10, 2022 8:34:33 AM org.postgresql.util.PGPropertyUtil convertPgPortToInt WARNING: JDBC URL invalid port number: Mar 10, 2022 8:34:33 AM

Re: Tomcat not starting up in secondary ip for 8443 port

Dabashish, On 2/9/22 11:55, Debashish Dey (HCL) wrote: We have windows 2019 where tomcat is installed with 8443 port and we have one NIC where 4 ips are configured. We want to start tomcat as autometic startup way with a specific ip and we are getting error port-bind suring autometic startup

AW: Tomcat not starting up in secondary ip for 8443 port

Hello, it sounds like another program is temporary using the port 443 but shuts down after booting. This would explain, that tomcat starts delayed but not automatic, during boot process. Maybe you can check which other programs/services are running during startup (maybe you can disable non

Tomcat not starting up in secondary ip for 8443 port

Hi, We have windows 2019 where tomcat is installed with 8443 port and we have one NIC where 4 ips are configured. We want to start tomcat as autometic startup way with a specific ip and we are getting error port-bind suring autometic startup but we are able to start autometic-delayed or

Re: Connector Port Issue

Chris, > Am 11.08.2021 um 16:40 schrieb Chris Strickland > : > >  > Anyone happen to know where in the server.xml file the attributes go for > clientAuth and sslEnabledProtocols? They goes in "protocols" and "certificateVerification" attributes of SSLHostConfig. Like this:

Re: Connector Port Issue

Anyone happen to know where in the server.xml file the attributes go for clientAuth and sslEnabledProtocols? I'm running Tomcat 10. Seems like I tried putting them under everything (Connector, SSLHostConfig, Certificate) but still get the warning in the logs: failed to set property. Thanks,Chr

Re: Connector Port Issue

Thank you. I will check out the info. chris On Thursday, August 5, 2021, 03:37:54 PM EDT, Peter Kreuser wrote: Chris, > Am 05.08.2021 um 18:32 schrieb Rob Sargent : > >  >>        Caused by: java.lang.IllegalArgumentException: No SSLHostConfig >>element was found with the hostName [

Re: Connector Port Issue

Chris, > Am 05.08.2021 um 18:32 schrieb Rob Sargent : > >  >>Caused by: java.lang.IllegalArgumentException: No SSLHostConfig >> element was found with the hostName [_default_] to match the >> defaultSSLHostConfigName for the connector [https-jsse-nio-9443] >> > The ssl-Options are n

Re: Connector Port Issue

> Caused by: java.lang.IllegalArgumentException: No SSLHostConfig > element was found with the hostName [_default_] to match the > defaultSSLHostConfigName for the connector [https-jsse-nio-9443] > Isn’t that the real issue? --

Connector Port Issue

Trying to figure out why I'm seeing the following errors in the log. I'm sure they are the reason why I cannot connect to my server via a browser on the specified port. Any help is greatly appreciated. Tomcat 10.0.7 is running (x below are intentionally left out): catalina.out 0

Re: Unable to parse forwarded port issue

post request fails with Unable to parse port in forwarded type headers please use forwardheaderfilter with remove only true. Can some one please assist on this. Weird why get is passing and not post This looks like a Spring issue and not a Tomcat one. The message suggests using

Unable to parse forwarded port issue

Hi Team I have been facing issues lately when a spring boot application acts as a proxy (using embedded tomcat 9.4) passes the request from load balancer to the end web server(jetty) However we see that get requests to through without any error but post request fails with Unable to parse port

Re: Problem with protocols, Re: SSL/TLS issue: can we listen on more than one secured port, with different protocols enabled?

On 19/07/2020 13:55, Christopher Schultz wrote: > Mark, > > On 7/18/20 10:01, Mark Thomas wrote: >> On 17/07/2020 21:47, James H. H. Lampert wrote: >>> Running two connectors seems to work just fine, but I'm having >>> trouble getting one of them to only take TLS 1.2 >>> >>> In reply to my query:

Re: Problem with protocols, Re: SSL/TLS issue: can we listen on more than one secured port, with different protocols enabled?

Mark Thomas and Christopher Schultz wrote: You want: sslProtocol="TLS" sslEnabledProtocols="TLSv1.2" And to answer my question above, because that is the way the JSSE API has been written. We should probably just merge these into a single attribute and "do the right thing": 1. If not specif

Re: Problem with protocols, Re: SSL/TLS issue: can we listen on more than one secured port, with different protocols enabled?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 7/18/20 10:01, Mark Thomas wrote: > On 17/07/2020 21:47, James H. H. Lampert wrote: >> Running two connectors seems to work just fine, but I'm having >> trouble getting one of them to only take TLS 1.2 >> >> In reply to my query: >> Gi

Re: request.getLocatHost() Different with port 80 vs mod_jk

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Jerry, On 7/18/20 18:29, Jerry Malcolm wrote: > I'm taking Christopher's advice to remove httpd and mod_jk out of > my process and go straight to Tomcat on port 80. At this point the > only thing I've done is stop the http

request.getLocatHost() Different with port 80 vs mod_jk

I'm taking Christopher's advice to remove httpd and mod_jk out of my process and go straight to Tomcat on port 80.  At this point the only thing I've done is stop the httpd service and change the Connector port to 80.  I'm running on my local machine.  I have

Re: Problem with protocols, Re: SSL/TLS issue: can we listen on more than one secured port, with different protocols enabled?

On 17/07/2020 21:47, James H. H. Lampert wrote: > Running two connectors seems to work just fine, but I'm having trouble > getting one of them to only take TLS 1.2 > > In reply to my query: > >>> Given all this, is it possible to (1) have Tomcat listen on two separate >>> HTTPS ports, and (2) hav

Re: Problem with protocols, Re: SSL/TLS issue: can we listen on more than one secured port, with different protocols enabled?

On 7/17/20 2:36 PM, jonmcalexan...@wellsfargo.com.INVALID wrote: This looks like a cipher, not an alias TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256 As I said, of course it's a cipher. I said up front that the lines were truncated, in order to fit in an email. I can't imagine w

Re: Problem with protocols, Re: SSL/TLS issue: can we listen on more than one secured port, with different protocols enabled?

On 7/17/20 2:36 PM, jonmcalexan...@wellsfargo.com.INVALID wrote: This looks like a cipher, not an alias TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256 It is. The lines are truncated at 72 characters for the email. -- JHHL ---

RE: Problem with protocols, Re: SSL/TLS issue: can we listen on more than one secured port, with different protocols enabled?

3:47 PM To: Tomcat Users List Subject: Problem with protocols, Re: SSL/TLS issue: can we listen on more than one secured port, with different protocols enabled? Running two connectors seems to work just fine, but I'm having trouble getting one of them to only take TLS 1.2 In reply to my

Problem with protocols, Re: SSL/TLS issue: can we listen on more than one secured port, with different protocols enabled?

Running two connectors seems to work just fine, but I'm having trouble getting one of them to only take TLS 1.2 In reply to my query: Given all this, is it possible to (1) have Tomcat listen on two separate HTTPS ports, and (2) have one of the ports require TLS 1.2, but the other accept someth

RE: SSL/TLS issue: can we listen on more than one secured port, with different protocols enabled?

To: users@tomcat.apache.org Subject: Re: SSL/TLS issue: can we listen on more than one secured port, with different protocols enabled? On 17/07/2020 17:55, James H. H. Lampert wrote: > I've got an issue here. > > On the one hand, we have a Tomcat server running on Amazon (in a >

Re: SSL/TLS issue: can we listen on more than one secured port, with different protocols enabled?

curity report from SSLLabs, > telling us that our security rating is capped at "B" because we allow > TLS 1.0 and 1.1. > > BUT, our entire office is on a static IP address, and we already know > how to open a port on our Amazon firewall to only accept traffic from > our of

SSL/TLS issue: can we listen on more than one secured port, with different protocols enabled?

because we allow TLS 1.0 and 1.1. BUT, our entire office is on a static IP address, and we already know how to open a port on our Amazon firewall to only accept traffic from our office IP. Given all this, is it possible to (1) have Tomcat listen on two separate HTTPS ports, and (2) have one

Re: Some questions regarding the TLS1.2 port 443 continuously communicating and too many open threads

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Raghav, On 4/30/20 03:02, Ragavendhiran Bhiman (rabhiman) wrote: > Hello Chris, > > Please see my reply below in line. > > Thanks & Regards, > > Raghav > > On 30/04/20, 9:23 AM, "Christopher Schultz" wrote: > > Raghav, > > On 4/29/20 22:26, Ragave

Re: Some questions regarding the TLS1.2 port 443 continuously communicating and too many open threads

t; Yes you are correct apache tomcat version 8.5.29 being used. >> >> On 29/04/20, 7:22 PM, "Ragavendhiran Bhiman (rabhiman)" >> wrote: >> >> Hi Mark, >> >> We have configured 450 threads for port number 443 with the >>

Re: Some questions regarding the TLS1.2 port 443 continuously communicating and too many open threads

rrect apache tomcat version 8.5.29 being used. >> >> On 29/04/20, 7:22 PM, "Ragavendhiran Bhiman (rabhiman)" >> wrote: >> >> Hi Mark, >> >> We have configured 450 threads for port number 443 with the >> following executer > >

Re: Some questions regarding the TLS1.2 port 443 continuously communicating and too many open threads

iman (rabhiman) wrote: > Yes you are correct apache tomcat version 8.5.29 being used. > > On 29/04/20, 7:22 PM, "Ragavendhiran Bhiman (rabhiman)" wrote: > > Hi Mark, > > We have configured 450 threads for port number 443 with the

Re: Some questions regarding the TLS1.2 port 443 continuously communicating and too many open threads

On 29/04/2020 14:53, Ragavendhiran Bhiman (rabhiman) wrote: > Yes you are correct apache tomcat version 8.5.29 being used. > > On 29/04/20, 7:22 PM, "Ragavendhiran Bhiman (rabhiman)" > wrote: > > Hi Mark, > > We have configured 450 threads for

Re: Some questions regarding the TLS1.2 port 443 continuously communicating and too many open threads

Yes you are correct apache tomcat version 8.5.29 being used. On 29/04/20, 7:22 PM, "Ragavendhiran Bhiman (rabhiman)" wrote: Hi Mark, We have configured 450 threads for port number 443 with the following executer I could see 450 threads open for ser

Re: Some questions regarding the TLS1.2 port 443 continuously communicating and too many open threads

Hi Mark, We have configured 450 threads for port number 443 with the following executer I could see 450 threads open for servicing the clients in one specific setup only what could be the reason? Thanks a lot. Regards, Raghav On 29/04/20, 7:18

Re: Some questions regarding the TLS1.2 port 443 continuously communicating and too many open threads

dor and version being used as well as OS. > Hi, > > I am seeing too many open threads to port number 443 with TLSv1.2, what could > be the primary reason for the same? Open threads? That doesn't make sense. Do you mean open ports, threads (idle, active, both) or something else?

Re: Some questions regarding the TLS1.2 port 443 continuously communicating and too many open threads

Apache version 8.5.29 From: "Ragavendhiran Bhiman (rabhiman)" Date: Wednesday, 29 April 2020 at 6:50 PM To: "users-ow...@tomcat.apache.org" , "users@tomcat.apache.org" Subject: Re: Some questions regarding the TLS1.2 port 443 continuously communicating and too ma

Re: Some questions regarding the TLS1.2 port 443 continuously communicating and too many open threads

Adding tomcat users as well. From: "Ragavendhiran Bhiman (rabhiman)" Date: Wednesday, 29 April 2020 at 6:45 PM To: "users-ow...@tomcat.apache.org" Subject: Some questions regarding the TLS1.2 port 443 continuously communicating and too many open threads Hi, I am seeing t

Re: Configure Tomcat for specific Urls on specific Port

2" >redirectPort="8443" maxHttpHeaderSize="16384"/> > server="" >connectionTimeout="2" >redirectPort="8443" maxHttpHeaderSize="16384"/> > >

Configure Tomcat for specific Urls on specific Port

Hi Team , We are using tomcat in one of our projects and we have tomcat ports 8080 and 8081 opened by the following configurations. Now we want to allow only specific url on each port. For eg urls contaning text /request1 should be allowed to access only on port 8080 and if /request1 is

Re: ajp port chosen at random

On 19/02/2020 11:00, Jonathan Yom-Tov wrote: > hi, > > I'm configuring a two tomcat cluster with session replication and > encountering a strange issue. One of the tomcats appears to choose the AJP > connector port at random. The other tomcat obeys the port directive from >

ajp port chosen at random

hi, I'm configuring a two tomcat cluster with session replication and encountering a strange issue. One of the tomcats appears to choose the AJP connector port at random. The other tomcat obeys the port directive from its connector without a problem. This is doubly strange because the s

Re: Tomcat 8.5 disabling port 80 listening

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Nitin, On 1/29/20 10:49 AM, Nitin Kadam wrote: > I have a tomcat 8.5 server configured in the production > environment. As per requirement, we need to disable all 80 port > listening from the application and only https (443) to b

RE: Tomcat 8.5 disabling port 80 listening

>> -Original Message- >> From: Nitin Kadam >> Sent: Wednesday, January 29, 2020 9:50 AM >> To: Tomcat Users List >> >> Subject: Tomcat 8.5 disabling port 80 listening >> Hi Team, >> I have a tomcat 8.5 server configured in the production

Tomcat 8.5 disabling port 80 listening

Hi Team, I have a tomcat 8.5 server configured in the production environment. As per requirement, we need to disable all 80 port listening from the application and only https (443) to be allowed. I have implemented SSL and the same is working fine. however, still, tomcat is showing listening on

Re: How change tomcat8.exe listening port 0.0.0.0:12345 to a different port

And just for fun, I searched Google for "tcp port 12345" and found this among others : https://www.speedguide.net/port.php?port=12345 On 27.08.2019 16:09, Patrick Heinen wrote: Thank you very much for your prompt and detailed feedback. Unfortunately, there are no such entries in th

RE: How change tomcat8.exe listening port 0.0.0.0:12345 to a different port

this. Thanks again. -Original Message- From: André Warnier (tomcat) [mailto:a...@ice-sa.com] Sent: Dienstag, 27. August 2019 15:43 To: users@tomcat.apache.org Subject: Re: How change tomcat8.exe listening port 0.0.0.0:12345 to a different port Addendum : On 27.08.2019 15:23, André Warnier

Re: How change tomcat8.exe listening port 0.0.0.0:12345 to a different port

Addendum : On 27.08.2019 15:23, André Warnier (tomcat) wrote: On 27.08.2019 14:05, Patrick Heinen wrote: Hi everyone, In our Apache Tomcat 8.5.31 installation, Tomcat8.exe ist listening on TCP port 12345, and we need to change this to a different port number. Unfortunatley, we cannot find a

Re: How change tomcat8.exe listening port 0.0.0.0:12345 to a different port

On 27.08.2019 14:05, Patrick Heinen wrote: Hi everyone, In our Apache Tomcat 8.5.31 installation, Tomcat8.exe ist listening on TCP port 12345, and we need to change this to a different port number. Unfortunatley, we cannot find a way to change this since it is not specified in server.xml or

How change tomcat8.exe listening port 0.0.0.0:12345 to a different port

Hi everyone, In our Apache Tomcat 8.5.31 installation, Tomcat8.exe ist listening on TCP port 12345, and we need to change this to a different port number. Unfortunatley, we cannot find a way to change this since it is not specified in server.xml or Java options. Does anybody know how this

Re: Tomcat 9 & Port 80

pache Tomcat 9.0.21 binary installation. I compiled the JSVC and created a setenv.sh file with some environmental variables. Tested starting Tomcat with daemon.sh and it came up on 8080. Now to get it to work on port 80: Install authbind and configure it o sudo apt install authbind o

Re: Tomcat 9 & Port 80

with daemon.sh and it came up on 8080. Now to get it to work on port 80: Install authbind and configure it o sudo apt install authbind o sudo touch /etc/authbind/byport/80 o sudo chmod 500 /etc/authbind/byport/80 o sudo chown tomcat /etc/authbind/byport/80 (this assumes y

Re: Tomcat 9 & Port 80

t seems that the issue below is more of a question for the >> Ubuntu list, than Tomcat's. >> >> The standard /etc/init.d/tomcat9 startup script included in the >> Ubuntu tomcat9 package, should allow starting tomcat 9 on port 80 >> without any changes to the tomcat

Re: Tomcat 9 & Port 80

list, than Tomcat's. The standard /etc/init.d/tomcat9 startup script included in the Ubuntu tomcat9 package, should allow starting tomcat 9 on port 80 without any changes to the tomcat configuration or scripts (other than setting the Connector to port 80 in server.xml).

Re: Tomcat 9 & Port 80

that the issue below is more of a question for the Ubuntu list, than Tomcat's. The standard /etc/init.d/tomcat9 startup script included in the Ubuntu tomcat9 package, should allow starting tomcat 9 on port 80 without any changes to the tomcat configuration or script

Re: Tomcat 9 & Port 80

Hi. Apologies for breaking conventions of this list and top-posting.. It seems that the issue below is more of a question for the Ubuntu list, than Tomcat's. The standard /etc/init.d/tomcat9 startup script included in the Ubuntu tomcat9 package, should allow starting tomcat 9 on po

Tomcat 9 & Port 80

Hello, I have Tomcat 9.0.21 installed (binary distribution) on an Ubuntu 16.04 server. My Java version is OpenJDK 11.0.4. I have the JSVC built and run the dameon.sh script to start and stop Tomcat via a systemd script. Everything works great, but now I need to run it on port 80 & 443. On

Re: current best practices for Tomcat with SSL on port 443

t;> Encrypt with Tomcat. > > > OK, I guess I didn't figure in the part about adding/configuring > the connector. But still there are a few things I have doubts > about, just looking over the document quickly: > > * There's still the issue about listening on low

Re: current best practices for Tomcat with SSL on port 443

there are a few things I have doubts about, just looking over the document quickly: * There's still the issue about listening on lower port numbers. From the presentation, it looks like I would need to teach myself about iptables. I wonder if students (and I) would find mucking

Re: current best practices for Tomcat with SSL on port 443

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Garret, On 2/7/19 12:22, Garret Wilson wrote: > On 2/7/2019 3:13 PM, Christopher Schultz wrote: >> … Have a look at this presentation: >> https://people.apache.org/~schultz/ApacheCon%20NA%202018/Let's%20Encr ypt >> >> %20Apache%20Tomcat.pdf > > T

  1   2   3   4   5   6   7   8   9   10   >