On 29/01/2014 21:03, Konstantin Kolinko wrote:
> 2014-01-29 Mark Thomas :
>> The proposed Apache Tomcat 8.0.0 release is now available for voting.
>>
>> (...)
>>
>> It can be obtained from:
>> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.0.0/
>> The Maven staging repo is:
>> https://re
2014-01-29 Mark Thomas :
> The proposed Apache Tomcat 8.0.0 release is now available for voting.
>
>(...)
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.0.0/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1
On 29/01/2014 14:32, Rainer Jung wrote:
> I'm seeing consistent unit test failures in TestAsyncContextImpl when
> using APR:
I can reproduce these and have hopefully found a fix. This is a serious
enough regression (async timeouts are broken in some cases) to justify
dropping 8.0.0 and tagging 8.0
I've reproduced this issue with Chrome 32.0.1700.102 and Chrome canary
34.0.1811.0.
Chrome 32 is already mainstream anyway (thanks evergreen browsers):
http://clicky.com/marketshare/global/web-browsers/google-chrome/
--
Brian Clozel
On Wed, Jan 29, 2014 at 4:38 PM, Yoav Shapira wrote:
> On We
On Wed, Jan 29, 2014 at 9:55 AM, Rossen Stoyanchev
wrote:
> I can confirm that the issue with the empty Sec-WebSocket-Protocol header
> also affects Chrome 31.0.1650.63.
I haven't tested 8.0.0 myself yet, but if it's broken on Chrome 31,
that's a far bigger problem than Chrome 32:
http://www.netm
I can confirm that the issue with the empty Sec-WebSocket-Protocol header
also affects Chrome 31.0.1650.63.
The actual issue appears as an "Invalid UTF-8 sequence in header value"
message in the Chrome dev tool. Although I had read what Martin reported
for Chrome 32, I couldn't confirm it's the sa
I'm seeing consistent unit test failures in TestAsyncContextImpl when
using APR:
Testcase: testDispatchErrorWithThreadSingleThenComplete took 5.171 sec
Testcase: testDispatchErrorSingleThenComplete took 2.226 sec
Testcase: testTimeoutListenerCompleteNonAsyncDispatch took 2.257 sec
FAILED
U
On Wed, Jan 29, 2014 at 12:37 PM, Mark Thomas wrote:
> On 29/01/2014 10:11, Martin Grigorov wrote:
> > Hi,
> >
> > Broken - do not release.
> >
> > It seems WebSocket support is broken for Google Chrome 32+.
> >
> > I tested Apache Wicket integration and it failed with:
> > WebSocket connection t
On 29/01/2014 10:11, Martin Grigorov wrote:
> Hi,
>
> Broken - do not release.
>
> It seems WebSocket support is broken for Google Chrome 32+.
>
> I tested Apache Wicket integration and it failed with:
> WebSocket connection to
> 'ws://localhost:8080/ws/wicket/websocket?pageId=0&wicket-ajax-base
2014-01-28 Mark Thomas
> The proposed Apache Tomcat 8.0.0 release is now available for voting.
>
> This is the first non-RC release so I am leaving all the stability
> options open to get an idea of where folks think we currently stand.
>
> The main changes since RC10 are:
> - Fix broken sendfile
Hi,
Broken - do not release.
It seems WebSocket support is broken for Google Chrome 32+.
I tested Apache Wicket integration and it failed with:
WebSocket connection to
'ws://localhost:8080/ws/wicket/websocket?pageId=0&wicket-ajax-baseurl=behavior?0'
failed: Invalid UTF-8 sequence in header value
Good to know.
We're still using Tomcat 6 to host Jira and Confluence and I wasn't
aware Tomcat 7 and soon Tomcat 8 could be used.
Thanks for the clue.
I'll test Tomcat 8 on a bunch of common CI apps and will told you.
Cheers
2014-01-29 Mark Thomas :
> On 28/01/2014 20:28, Mark Thomas wrote:
>>
On 28/01/2014 20:28, Mark Thomas wrote:
> The proposed Apache Tomcat 8.0.0 release is now available for voting.
FYI, the production ASF Jira instance is now running on Tomcat 8.0.0. It
is early days (more like minutes than days) and I have already had to
work around one Jira bug [1]. Apart from th
The proposed Apache Tomcat 8.0.0 release is now available for voting.
This is the first non-RC release so I am leaving all the stability
options open to get an idea of where folks think we currently stand.
The main changes since RC10 are:
- Fix broken sendfile support in NIO
- Add a readOnly opti
On 24/12/2013 23:42, Rainer Jung wrote:
> On 19.12.2013 19:38, Mark Thomas wrote:
>> The proposed Apache Tomcat 8.0.0 release candidate 10 is now available
>> for voting.
As always, many thanks for the detailed review.
> - One special observation in unit tests: Test
> org.apache.catalina.core.T
On 19.12.2013 19:38, Mark Thomas wrote:
> The proposed Apache Tomcat 8.0.0 release candidate 10 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC5 are:
> - Better handling of generic types i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/12/2013 17:35, Christopher Schultz wrote:
> On 12/23/13, 6:31 AM, Konstantin Kolinko wrote:
>> You cannot build a Windows Installer on an Unix system without
>> wine. (The installer is built by NSIS which is a Windows
>> executable).
>
> Does t
2013/12/23 Christopher Schultz :
> Konstantin,
>
> On 12/23/13, 6:31 AM, Konstantin Kolinko wrote:
>> 2013/12/23 Andrew Carr :
>>> Wine not found?? im on a headless server, what did i do wrong? See
>>> error below...
>>>
>>> Clean setup to test:
>>>
>>> Fresh VM with Ubuntu 13.10 64 bit server
>>
Konstantin,
On 12/23/13, 6:31 AM, Konstantin Kolinko wrote:
> 2013/12/23 Andrew Carr :
>> Wine not found?? im on a headless server, what did i do wrong? See
>> error below...
>>
>> Clean setup to test:
>>
>> Fresh VM with Ubuntu 13.10 64 bit server
>> Apache Ant(TM) version 1.9.2 compiled on Jul
Thank you for the clarification Mark. That all makes sense.
On Mon, Dec 23, 2013 at 10:08 AM, Mark Thomas wrote:
> On 23/12/2013 14:54, Andrew Carr wrote:
>> Hello Konstantin,
>>
>> Thank you very much for the reply. I understand what Wine is and why
>> you can't build the installer without it.
On 23/12/2013 14:54, Andrew Carr wrote:
> Hello Konstantin,
>
> Thank you very much for the reply. I understand what Wine is and why
> you can't build the installer without it. What I don't understand is
> why the configuration tries to build it by default.
A release build needs to build the Wi
Hello Konstantin,
Thank you very much for the reply. I understand what Wine is and why
you can't build the installer without it. What I don't understand is
why the configuration tries to build it by default. Wine is not a
prerequesite in the documentation. Maybe the default build.properties
sh
2013/12/23 Andrew Carr :
> Wine not found?? im on a headless server, what did i do wrong? See
> error below...
>
> Clean setup to test:
>
> Fresh VM with Ubuntu 13.10 64 bit server
> Apache Ant(TM) version 1.9.2 compiled on July 14 2013
> OpenJDK Runtime Environment (IcedTea 2.3.12) (7u25-2.3.12-
My aPologIzes, While ThE build floundered with a fail message, the
output folder dist was intact. Ran some tests and all appears good.
Still the build failure thingy threw me off.
Flip flopping on my vote =)
> [] Broken - do not release
> [X] Alpha - go ahead and release as 8.0.0-RC10 alpha
O
Wine not found?? im on a headless server, what did i do wrong? See
error below...
Clean setup to test:
Fresh VM with Ubuntu 13.10 64 bit server
Apache Ant(TM) version 1.9.2 compiled on July 14 2013
OpenJDK Runtime Environment (IcedTea 2.3.12) (7u25-2.3.12-4ubuntu3)
fresh checkout of 8_0_0RC10
2013/12/19 Mark Thomas
>
> The proposed Apache Tomcat 8.0.0 release candidate 10 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC5 are:
> - Better handling of generic types in the WebSocket
On Thu, Dec 19, 2013 at 1:38 PM, Mark Thomas wrote:
> The proposed Apache Tomcat 8.0.0 release candidate 10 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC5 are:
> - Better handling of gen
2013/12/19 Mark Thomas
> The proposed 8.0.0-RC10 release is:
> [ ] Broken - do not release
> [X] Alpha - go ahead and release as 8.0.0-RC10 alpha
>
> Rémy
On 20/12/2013 12:36, Rainer Jung wrote:
> Can you please add the signature files for
> apache-tomcat-8.0.0-RC10.tar.gz and apache-tomcat-8.0.0-RC10.zip. The
> other signature files are present, but not for those two files.
Done. No idea how they got missed. I'll keep an eye on the next release.
M
Can you please add the signature files for
apache-tomcat-8.0.0-RC10.tar.gz and apache-tomcat-8.0.0-RC10.zip. The
other signature files are present, but not for those two files.
Thanks!
Rainer
-
To unsubscribe, e-mail: dev-unsubs
On 2013-12-19 1:38 PM, Mark Thomas wrote:
The proposed 8.0.0-RC10 release is:
[ ] Broken - do not release
[X] Alpha - go ahead and release as 8.0.0-RC10 alpha
Tested jsr356 & AsyncContext with Atmosphere, no issue.
-- Jeanfrancois
Mark
---
On 20/12/2013 01:40, Andrew Carr wrote:
> On Thu, Dec 19, 2013 at 3:04 PM, sebb wrote:
>> On 19 December 2013 18:38, Mark Thomas wrote:
>>> The proposed Apache Tomcat 8.0.0 release candidate 10 is now available
>>> for voting.
>>>
>>> Given this is a release candidate I am working on the basis th
On Thu, Dec 19, 2013 at 3:04 PM, sebb wrote:
> On 19 December 2013 18:38, Mark Thomas wrote:
>> The proposed Apache Tomcat 8.0.0 release candidate 10 is now available
>> for voting.
>>
>> Given this is a release candidate I am working on the basis that it is
>> equivalent to an alpha. The main ch
On 19 December 2013 18:38, Mark Thomas wrote:
> The proposed Apache Tomcat 8.0.0 release candidate 10 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC5 are:
> - Better handling of generic t
Mark,
2013/12/19 Mark Thomas
>
> The proposed Apache Tomcat 8.0.0 release candidate 10 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC5 are:
> - Better handling of generic types in the W
On 19/12/2013 18:38, Mark Thomas wrote:
> The proposed Apache Tomcat 8.0.0 release candidate 10 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC5 are:
> - Better handling of generic types i
The proposed Apache Tomcat 8.0.0 release candidate 10 is now available
for voting.
Given this is a release candidate I am working on the basis that it is
equivalent to an alpha. The main changes since RC5 are:
- Better handling of generic types in the WebSocket 1.0 implementation
- Refactor resour
On 18/12/2013 14:51, Jeanfrancois Arcand wrote:
>
> On 2013-12-17 7:59 PM, Mark Thomas wrote:
>>
>> The proposed 8.0.0-RC9 release is:
>> [X] Broken - do not release
>> [ ] Alpha - go ahead and release as 8.0.0-RC9 alpha
> Atmosphere stopped working with 8.0.0-RC9. With all previous RC from 1
> to
On 2013-12-17 7:59 PM, Mark Thomas wrote:
The proposed 8.0.0-RC9 release is:
[X] Broken - do not release
[ ] Alpha - go ahead and release as 8.0.0-RC9 alpha
Atmosphere stopped working with 8.0.0-RC9. With all previous RC from 1
to 7 it worked (didn't test 8) and websockets properly handled for
On Dec 17, 2013, at 7:59 PM, Mark Thomas wrote:
> The proposed Apache Tomcat 8.0.0 release candidate 9 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC5 are:
> - Better handling of generi
On 18/12/2013 00:59, Mark Thomas wrote:
> The proposed Apache Tomcat 8.0.0 release candidate 9 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC5 are:
> - Better handling of generic types in
2013/12/18 Mark Thomas
> The proposed Apache Tomcat 8.0.0 release candidate 9 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC5 are:
> - Better handling of generic types in the WebSocket 1
The proposed Apache Tomcat 8.0.0 release candidate 9 is now available
for voting.
Given this is a release candidate I am working on the basis that it is
equivalent to an alpha. The main changes since RC5 are:
- Better handling of generic types in the WebSocket 1.0 implementation
- Refactor resourc
On 17/12/2013 14:27, Daniel Mikusa wrote:
> On Dec 17, 2013, at 6:32 AM, Mark Thomas wrote:
>
>> The proposed Apache Tomcat 8.0.0 release candidate 8 is now available
>> for voting.
>>
>> Given this is a release candidate I am working on the basis that it is
>> equivalent to an alpha. The main ch
On Dec 17, 2013, at 6:32 AM, Mark Thomas wrote:
> The proposed Apache Tomcat 8.0.0 release candidate 8 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC5 are:
> - Better handling of generi
The proposed Apache Tomcat 8.0.0 release candidate 8 is now available
for voting.
Given this is a release candidate I am working on the basis that it is
equivalent to an alpha. The main changes since RC5 are:
- Better handling of generic types in the WebSocket 1.0 implementation
- Refactor resourc
Hi Mark,
> -Original Message-
> From: Mark Thomas [mailto:ma...@apache.org]
> Sent: Monday, December 16, 2013 3:44 PM
> To: Tomcat Developers List
> Subject: Re: [VOTE] Release Apache Tomcat 8.0.0-RC7
>
> On 16/12/2013 14:07, Mark Thomas wrote:
> > On 14/12/201
On 16/12/2013 14:07, Mark Thomas wrote:
> On 14/12/2013 15:37, Konstantin Preißer wrote:
>
>> If more info is needed to debug the problem, please let me know.
>
> No more info needed at the moment.
>
> I can re-create the problem.
The additional issues I thought I was seeing were user error rat
On 14/12/2013 15:37, Konstantin Preißer wrote:
> If more info is needed to debug the problem, please let me know.
No more info needed at the moment.
I can re-create the problem.
The issues appear to be related to the changes I made to support
non-blocking IO with AJP so they should be limited t
> -Original Message-
> From: Konstantin Preißer [mailto:kpreis...@apache.org]
> Sent: Saturday, December 14, 2013 1:53 PM
> To: 'Tomcat Developers List'
> Subject: RE: [VOTE] Release Apache Tomcat 8.0.0-RC7
>
> Hi Mark,
>
> > -Original Messa
Hi Mark,
> -Original Message-
> From: Mark Thomas [mailto:ma...@apache.org]
> Sent: Thursday, December 12, 2013 12:28 AM
> > The proposed 8.0.0-RC7 release is:
> > [ ] Broken - do not release
> > [ ] Alpha - go ahead and release as 8.0.0-RC7 alpha
While the issue with large static file
2013/12/13 Rémy Maucherat
>
> 2013/12/13 Violeta Georgieva
>
> > Here [1] is the test
> >
> > [1] https://www.dropbox.com/s/3zd106lpqfb3ytv/test.zip
> >
>
> Fixed. I didn't add the test yet since I suppose adding a binary should be
> avoided.
Thanks it is working now.
2013/12/13 Violeta Georgieva
> Here [1] is the test
>
> [1] https://www.dropbox.com/s/3zd106lpqfb3ytv/test.zip
>
Fixed. I didn't add the test yet since I suppose adding a binary should be
avoided.
Rémy
2013/12/13 Rémy Maucherat
>
> 2013/12/13 Violeta Georgieva
>
> > Unfortunately with that fix I'm receiving FNF:
> >
> > java.io.FileNotFoundException: /META-INF/tags/my.tag
> >
> >
org.apache.jasper.servlet.JspServletWrapper.loadTagFile(JspServletWrapper.java:235)
> >
> >
org.apache.jasper.compil
2013/12/13 Violeta Georgieva
> Unfortunately with that fix I'm receiving FNF:
>
> java.io.FileNotFoundException: /META-INF/tags/my.tag
>
> org.apache.jasper.servlet.JspServletWrapper.loadTagFile(JspServletWrapper.java:235)
>
> org.apache.jasper.compiler.TagFileProcessor.loadTagFile(TagFileProcess
2013/12/13 Rémy Maucherat
>
> 2013/12/13 Violeta Georgieva
>
> > I found another issue:
> > If a tag file is placed in a jar file in WEB-INF/lib and then is used,
the
> > The change in the code is introduced with r1541960
> >
> > Besides that the message is wrong because we check only for WEB-INF
On 13/12/2013 14:35, Rémy Maucherat wrote:
> 2013/12/13 Violeta Georgieva
>
>> I found another issue:
>> If a tag file is placed in a jar file in WEB-INF/lib and then is used, the
>> The change in the code is introduced with r1541960
>>
>> Besides that the message is wrong because we check only f
2013/12/13 Violeta Georgieva
> I found another issue:
> If a tag file is placed in a jar file in WEB-INF/lib and then is used, the
> The change in the code is introduced with r1541960
>
> Besides that the message is wrong because we check only for WEB-INF/tags
> [1], what should be done in additi
2013/12/12 Mark Thomas
>
> The proposed Apache Tomcat 8.0.0 release candidate 7 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC5 are:
> - Better handling of generic types in the WebSocket
2013/12/13 Violeta Georgieva
> I'm receiving NPE when testing an application with jsp that specifies tld
> location with relative path:
>
> java.lang.NullPointerException
> org.apache.jasper.compiler.TldCache.getTaglibXml(TldCache.java:97)
>
> org.apache.jasper.compiler.TagLibraryInfoImpl
2013/12/12 Mark Thomas
>
> The proposed Apache Tomcat 8.0.0 release candidate 7 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC5 are:
> - Better handling of generic types in the WebSocket
2013/12/12 Mark Thomas
> The proposed Apache Tomcat 8.0.0 release candidate 7 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC5 are:
> - Better handling of generic types in the WebSocket 1
On 11/12/2013 23:24, Mark Thomas wrote:
> The proposed Apache Tomcat 8.0.0 release candidate 7 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC5 are:
> - Better handling of generic types in
On 2013-12-11 6:24 PM, Mark Thomas wrote:
The proposed 8.0.0-RC7 release is:
[ ] Broken - do not release
[X] Alpha - go ahead and release as 8.0.0-RC7 alpha
-- Jeanfrancois
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.ap
On Dec 11, 2013, at 6:24 PM, Mark Thomas wrote:
> The proposed Apache Tomcat 8.0.0 release candidate 7 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC5 are:
> - Better handling of generi
On 11/12/2013 23:24, Mark Thomas wrote:
> The proposed Apache Tomcat 8.0.0 release candidate 7 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC5 are:
> - Better handling of generic types in
The proposed Apache Tomcat 8.0.0 release candidate 7 is now available
for voting.
Given this is a release candidate I am working on the basis that it is
equivalent to an alpha. The main changes since RC5 are:
- Better handling of generic types in the WebSocket 1.0 implementation
- Refactor resourc
Hi,
> -Original Message-
> From: Mark Thomas [mailto:ma...@apache.org]
> Sent: Tuesday, December 10, 2013 1:22 AM
>
> > Any idea what is going on there? Why would Tomcat create such a big
> > byte array for a static file?
>
> Lots of things going on here.
>
> 1. The content of resourc
On 09/12/2013 21:40, Konstantin Preißer wrote:
> With Tomcat 8.0.0-RC6, I seem to have problems serving large static
> files in one of my webapps.
>
> I've run it on a Windows Server 2012 R2 system with Java 1.7.0_45
> (64-Bit) and the NIO HTTP connector. The webapp contains a large
> static file
Konstantin,
On 12/9/13, 4:40 PM, Konstantin Preißer wrote:
> The webapp contains a large static file with a size of 4,582,875,812 bytes.
I believe that static file is better-described as "huge", "enormous",
[bleeping] gigantic. Anything bigger than 2^32 bytes deserves a proper
adjective. :)
-chr
Hi Mark,
> -Original Message-
> From: Mark Thomas [mailto:ma...@apache.org]
> Sent: Monday, December 9, 2013 9:19 PM
> To: Tomcat Developers List
> Subject: [VOTE] Release Apache Tomcat 8.0.0-RC6
>
> The proposed Apache Tomcat 8.0.0 release candidate 6 is now a
On 09/12/2013 20:18, Mark Thomas wrote:
> The proposed Apache Tomcat 8.0.0 release candidate 6 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC5 are:
> - Better handling of generic types in
The proposed Apache Tomcat 8.0.0 release candidate 6 is now available
for voting.
Given this is a release candidate I am working on the basis that it is
equivalent to an alpha. The main changes since RC5 are:
- Better handling of generic types in the WebSocket 1.0 implementation
- Refactor resourc
On 16/10/2013 19:21, Mark Thomas wrote:
> The proposed Apache Tomcat 8.0.0 release candidate 5 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC4 are:
> - Stability fixes in the APR/native c
2013/10/16 Mark Thomas
>
> The proposed Apache Tomcat 8.0.0 release candidate 5 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC4 are:
> - Stability fixes in the APR/native connector
> - St
On Wed, Oct 16, 2013 at 2:21 PM, Mark Thomas wrote:
> The proposed 8.0.0-RC5 release is:
> [ ] Broken - do not release
> [ X ] Alpha - go ahead and release as 8.0.0-RC5 alpha
Yoav
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat
Mark,
On 16.10.2013 20:21, Mark Thomas wrote:
The proposed Apache Tomcat 8.0.0 release candidate 5 is now available
for voting.
...
The proposed 8.0.0-RC5 release is:
[ ] Broken - do not release
[X] Alpha - go ahead and release as 8.0.0-RC5 alpha
Tested .zip distribution on Windows 7 64-bit,
On 16.10.2013 20:21, Mark Thomas wrote:
> The proposed Apache Tomcat 8.0.0 release candidate 5 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC4 are:
> - Stability fixes in the APR/native c
Hi Mark,
> -Original Message-
> From: Mark Thomas [mailto:ma...@apache.org]
> Sent: Wednesday, October 16, 2013 8:21 PM
> To: Tomcat Developers List
> Subject: [VOTE] Release Apache Tomcat 8.0.0-RC5
>
> The proposed Apache Tomcat 8.0.0 release candidate 5 is now a
The proposed Apache Tomcat 8.0.0 release candidate 5 is now available
for voting.
Given this is a release candidate I am working on the basis that it is
equivalent to an alpha. The main changes since RC4 are:
- Stability fixes in the APR/native connector
- Stability fixes for non-blocking IO and W
Because of the easily triggered JVM crash when using APR, SSL and
upgraded connections (e.g. via WebSocket) I am cancelling this release vote.
I did think about letting this vote run but a known JVM crash seemed too
serious to allow the vote to continue and it isn't as if rolling a new
RC is a gre
On 15/10/2013 15:23, Daniel Mikusa wrote:
> Tested a couple apps that I have and everything worked OK for me.
> One note though, there are some errors with the examples when I run
> with the security manager enabled.
>
> Here are the steps to replicate the issues:
>
> 1.) Downloaded Tomcat 8.0.0-
On 15/10/2013 17:31, Konstantin Preißer wrote:
> Note, that the documentation index.html included in the binaries
> says:
>
> "Apache Tomcat version @VERSION_MAJOR_MINOR@ implements the Servlet
> 3.1 and JavaServer Pages 2.3 specifications from the Java Community
> Process [...]"
>
> I guess thi
[X] Alpha - go ahead and release as 8.0.0-RC4 alpha
Focused on websocket testing, default configuration.
-- Jeanfrancois
On 2013-10-15 8:48 AM, Mark Thomas wrote:
The proposed Apache Tomcat 8.0.0 release candidate 4 is now available
for voting.
Given this is a release candidate I am working
> -Original Message-
> From: Mark Thomas [mailto:ma...@apache.org]
> Sent: Tuesday, October 15, 2013 2:49 PM
> To: Tomcat Developers List
> Subject: [VOTE] Release Apache Tomcat 8.0.0-RC4
>
> The proposed Apache Tomcat 8.0.0 release candidate 4 is now available
>
On Oct 15, 2013, at 8:48 AM, Mark Thomas wrote:
> The proposed Apache Tomcat 8.0.0 release candidate 4 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC3 are:
> - Stability fixes in the AP
The proposed Apache Tomcat 8.0.0 release candidate 4 is now available
for voting.
Given this is a release candidate I am working on the basis that it is
equivalent to an alpha. The main changes since RC3 are:
- Stability fixes in the APR/native connector
- Stability fixes for non-blocking IO and W
+1 (alpha) : binding - markt, schultz, rjung, jfarcand
non-binding - Martin Grigorov
No other votes were cast. The vote therefore passes.
I'll start the process of releasing the bits.
Mark
-
To unsubscribe, e-mail:
[X] Alpha - go ahead and release as 8.0.0-RC3 alpha
Tested with Atmosphere jsr356 and Servlet 3 Async API.
-- Jeanfrancois
On 2013-09-20 6:36 AM, Mark Thomas wrote:
The proposed Apache Tomcat 8.0.0 release candidate 3 is now available
for voting.
Given this is a release candidate I am working
On 20.09.2013 12:36, Mark Thomas wrote:
> The proposed 8.0.0-RC3 release is:
> [ ] Broken - do not release
> [X] Alpha - go ahead and release as 8.0.0-RC3 alpha
+1 as alpha.
Overview:
- MD5 OK
- signatures OK
- key in KEYS file
- gz and zip for src and bin consistent
- src consistent with svn t
Mark,
On 9/20/13 6:36 AM, Mark Thomas wrote:
> The proposed Apache Tomcat 8.0.0 release candidate 3 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC1 are:
> - Updated spec implementations
On Fri, Sep 20, 2013 at 12:36 PM, Mark Thomas wrote:
> The proposed Apache Tomcat 8.0.0 release candidate 3 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC1 are:
> - Updated spec implemen
2013/9/20 Mark Thomas
>
> The proposed Apache Tomcat 8.0.0 release candidate 3 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC1 are:
> - Updated spec implementations with results of variou
On 23/09/2013 06:20, Henri Gomez wrote:
> Hi Mark
>
> What kind of tests, specific to TC 8.0 are awaited to 'qualify' ?
Not sure what you mean.
The only tests we have are the unit tests. We do not have access to the
Java EE 7 TCKs.
In terms of this release, I am personally happy if the unit tes
Hi Mark
What kind of tests, specific to TC 8.0 are awaited to 'qualify' ?
2013/9/23 Mark Thomas
> On 20/09/2013 12:35, Mark Thomas wrote:
> > On 20/09/2013 11:36, Mark Thomas wrote:
> >> The proposed Apache Tomcat 8.0.0 release candidate 3 is now available
> >> for voting.
> >>
> >> Given this
On 20/09/2013 12:35, Mark Thomas wrote:
> On 20/09/2013 11:36, Mark Thomas wrote:
>> The proposed Apache Tomcat 8.0.0 release candidate 3 is now available
>> for voting.
>>
>> Given this is a release candidate I am working on the basis that it is
>> equivalent to an alpha. The main changes since RC
On 20/09/2013 11:36, Mark Thomas wrote:
> The proposed Apache Tomcat 8.0.0 release candidate 3 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC1 are:
> - Updated spec implementations with r
The proposed Apache Tomcat 8.0.0 release candidate 3 is now available
for voting.
Given this is a release candidate I am working on the basis that it is
equivalent to an alpha. The main changes since RC1 are:
- Updated spec implementations with results of various "grey area"
discussions from the E
On 19.09.2013 18:32, Rainer Jung wrote:
> On 19.09.2013 13:01, Mark Thomas wrote:
>> On 19/09/2013 09:12, Mark Thomas wrote:
>>> On 19/09/2013 07:18, Rainer Jung wrote:
I get a crash when using tcnative 1.1.28 and JDK 1.7.0_40 on Solaris 10:
WARN: Test failure in
'output/build/l
On 19.09.2013 13:01, Mark Thomas wrote:
> On 19/09/2013 09:12, Mark Thomas wrote:
>> On 19/09/2013 07:18, Rainer Jung wrote:
>>> I get a crash when using tcnative 1.1.28 and JDK 1.7.0_40 on Solaris 10:
>>>
>>> WARN: Test failure in
>>> 'output/build/logs/TEST-org.apache.tomcat.websocket.TestWsWebSo
1 - 100 of 128 matches
Mail list logo
