Resending with correct dates. Apologies for the noise.
The Apache Tomcat team announces that support for Apache Tomcat 8.0.x
will end on 30 June 2018.
This means that after 30 June 2018:
- releases from the 8.0.x branch are highly unlikely
- bugs affecting only the 8.0.x branch will not be addres
On 30/06/17 22:47, Bob Hall wrote:
> On Friday, June 30, 2017 2:32 PM, Mark Thomas wrote:
>
>
>
> The Apache Tomcat team announces that support for Apache Tomcat 8.0.xwill end
> on 30 June 2018.
> This means that after 30 June 2018:- releases from the 8.0.x branch are
> highly unlikely- bug
On Friday, June 30, 2017 2:32 PM, Mark Thomas wrote:
The Apache Tomcat team announces that support for Apache Tomcat 8.0.xwill end
on 30 June 2018.
This means that after 30 June 2018:- releases from the 8.0.x branch are highly
unlikely- bugs affecting only the 8.0.x branch will not be addre
The Apache Tomcat team announces that support for Apache Tomcat 8.0.x
will end on 30 June 2018.
This means that after 30 June 2018:
- releases from the 8.0.x branch are highly unlikely
- bugs affecting only the 8.0.x branch will not be addressed
- security vulnerability reports will not be checked
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Todd,
On 6/30/17 1:30 PM, Todd wrote:
> Christopher Schultz-2 wrote
>> Yup: if you use iptables (ipchains hasn't been used in ...
>> decades?) to do port-redirection, then you are in fact hitting
>> Tomcat / JVM (essentially) directly.
>
> Yes - ip
Todd
>> Peter Kreuser wrote
>>>
>>> Can you provide a clean configuration that exhibits this behavior?
>>>
>>> What are you using to test the effective configuration?
>>
>> Another question: are you sure that you hit the Connector that you
>> configure? Tomcat should be reasonably configured in
Christopher Schultz-2 wrote
> Yup: if you use iptables (ipchains hasn't been used in ... decades?)
> to do port-redirection, then you are in fact hitting Tomcat / JVM
> (essentially) directly.
Yes - iptables, sorry brain fart.
Christopher Schultz-2 wrote
> Can you confirm whether or not you a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Frank,
On 6/30/17 8:43 AM, Frank Taffelt wrote:
> Hi all,
>
> while playing with some ssl setups i stumbled upon the following
> behaviour that seems like bug to me ? As long as all keyentries in
> a keystore have the same password all is fine. Usi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Todd,
On 6/30/17 10:21 AM, Todd wrote:
> Peter Kreuser wrote
>>>
>>> Can you provide a clean configuration that exhibits this
>>> behavior?
>>>
>>> What are you using to test the effective configuration?
>>
>> Another question: are you sure that
Thanks & Regards
Subhro Paul
Tata Consultancy Services
Cell:- +919051415167
Mailto: subhro.p...@tcs.com
Website: http://www.tcs.com
Experience certainty. IT Services
Business Solutions
Consulting
-Nir
Hi Subhro,
tomcat document has the all the info you are looking for.
https://tomcat.apache.org/tomcat-7.0-doc/RUNNING.txt
https://tomcat.apache.org/tomcat-8.0-doc/RUNNING.txt
look for "Advanced Configuration - Multiple Tomcat Instances" in that page.
thanks
Niranjan
On Fri, Jun 30, 2017 at 11:
-Christopher Schultz wrote: -
To: users@tomcat.apache.org
From: Christopher Schultz
Date: 06/29/2017 12:35PM
Subject: Re: Tomcat managed server
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Subhro,
On 6/29/17 11:57 AM, Subhro Paul wrote:
> Can you tell me if we can create manged serv
Peter Kreuser wrote
>>
>> Can you provide a clean configuration that exhibits this behavior?
>>
>> What are you using to test the effective configuration?
>
> Another question: are you sure that you hit the Connector that you
> configure? Tomcat should be reasonably configured in defaults with a
Hi all,
while playing with some ssl setups i stumbled upon the following behaviour that
seems like bug to me ?
As long as all keyentries in a keystore have the same password all is fine.
Using entries with different password tomcat doesnt startup.
For testing:
At first create 2 different keysto
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ivan,
On 6/29/17 9:32 PM, Yin, Ivan wrote:
> I am using Tomcat7 and have deployed a web server on it.
>
> Currently the client side is running into the error
> “*java.net.SocketTimeoutException: Read timed out*” after running
> the web service fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 6/29/17 5:22 PM, Caldarale, Charles R wrote:
>> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
>> Subject: Re: RemoteEndpoint.Async sendText blocking
>
>> When the BIO connector is in use, you end up with weird things
>> like
16 matches
Mail list logo
