https://bz.apache.org/bugzilla/show_bug.cgi?id=62657
Bug ID: 62657
Summary: Protocol handler destroy failed
Product: Tomcat 9
Version: 9.0.11
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Compo
Thanks Mark for confirming fix.
Rgds,Rory
On 24/08/2018 18:19, Mark Thomas wrote:
On 24/08/18 10:30, Rory O'Donnell wrote:
Hi Mark,
*JDK 11 build 28 is our first JDK 11 Release Candidate [1]
*
* JDK 11 Early Access build 28 is available at : - jdk.java.net/11/
*FOSS fixes in recent buil
Am 24.08.2018 um 18:56 schrieb Mark Thomas:
Tag:
http://svn.apache.org/viewvc/tomcat/jk/tags/JK_1_2_44/
Source:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-connectors/jk/
This is a maintenance release with a handful of bug fixes and some
clean-up. It also includes Windows binaries for
https://bz.apache.org/bugzilla/show_bug.cgi?id=62657
Mark Thomas changed:
What|Removed |Added
OS||Mac OS X 10.13
Hardware|PC
https://bz.apache.org/bugzilla/show_bug.cgi?id=62657
Mark Thomas changed:
What|Removed |Added
OS||All
Status|NEW
On 31/05/18 19:16, Igal Sapir wrote:
> On 5/31/2018 3:00 AM, Mark Thomas wrote:
>> Hi,
>>
>> The next issue to resolve for the Git migration is developer process.
>>
>> Note that this does not cover branch names, merge strategy etc. This is
>> issue is about the options available for developers to
We refer to svn in various places. Main web site, docs, BUILDING.txt etc.
The issue is when do we update the various docs. The main website we can
update whenever, but the version specific docs normally only get updated
when we do a release.
My suggested solution is to do the migration and once w
Author: markt
Date: Mon Aug 27 20:50:05 2018
New Revision: 1839373
URL: http://svn.apache.org/viewvc?rev=1839373&view=rev
Log:
Update version number for next dev cycle
Modified:
tomcat/jk/trunk/native/STATUS.txt
tomcat/jk/trunk/native/common/jk_version.h
tomcat/jk/trunk/native/configu
https://bz.apache.org/bugzilla/show_bug.cgi?id=62633
--- Comment #3 from saiya <1005136...@qq.com> ---
(In reply to Mark Thomas from comment #1)
> The provided sample application does not demonstrate a memory leak in Apache
> Tomcat. WsSession objects are retained while the session is open and
> r
https://bz.apache.org/bugzilla/show_bug.cgi?id=62657
--- Comment #3 from quaff ---
Finally I find it cause by VPN software, but I don't know why tomcat8.0 is not
affected.
--
You are receiving this mail because:
You are the assignee for the bug.
-
10 matches
Mail list logo