[GitHub] tomcat issue #33: Clear up confusion about mbeans-descriptors.xml in docs; f...

Github user violetagg commented on the issue: https://github.com/apache/tomcat/pull/33 Hi, I have one comment about renaming the page. If there are bookmarks to that page with this change we will break these bookmarks. Otherwise the change is OK. Wdyt?

Early Access builds of JDK 8u112 b04, JDK 9 b130 are available on java.net

Hi Mark, There are two fixes to bugs reported by you in b130, can you confirm fixes ? Early Access b130 for JDK 9 is available on java.net, summary of changes are listed here . 8156824 core-libs

Re: Early Access builds of JDK 8u112 b04, JDK 9 b130 are available on java.net

> On 8 Aug 2016, at 08:51, Rory O'Donnell wrote: > > Hi Mark, > > There are two fixes to bugs reported by you in b130, can you confirm fixes ? > > Early Access b130 for JDK 9 is available on > java.net, summary of changes are listed here >

Re: Early Access builds of JDK 8u112 b03, JDK 9 b128 are available on java.net

On 22/07/2016 09:43, Rory O'Donnell wrote: > > Hi Mark, > > Fix for JDK-8158237: JVMTI hides critical debug information for memory > leak tracing is in b126. > Can you confirm fix ? Rory, Sorry for the delay in getting back to you. It has been a busy month. I have just downloaded Java 9, b129

Re: Early Access builds of JDK 8u112 b03, JDK 9 b128 are available on java.net

Thanks for confirming fixes Mark. I will pass on the kudos! Rgds,Rory On 08/08/2016 15:08, Mark Thomas wrote: On 22/07/2016 09:43, Rory O'Donnell wrote: Hi Mark, Fix for JDK-8158237: JVMTI hides critical debug information for memory leak tracing is in b126. Can you confirm fix ? Rory, So

Re: Early Access builds of JDK 8u112 b04, JDK 9 b130 are available on java.net

On 08/08/2016 11:20, Chris Hegarty wrote: > >> On 8 Aug 2016, at 08:51, Rory O'Donnell wrote: >> >> Hi Mark, >> >> There are two fixes to bugs reported by you in b130, can you confirm fixes ? >> >> Early Access b130 for JDK 9 is available >> on java.net, summar

svn commit: r1755511 - in /tomcat/trunk: java/org/apache/catalina/core/JreMemoryLeakPreventionListener.java webapps/docs/changelog.xml

Author: markt Date: Mon Aug 8 15:19:28 2016 New Revision: 1755511 URL: http://svn.apache.org/viewvc?rev=1755511&view=rev Log: Add links to JRE bugs. Disable protection when running on a JRE that is known to be fixed. Modified: tomcat/trunk/java/org/apache/catalina/core/JreMemoryLeakPreventi

Re: Early Access builds of JDK 8u112 b04, JDK 9 b130 are available on java.net

On 08/08/2016 16:09, Mark Thomas wrote: > I need to review the remaining things in JreMemoryLeakPreventionListener > to see if any of them need to be raised as bugs. I've now done this and I only found one issue that I think is reasonable to raise as a JDK issue. JarURLConnection needs to disable

Re: Should the RequestDispatcher decode the provided path?

On Thu, 2016-07-14 at 21:11 +0200, Mark Thomas wrote: > > The only thing it might break was if someone tried to use a URL > > containing a % sign that wasn't encoded: > > > > String target = "/foo/bar?percent=%&hash=#"; > > request.getRequestDispatcher(target).forward(request, response); > > > >

Re: Should the RequestDispatcher decode the provided path?

On 08/08/2016 21:25, Wang, Andy wrote: > On Thu, 2016-07-14 at 21:11 +0200, Mark Thomas wrote: >>> The only thing it might break was if someone tried to use a URL >>> containing a % sign that wasn't encoded: >>> >>> String target = "/foo/bar?percent=%&hash=#"; >>> request.getRequestDispatcher(targe