On 18/11/2019 14:14, Mark Thomas wrote:
> On 18/11/2019 12:06, M. Manna wrote:
>> Mark and others,
>>
>> On Mon, 18 Nov 2019 at 12:01, Mark Thomas wrote:
>>
>>> OK, it looks like I can reproduce this.
>>>
>>> Steps to reproduce:
>>>
>>> - Windows 2016 Server fully patched
>>> - Java 1.8.0u144
>>>
On 11/17/2019 9:01 AM, Mark Thomas wrote:
On 16/11/2019 22:08, Adam Rauch wrote:
While testing 8.5.48, we now see NullPointerExceptions when our
ImageServlet code attempts to forward a request to a new location. In
8.5.47, the code works fine.
Thanks for reporting this. I can see what the pro
On 18/11/2019 12:06, M. Manna wrote:
> Mark and others,
>
> On Mon, 18 Nov 2019 at 12:01, Mark Thomas wrote:
>
>> OK, it looks like I can reproduce this.
>>
>> Steps to reproduce:
>>
>> - Windows 2016 Server fully patched
>> - Java 1.8.0u144
>> - Install Tomcat 8.5.45 from windows installer
>> -
-Original Message-
From: Mark Thomas
Sent: Monday, November 18, 2019 3:41 AM
To: users@tomcat.apache.org
Subject: Re: Tomcat 8.5.48: NullPointerException in
ApplicationMapping.getHttpServletMapping()
On 18/11/2019 04:36, jonmcalexan...@wellsfargo.com.INVALID wrote:
> Oh yippee. Another
Mark and others,
On Mon, 18 Nov 2019 at 12:01, Mark Thomas wrote:
> OK, it looks like I can reproduce this.
>
> Steps to reproduce:
>
> - Windows 2016 Server fully patched
> - Java 1.8.0u144
> - Install Tomcat 8.5.45 from windows installer
> - Add tcnative-1.dll (64-bit) from Tomcat Native 1.2.2
OK, it looks like I can reproduce this.
Steps to reproduce:
- Windows 2016 Server fully patched
- Java 1.8.0u144
- Install Tomcat 8.5.45 from windows installer
- Add tcnative-1.dll (64-bit) from Tomcat Native 1.2.23
- Modify server.xml to use Http11AprProtocol on port 8080
- Make a single request
On 16/11/2019 09:29, Alexander Norz wrote:
> Am 15.11.2019 22:23, schrieb Mark Thomas:
>
> That is the point:
>
>> Because Oracle changed the directory layout and names of the standard
>> registry entries and the installer probably hasn't been updated to take
>> account of that yet.
>
> The envi
On 18/11/2019 04:36, jonmcalexan...@wellsfargo.com.INVALID wrote:
> Oh yippee. Another release. :-D
I'm not sure how to take that. My impression is that you think another
release is a bad thing. My expectation was that regular releases would
be viewed as a good thing. I apologise if I have misint