release plan for tomcat 7.x for java9

hello good folks! I see that the endorsed directory related problem in tomcat 7.x for running in java 9 has been fixed by the patch by rjung in https://github.com/apache/tomcat70/commit/e7ae8664922cd54fabe847527bad614bcd5ce301#diff-da184cf589a25174c11dc3f4dbaeb0b4 Do we know the approximate

Re: TLD scanning performance question

And haveged works GREAT! Thanks Markus. On Wednesday, October 25, 2017 10:53 AM, "i...@flyingfischer.ch" wrote: > > Yes, it's the SecureRandom initialization that is killing you. Being a > virtual server, it likely has no direct source of true randomness so >

Re: TLD scanning performance question

> > Yes, it's the SecureRandom initialization that is killing you. Being a > virtual server, it likely has no direct source of true randomness so > it needs to pull from whatever the hypervisor is willing to provide. > > You'll need to ask your virtualization vendor for how to get access to >

Re: TLD scanning performance question

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Ray, On 10/25/17 9:08 AM, Ray Holme wrote: > I asked this question before (differently) and got some answers but > now I think I understand what is really happening. I just want to > confirm that I have finally understood what is happening. Given

Re: The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Karen, On 10/20/17 1:11 AM, Karen Goh wrote: > Today I receive an error message that I have never come across. > > "Https status 404 - not found " "The origin server did not find a > current representation for the target resource or is not willing

TLD scanning performance question

I asked this question before (differently) and got some answers but now I think I understand what is really happening. I just want to confirm that I have finally understood what is happening. Given two Linux boxes running the same application, one is much slower starting  (think that  "slower"

Re: Tomcat 8.0.33 Crashed

Still can you help me explain little more about the root cause? That will help me to explain it to customer and setup a test environment for future. Thanks and Regards Atanu Pal E2Infosystems - Chennai On Wed, Oct 25, 2017 at 5:36 PM, Atanu Pal wrote: > Thanks Mark,

Re: Tomcat 8.0.33 Crashed

Thanks Mark, I was inclining to the same, I will try 8.0.47 first before jumping to 8.5.x, will let you know what happens. Thanks and Regards Atanu Pal E2Infosystems - Chennai On Wed, Oct 25, 2017 at 5:30 PM, Mark Thomas wrote: > On 25/10/17 11:43, Atanu Pal wrote: >> Hi, >>

Re: Tomcat 8.0.33 Crashed

On 25/10/17 11:43, Atanu Pal wrote: > Hi, > > We have application deployed on tomcat & its working good for most of > the customer, but recently we installed it for two customers on a > virtual machine & it looks like tomcat is crashing after few days of > successful run. > > Machine Details: >

Tomcat 8.0.33 Crashed

Hi, We have application deployed on tomcat & its working good for most of the customer, but recently we installed it for two customers on a virtual machine & it looks like tomcat is crashing after few days of successful run. Machine Details: - It is a Virtual Machine - Windows Server 2012 R2 -

Re: Default response charset

Thanks a lot Mark! On Wed, Oct 25, 2017 at 12:51 PM, Mark Thomas wrote: > On 25/10/17 10:23, Mark Thomas wrote: > > On 24/10/17 07:36, Lazar Kirchev wrote: > >> Hello, > >> > >> Change http://svn.apache.org/viewvc?view=revision=1801052 > tries, > >> in case no charset is

Re: Default response charset

On 25/10/17 10:23, Mark Thomas wrote: > On 24/10/17 07:36, Lazar Kirchev wrote: >> Hello, >> >> Change http://svn.apache.org/viewvc?view=revision=1801052 tries, >> in case no charset is specified for the response, to determine a default >> one based on the content language if such is present. For

Re: Default response charset

On 24/10/17 07:36, Lazar Kirchev wrote: > Hello, > > Change http://svn.apache.org/viewvc?view=revision=1801052 tries, > in case no charset is specified for the response, to determine a default > one based on the content language if such is present. For en and fr > languages the ISO-8859-1 charset

Re: At a loss!

On 24/10/17 12:23, Courtney Meade wrote: > tomcat-connectors-1.2.42-windows-x86_64-iis.zip Good. That should be the correct version of the DLL since Windows 2012 is only available in 64 bit. The error you are seeing is typically seen when there is a configuration issue of some kind. The Tomcat