Reminder: Community Over Code Asia 2024 CFP closes on Apr 22nd

[Huxing Zhang]

Hi All,

The CFP for Community Over Code Asia, including the Web server and
Tomcat track, is closing very soon -  at 4:00 PM on 22 Apr 2024
Beijing time.

Details: https://sessionize.com/communityovercode-asia-2024

Please do not wait until the last minute. We hope to see you in Hangzhou!

-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

CommunityOverCode Asia 2024 is calling for Presentations!

[Huxing Zhang]

Hi All,

Community over Code Asia 2024 will be held in person this year in
Hangzhou, China [1].

The CFP will end on April 21st, 2024 11:59 PM (Beijing time - UTC +8).

For details could be found on the website [1].

Note that for the topics that can't be presented in person, a
pre-recorded video is
also acceptable.

Please do not hesitate to submit, including the Web Server/Tomcat
track as well as the others!

[1] https://asia.communityovercode.org/

-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

CommunityOverCode Asia 2023 is calling for Presentations!

[Huxing Zhang]

Hi All,

Community over Code Asia 2023 (formerly ApacheCon Asia) will be held
in person this year in Beijing [1].

The CFP will end on Tuesday, Jun 6th, 2023 8:00 AM (Beijing time - UTC +8).

For details could be found on the website [1].

Note that for those that can't be present, a pre-recorded video is
also acceptable.

Please do not hesitate to submit, including the Web Server/Tomcat
track as well as the others!

[1] https://www.bagevent.com/event/cocasia-2023-EN

-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reminder: ApacheCon Asia 2022 CFP closes on May 31st

[Huxing Zhang]

Hi All,

Just a kind reminder that the CALL FOR PRESENTATIONS of ApacheCon Asia
2022 closes at 8 AM (Beijing Time), May 31st. Please do not wait until
the last minute. :)

Details: https://apachecon.com/acasia2022/cfp.html

The event  is completely virtual and the talk is pre-recorded. The
presentation could be either in English or in Chinese.

Submission: https://shimo.im/forms/6ZTBLanjqW8pY3dj/fill?channel=website

-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

ApacheCon Asia 2022 is calling for Presentations!

[Huxing Zhang]

Hi All,

ApacheCon Asia is coming again as a virtual event this July 29 - 31.
The CFP will end on Tuesday, May 31st, 2022 8:00 AM (Beijing time -
UTC +8).

More details could be found here:

https://apachecon.com/acasia2022/cfp.html

Please remember that there is no need to be present at the conference,
it is completely virtual,
the talk is pre-recorded.

The presentation could be either in English or in Chinese.

Please free free to submit your ideas related to Web server / Tomcat
or other topics here:

https://shimo.im/forms/6ZTBLanjqW8pY3dj/fill?channel=website

--
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

ApacheCon Asia 2021 is calling for Presentations!

[Huxing Zhang]

Hi All,

ApacheCon Asia is coming virtually this August 6 - 8. The CFP will end
on Monday, May 3rd, 2021 8:00 AM (Beijing time - UTC +8).

More details could be found here:

https://apachecon.com/acasia2021/cfp.html

If you have concern with the date and time, please remember that there
is no need to be present at the conference, it is completely virtual,
the talk is pre-recorded.

The presentation could be either in English or in Chinese.

Please free free to submit your ideas related to Web server / Tomcat
or other topics here:

https://acasia2021.jamhosted.net/

-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: Git migration read for testing

[Huxing Zhang]

Hi,

It looks good to me.

I think it is better to add some description and tags in the headline
of Github, to make it more informative and searchable.

For example: Apache Tomcat® is an open source implementation of the
Java Servlet, JavaServer Pages, Java Expression Language and Java
WebSocket technologies.

Also I think the CONTRIBUTING file need to be update, to deprecate the
usage of svn.

Further search using SVN as keyword in the repo shows more work need
to be updated.

[1] https://github.com/apache/tomcat/blob/master/CONTRIBUTING.md

On Tue, Feb 26, 2019 at 8:33 PM Mark Thomas  wrote:
>
> All,
>
> https://github.com/apache/tomcat
>
> is now ready for testing.
>
> It should contain:
> branches
> - master (9.0.x)
> - 8.5.x
> - 7.0.x
>
> Tags:
> - one for each 7.0.x, 8.5.x and 9.0.x release
>
> Tags have all been renamed to follow a a.b.c-MODIFIERn format for
> version number where modifier is RC or M.
>
> The repository is probably read/write for all committers now but please
> refrain from making any changes until we confirm that all is well.
>
> If you have some time available now, please test this new repository and
> report and questions or concerns to this thread.
>
> Assuming no issues are discovered, I'd like to formally move over to git
> later today.
>
> Mark
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>


-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Migrate to git

[Huxing Zhang]

Hi,


> >
> > This is a VOTE to migrate the primary source code repository for Apache
> > Tomcat 9.0.x, 8.5.x and 7.0.x from svn to git.
> >

[X] +1 Go ahead with the migration

Thanks for the work!

-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Access to thread pool task queue size via JMX

[Huxing Zhang]

Hi,

Currently Tomcat's thread pool implementation, which is under
org.apache.tomcat.util.net.AbstractEndpoint, does not expose task
queue size via JMX, while in
org.apache.catalina.core.StandardThreadExecutor it can be accessed via
JMX.

The background is that I am involved with a project to auto scale web
application and the size of task queue is helpful to make the
decision.

Therefore I propose to expose it via JMX. The implementation could be
adding a simple method to org.apache.tomcat.util.net.AbstractEndpoint:

public int getThreadPoolTaskQueueSize() {
if (executor!=null) {
if (executor instanceof ThreadPoolExecutor) {
return ((ThreadPoolExecutor)executor).getQueue().size();
} else if (executor instanceof StandardThreadExecutor) {
return ((StandardThreadExecutor)executor).getQueueSize();
} else {
return -1;
}
} else {
return -2;
}
}

Another issue is that the default implementation of task queue is hard
coded to be infinite, I think it is better to make it configurable,
just like what StandardThreadExecutor does. But I think it worth
discussion in another thread.

Comments welcome.

-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 7.0.93

[Huxing Zhang]

Hi,

On Sun, Feb 17, 2019 at 1:41 AM Violeta Georgieva  wrote:
>
> The proposed Apache Tomcat 7.0.93 release is now available for voting.
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.93/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1204/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_93/
>

The proposed 7.0.93 release is:
[ ] Broken - do not release
[X] Stable - go ahead and release as 7.0.93 Stable

Signatures and hashes are good for the source release.
Unit test passed.
Example web application works fine.

>
> Regards,
> Violeta



-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: svn commit: r1853777 - in /tomcat/tc8.5.x/tags/TOMCAT_8_5_15/res: welcome.bin.html welcome.main.html

[Huxing Zhang]

Hi,

Something went wrong in my local environment, it looks like I pushed
to the wrong branch, I am going to revert it and push to
/tomcat/tc8.5.x/trunk/

On Mon, Feb 18, 2019 at 1:07 PM  wrote:
>
> Author: huxing
> Date: Mon Feb 18 05:07:36 2019
> New Revision: 1853777
>
> URL: http://svn.apache.org/viewvc?rev=1853777=rev
> Log:
> Remove extra dot
>
> Modified:
> tomcat/tc8.5.x/tags/TOMCAT_8_5_15/res/welcome.bin.html
> tomcat/tc8.5.x/tags/TOMCAT_8_5_15/res/welcome.main.html
>
> Modified: tomcat/tc8.5.x/tags/TOMCAT_8_5_15/res/welcome.bin.html
> URL: 
> http://svn.apache.org/viewvc/tomcat/tc8.5.x/tags/TOMCAT_8_5_15/res/welcome.bin.html?rev=1853777=1853776=1853777=diff
> ==
> --- tomcat/tc8.5.x/tags/TOMCAT_8_5_15/res/welcome.bin.html (original)
> +++ tomcat/tc8.5.x/tags/TOMCAT_8_5_15/res/welcome.bin.html Mon Feb 18 
> 05:07:36 2019
> @@ -94,7 +94,7 @@ RELEASE-NOTES and the RUNNING.txt file i
>  
>  
>
> -Thank you for using http://tomcat.apache.org/;>Tomcat!.
> +Thank you for using http://tomcat.apache.org/;>Tomcat!
>  
>  The Apache Tomcat Project   href="http://tomcat.apache.org/;>http://tomcat.apache.org/
>
> Modified: tomcat/tc8.5.x/tags/TOMCAT_8_5_15/res/welcome.main.html
> URL: 
> http://svn.apache.org/viewvc/tomcat/tc8.5.x/tags/TOMCAT_8_5_15/res/welcome.main.html?rev=1853777=1853776=1853777=diff
> ==
> --- tomcat/tc8.5.x/tags/TOMCAT_8_5_15/res/welcome.main.html (original)
> +++ tomcat/tc8.5.x/tags/TOMCAT_8_5_15/res/welcome.main.html Mon Feb 18 
> 05:07:36 2019
> @@ -94,7 +94,7 @@ RELEASE-NOTES and the RUNNING.txt file i
>  
>  
>
> -Thank you for using http://tomcat.apache.org/;>Tomcat!.
> +Thank you for using http://tomcat.apache.org/;>Tomcat!
>  
>  The Apache Tomcat Project   href="http://tomcat.apache.org/;>http://tomcat.apache.org/
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>


--
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [ANN] New committer: Woonsan Ko

[Huxing Zhang]

Congratulations Woonsan!

On Tue, Dec 25, 2018 at 1:45 AM Igal Sapir  wrote:
>
> W00t w00t!  Congrats Woonsan :)
>
> Igal
>
> On 12/19/2018 6:05 PM, Woonsan Ko wrote:
>
> > Thank you very much for the warm welcomes!
> > I have watched many volunteering hearts here, helping each other in
> > this community, for years. This community has been my biggest input
> > source from which I have learned how to grow ourselves together, in
> > positive, collaborative, collective, inclusive, sustainable ways.
> > I will do my best where I can help to keep the health of our heartbeats.
> >
> > Kind regards,
> >
> > Woonsan Ko
> >
> > On Wed, Dec 19, 2018 at 6:56 PM Mark Thomas  wrote:
> >> On behalf of the Tomcat committers I am pleased to announce that
> >> Woonsan Ko (woonsan) has been voted in as a new Tomcat committer.
> >>
> >> Please join me in welcoming him.
> >>
> >> Kind regards,
> >>
> >> Mark
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> >> For additional commands, e-mail: dev-h...@tomcat.apache.org
> >>
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> > For additional commands, e-mail: dev-h...@tomcat.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>


-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

ApacheCon NA 2018 slides

[Huxing Zhang]

Hi,

I am wondering if we could add more slides/audios/videos into [1] for
the ApacheCon NA 2018.
I do see some of the slides are uploaded to [2], but I think it is
better to summarize them to the official pages.

[1] http://tomcat.apache.org/presentations.html
[2] https://apachecon.dukecon.org/acna/2018/#/timetable

-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 7.0.91

[Huxing Zhang]

Hi,

On Fri, Sep 14, 2018 at 4:28 AM Violeta Georgieva  wrote:
>
> The proposed Apache Tomcat 7.0.91 release is now available for voting.
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.91/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1195/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_91/
>
The proposed 7.0.91 release is:
[ ] Broken - do not release
[X] Stable - go ahead and release as 7.0.91 Stable


Unit test passed.
Examples ok.
Test web application works well.
>
> Regards,
> Violeta



-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 9.0.12

[Huxing Zhang]

The proposed 9.0.12 release is:
[ ] Broken - do not release
[X] Stable - go ahead and release as 9.0.12

Unit test passed.
Test web application works fine.

On Wed, Sep 5, 2018 at 6:32 AM Mark Thomas  wrote:
>
> The proposed Apache Tomcat 9.0.12 release is now available for voting.
>
> The major changes compared to the 9.0.11 release are:
>
> - Fix multiple issues associated with using the asynchronous Servlet
>   API in combination with HTTP/2
>
> - Add recursion to rewrite substitution parsing
>
> - Expand the information in the documentation web application
>   regarding the use of CATALINA_HOME and CATALINA_BASE.
>   Patch provided by Marek Czernek.
>
>
> Along with lots of other bug fixes and improvements.
>
> For full details, see the changelog:
> http://svn.apache.org/repos/asf/tomcat/trunk/webapps/docs/changelog.xml
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.12/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1193/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tags/TOMCAT_9_0_12/
>
> The proposed 9.0.12 release is:
> [ ] Broken - do not release
> [ ] Stable - go ahead and release as 9.0.12
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>


-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: Duplicate registration of ServletContextListerner

[Huxing Zhang]

On Fri, Jul 27, 2018 at 3:02 AM, Mark Thomas  wrote:
> On July 26, 2018 6:08:09 PM UTC, Christopher Schultz 
>  wrote:
>>-BEGIN PGP SIGNED MESSAGE-
>>Hash: SHA256
>>
>>Mark,
>>
>>On 7/26/18 5:21 AM, Mark Thomas wrote:
>>> On 26/07/2018 04:29, Huxing Zhang wrote:
>>>> Hi,
>>>>
>>>> On Thu, Jul 26, 2018 at 2:57 AM, Christopher Schultz
>>>>  wrote:
>>>
>>> 
>>>
>>>>> Can you think of a use-case where addListener() shouldn't
>>>>> automatically perform de-duplication?
>>>>
>>>> No, I can't think of that case.
>>>
>>> Yes, although only for the programmatic case.
>>>
>>> Multiple instances of the same listener configured differently.
>>> E.g. I can see a use for a simple
>>> javax.servlet.http.HttpSessionAttributeListener that might be
>>> added multiple times in a single app to define different actions
>>> for different attributes. Yes it could be implemented as a single
>>> listener but I can certainly see some scenarios where adding the
>>> same listener multiple times would give cleaner / simpler code.
>>>
>>>> If there is really a case, I think we can use
>>>> javax.servlet.ServletContext#setInitParameter to control that
>>>> behavior. For example, use a initialization parameter named
>>>> DEDUPLICATE_LISTENERS, if set to true, any further registration
>>>> will be de-duplicated. This parameter is better to be a per call
>>>> parameter rather than a global parameter, because it might be
>>>> updated from multiple place.
>>>
>>> Configuration at that point may cause problems. I'm not sure that
>>> the ServletContext would be available early enough. It would be
>>> better as an attribute on the Context. That would also be
>>> consistent with other such configuration parameters.
>>>
>>>>> I'm thinking that Tomcat should simply take a call to
>>>>> addListener() and ignore any registrations after the first one.
>>>>> >
>>>> Yes, I think it is important to have consistent behavior between
>>>> web-fragement/@WebListener and programmatic API.
>>>
>>> -1. That behaviour is not consistent with the Servlet spec. The
>>> spec expects multiple instances. It isn't explicit but it is very
>>> strongly implied both by the wording used and the complete absence
>>> of any indication of how de-duplication should be performed.


>>>
>>> Further, de-duplication is not that simple. Some users will want
>>> the fist listener added. Some the most recent. There are probably
>>> other complications I haven't thought of.
>>>
>>>>> Would that make sense? Would it violate any spec-defined
>>>>> behavior?
>>>>
>>>> I can't find any spec describing how to handle the duplications
>>>> on that part, so I guess it is safe to do so. :)
>>>
>>> There are lots of behaviours the spec doesn't define. That doesn't
>>> mean implementing them is spec compliant. Exactly the opposite in
>>> fact.
>>>
>>>> Maybe we can improve spec as well.
>>>
>>> Hopefully, with the move to Eclipse, the various clarifications
>>> that have been open for a number of years will now start to be
>>> addressed. I'd recommend adding this to them
>>>
>>> https://github.com/eclipse-ee4j/servlet-api/issues
>>
>>FWIW, I was not suggesting that all types of listeners be
>>deduplicated. I was instead focusing on ServletContextListeners, since
>>that was Huxing's use-case. I should have been more clear in my
>>proposal
>>.
>>
>>On the other hand, listeners cannot be registered with any information
>>other than their class. Therefore I'm not sure that adding the same
>>class multiple times to the event-notification list would accomplish
>>anything useful.
>>
>>Hmm... I just realized that the programmatic interface allows
>>listeners to be added by /instance/ and not just by class (name), so
>>theoretically one could instantiate two instances of a single class,
>>each with different behaviors (configured via constructors or other
>>mutators) and they would therefore be "distinct".
>>
>>Rather than deduplicating by class, perhaps we could deduplicate by
>>using .equals(). In that case, if you had something like this:
>>
>>class MyListener extends HttpSessionAttributeListener {
>&g

Re: Duplicate registration of ServletContextListerner

[Huxing Zhang]

Hi,

On Thu, Jul 26, 2018 at 2:57 AM, Christopher Schultz
 wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Huxing,
>
> On 7/25/18 11:28 AM, Huxing Zhang wrote:
>> Hi,
>>
>> Recently I am working on implementing a feature that can
>> automatically register a ServletContextListerner instance, say A,
>> to servletContext programmatically during startup.
>>
>> I use ServletContainerInitializer and call the
>> servletContext.addListener() method. This is fine for most of the
>> cases. But if user has specified A in web.xml, it turns that A will
>> be registered twice, which will lead to undesired behavior.
>>
>> My expected behavior will be registering A only once regardless of
>> user specified A in web.xml or not.
>>
>> I can achieve this by specifying A in web-fragment.xml, since it
>> will get merged into web.xml whenever A is defined in web.xml or
>> not, which means duplicates can be removed.
>>
>> I am wondering why we can not achieve this using programatic API.
>>
>> I've checked servlet 4.0/3.1 spec, in 4.4.3.1 "void
>> addListener(String className)", it says:
>>
>> If the class with the given name implements a listener interface
>> whose invocation order corresponds to the declaration order, that
>> is, if it implements javax.servlet.ServletRequestListener,
>> javax.servlet.ServletContextListener or
>> javax.servlet.http.HttpSessionListener, then the new listener will
>> be added to the end of the ordered list of listeners of that
>> interface.
>>
>> It looks tomcat's behavior is spec-compliant.
>>
>> My idea is if I can get all the existing listeners from
>> servletContext, then I can decide whether to add A or not.
>>
>> But I can't find that kind of API from servletContext.
>>
>> I also noticed that there are getServletRegistrations() and
>> getFilterRegistrations() in servletContext, why can't we have API
>> like getListeners()?
>
> Can you think of a use-case where addListener() shouldn't
> automatically perform de-duplication?

No, I can't think of that case.

If there is really a case, I think we can use
javax.servlet.ServletContext#setInitParameter to control that
behavior.
For example, use a initialization parameter named
DEDUPLICATE_LISTENERS, if set to true, any further registration will
be de-duplicated.
This parameter is better to be a per call parameter rather than a
global parameter, because it might be updated from multiple place.

Overall, I don't  think it is necessary to have unless there is a case.

> I'm thinking that Tomcat should
> simply take a call to addListener() and ignore any registrations after
> the first one.

Yes, I think it is important to have consistent behavior between
web-fragement/@WebListener and programmatic API.

>
> Would that make sense? Would it violate any spec-defined behavior?

I can't find any spec describing how to handle the duplications on
that part, so I guess it is safe to do so. :)

Maybe we can improve spec as well.

>
> - -chris
> -BEGIN PGP SIGNATURE-
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAltYyDIACgkQHPApP6U8
> pFhSmA//We21JrL+KwpbPrNgicIM0T77/WFMQyNoaFrW0+QdJ96CUAWYr6NKn17t
> 0Y0mk9WpRDSIsknpXPTYfisO1RllO7Mde1KuGH6EUMZyYWr84E9YhqBVyOHG48if
> Y/COneCHK3Gs7QlywgRhyKDZFogDFS/X5zW+AGctFIdcdgBu0z8U85a/wlPLUTuk
> XA00qPLrIWSXerB97nsqcdreh7Qs2Uyx3Eye74JE4RwzRYkGVYrMuPpPQwudbAUF
> f2fgAHC5lrJBGLK4yiFce53KcwTzeyBM2yskux/1y02NUyHIASpjV8DqADthV61o
> SOFgG25PJChShsLQipjhcNQtqiluP4FNo1sN78ieMABfOm1zlIh4T4/4M8VD0MqP
> qdoXgqC8vEsCiGUY7rqQKIRTAe6Hpf2yz6Oygwhfk+6z2CpJ4RQfsAFMVJMf2KOM
> wjb6akXnrEzxPG6UEVxtep2cLLVraHlbjDHzNqMrecBC2EYHU/Ovh+gpsHXtJG8v
> +Koh9HR2Ps5h92PI5ND39JsD1KyNhO+zayYD/a+I9ryrQEKV584JyU6q3vyWIwXk
> m8eDlYo0ChCeiGwQ22bAOsdKYTJHruGPEg92VbbDipPLJ+8uzAbtEAlXmiGYkv2B
> Q3EtprVkD1sI88v/iRU8QZg7ux5ebKDHGIk1f33BP3AYUWnwcyY=
> =jKMW
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>



-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Duplicate registration of ServletContextListerner

[Huxing Zhang]

Hi,

Recently I am working on implementing a feature that can automatically
register a ServletContextListerner instance, say A, to servletContext
programmatically during startup.

I use ServletContainerInitializer and call the
servletContext.addListener() method. This is fine for most of the
cases. But if user has specified A in web.xml, it turns that A will be
registered twice, which will lead to undesired behavior.

My expected behavior will be registering A only once regardless of
user specified A in web.xml or not.

I can achieve this by specifying A in web-fragment.xml, since it will
get merged into web.xml whenever A is defined in web.xml or not, which
means duplicates can be removed.

I am wondering why we can not achieve this using programatic API.

I've checked servlet 4.0/3.1 spec, in 4.4.3.1 "void addListener(String
className)", it says:

If the class with the given name implements a listener interface whose
invocation order corresponds to the declaration order, that is, if it
implements javax.servlet.ServletRequestListener,
javax.servlet.ServletContextListener or
javax.servlet.http.HttpSessionListener, then the new listener will be
added to the end of the ordered list of listeners of that interface.

It looks tomcat's behavior is spec-compliant.

My idea is if I can get all the existing listeners from
servletContext, then I can decide whether to add A or not.

But I can't find that kind of API from servletContext.

I also noticed that there are getServletRegistrations() and
getFilterRegistrations() in servletContext, why can't we have API like
getListeners()?


-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 7.0.90

[Huxing Zhang]

Hi,

The proposed 7.0.90 release is:
[ ] Broken - do not release
[X] Stable - go ahead and release as 7.0.90 Stable

Unit test passed.
Exampels ok.
Test web application works fine.



On Tue, Jul 3, 2018 at 1:36 AM, Violeta Georgieva  wrote:
> The proposed Apache Tomcat 7.0.90 release is now available for voting.
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.90/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1190/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_90/
>
> The proposed 7.0.90 release is:
> [ ] Broken - do not release
> [ ] Stable - go ahead and release as 7.0.90 Stable
>
> Regards,
> Violeta



-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: Slides for ApacheCon EU Roadshow 2018

[Huxing Zhang]

>From the youtube playlist[1] of Apache EU roadshow, I can see Rainer's
topic about Apache Web Server[2].

But I did not find any tomcat related topics there.

So I guess not every talk is getting recorded?

[1] https://www.youtube.com/playlist?list=PLU2OcwpQkYCyuV8Fza7dVAEg5FW2Pzg-8
[2] 
https://www.youtube.com/watch?v=MRx0PZilMBY=15=PLU2OcwpQkYCyuV8Fza7dVAEg5FW2Pzg-8=219s

On Wed, Jun 27, 2018 at 3:39 PM, Rainer Jung  wrote:
> Am 27.06.2018 um 01:40 schrieb Huxing Zhang:
>>
>> Hi All,
>>
>> I have check the presentation page[1] but could only find slide of
>> Mark's "State of the Cat" topic.
>>
>> Do we have slides/recordings for the other topics?
>>
>> [1] http://tomcat.apache.org/presentations.html
>
>
> Thanks for asking. I just added my two presentations.
>
> More to come from others?
>
> Regards,
>
> Rainer
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>



-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Slides for ApacheCon EU Roadshow 2018

[Huxing Zhang]

Hi All,

I have check the presentation page[1] but could only find slide of
Mark's "State of the Cat" topic.

Do we have slides/recordings for the other topics?

[1] http://tomcat.apache.org/presentations.html

-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 8.5.32

[Huxing Zhang]

Hi,

The proposed 8.5.32 release is:
[ ] Broken - do not release
[X] Stable - go ahead and release as 8.5.32

Unit test passed on Java 10.
Examples ok.
Test web application works fine.

On Thu, Jun 21, 2018 at 4:27 AM, Mark Thomas  wrote:
> The proposed Apache Tomcat 8.5.32 release is now available for voting.
>
> The major changes compared to the 8.5.31 release are:
>
> - Add the RemoteCIDRFilter and RemoteCIDRValve that can be used to
>   allow/deny requests based on IPv4 and/or IPv6 client address where the
>   IP ranges are defined using CIDR notation.
>   Based on a patch by Francis Galiegue.
>
> - Update the packaged version of the Tomcat Native Library to 1.2.17 to
>   pick up the latest Windows binaries built with APR 1.6.3 and OpenSSL
>   1.0.2o.
>
> - Correct a regression in the Host validation by removing the
>   requirement that the final component of a FQDN must be alphabetic.
>
> Along with lots of other bug fixes and improvements.
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.32/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1187/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc8.5.x/tags/TOMCAT_8_5_32/
>
> The proposed 8.5.32 release is:
> [ ] Broken - do not release
> [ ] Stable - go ahead and release as 8.5.32
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>



-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 9.0.10

[Huxing Zhang]

Hi,

The proposed 9.0.10 release is:
[ ] Broken - do not release
[X] Stable - go ahead and release as 9.0.10

Unit test passed on Java 10.
Examples ok.
Test web application works fine.

On Thu, Jun 21, 2018 at 3:45 AM, Mark Thomas  wrote:
> The proposed Apache Tomcat 9.0.10 release is now available for voting.
>
> Note:
> 9.0.9 was tagged and uploaded when BZ 62476 was created and the decision
> was taken to re-tag to pick up that fix.
>
> The major changes compared to the 9.0.8 release are:
>
> - Add the RemoteCIDRFilter and RemoteCIDRValve that can be used to
>   allow/deny requests based on IPv4 and/or IPv6 client address where the
>   IP ranges are defined using CIDR notation.
>   Based on a patch by Francis Galiegue.
>
> - Use NIO2 API for websockets writes.
>
> - Update the packaged version of the Tomcat Native Library to 1.2.17 to
>   pick up the latest Windows binaries built with APR 1.6.3 and OpenSSL
>   1.0.2o.
>
> - Correct a regression in the Host validation by removing the
>   requirement that the final component of a FQDN must be alphabetic.
>
> Along with lots of other bug fixes and improvements.
>
> For full details, see the changelog:
> http://svn.apache.org/repos/asf/tomcat/trunk/webapps/docs/changelog.xml
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.10/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1186/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tags/TOMCAT_9_0_10/
>
> The proposed 9.0.10 release is:
> [ ] Broken - do not release
> [ ] Stable - go ahead and release as 9.0.10
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>



-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 7.0.88

[Huxing Zhang]

Hi,

On Mon, May 7, 2018 at 8:06 PM, Violeta Georgieva  wrote:
> The proposed Apache Tomcat 7.0.88 release is now available for voting.
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.88/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1184/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_88/
>
> The proposed 7.0.88 release is:
> [ ] Broken - do not release
> [X] Stable - go ahead and release as 7.0.88 Stable

Signatures ok.
SHA512 checksum ok.
Unit test passed.

>
> Regards,
> Violeta



-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [Git migration] Old git repositories

[Huxing Zhang]

+1 for deleting them.

On Tue, May 1, 2018 at 5:36 AM, Coty Sutherland  wrote:
> On Mon, Apr 30, 2018, 16:48 Mark Thomas  wrote:
>
>> The current plan is to merge all of the existing branches into a single
>> Git repo. This will be mirrored at GitHub under apache/tomcat. This is
>> currently used for the svn mirror for trunk only.
>>
>> This raises the question what to do with:
>> apache/tomcat7
>> apache/tomcat8
>> apache/tomcat85
>>
>> I think there are two options:
>>
>> 1. Retain them but make them read-only
>>
>> 2. Delete them
>>
>> Suggestions for other options welcome.
>>
>> I'm actually leaning towards deleting them. My reasoning is that we
>> deleted apache/tomcat55 and apache/tomcat6 when those releases reached
>> EOL and no-one complained. As far as I recall, no-one even mentioned the
>> deletions on list. Therefore, I'd be happy to delete those mirrors just
>> as soon as apache/tomcat was up and running.
>>
>
> I don't see a reason for keeping them so I'm +1 for deleting them.
>
>
>> Mark
>>
>> P.S. Don't forget that apache/tomcat will become writeable as part of
>> the migration and will sync with gitbox.apache.org in a dual master
>> configuration
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: dev-h...@tomcat.apache.org
>>
>>



-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 7.0.86

[Huxing Zhang]

Hi,

On Tue, Apr 10, 2018 at 5:07 AM, Violeta Georgieva  wrote:
> The proposed Apache Tomcat 7.0.86 release is now available for voting.
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.86/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1178/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_86/
>
> The proposed 7.0.86 release is:
> [ ] Broken - do not release
> [X] Stable - go ahead and release as 7.0.86 Stable

Unit test passed.
Examples: ok.
Test running on Java 10: ok

>
> Regards,
> Violeta



-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 8.5.30

[Huxing Zhang]

Hi,

The proposed 8.5.30 release is:
[ ] Broken - do not release
[X] Stable - go ahead and release as 8.5.30

Unit test: ok
Examples: ok
Tested running on Java 10: ok

On Wed, Apr 4, 2018 at 4:36 AM, Mark Thomas  wrote:
> The proposed Apache Tomcat 8.5.30 release is now available for voting.
>
> The major changes compared to the 8.5.29 release are:
>
> - Add support for the maxDays attribute to the AccessLogValve and
>   ExtendedAccessLogValve. This allows the maximum number of days for
>   which rotated access logs should be retained before deletion to be
>   defined.
>
> - Avoid infinite recursion, when trying to validate a session while
>   loading it with PersistentManager.
>
> - Correct two protocol errors with HTTP/2 PUSH_PROMISE frames.
>
> - The OpenSSL engine SSL session will now ignore invalid accesses.
>
> Along with lots of other bug fixes and improvements.
>
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.30/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1177/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc8.5.x/tags/TOMCAT_8_5_30/
>
> The proposed 8.5.30 release is:
> [ ] Broken - do not release
> [ ] Stable - go ahead and release as 8.5.30
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>



-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 9.0.7

[Huxing Zhang]

Hi,

The proposed 9.0.7 release is:
[ ] Broken - do not release
[X] Stable - go ahead and release as 9.0.7

Unit test ok.
Examples ok.
Tested running on Java 10: ok.

On Wed, Apr 4, 2018 at 4:25 AM, Mark Thomas  wrote:
> The proposed Apache Tomcat 9.0.7 release is now available for voting.
>
> The major changes compared to the 9.0.6 release are:
>
> - Add support for the maxDays attribute to the AccessLogValve and
>   ExtendedAccessLogValve. This allows the maximum number of days for
>   which rotated access logs should be retained before deletion to be
>   defined.
>
> - Avoid infinite recursion, when trying to validate a session while
>   loading it with PersistentManager.
>
> - Correct two protocol errors with HTTP/2 PUSH_PROMISE frames.
>
> - The OpenSSL engine SSL session will now ignore invalid accesses.
>
>
> Along with lots of other bug fixes and improvements.
>
> For full details, see the changelog:
> http://svn.apache.org/repos/asf/tomcat/trunk/webapps/docs/changelog.xml
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.7/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1176/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tags/TOMCAT_9_0_7/
>
> The proposed 9.0.7 release is:
> [ ] Broken - do not release
> [ ] Stable - go ahead and release as 9.0.7
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>

-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 8.5.29

[Huxing Zhang]

Hi,

The proposed 8.5.29 release is:
[ ] Broken - do not release
[X] Stable - go ahead and release as 8.5.29

Unit test passed.
Examples ok.
Our test web application works fine.

On Mon, Mar 5, 2018 at 9:51 PM, Mark Thomas  wrote:
> The proposed Apache Tomcat 8.5.29 release is now available for voting.
>
> The major changes compared to the 8.5.28 release are:
>
> - TLS stability improvements.
>
> - Correct a regression in the fix for 60276 that meant that compression
>   was applied to all MIME types.
>   Patch provided by Stefan Knoblich.
>
> - Add documentation for the Host Manager web application.
>   Patch provided by Marek Czernek.
>
> Along with lots of other bug fixes and improvements.
>
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.29/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1175/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc8.5.x/tags/TOMCAT_8_5_29/
>
> The proposed 8.5.29 release is:
> [ ] Broken - do not release
> [ ] Stable - go ahead and release as 8.5.29
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>



-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 9.0.6

[Huxing Zhang]

Hi,

The proposed 9.0.6 release is:
 [ ] Broken - do not release
 [X] Stable - go ahead and release as 9.0.6

Unit test passed.
Examples ok.
Test web application works fine.

On Mon, Mar 5, 2018 at 6:53 PM, Mark Thomas  wrote:
> The proposed Apache Tomcat 9.0.6 release is now available for voting.
>
> The major changes compared to the 9.0.5 release are:
>
> - TLS stability improvements.
>
> - Add the ability to specify static HTML responses for specific error
>   codes and/or exception types with the ErrorReportValve.
>
> - Add async HTTP/2 parser for NIO2.
>
> - Add documentation for the Host Manager web application.
>   Patch provided by Marek Czernek.
>
> Along with lots of other bug fixes and improvements.
>
> For full details, see the changelog:
> http://svn.apache.org/repos/asf/tomcat/trunk/webapps/docs/changelog.xml
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.6/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1174/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tags/TOMCAT_9_0_6/
>
> The proposed 9.0.6 release is:
> [ ] Broken - do not release
> [ ] Stable - go ahead and release as 9.0.6
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>



-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 8.5.28

[Huxing Zhang]

Hi,

The proposed 8.5.28 release is:
[ ] Broken - do not release
[ X ] Stable - go ahead and release as 8.5.28

Unit test passed.
Examples ok.
Our test web application works fine.

On Wed, Feb 7, 2018 at 7:33 AM, Mark Thomas  wrote:
> The proposed Apache Tomcat 8.5.28 release is now available for voting.
>
> The major changes compared to the 8.5.27 release are:
>
> - Fix truncated request input streams when using NIO2 with TLS.
>
> - Improved error handling and reporting for TLS configuration.
>
> - Enhance the JMX support for jdbc-pool in order to expose
>   PooledConnection and JdbcInterceptors.
>
> Along with lots of other bug fixes and improvements.
>
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.28/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1171/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc8.5.x/tags/TOMCAT_8_5_28/
>
> The proposed 8.5.28 release is:
> [ ] Broken - do not release
> [ ] Stable - go ahead and release as 8.5.28
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>



-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [Git migration] Merge strategy

[Huxing Zhang]

+1 on Option 1.
Our internal Tomcat fork has basically the same structure, and we use option 1.
I can't find an easy way to implement option 2.

On Tue, Jan 23, 2018 at 5:16 AM, Mark Thomas  wrote:
> The plan when we migrate to git is to migrate to single git repo with
> the following branches:
>
> master - 9.0.x development
> tc8.5  - 8.5.x development
> tc8.0  - 8.0.x development
> tc7.0  - 7.0.x development
>
> We need to decide how we are going to handle a fix that applies to
> multiple versions.
>
> I can see two options:
>
> 1. Make the change in master and cherry-pick as required to earlier
>versions. This is, essentially, what we do now in svn.
>
> 2. Make the change in the earliest applicable version and them merge
>forward. This appears to be the more natural git way of doing things.
>
> These options are based on my fairly limited understanding of git.
> Suggestions for other approaches welcome.
>
> Thoughts? Comments?
>
> Mark
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>



-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 8.5.27

[Huxing Zhang]

Hi, 

The proposed 8.5.27 release is:
[ ] Broken - do not release
[ X ] Stable - go ahead and release as 8.5.27

Unit test passed.
Examples ok.
Our test web application works fine.

--
Violeta Georgieva 
2018 Jan 21 (Sun) 22:21
Tomcat Developers List 
Re: [VOTE] Release Apache Tomcat 8.5.27


2018-01-18 22:43 GMT+02:00 Mark Thomas :
>
> The proposed Apache Tomcat 8.5.27 release is now available for voting.
>
> The major changes compared to the 8.5.24 release are:
>
> - Add support for GZIP compression with HTTP/2
>
> - Expand the TLS functionality exposed via the Manager application
>
> - Return a simple, plain text error message if a client attempts to make
>   a plain text HTTP connection to a TLS enabled NIO or NIO2 Connector.
>
> - Add a new system property
>   (org.apache.jasper.runtime.BodyContentImpl.BUFFER_SIZE) to control the
>   size of the buffer used by Jasper when buffering tag bodies.
>
>
> Along with lots of other bug fixes and improvements.
>
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.27/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1167/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc8.5.x/tags/TOMCAT_8_5_27/
>
> The proposed 8.5.27 release is:
> [ ] Broken - do not release
> [X] Stable - go ahead and release as 8.5.27

+1

Regards,
Violeta

Re: [VOTE] Release Apache Tomcat 7.0.84

[Huxing Zhang]

Hi

The proposed 7.0.84 release is:
[ ] Broken - do not release
[ X ] Stable - go ahead and release as 7.0.84 Stable

Unit test passed on Java 9.
Examples ok.
Our test web application works fine.

--
Violeta Georgieva 
2018 Jan 19 (Fri) 23:41
Tomcat Developers List 
[VOTE] Release Apache Tomcat 7.0.84


The proposed Apache Tomcat 7.0.84 release is now available for voting.

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.84/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1168/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_84/

The proposed 7.0.84 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 7.0.84 Stable

Regards,
Violeta

Re: [VOTE] Release Apache Tomcat 9.0.4

[Huxing Zhang]

Hi 

The proposed 9.0.4 release is:
[ ] Broken - do not release
[ ] Alpha  - go ahead and release as 9.0.4
[ ] Beta   - go ahead and release as 9.0.4
[ X ] Stable - go ahead and release as 9.0.4

Unit test all passed.
Examples ok.
Our test web application works fine.

--
Mark Thomas 
2018 Jan 19 (Fri) 04:14
Tomcat Developers List 
[VOTE] Release Apache Tomcat 9.0.4


The proposed Apache Tomcat 9.0.4 release is now available for voting.

The major changes compared to the 9.0.2 release are:

- Modify the Default and WebDAV Servlets so that a 405 status code is
  returned for PUT and DELETE requests when disabled via the readonly
  initialisation parameter.

- Add support for GZIP compression with HTTP/2

- Expand the TLS functionality exposed via the Manager application

- Return a simple, plain text error message if a client attempts to make
  a plain text HTTP connection to a TLS enabled NIO or NIO2 Connector.

Along with lots of other bug fixes and improvements.


For full details, see the changelog:
http://svn.apache.org/repos/asf/tomcat/trunk/webapps/docs/changelog.xml

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.4/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1166/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tags/TOMCAT_9_0_4/

The proposed 9.0.4 release is:
[ ] Broken - do not release
[ ] Alpha  - go ahead and release as 9.0.4
[ ] Beta   - go ahead and release as 9.0.4
[ ] Stable - go ahead and release as 9.0.4

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 9.0.3

[Huxing Zhang]

Hi,

The proposed 9.0.3 release is:
[ ] Broken - do not release
[ ] Alpha  - go ahead and release as 9.0.3
[ ] Beta   - go ahead and release as 9.0.3
[ X ] Stable - go ahead and release as 9.0.3

Unit test passed, except for one UT failure when running on Java 9 [1], which I 
am planning to investigate in the next few days.
Examples ok.
Our test web application works fine.

Re: Migrating to git

[Huxing Zhang]

Hi, 

I am +1 on migrating to git. I think this will help people easier to get 
involved.

One quick question to Plan A:
After migration to git, will the previous mirrors, e.g. 
https://github.com/apache/tomcat70, be removed?
 
We maintain an internal repository with selective tomcat versions, which depend 
on these mirrors to merge the latest releases.

--
Mark Thomas 
2017 Dec 6 (Wed) 04:03
Tomcat Developers List 
Migrating to git


Hi all,

I've been doing some experiments to see how we might migrate from our
current svn structure to git. It appears that git svn is able to follow
directory moves so, with that in mind, I'd like to propose the following
outline plan:

Plan A
==

0. Run plan past infra
1. Restructure svn
2. Get infra to re-mirror new structure
3. Validate mirror
4. Pick a date to switch

This assumes that we do want to switch to git. My sense from the most
recent discussion was that we did.

To expand on the point one, the restructuring would look like:

/trunk  -> no change
/tags/TOMCAT_9* -> tags/tc9.0.x/
/tc8.5.x/trunk  -> branches/tc8.5.x
/tc8.5.x/tags/* -> tags/tc8.5.x/
/tc8.0.x/trunk  -> branches/tc8.0.x
/tc8.0.x/tags/* -> tags/tc8.0.x/
/tc7.0.x/trunk  -> branches/tc7.0.x
/tc7.0.x/tags/* -> tags/tc7.0.x/

and then migrate /trunk, /tags and /branches to git, leaving the rest in
place. Most will stay there. Some components may move to git in the future.

Plan B
==

Pick a different component (native, jk) and migrate that first.


If we do want to migrate there will be lots of details to work out such
as how to migrate the "view differences" feature of the migration page
but I'm sure we'll be able to work something out.

Thoughts, comments etc.?

Mark

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 7.0.83

[Huxing Zhang]

Hi,

The proposed 7.0.83 release is:
[ ] Broken - do not release
[ X ] Stable - go ahead and release as 7.0.83 Stable

Unit test passed on JDK6
Examples: ok
Our test web application runs fine.

One thing that I want to confirm is:

I use Java 9 to build the source code, however it failed with the following 
message:

build:
[javac] Compiling 32 source files to 
/Users/huxing/work/apache-tomcat/tomcat7/trunk/output/jdbc-pool/classes
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.5
[javac] error: Source option 1.5 is no longer supported. Use 1.6 or later.
[javac] error: Target option 1.5 is no longer supported. Use 1.6 or later.

BUILD FAILED
/Users/huxing/work/apache-tomcat/tomcat7/trunk/build.xml:1077: The following 
error occurred while executing this line:
/Users/huxing/work/apache-tomcat/tomcat7/trunk/modules/jdbc-pool/build.xml:153: 
Compile failed; see the compiler error output for details.

I've checked the modules/jdbc-pool/build.properties.default, the default 
compile source/target level is 1.5.

Changing compile source/target to 1.6 will solve this issue.

However, the compile source/target of jdbc-pool conforms to the minimal Java 
version tomcat requires in tomcat 8 (1.7), tomcat 8.5 (1.7), and tomcat 9(1.8).

Therefore I think it might be a bug of tomcat 7. 



--
Violeta Georgieva 
2017 Dec 1 (Fri) 03:37
Tomcat Developers List 
[VOTE] Release Apache Tomcat 7.0.83


The proposed Apache Tomcat 7.0.83 release is now available for voting.

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.83/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1163/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_83/

The proposed 7.0.83 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 7.0.83 Stable

Regards,
Violeta

Re: [VOTE] Release Apache Tomcat 8.5.24

[Huxing Zhang]

Hi, 

The proposed 8.5.24 release is:
[ ] Broken - do not release
[ X ] Stable - go ahead and release as 8.5.24

Unit test passed.

Examples ok, except for the following one issue:
in example/servlets/index.html  "Servlet 4.0 Early Preview examples" is no 
longer early preview. (Fixed in r1816673)

Our test web application works fine.

--
Mark Thomas 
2017 Nov 27 (Mon) 21:46
Tomcat Developers List 
[VOTE] Release Apache Tomcat 8.5.24


The proposed Apache Tomcat 8.5.24 release is now available for voting.

The major changes compared to the 8.5.23 release are:

- Java 9 is fully supported

- Fixed a number of HTTP/2 issues

- Fixed numerous JASPIC issues with patches from Lazar

- Update the packaged version of the Tomcat Native Library to
  1.2.16 to pick up the latest Windows binaries built with
  APR 1.6.3 and OpenSSL 1.0.2m


Along with lots of other bug fixes and improvements.


It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.24/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1161/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc8.5.x/tags/TOMCAT_8_5_24/

The proposed 8.5.24 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 8.5.24

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: svn commit: r23327 - in /dev/tomcat/tomcat-8/v8.5.24/bin/embed: apache-tomcat-8.5.24-embed.tar.gz.sha512 apache-tomcat-8.5.24-embed.zip.sha512

[Huxing Zhang]

> Log:
> AAdd missing sha512 hashes


AAdd -> Add ?

--
markt 
2017 Nov 30 (Thu) 03:57
dev 
svn commit: r23327 - in /dev/tomcat/tomcat-8/v8.5.24/bin/embed: 
apache-tomcat-8.5.24-embed.tar.gz.sha512 apache-tomcat-8.5.24-embed.zip.sha512


Author: markt
Date: Wed Nov 29 19:57:15 2017
New Revision: 23327

Log:
AAdd missing sha512 hashes

Added:

dev/tomcat/tomcat-8/v8.5.24/bin/embed/apache-tomcat-8.5.24-embed.tar.gz.sha512
dev/tomcat/tomcat-8/v8.5.24/bin/embed/apache-tomcat-8.5.24-embed.zip.sha512

Added: 
dev/tomcat/tomcat-8/v8.5.24/bin/embed/apache-tomcat-8.5.24-embed.tar.gz.sha512
==
--- 
dev/tomcat/tomcat-8/v8.5.24/bin/embed/apache-tomcat-8.5.24-embed.tar.gz.sha512 
(added)
+++ 
dev/tomcat/tomcat-8/v8.5.24/bin/embed/apache-tomcat-8.5.24-embed.tar.gz.sha512 
Wed Nov 29 19:57:15 2017
@@ -0,0 +1 @@
+4c8478908ca844ea1f5b3c4e22d6def183d9e60da626c7070a43379967d9df43dcd8545426a3792a349a8e11ba38e9d4ea9e24cad11f1c130061bd5e2b33cd0e
 *apache-tomcat-8.5.24-embed.tar.gz
\ No newline at end of file

Added: 
dev/tomcat/tomcat-8/v8.5.24/bin/embed/apache-tomcat-8.5.24-embed.zip.sha512
==
--- dev/tomcat/tomcat-8/v8.5.24/bin/embed/apache-tomcat-8.5.24-embed.zip.sha512 
(added)
+++ dev/tomcat/tomcat-8/v8.5.24/bin/embed/apache-tomcat-8.5.24-embed.zip.sha512 
Wed Nov 29 19:57:15 2017
@@ -0,0 +1 @@
+90a3e5297b02ea11ccb4c7cce1bc909f9f8d67b3afc1b3876e3073570c4a7e272a6fb5d686631dd5ebc7bd438943e506761f37b2a6867b871ac7feeeb792fc39
 *apache-tomcat-8.5.24-embed.zip
\ No newline at end of file



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: svn commit: r1816544 - /tomcat/trunk/test/org/apache/tomcat/websocket/TestWebSocketFrameClient.java

[Huxing Zhang]

> It would be safer to use \u for non-ASCII characters in strings to
> avoid depending on IDE encoding preference.
> (\u00A3 for the pound currency character here.)

I agree. I will take that change.

--
Konstantin Kolinko 
2017 Nov 29 (Wed) 00:25
Tomcat Developers List 
Re: svn commit: r1816544 - 
/tomcat/trunk/test/org/apache/tomcat/websocket/TestWebSocketFrameClient.java


2017-11-28 17:04 GMT+03:00 Martin Grigorov :
> On Tue, Nov 28, 2017 at 3:52 PM,  wrote:
>
>> Author: huxing
>> Date: Tue Nov 28 13:52:58 2017
>> New Revision: 1816544
>>
>> URL: http://svn.apache.org/viewvc?rev=1816544=rev
>> Log:
>> Change file encoding to UTF-8
>>
>> Modified:
>> tomcat/trunk/test/org/apache/tomcat/websocket/
>> TestWebSocketFrameClient.java
>>
>> Modified: tomcat/trunk/test/org/apache/tomcat/websocket/
>> TestWebSocketFrameClient.java
>> URL: http://svn.apache.org/viewvc/tomcat/trunk/test/org/apache/
>> tomcat/websocket/TestWebSocketFrameClient.java?rev=1816544=1816543=
>> 1816544=diff
>> 
>> ==
>> --- 
>> tomcat/trunk/test/org/apache/tomcat/websocket/TestWebSocketFrameClient.java
>> (original)
>> +++ 
>> tomcat/trunk/test/org/apache/tomcat/websocket/TestWebSocketFrameClient.java
>> Tue Nov 28 13:52:58 2017
>> @@ -145,7 +145,7 @@ public class TestWebSocketFrameClient ex
>>  SecurityCollection collection = new SecurityCollection();
>>  collection.addPatternDecoded("/");
>>  String utf8User = "test";
>> -String utf8Pass = "123£";
>> +String utf8Pass = "123£";
>>
>
> The old value looked better.

It would be safer to use \u for non-ASCII characters in strings to
avoid depending on IDE encoding preference.
(\u00A3 for the pound currency character here.)

Though it is likely that we have already used UTF-8 chars elsewhere.

>>  tomcat.addUser(utf8User, utf8Pass);
>>  tomcat.addRole(utf8User, ROLE);
>>

Best regards,
Konstantin Kolinko

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 8.5.24

[Huxing Zhang]

Thanks, I will give it a try.

--
Konstantin Kolinko <knst.koli...@gmail.com>
2017 Nov 29 (Wed) 00:30
Tomcat Developers List <dev@tomcat.apache.org>; Huxing 
<huxing@alibaba-inc.com>
Re: [VOTE] Release Apache Tomcat 8.5.24


2017-11-28 18:08 GMT+03:00 Huxing Zhang <huxing@alibaba-inc.com>:
> Hi,
>
> I am wondering that is there any mirror of either of the following links:
>
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.24/

dist/dev has no mirrors, dist/release has many mirrors

> http://svn.apache.org/repos/asf/tomcat/tc8.5.x/tags/TOMCAT_8_5_24/

svn-us.apache.org, svn-eu.apache.org  (usable with https:),
formerly svn.us.apache.org, svn.eu.apache.org (causes certificate name
mismatch warning with https)

Tomcat 8.5 is also mirrored to Git

> Recently the download speed gets unbelievably slow, (sometimes <1KB/s)...


Best regards,
Konstantin Kolinko
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 8.5.24

[Huxing Zhang]

Hi, 

I am wondering that is there any mirror of either of the following links:

https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.24/
http://svn.apache.org/repos/asf/tomcat/tc8.5.x/tags/TOMCAT_8_5_24/

Recently the download speed gets unbelievably slow, (sometimes <1KB/s)...

--
Mark Thomas 
2017 Nov 27 (Mon) 21:46
Tomcat Developers List 
[VOTE] Release Apache Tomcat 8.5.24


The proposed Apache Tomcat 8.5.24 release is now available for voting.

The major changes compared to the 8.5.23 release are:

- Java 9 is fully supported

- Fixed a number of HTTP/2 issues

- Fixed numerous JASPIC issues with patches from Lazar

- Update the packaged version of the Tomcat Native Library to
  1.2.16 to pick up the latest Windows binaries built with
  APR 1.6.3 and OpenSSL 1.0.2m


Along with lots of other bug fixes and improvements.


It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.24/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1161/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc8.5.x/tags/TOMCAT_8_5_24/

The proposed 8.5.24 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 8.5.24

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: svn commit: r1816544 - /tomcat/trunk/test/org/apache/tomcat/websocket/TestWebSocketFrameClient.java

[Huxing Zhang]

Hi Martin,

As Mark said, there is something wrong with the text in the mailing list.
I changed the encoding because my laptop (default encoding as UTF-8) complains 
with the following error when compiling this class:

Error:(148, 31) java: unmappable character (0xA3) for encoding UTF-8

--
Mark Thomas 
2017 Nov 28 (Tue) 22:16
Tomcat Developers List 
Re: svn commit: r1816544 - 
/tomcat/trunk/test/org/apache/tomcat/websocket/TestWebSocketFrameClient.java


On 28/11/17 14:04, Martin Grigorov wrote:
> On Tue, Nov 28, 2017 at 3:52 PM,  wrote:
> 
>> Author: huxing
>> Date: Tue Nov 28 13:52:58 2017
>> New Revision: 1816544
>>
>> URL: http://svn.apache.org/viewvc?rev=1816544=rev
>> Log:
>> Change file encoding to UTF-8
>>
>> Modified:
>> tomcat/trunk/test/org/apache/tomcat/websocket/
>> TestWebSocketFrameClient.java
>>
>> Modified: tomcat/trunk/test/org/apache/tomcat/websocket/
>> TestWebSocketFrameClient.java
>> URL: http://svn.apache.org/viewvc/tomcat/trunk/test/org/apache/
>> tomcat/websocket/TestWebSocketFrameClient.java?rev=1816544=1816543=
>> 1816544=diff
>> 
>> ==
>> --- 
>> tomcat/trunk/test/org/apache/tomcat/websocket/TestWebSocketFrameClient.java
>> (original)
>> +++ 
>> tomcat/trunk/test/org/apache/tomcat/websocket/TestWebSocketFrameClient.java
>> Tue Nov 28 13:52:58 2017
>> @@ -145,7 +145,7 @@ public class TestWebSocketFrameClient ex
>>  SecurityCollection collection = new SecurityCollection();
>>  collection.addPatternDecoded("/");
>>  String utf8User = "test";
>> -String utf8Pass = "123£";
>> +String utf8Pass = "123£";
>>
> 
> The old value looked better.

It looks OK on my (UTF-8 by default) system. From memory something in
the svn diff -> mailing list process mangles UTF-8 text.

Mark


> 
> 
>>
>>  tomcat.addUser(utf8User, utf8Pass);
>>  tomcat.addRole(utf8User, ROLE);
>>
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: dev-h...@tomcat.apache.org
>>
>>
> 


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 9.0.2

[Huxing Zhang]

Hi, 

The proposed 9.0.2 release is:
[ ] Broken - do not release
[ ] Alpha  - go ahead and release as 9.0.2
[ X ] Beta   - go ahead and release as 9.0.2
[ ] Stable - go ahead and release as 9.0.2

Unit test passed on JDK8, but failed on JDK9:

Testsuite: org.apache.tomcat.util.scan.TestStandardJarScanner
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.397 sec

Testcase: testWebappClassPath took 0.276 sec
FAILED
Unexpected class loader type: jdk.internal.loader.ClassLoaders$AppClassLoader
junit.framework.AssertionFailedError: Unexpected class loader type: 
jdk.internal.loader.ClassLoaders$AppClassLoader
at 
org.apache.tomcat.util.scan.TestStandardJarScanner.testWebappClassPath(TestStandardJarScanner.java:74)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

Testcase: skipsInvalidClasspathURLNoFilePartNoFileScheme took 0.068 sec

This is because jdk.internal.loader.ClassLoaders$AppClassLoader is no longer a 
sub class or URLClassLoader from JDK9, I can't find a easy way to work it 
around except for using reflection.

Examples runs fine under both JDK8 and JDK9.

Our test web application runs fine on JDK8, but failed on JDK9 (it is not a 
tomcat issue.)

--
Mark Thomas 
2017 Nov 26 (Sun) 05:36
Tomcat Developers List 
[VOTE] Release Apache Tomcat 9.0.2


The proposed Apache Tomcat 9.0.2 release is now available for voting.

The major changes compared to the 9.0.1 release are:

- Java 9 is fully supported

- Fixed numerous JASPIC issues with patches from Lazar

- Update the packaged version of the Tomcat Native Library to
  1.2.16 to pick up the latest Windows binaries built with
  APR 1.6.3 and OpenSSL 1.0.2m

Along with lots of other bug fixes and improvements.


For full details, see the changelog:
http://svn.apache.org/repos/asf/tomcat/trunk/webapps/docs/changelog.xml

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.2/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1160/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tags/TOMCAT_9_0_2/

The proposed 9.0.2 release is:
[ ] Broken - do not release
[ ] Alpha  - go ahead and release as 9.0.2
[ ] Beta   - go ahead and release as 9.0.2
[ ] Stable - go ahead and release as 9.0.2

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: Java 9, modularisation and build systems

[Huxing Zhang]

Maven has another advantage that it provides a centralized repository for 
dependencies, which can be easily mirrored.
The current build process for Tomcat requires different repositories such as:
- apache.org(mirrors available)
- archive.apache.org(mirrors unavailable, access unstable)
- maven repo(mirrors available)
- sourceforge.net (mirrors available, access unstable)

which makes it incredibly slow for a clean build of tomcat in countries like 
China, making new comers difficult to start.
--
Mark Thomas 
2017 Oct 6 (Fri) 16:18
Tomcat Developers List 
Java 9, modularisation and build systems


Hi all,

As you have probably seen, I've been working on improving Java 9
support. The current TODO list is:

- module path scanning
- handling multi-release JARs in the JarScanner

I've been looking at the module path scanning and while there are
various approaches, they all make fairly heavy use of Java 9 APIs.
Implementing them via the existing JreCompat approach is going to
require a lot of reflection. That got me thinking about the obvious
alternative: multi-release JARs.

Handling multi-release JARs is going to require some changes / additions
to the build process and source layout. That reminded me of a comment
that Rémy made at TomcatCon in London regarding modularisation and build
tools and whether we wanted to do things differently. If we want to make
changes in that area it probably makes sense to make them now - hence
this e-mail.

Modularisation and build tools are inter-related so I think it makes
sense to discuss them together. Hence this thread.

I'm going to start with what I think is the easy one: Modularisation.

Tomcat is already modular. You can remove some features (JSP, WebSocket,
clustering?, store-config?) simply by removing the JARs. Do we want to
take this further? Nothing immediately springs to mind hence the fairly
open question: what changes could we implement to make Tomcat more
modular and how would those changes benefit our users?

The build tools aspect has, historically, been the area where fairly
strong opinions have been expressed.

The argument against Ant is that it isn't as well known amongst
prospective new contributors as other tools and hence creates a barrier
to contributing that harms the community. The argument for Ant is that
it works, it isn't causing any pain points and it has the flexibility to
handle all aspects of our build.

The usual candidate for an alternative build system is Maven. The
argument for Maven is that it is more widely known and hence easier to
get started with. The argument against is broadly that Maven is very
opinionated and they way Tomcat currently does things is not consistent
with what Maven expects and some things (e.g. the Windows installer) are
well outside the typical Maven build. Therefore switching to Maven would
require a fair amount of effort.

I'd like to suggest a third alternative: Gradle. The argument for Gradle
is that it can boot-strap itself so, unlike Ant, a new user doesn't need
to download the build tool. Gradle can also import Ant build files so we
could start with a simple Gradle script that simply imported the current
Ant script and then migrate slowly over time. The argument against is
that it isn't as widely known as Maven.


My own views are neutral at this point on modularisation. I don't have
any immediate suggestions for changes but I'd like to hear what ideas
others have. On build systems, I'm not convinced that the benefits of
switching to Maven justify the costs. Gradle looks promising and I do
like the boot-strapping feature. If there was consensus to move to
Gradle, I'd be willing to help that process.


Mark

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 7.0.82

[Huxing Zhang]

Hi

The proposed 7.0.82 release is:
[ ] Broken - do not release
[ X ] Stable - go ahead and release as 7.0.82 Stable

Unit test passed.
Test web application works fine.

--
Violeta Georgieva 
2017 Sep 29 (Fri) 21:16
Tomcat Developers List 
[VOTE] Release Apache Tomcat 7.0.82


The proposed Apache Tomcat 7.0.82 release is now available for voting.

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.82/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1158/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_82/

The proposed 7.0.82 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 7.0.82 Stable

Regards,
Violeta

Re: [VOTE] Release Apache Tomcat 8.5.23

[Huxing Zhang]

Hi,

The proposed 8.5.23 release is:
[ ] Broken - do not release
[ X ] Stable - go ahead and release as 8.5.23

* Unit test passed.
* Test web application works fine.
* Tested clean tomcat running under JDK9: ok, but with following message during 
stop:
29-Sep-2017 20:36:09.474 INFO [Thread-3] 
org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler 
["http-nio-8180"]
29-Sep-2017 20:36:09.532 INFO [Thread-3] 
org.apache.catalina.core.StandardService.stopInternal Stopping service 
[Catalina]
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
org.apache.catalina.loader.WebappClassLoaderBase 
(file:/home/admin/tomcat/apache-tomcat80/svn/8.5.23/output/build/lib/catalina.jar)
 to field java.lang.Thread.threadLocals
WARNING: Please consider reporting this to the maintainers of 
org.apache.catalina.loader.WebappClassLoaderBase
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
* Tested clean tomcat running under JDK9: ok, but with the same warning message 
shown above

--
Mark Thomas 
2017 Sep 28 (Thu) 19:21
Tomcat Developers List 
[VOTE] Release Apache Tomcat 8.5.23


The proposed Apache Tomcat 8.5.23 release is now available for voting.

The major changes compared to the 8.5.21 release are:

- Fix CVE-2017-12617

- Add ExtractingRoot, a new WebResourceRoot implementation that extracts
  JARs to the work directory for improved performance when deploying
  packed WAR files.

Along with lots of other bug fixes and improvements.


It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.23/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1157/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc8.5.x/tags/TOMCAT_8_5_23/

The proposed 8.5.23 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 8.5.23

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 9.0.1

[Huxing Zhang]

Hi,

The proposed 9.0.1 release is:
[ ] Broken - do not release
[ ] Alpha  - go ahead and release as 9.0.1
[ X  ] Beta   - go ahead and release as 9.0.1
[ ] Stable - go ahead and release as 9.0.1

Unit test passed.
Test web application works fine.
Tested clean tomcat running on JDK9: ok
Tested clean tomcat running on JDK9 with security manager: ok
--
Mark Thomas 
2017 Sep 28 (Thu) 02:43
Tomcat Developers List 
[VOTE] Release Apache Tomcat 9.0.1


The proposed Apache Tomcat 9.0.1 release is now available for voting.

The major changes compared to the 9.0.0.M27 release are:

- Fix CVE-2017-12617

- Servlet 4.0 implementation is complete

- Add the ability to reconfigure TLS connectors at runtime without
  stopping the connector

- Stricter validation of the Host header

Along with lots of other bug fixes and improvements.


For full details, see the changelog:
http://svn.apache.org/repos/asf/tomcat/trunk/webapps/docs/changelog.xml

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.1/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1156/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tags/TOMCAT_9_0_1/

The proposed 9.0.1 release is:
[ ] Broken - do not release
[ ] Alpha  - go ahead and release as 9.0.1
[ ] Beta   - go ahead and release as 9.0.1
[ ] Stable - go ahead and release as 9.0.1

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [PROPOSAL] Deprecate and eventually remove the o.a.c.servlet4preview package in 8.5.x

[Huxing Zhang]

+1 to remove the preview packages.

--
Mark Thomas 
2017 Sep 28 (Thu) 03:08
Tomcat Developers List 
[PROPOSAL] Deprecate and eventually remove the o.a.c.servlet4preview package in 
8.5.x


All,

I'd like to propose removing this for the following reasons:

1. Now the Servlet 4.0 spec is final, users can use Tomcat 9 for Servlet
4.0 features.

2. The preview is not complete and may be out of date in places.

3. I'm not aware of any user feedback so usage seems to be very low.

My proposal is to deprecate it now with the intention to remove it after
a year.

As an alternative is deprecate it now with the intention to remove it 1
year after the first stable 9.0.x release.

Thoughts? Comments? Questions?

Mark

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 8.5.22

[Huxing Zhang]

Hi,

The proposed 8.5.22 release is:
[ ] Broken - do not release
[ X ] Stable - go ahead and release as 8.5.22

Unit test passed.
Tested on our web application and it works fine.

--
Mark Thomas 
2017 Sep 23 (Sat) 04:34
Tomcat Developers List 
[VOTE] Release Apache Tomcat 8.5.22


The proposed Apache Tomcat 8.5.22 release is now available for voting.

The major changes compared to the 8.5.21 release are:

- Fix CVE-2017-12617

- Add ExtractingRoot, a new WebResourceRoot implementation that extracts
  JARs to the work directory for improved performance when deploying
  packed WAR files.

Along with lots of other bug fixes and improvements.


It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.22/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1155/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc8.5.x/tags/TOMCAT_8_5_22/

The proposed 8.5.22 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 8.5.22

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 9.0.0.M27

[Huxing Zhang]

Hi, here is my test result,  although the vote has finished:

The proposed 9.0.0.M27 release is:
[ ] Broken - do not release
[ X ] Alpha - go ahead and release as 9.0.0.M27

Unit test passed.
Our web application works fine.
--
Mark Thomas 
2017 Sep 14 (Thu) 02:49
Tomcat Developers List 
[VOTE] Release Apache Tomcat 9.0.0.M27


The proposed Apache Tomcat 9.0.0.M27 release is now available for voting.

This is a milestone release for the 9.0.x branch. It should be
noted that, as a milestone release:
- Servlet 4.0 is not finalised
- It is not known if there will be a minor maintenance release for
  JSP 2.4, EL 3.1 or WebSocket 1.2

The major changes compared to the 9.0.0.M26 release are:

- Additional capabilities for the CGI Servlet. Based on patches provided
  by jm009.

- Added support for the OpenSSL SSL_CONF API. To support this the
  minimum required Tomcat Native version is 1.2.14.

Along with lots of other bug fixes and improvements.


For full details, see the changelog:
http://svn.apache.org/repos/asf/tomcat/trunk/webapps/docs/changelog.xml

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.0.M27/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1152/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tags/TOMCAT_9_0_0_M27/

The proposed 9.0.0.M27 release is:
[ ] Broken - do not release
[ ] Alpha - go ahead and release as 9.0.0.M27

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 7.0.81

[Huxing Zhang]

Hi
The proposed 7.0.81 release is:
[ ] Broken - do not release
[ X ] Stable - go ahead and release as 7.0.81 Stable

Unit test passed.
Our test web application works fine.

--
Violeta Georgieva 
2017 Aug 11 (Fri) 19:14
Tomcat Developers List 
[VOTE] Release Apache Tomcat 7.0.81


The proposed Apache Tomcat 7.0.81 release is now available for voting.

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.81/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1151/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_81/

The proposed 7.0.81 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 7.0.81 Stable

Regards,
Violeta

Re: [VOTE] Release Apache Tomcat 8.5.20

[Huxing Zhang]

Hi,

The proposed 8.5.20 release is:
[ ] Broken - do not release
[ X ] Stable - go ahead and release as 8.5.20

Unit test passed.
Our test web application works fine.

--
From:Mark Thomas 
Time:2017 Aug 3 (Thu) 06:10
To:Tomcat Developers List 
Subject:[VOTE] Release Apache Tomcat 8.5.20


The proposed Apache Tomcat 8.5.20 release is now available for voting.

The major changes compared to the 8.5.16 release are:

- Enable TLS connectors to use Java key stores that contain multiple
  keys where each key has a separate password. Based on a patch by Frank
  Taffelt.

- Make asynchronous error handling more robust. In particular ensure
  that onError() is called for any registered AsyncListeners after an
  I/O error on a non-container thread.

- Sync SSL session access for the APR connector to prevent errors when
  accessing the session.


Along with lots of other bug fixes and improvements.


It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.20/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1148/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc8.5.x/tags/TOMCAT_8_5_20/

The proposed 8.5.20 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 8.5.20

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 9.0.0.M25

[Huxing Zhang]

The proposed 9.0.0.M25 release is:
[ ] Broken - do not release
[ X ] Alpha - go ahead and release as 9.0.0.M25

Unit test passed.
Our test web application runs fine.

--
From:Mark Thomas 
Time:2017 Jul 25 (Tue) 07:19
To:Tomcat Developers List 
Subject:[VOTE] Release Apache Tomcat 9.0.0.M25


The proposed Apache Tomcat 9.0.0.M25 release is now available for voting.

This is a milestone release for the 9.0.x branch. It should be
noted that, as a milestone release:
- Servlet 4.0 is not finalised
- The EGs have not started work on JSP 2.4, EL 3.1 or WebSocket 1.2/2.0

Note that the 9.0.0.M23 and 9.0.0.M24 release votes were cancelled due
to regressions.

The major changes compared to the 9.0.0.M22 release are:

- Correct a regression in 9.0.0.M22 that prevented Tomcat from shutting
  down cleanly.

- Add LoadBalancerDrainingValve, a Valve designed to reduce the amount
  of time required for a node to drain its authenticated users.

- When generating JSP runtime error messages that quote the relevant JSP
  source code, switch from using the results of the JSP page parsing
  process to using the JSR 045 source map data to identify the correct
  part of the JSP source from the stack trace. This significantly
  reduces the memory footprint of Jasper in development mode, provides a
  small performance improvement for error page generation and enables
  source quotes to continue to be provided after a Tomcat restart.

- Add support for a Tomcat specific deployment descriptor,
  /WEB-INF/tomcat-web.xml

- Add ExtractingRoot, a new WebResourceRoot implementation that extracts
  JARs to the work directory for improved performance when deploying
  packed WAR files.

Along with lots of other bug fixes and improvements.


For full details, see the changelog:
http://svn.apache.org/repos/asf/tomcat/trunk/webapps/docs/changelog.xml

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.0.M25/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1145/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tags/TOMCAT_9_0_0_M25/

The proposed 9.0.0.M25 release is:
[ ] Broken - do not release
[ ] Alpha - go ahead and release as 9.0.0.M25

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 9.0.0.M24

[Huxing Zhang]

The proposed 9.0.0.M24 release is:
[ ] Broken - do not release
[ X ] Alpha - go ahead and release as 9.0.0.M24

Unit test passed.
Our test web application runs fine.
New feature tomcat-web.xml works fine.

--
From:Mark Thomas 
Time:2017 Jul 18 (Tue) 19:43
To:Tomcat Developers List 
Subject:[VOTE] Release Apache Tomcat 9.0.0.M24


The proposed Apache Tomcat 9.0.0.M24 release is now available for voting.

This is a milestone release for the 9.0.x branch. It should be
noted that, as a milestone release:
- Servlet 4.0 is not finalised
- The EGs have not started work on JSP 2.4, EL 3.1 or WebSocket 1.2/2.0

Note that the 9.0.0.M23 release vote was cancelled due to a regression.

The major changes compared to the 9.0.0.M22 release are:

- Correct a regression in 9.0.0.M22 that prevented Tomcat from shutting
  down cleanly.

- Add LoadBalancerDrainingValve, a Valve designed to reduce the amount
  of time required for a node to drain its authenticated users.

- When generating JSP runtime error messages that quote the relevant JSP
  source code, switch from using the results of the JSP page parsing
  process to using the JSR 045 source map data to identify the correct
  part of the JSP source from the stack trace. This significantly
  reduces the memory footprint of Jasper in development mode, provides a
  small performance improvement for error page generation and enables
  source quotes to continue to be provided after a Tomcat restart.

- Add support for a Tomcat specific deployment descriptor,
  /WEB-INF/tomcat-web.xml

Along with lots of other bug fixes and improvements.


For full details, see the changelog:
http://svn.apache.org/repos/asf/tomcat/trunk/webapps/docs/changelog.xml

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.0.M24/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1143/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tags/TOMCAT_9_0_0_M24/

The proposed 9.0.0.M24 release is:
[ ] Broken - do not release
[ ] Alpha - go ahead and release as 9.0.0.M24

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Incorrect tag name "TONCAT_9_0_0_M23" in github mirror

[Huxing Zhang]

Hi,

I've noticed that there is a incorrect tag name "TONCAT_9_0_0_M23"  in github 
mirror:

https://github.com/apache/tomcat/tree/TONCAT_9_0_0_M23

I've checked the svn repo, looks like it has been corrected already:

https://svn.apache.org/viewvc/tomcat/tags/

It seems that the change in svn repo is not synced to github mirror.

Any idea how to fix that?
---
Thanks,
Huxing

Re: [VOTE] Release Apache Tomcat 8.5.17

[Huxing Zhang]

Hi,

The proposed 8.5.17 release is:
[ ] Broken - do not release
[ X ] Stable - go ahead and release as 8.5.17

Unit test passed.
Our test web application works fine.
--
From:Mark Thomas 
Time:2017 Jul 4 (Tue) 16:40
To:Tomcat Developers List 
Subject:[VOTE] Release Apache Tomcat 8.5.17


The proposed Apache Tomcat 8.5.17 release is now available for voting.

The major changes compared to the 8.5.17 release are:

- Make asynchronous error handling more robust. In particular ensure
  that onError() is called for any registered AsyncListeners after an
  I/O error on a non-container thread.

- Correct a regression in 9.0.0.M22 that prevented Tomcat from shutting
  down cleanly.

- Sync SSL session access for the APR connector to prevent errors when
  accessing the session.


Along with lots of other bug fixes and improvements.


It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.17/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1142/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc8.5.x/tags/TOMCAT_8_5_17/

The proposed 8.5.17 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 8.5.17

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 9.0.0.M23

[Huxing Zhang]

Hi,

The proposed 9.0.0.M23 release is:
[ ] Broken - do not release
[ X ] Alpha - go ahead and release as 9.0.0.M23

Unit test passed.
Our test web app works fine.

--
From:Mark Thomas 
Time:2017 Jul 4 (Tue) 16:19
To:Tomcat Developers List 
Subject:[VOTE] Release Apache Tomcat 9.0.0.M23


The proposed Apache Tomcat 9.0.0.M23 release is now available for voting.

This is a milestone release for the 9.0.x branch. It should be
noted that, as a milestone release:
- Servlet 4.0 is not finalised
- The EGs have not started work on JSP 2.4, EL 3.1 or WebSocket 1.2/2.0

The major changes compared to the 9.0.0.M22 release are:

- Correct a regression in 9.0.0.M22 that prevented Tomcat from shutting
  down cleanly.

- Add LoadBalancerDrainingValve, a Valve designed to reduce the amount
  of time required for a node to drain its authenticated users.

- When generating JSP runtime error messages that quote the relevant JSP
  source code, switch from using the results of the JSP page parsing
  process to using the JSR 045 source map data to identify the correct
  part of the JSP source from the stack trace. This significantly
  reduces the memory footprint of Jasper in development mode, provides a
  small performance improvement for error page generation and enables
  source quotes to continue to be provided after a Tomcat restart.

Along with lots of other bug fixes and improvements.


For full details, see the changelog:
http://svn.apache.org/repos/asf/tomcat/trunk/webapps/docs/changelog.xml

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.0.M23/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1141/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tags/TOMCAT_9_0_0_M23/

The proposed 9.0.0.M23 release is:
[ ] Broken - do not release
[ ] Alpha - go ahead and release as 9.0.0.M23

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: ApacheCon slides with .odp extension

[Huxing Zhang]

Hi Chris,

Works for me, thanks!

--
From:Christopher Schultz <ch...@christopherschultz.net>
Time:2017 Jul 5 (Wed) 23:47
To:dev <dev@tomcat.apache.org>
Subject:Re: ApacheCon slides with .odp extension


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Huxing,

On 6/20/17 10:48 PM, Huxing Zhang wrote:
> These two pdf files are not accessible to me: 
> http://people.apache.org/~schultz/ApacheCon%20NA%202017/Let's%20Encryp
t%20Apache%20Tomcat.pdf
>
> 
http://people.apache.org/~schultz/ApacheCon%20NA%202017/Seamless%20Upgra
des%20for%20Credential%20Security%20in%20Apache%20Tomcat.pdf
> 
> I got 403 FORBIDDEN for the above links.

Apologies for the late reply: the permissions on these files have been
corrected.

I'm also going to be changing the public URLs to the presentations to
be the .pdf versions.

Thanks,
- -chris

> -- 
> From:Christopher Schultz <ch...@christopherschultz.net> Time:2017
> Jun 21 (Wed) 02:05 To:dev <dev@tomcat.apache.org> Subject:Re:
> ApacheCon slides with .odp extension
> 
> 
> Huxing,
> 
> On 6/16/17 1:40 AM, Huxing Zhang wrote:
>> Hi
>> 
>> I have noticed that some of the ApacheCon slides are in .odp
>> format:
>> 
>> 
> http://people.apache.org/~schultz/ApacheCon%20NA%202017/Seamless%20Upg
rades%20for%20Credential%20Security%20in%20Apache%20Tomcat.odp
>>
>
> 
http://people.apache.org/~schultz/ApacheCon%20NA%202017/Let's%20Encrypt%
20Apache%20Tomcat.odp
>> 
>> The .odp format does not work for me because it is for OpenOffice
>> (I
> don't have OpenOffice installed on my Mac OS), and neither Pages
> and Microsoft PowerPoint could open it.
>> 
>> I am wondering that should it be convert it to a more universal
>> format
> like pdf, so that more people can open it without any confusion.
> 
> Sorry about that... I usually convert to PDF as well. Looks like I
> idn't do it in this case. I've published the PDF versions in the
> same directory.
> 
> Thanks, -chris 
> -
>
> 
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
> 
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJZXQoOAAoJEBzwKT+lPKRYkssP/j14YbaWsJoiu+2nNKKTnYRv
Phj40Fw0DjnnuUEocFn9eVzYsC+MO2Rga4jjRTgWpavAEdyuZntC0vD1M9j7NY1Z
w6gZP+F5H3x3VnJgVJBrikPZKxHkivJaFHLWl/zxQEPOeNxPlVuj6M0eBsuditcU
vDvrmGtL/XscWvUaSHgWF7oIZLxJJXx2AqmQojQbUkXweW97J2/TblZaiDH9CfRF
a4NOqWtpeZzvxXSYu2CBVlK91XxmWmYqYha2/SpbCiX1IUDQjEBWFcomk07ba4mg
vBJwt9IR0dOyGQ0jxzgrdjH7H1GxGj6lIcTSlt9yIDVSyViAL/TBFPzLdQPzqAAy
V4RePhhVg+h1VFn1QhxChFgJ0A79hQZwEQTTwuhrVLTa+liBG0OeEm3z+aImYg0f
N1/XMQ4jW22hGu3SaGHCo37AlkEYTewfhNZ6no9aKlvtDjH+yRKJBphbJ0pp3flY
GC4J5u6jkrOrkyBNvFykcbtKMMs2fCBacCRdrmhKdXkqq/ZaJhZGTuoMqjCTZAvM
ij39Nyp4/UnvC3LvjYsAK+fBlBZTLUvKuJrCZDcO6ah9d7ELD/k/UxMPOmwb0ETD
GWYpQQphF2cu4x40041A50weP1WKSeQOV4aoKKbnGahgrWJ3GhC5QzPQBENyO1PY
k3t0e/ua53ASYTt9jZUy
=7eVk
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 7.0.79

[Huxing Zhang]

Hi,

The proposed 7.0.79 release is:
[ ] Broken - do not release
[ X ] Stable - go ahead and release as 7.0.79 Stable

Unit test passed.
Test web application works fine.

--
From:Violeta Georgieva 
Time:2017 Jun 27 (Tue) 01:22
To:Tomcat Developers List 
Subject:[VOTE] Release Apache Tomcat 7.0.79


The proposed Apache Tomcat 7.0.79 release is now available for voting.

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.79/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1139/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_79/

The proposed 7.0.79 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 7.0.79 Stable

Regards,
Violeta
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] 8.0.x EOL - 30 June 2018

[Huxing Zhang]

Hi,

The main reason is RFC6265 is released after IE9, and IE9 is still in our 
supported browser list (though not recommended). 
I'm personally fine with using LegacyCookieProcessor instead of 
RFC6265CookieProcessor for LEGACY issues.
However, it is not easy for an embedded Tomcat in an Spring-boot application to 
switch RFC6265CookieProcessor to LegacyCookieProcessor, unless we change the 
Spring-boot code.
I am thinking of adding an system property, e.g. 
"org.apache.tomcat.util.http.CookieProcessor", to make the process easier.

--
From:Mark Thomas <ma...@apache.org>
Time:2017 Jun 26 (Mon) 17:55
To:Tomcat Developers List <dev@tomcat.apache.org>
Subject:Re: [VOTE] 8.0.x EOL - 30 June 2018


On 26/06/17 03:19, Huxing Zhang wrote:
>> The only thing I can think of is lack of support for the BIO connectors.
>> I have an easy fix for that if there is interest. Anything else?
> 
> Also the RFC6265CookieProcessor.  We've experienced several incompatibility 
> with LegacyCookieProcessor.
> For example,  cookies with leading dot is no longer valid in 
> RFC6265CookieProcessor.

Since RFC6265 is clear that the leading '.' should not be there, I'm
reluctant to introduce a change to allow it. Unsurprisingly, it is IE
that needs the leading '.' in some cases.

We have made exceptions for IE in the past. Do we want to do that here?
LegacyCookieProcessor remains an option for those that need to support
this particular quirk of IE.

Personally, I'd prefer not to introduce a new option but I could be
persuaded to support such a change if there was sufficient demand.

Mark


> --
> From:Mark Thomas <ma...@apache.org>
> Time:2017 Jun 24 (Sat) 23:26
> To:Tomcat Developers List <dev@tomcat.apache.org>
> Subject:Re: [VOTE] 8.0.x EOL - 30 June 2018
> 
> 
> On 23/06/17 23:17, Emmanuel Bourg wrote:
>> Le 23/06/2017 à 21:15, Christopher Schultz a écrit :
>>
>>> The idea was to encourage package repository maintainers to migrate to
>>> Tomcat 8.5. If we never sundown Tomcat 8.0, they'll never move (witness
>>> the presence of Tomcat 6.0 still lurking around half the Internet).
>>
>> As far as Debian is concerned, the migration to Tomcat 8.5 did happen in
>> Debian 9. But Debian 8 users are stuck with Tomcat 8.0.x until June
>> 2020. Tomcat 8.5 isn't a drop-in replacement for Tomcat 8.0
>> unfortunately, so it's a bit difficult to push this upgrade in a stable
>> distribution.
> 
> If 8.5.x was a drop-in replacement would that make a difference?
> 
> And as a follow-up, what would need to change so 8.5.x was viewed a
> drop-in replacement?
> 
> The only thing I can think of is lack of support for the BIO connectors.
> I have an easy fix for that if there is interest. Anything else?
> 
> Mark
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] 8.0.x EOL - 30 June 2018

[Huxing Zhang]

> The only thing I can think of is lack of support for the BIO connectors.
> I have an easy fix for that if there is interest. Anything else?

Also the RFC6265CookieProcessor.  We've experienced several incompatibility 
with LegacyCookieProcessor.
For example,  cookies with leading dot is no longer valid in 
RFC6265CookieProcessor.
--
From:Mark Thomas 
Time:2017 Jun 24 (Sat) 23:26
To:Tomcat Developers List 
Subject:Re: [VOTE] 8.0.x EOL - 30 June 2018


On 23/06/17 23:17, Emmanuel Bourg wrote:
> Le 23/06/2017 à 21:15, Christopher Schultz a écrit :
> 
>> The idea was to encourage package repository maintainers to migrate to
>> Tomcat 8.5. If we never sundown Tomcat 8.0, they'll never move (witness
>> the presence of Tomcat 6.0 still lurking around half the Internet).
> 
> As far as Debian is concerned, the migration to Tomcat 8.5 did happen in
> Debian 9. But Debian 8 users are stuck with Tomcat 8.0.x until June
> 2020. Tomcat 8.5 isn't a drop-in replacement for Tomcat 8.0
> unfortunately, so it's a bit difficult to push this upgrade in a stable
> distribution.

If 8.5.x was a drop-in replacement would that make a difference?

And as a follow-up, what would need to change so 8.5.x was viewed a
drop-in replacement?

The only thing I can think of is lack of support for the BIO connectors.
I have an easy fix for that if there is interest. Anything else?

Mark


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 8.5.16

[Huxing Zhang]

Hi, 

The proposed 8.5.16 release is:
[ ] Broken - do not release
[ X ] Stable - go ahead and release as 8.5.16

Unit test passed.
Our test web application works fine.

--
From:Mark Thomas 
Time:2017 Jun 22 (Thu) 05:37
To:Tomcat Developers List 
Subject:[VOTE] Release Apache Tomcat 8.5.16


The proposed Apache Tomcat 8.5.16 release is now available for voting.

The major changes compared to the 8.5.16 release are:

- Add a new JULI FileHandler configuration for specifying the maximum
  number of days to keep the log files. By default the log files will be
  kept 90 days.

- Improvements to enable the Manager and HostManager to work in the
  default configuration when working under a security manager

- Introduce new API o.a.tomcat.websocket.WsSession#suspend/
  o.a.tomcat.websocket.WsSession#resume that can be used to
  suspend/resume reading of the incoming messages.


It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.16/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1138/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc8.5.x/tags/TOMCAT_8_5_16/

The proposed 8.5.16 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 8.5.16

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: svn commit: r1799653 - /tomcat/trunk/test/org/apache/coyote/http2/TestStream.java

[Huxing Zhang]

Mark, thanks for the fix!

> On 23 Jun 2017, at 18:29, ma...@apache.org wrote:
> 
> Author: markt
> Date: Fri Jun 23 10:29:56 2017
> New Revision: 1799653
> 
> URL: http://svn.apache.org/viewvc?rev=1799653=rev
> Log:
> Fixing typo (r1799648) changed response body length so test needed to be 
> updated.
> 
> Modified:
>tomcat/trunk/test/org/apache/coyote/http2/TestStream.java
> 
> Modified: tomcat/trunk/test/org/apache/coyote/http2/TestStream.java
> URL: 
> http://svn.apache.org/viewvc/tomcat/trunk/test/org/apache/coyote/http2/TestStream.java?rev=1799653=1799652=1799653=diff
> ==
> --- tomcat/trunk/test/org/apache/coyote/http2/TestStream.java (original)
> +++ tomcat/trunk/test/org/apache/coyote/http2/TestStream.java Fri Jun 23 
> 10:29:56 2017
> @@ -115,7 +115,7 @@ public class TestStream extends Http2Tes
> "3-Header-[content-type]-[text/plain;charset=UTF-8]\n" +
> "3-Header-[date]-[Wed, 11 Nov 2015 19:18:42 GMT]\n" +
> "3-HeadersEnd\n" +
> -"3-Body-43\n" +
> +"3-Body-44\n" +
> "3-HeadersStart\n" +
> "3-Header-[x-trailer-2]-[Trailer value two]\n" +
> "3-Header-[x-trailer-1]-[Trailer value one]\n" +
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
> 

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] 8.0.x EOL - 30 June 2018

[Huxing Zhang]

[ X ] +1 We should announce 8.0.x EOL for 30 June 2018

--
From:Mark Thomas 
Time:2017 Jun 22 (Thu) 23:18
To:Tomcat Developers List 
Subject:[VOTE] 8.0.x EOL - 30 June 2018


We had a couple of threads discussing this. I think it is time for a vote.

[ ] +1 We should announce 8.0.x EOL for 30 June 2018
[ ] -1 We should announce 8.0.x EOL for [insert date here]
[ ] -1 We should not announce 8.0.x EOL at this time

Thanks,

Mark

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 9.0.0.M22

[Huxing Zhang]

Hi,

The proposed 9.0.0.M22 release is:
[ ] Broken - do not release
[ X ] Alpha - go ahead and release as 9.0.0.M22

Unit test passed.
Our test web application works fine.

1. There is a typo in trailers.ResponseTrailers, I will fix that later.
2. Actually I have a concern of the trailer field implementation. Should we add 
an extra whitespace between the trailer field name and trailer field, just to 
keep align with the head field format?

In rfc7230 section 4.1.2 says the white space is optional.
header-field   = field-name ":" OWS field-value OWS

But right now the format is inconsistent between header and trailer field.

Examples: 

Escape character is '^]'.
GET /examples/servlets/trailers/response HTTP/1.1
Host: hsf.taobao.net:8180
User-Agent: curl/7.47.0
Accept: */*

HTTP/1.1 200
Content-Type: text/plain;charset=UTF-8
Transfer-Encoding: chunked
Date: Fri, 23 Jun 2017 05:49:14 GMT

2b
This reponse should include trailer fields.
0
x-trailer-2:Trailer value two
x-trailer-1:Trailer value one

BTW, Jetty[1] has an white space between trailer field name and value. 
https://webtide.com/http-trailers-in-jetty/

--
From:Mark Thomas 
Time:2017 Jun 21 (Wed) 22:18
To:Tomcat Developers List 
Subject:[VOTE] Release Apache Tomcat 9.0.0.M22


The proposed Apache Tomcat 9.0.0.M22 release is now available for voting.

This is a milestone release for the 9.0.x branch. It should be
noted that, as a milestone release:
- Servlet 4.0 is not finalised
- The EGs have not started work on JSP 2.4, EL 3.1 or WebSocket 1.2/2.0

The major changes compared to the 9.0.0.M21 release are:

- Add a new JULI FileHandler configuration for specifying the maximum
  number of days to keep the log files. By default the log files will be
  kept 90 days.

- Update the Servlet 4.0 implementation to add support for setting
  trailer fields for HTTP responses.

- When pre-compiling with JspC, report all compilation errors rather
  than stopping after the first error.

Along with lots of other bug fixes and improvements

For full details, see the changelog:
http://svn.apache.org/repos/asf/tomcat/trunk/webapps/docs/changelog.xml

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.0.M22/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1137/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tags/TOMCAT_9_0_0_M22/

The proposed 9.0.0.M22 release is:
[ ] Broken - do not release
[ ] Alpha - go ahead and release as 9.0.0.M22

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: ApacheCon slides with .odp extension

[Huxing Zhang]

Chris,

These two pdf files are not accessible to me:
http://people.apache.org/~schultz/ApacheCon%20NA%202017/Let's%20Encrypt%20Apache%20Tomcat.pdf
http://people.apache.org/~schultz/ApacheCon%20NA%202017/Seamless%20Upgrades%20for%20Credential%20Security%20in%20Apache%20Tomcat.pdf

I got 403 FORBIDDEN for the above links.

--
From:Christopher Schultz <ch...@christopherschultz.net>
Time:2017 Jun 21 (Wed) 02:05
To:dev <dev@tomcat.apache.org>
Subject:Re: ApacheCon slides with .odp extension


Huxing,

On 6/16/17 1:40 AM, Huxing Zhang wrote:
> Hi
>
> I have noticed that some of the ApacheCon slides are in .odp format:
>
>
http://people.apache.org/~schultz/ApacheCon%20NA%202017/Seamless%20Upgrades%20for%20Credential%20Security%20in%20Apache%20Tomcat.odp
>
http://people.apache.org/~schultz/ApacheCon%20NA%202017/Let's%20Encrypt%20Apache%20Tomcat.odp
>
> The .odp format does not work for me because it is for OpenOffice (I
don't have OpenOffice installed on my Mac OS), and neither Pages and
Microsoft PowerPoint could open it.
>
> I am wondering that should it be convert it to a more universal format
like pdf, so that more people can open it without any confusion.

Sorry about that... I usually convert to PDF as well. Looks like I idn't
do it in this case. I've published the PDF versions in the same directory.

Thanks,
-chris

ApacheCon slides with .odp extension

[Huxing Zhang]

Hi

I have noticed that some of the ApacheCon slides are in .odp format:

http://people.apache.org/~schultz/ApacheCon%20NA%202017/Seamless%20Upgrades%20for%20Credential%20Security%20in%20Apache%20Tomcat.odp
http://people.apache.org/~schultz/ApacheCon%20NA%202017/Let's%20Encrypt%20Apache%20Tomcat.odp

The .odp format does not work for me because it is for OpenOffice (I don't have 
OpenOffice installed on my Mac OS), and neither Pages and Microsoft PowerPoint 
could open it.

I am wondering that should it be convert it to a more universal format like 
pdf, so that more people can open it without any confusion.

Thanks,
Huxing

Re: [Bug 61105] Roll log files by default

[Huxing Zhang]

Hi,

> There was no concern expressed about the log files that are currently not
> rolled (generally, I suspect, because well written apps won;t trigger content
> to those files).

We do have concerns about rotate the output to stdout/stderr.
In most of our cases, this is due to logging framework conflict between log4j 
and logback in a web application.
The default behavior is that all the logging content are eventually gone to 
catalina.out.
Most of the users even won't be aware of it, until being alerted by running out 
of the disk space (The web application may run for months).

To avoid this, we actually have implemented a feature in Tomcat to rotate 
catalina.out on a daily basis.
Under the hood we use a customized PrintStream to replace 
System.out/System.err, capture the content, and output to JULI.
Since it is rotated by day, it make us easier to keep the latest N files.

I know the best solution will be solving the conflict, but according to our 
experience, most of the user don't know there is a conflict.

In there any interest in adding this feature to Tomcat? 

--
From:bugzilla 
Time:2017 Jun 6 (Tue) 03:45
To:dev 
Subject:[Bug 61105] Roll log files by default


https://bz.apache.org/bugzilla/show_bug.cgi?id=61105

--- Comment #2 from Mark Thomas  ---
The conversation at TomcatCon was around putting a (relatively large) limit on
the number of files that are kept by default. Picking a number of of thin air,
how does 90 days sound?

There was no concern expressed about the log files that are currently not
rolled (generally, I suspect, because well written apps won;t trigger content
to those files).

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 8.5.15

[Huxing Zhang]

The proposed 8.5.15 release is:
[ ] Broken - do not release
[ X ] Stable - go ahead and release as 8.5.15

Test cases: OK.
Our test web application works fine.

--
From:Mark Thomas 
Time:2017 May 5 (Fri) 19:39
To:Tomcat Developers List 
Subject:Re: [VOTE] Release Apache Tomcat 8.5.15


On 05/05/17 12:38, Mark Thomas wrote:
> The proposed Apache Tomcat 8.5.15 release is now available for voting.
>
> The major changes compared to the 8.5.13 release are:
>
> - Various improvements to the handling of static custom error pages
>
> - Update to Eclipse JDT Compiler 4.6.3
>
> - Review those places where Tomcat re-encodes a URI or URI component
>   and ensure that that correct encoding is consistently applied.
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.15/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1134/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc8.5.x/tags/TOMCAT_8_5_15/
>
> The proposed 8.5.15 release is:
> [ ] Broken - do not release
> [X] Stable - go ahead and release as 8.5.15

Tests passed for me with NIO, NIO2, APR/native (with 1.2.12) on 64 bit
Windows, Linux and OSX.

Mark



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 9.0.0.M21

[Huxing Zhang]

The proposed 9.0.0.M21 release is:
[ ] Broken - do not release
[ X ] Alpha - go ahead and release as 9.0.0.M21

Test cases OK.
Our test web application works fine.
--
From:Mark Thomas 
Time:2017 May 5 (Fri) 17:03
To:Tomcat Developers List 
Subject:[VOTE] Release Apache Tomcat 9.0.0.M21


The proposed Apache Tomcat 9.0.0.M21 release is now available for voting.

This is a milestone release for the 9.0.x branch. It should be
noted that, as a milestone release:
- Servlet 4.0 is not finalised
- The EGs have not started work on JSP 2.4, EL 3.1 or WebSocket 1.2/2.0

The major changes compared to the 9.0.0.M20 release are:

- Update the default URIEncoding for a Connector to UTF-8 as required
  by the Servlet 4.0 specification.

- Various improvements to the handling of static custom error pages

- Update to Eclipse JDT Compiler 4.6.3

Along with lots of other bug fixes and improvements

For full details, see the changelog:
http://svn.apache.org/repos/asf/tomcat/trunk/webapps/docs/changelog.xml

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.0.M21/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1133/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tags/TOMCAT_9_0_0_M21/

The proposed 9.0.0.M21 release is:
[ ] Broken - do not release
[ ] Alpha - go ahead and release as 9.0.0.M21

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [ANN] New committer: Michael Osipov

[Huxing Zhang]

Congratulations!

--
From:Mark Thomas 
Time:2017 May 8 (Mon) 16:08
To:Tomcat Users List 
Cc:Tomcat Developers List 
Subject:[ANN] New committer: Michael Osipov


On behalf of the Tomcat committers I am pleased to announce that
Michael Osipov (michaelo) has been voted in as a new Tomcat committer.

Please join me in welcoming him.

Regards,

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 8.5.14

[Huxing Zhang]

The proposed 8.5.14 release is:
[ ] Broken - do not release
[ X ] Stable - go ahead and release as 8.5.14

Test case: ok
Our test web application works fine

--
From:Mark Thomas 
Time:2017 Apr 13 (Thu) 21:13
To:Tomcat Developers List 
Subject:[VOTE] Release Apache Tomcat 8.5.14


The proposed Apache Tomcat 8.5.14 release is now available for voting.

The major changes compared to the 8.5.13 release are:

- Correct a regression that broke JMX operations (including the Manager
  web application) if the operation took parameters

- Add JMX support for Tribes components

- Calls to isReady() no longer throw exceptions after timeouts for async
  servlets


It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.14/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1132/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc8.5.x/tags/TOMCAT_8_5_14/

The proposed 8.5.14 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 8.5.14

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 9.0.0.M20

[Huxing Zhang]

Hi,

The proposed 9.0.0.M20 release is:
[ ] Broken - do not release
[ X ] Alpha - go ahead and release as 9.0.0.M20

Test cases: ok.
Our test web app works fine.

--
From:Mark Thomas 
Time:2017 Apr 13 (Thu) 04:20
To:Tomcat Developers List 
Subject:[VOTE] Release Apache Tomcat 9.0.0.M20


The proposed Apache Tomcat 9.0.0.M20 release is now available for voting.

This is a milestone release for the 9.0.x branch. It should be
noted that, as a milestone release:
- Servlet 4.0 is not finalised
- The EGs have not started work on JSP 2.4, EL 3.1 or WebSocket 1.2/2.0

The major changes compared to the 9.0.0.M19 release are:

- Correct a regression that broke JMX operations (including the Manager
  web application) if the operation took parameters

- Add JMX support for Tribes components

- Calls to isReady() no longer throw exceptions after timeouts for async
  servlets


Along with lots of other bug fixes and improvements

For full details, see the changelog:
http://svn.apache.org/repos/asf/tomcat/trunk/webapps/docs/changelog.xml

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.0.M20/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1131/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tags/TOMCAT_9_0_0_M20/

The proposed 9.0.0.M20 release is:
[ ] Broken - do not release
[ ] Alpha - go ahead and release as 9.0.0.M20

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 7.0.76

[Huxing Zhang]

Hi,
 
The proposed 7.0.76 release is:
[  ] Broken - do not release
[ X ] Stable - go ahead and release as 7.0.76 Stable

Test cases all passed.
Our test webapp runs fine.
--
From:Mark Thomas 
Time:2017 Mar 9 (Thu) 22:11
To:Tomcat Developers List 
Subject:[VOTE] Release Apache Tomcat 7.0.76


The proposed Apache Tomcat 7.0.76 release is now available for voting.

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.76/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1123/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_76/

The proposed 7.0.76 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 7.0.76 Stable

Regards,
Violeta


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 8.5.12

[Huxing Zhang]

The proposed 8.5.12 release is:
[ ] Broken - do not release
[ X ] Stable - go ahead and release as 8.5.12

Test cases all passed.
Our test web app works fine.

One exception. The server push example will be failing by throwing an NPE if 
HTTP/2 is not supported.

Stack trace is:
java.lang.NullPointerException
  http2.SimpleImagePush.doGet(SimpleImagePush.java:36)
  javax.servlet.http.HttpServlet.service(HttpServlet.java:635)
  javax.servlet.http.HttpServlet.service(HttpServlet.java:742)
  org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
  
org.apache.catalina.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:108)
 

This issue has been fixed in revision 1786293.

--
From:Mark Thomas 
Time:2017 Mar 9 (Thu) 02:56
To:dev@tomcat.apache.org 
Subject:[VOTE] Release Apache Tomcat 8.5.12


The proposed Apache Tomcat 8.5.12 release is now available for voting.

The major changes compared to the 8.5.11 release are:

- Updates to the early access version of the Serlet 4.0 API to align it
  with the most recent discussions in the Servlet EG

- Support for Java 9 during annotation scanning

- Update Tomcat Native to 1.2.12 to pick up the latest Windows binaries
  built with OpenSSL 1.0.2k

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.12/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1121/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc8.5.x/tags/TOMCAT_8_5_12/

The proposed 8.5.12 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 8.5.12

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 9.0.0.M18

[Huxing Zhang]

The proposed 9.0.0.M18 release is:
[ ] Broken - do not release
[ X ] Alpha - go ahead and release as 9.0.0.M18

Test cases all passed.
Our test web app works fine.

One exception. The server push example will be failing by throwing an NPE if 
HTTP/2 is not supported.

Stack trace is:
java.lang.NullPointerException
  http2.SimpleImagePush.doGet(SimpleImagePush.java:36)
  javax.servlet.http.HttpServlet.service(HttpServlet.java:635)
  javax.servlet.http.HttpServlet.service(HttpServlet.java:742)
  org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
  
org.apache.catalina.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:108)
 

This issue has been fixed in revision 1786292.

--
From:Mark Thomas 
Time:2017 Mar 8 (Wed) 23:56
To:dev@tomcat.apache.org 
Subject:[VOTE] Release Apache Tomcat 9.0.0.M18


The proposed Apache Tomcat 9.0.0.M18 release is now available for voting.

This is a milestone release for the 9.0.x branch. It should be
noted that, as a milestone release:
- Servlet 4.0 is not finalised
- The EGs have not started work on JSP 2.4, EL 3.1 or WebSocket 1.2/2.0

The major changes compared to the 9.0.0.M17 release are:

- Updates to the early access version of the Serlet 4.0 API to align it
  with the most recent discussions in the Servlet EG

- Support for Java 9 during annotation scanning

- Enable ALPN (and hence HTTP/2) for NIO and NIO2 connectors when using
  JSSE for TLS on Java 9

- Update Tomcat Native to 1.2.12 to pick up the latest Windows binaries
  built with OpenSSL 1.0.2k

Along with lots of other bug fixes and improvements

For full details, see the changelog:
http://svn.apache.org/repos/asf/tomcat/trunk/webapps/docs/changelog.xml

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.0.M18/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1120/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tags/TOMCAT_9_0_0_M18/

The proposed 9.0.0.M18 release is:
[ ] Broken - do not release
[ ] Alpha - go ahead and release as 9.0.0.M18

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [POLL] Will you be at ApacheCon NA 2017?

[Huxing Zhang]

Hi, 

Here is my answer:

I will be attending ApacheCon NA:

[   ] Yes
[ X  ] Maybe
[   ] No

If attending, I would be willing to present a session at TomcatCon:

[ X  ] Yes
[   ] Maybe
[   ] No

I have submitted a proposal here:
http://events.linuxfoundation.org/cfp/proposals/14951/13401

Any suggestions is appreciated!

I've had a brief talk to my boss, and he will agree if the proposal got 
accepted.

One more question, I cannot login to [1] with my apache account, is that 
expected? A registration is necessary?

https://cwiki.apache.org/confluence/display/TOMCAT/TomcatCon+NA+2017

--
From:Mark Thomas 
Time:2017 Jan 24 (Tue) 23:46
To:dev@tomcat.apache.org 
Subject:[POLL] Will you be at ApacheCon NA 2017?


Hi,

I'm sure you have all seen the TomcatCon discussion I started on the
users@ list. We are getting enthusiastic support from the ApacheCon
organisers at both the ASF and the Linux Foundation.

I am starting to think about the overall schedule. Key to that is which
talks we can find someone to give. I'd like to get a wide a range of
speakers as possible. I've started to reach out privately to a few
potential session speakers but my expectation at this point is that most
speakers will come from within the Tomcat community. With that in mind
it would be extremely helpful if you could complete the following poll:

I will be attending ApacheCon NA:

[   ] Yes
[   ] Maybe
[   ] No

If attending, I would be willing to present a session at TomcatCon:

[   ] Yes
[   ] Maybe
[   ] No

If you have an idea / some ideas about potential session topics please
feel free to suggest them. The ideas so far are summarized on the wiki
[1]. Both new suggestions and amendments to existing ideas are very welcome.

Thanks,

Mark


[1] https://cwiki.apache.org/confluence/display/TOMCAT/TomcatCon+NA+2017

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: HTTP response reason phrases

[Huxing Zhang]

Hi,

I think the problem is that how we target tomcat 8.5 to the users.
Is it a biased to 8.0, or is it biased to 9.0?

For the former case, we should keep the backward compatibility as much
as possible.
For the latter case, breaking things should be assumable by end users.

IMO, 8.5 should be the former case. However, I don't think most of the
user will be affected by this change.
Therefore the priority should be MINOR or even TRIVIAL.

Overall, I am +0 to add an option to restore the reason phase in 8.5(
a warning message should be logged if this option is turned on), and
drop the option in 9.x.

Anyway, we should note this change in 8.5 migration guide [1].

[1] http://tomcat.apache.org/migration-85.html



On Wed, Jan 25, 2017 at 3:08 AM, Christopher Schultz
 wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> All,
>
> I'm cross-posting dev@ and users@, but please only reply to dev@ if
> you'd like to get involved in this discussion.
>
> I'd like to openly-discuss r1702765 [1]. There have been some
> complaints on both users@ and dev@ and some BZ issues filed against
> Tomcat 8.5 and 9.0 for removing the reason phrase. It happened in
> r1702765 with no referenced BZ issue and was first released with
> Tomcat 8.5.0 -- the initial release of Tomcat 8.5 -- as well as 9.0.0.M1
> .
>
> This issue doesn't really affect me, but some recent conversations
> about the "stability" (in terms of "things not changing") of Tomcat
> have me thinking about the implications of making this change in
> Tomcat 8.5.x and not in just Tomcat 9.0.x.
>
> It is well-known within this community that Tomcat 8.0.x and Tomcat
> 8.5.x are distinct versions, but since the major version number is the
> same, many have expectations that nothing serious is going to change.
> Of course, 8.5.x has *many* serious changes to it with respect to
> Tomcat 8.0.x. But this one seems to be tripping a lot of people up.
>
> Those who are filing bugs, etc. are quite adamant that the reason
> phrase is "required" for certain things. To be sure, the reason phrase
> will only be required by non-compliant clients, and so technically the
> client is at fault, here.
>
> I'm wondering what the wider community thinks about this change and
> whether or not we should consider reverting it for Tomcat 8.5.x.
>
> Again, please reply to the dev@ list, since that's where this
> discussion belongs. I just wanted to make sure I reached the widest
> audience possible to begin a discussion.
>
> Thanks,
> - -chris
>
> [1] http://svn.apache.org/viewvc?view=revision=r1702765
> -BEGIN PGP SIGNATURE-
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBCAAGBQJYh6ZCAAoJEBzwKT+lPKRYnJgQAIe57jJw2iUk86I63NGsqPnY
> IKWjZoMuqd8vlczn8/FF/drWMV7ObYsrhsYmJATR5iVI+/xdEXB7n8cMO7B7+ryV
> Sxe1Tcmh/tBNJ83a8C+zSHWvnIELYRonHm9syApa7onPKcsoEe6MTrsdL1M+An9U
> 9IvXtH3BfYKAynze5pkNS6I+ILjgWvNSclJFHmDNHWmRPyqdob4OtMWkSSU3qRBX
> FfbEk9IMrEbIit6CH75dw9xfaUDDRudnw3MBkKaV8VOLUoykvSMK1w9GdufO4ohP
> Dw/+l6CkXl8xCSRcNwXrDdJcisT9gN6Ey7+g7zrgAcg62RP3ftrQMCzT2VDQV3b4
> IlZfTi+vEdsKKzGUdH+OLbN0+hiW0bnuxJmTG2zQSGwKsIh78aFdPKShv4u22XKB
> xfcKn9c6XGUHH88j0ZVSOLh2AmORCvuDfQNA3NJCOceRwQsV1OHAda65fFlkjyiz
> Q/yMMV8VlblGJRItN1nEwheIs9ru3MokRBhaXQ78ehSkRxbkIPawP6ZSiojmv/80
> aKx3/T413GOK4e18sK3XFHP4NowkR7VR/a1R5Py7L2kpzhMJcc4bstYuE9hugfiN
> BaECAT66qahCmP0xVoiFEB2A0+sD0wRKZ6K1gPCarPdLKh6cX4poRcMK4i0jgG2a
> cao/Frb1y8JDm8maw1Q8
> =oQCi
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>



-- 
Best Regards！

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [ANN] New committer: Emmanuel Bourg

[Huxing Zhang]

Congratulations and welcome!


--
From:Mark Thomas 
Time:2017 Jan 21 (Sat) 01:12
To:Tomcat Users List 
Cc:Tomcat Developers List 
Subject:[ANN] New committer: Emmanuel Bourg


On behalf of the Tomcat committers I am pleased to announce that
Emmanuel Bourg (ebourg) has been voted in as a new Tomcat committer.

Please join me in welcoming him.

Regards,

Mark

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 8.5.11

[Huxing Zhang]

Hi,

The proposed 8.5.11 release is:
[ ] Broken - do not release
[ X ] Stable - go ahead and release as 8.5.11

Test cases all pass.
Test web application runs fine.

--
From:Mark Thomas 
Time:2017 Jan 11 (Wed) 05:28
To:dev@tomcat.apache.org 
Subject:[VOTE] Release Apache Tomcat 8.5.11


The proposed Apache Tomcat 8.5.11 release is now available for voting.

The major changes compared to the 8.5.9 release are:

- HTTP/2 fixes and improvements

- Improve the logic that selects an address to use to unlock the
  Acceptor to take account of platforms what do not listen on all
  local addresses when configured with an address of 0.0.0.0 or ::

- Fix a bug in APR/native socket close handling that resulted in
  unexpected errors for upgraded connections

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.11/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1113/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc8.5.x/tags/TOMCAT_8_5_11/

The proposed 8.5.11 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 8.5.11

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 9.0.0.M17

[Huxing Zhang]

Hi,

The proposed 9.0.0.M17 release is:
[ ] Broken - do not release
[ X ] Alpha - go ahead and release as 9.0.0.M17

Test case all passed.
Test web application runs fine.
--
From:Mark Thomas 
Time:2017 Jan 11 (Wed) 05:28
To:dev@tomcat.apache.org 
Subject:[VOTE] Release Apache Tomcat 9.0.0.M17


The proposed Apache Tomcat 9.0.0.M17 release is now available for voting.

This is a milestone release for the 9.0.x branch. It should be
noted that, as a milestone release:
- Servlet 4.0 is not finalised
- The EGs have not started work on JSP 2.4, EL 3.1 or WebSocket 1.2/2.0

The major changes compared to the 9.0.0.M15 release are:

- HTTP/2 fixes and improvements

- Improve the logic that selects an address to use to unlock the
  Acceptor to take account of platforms what do not listen on all
  local addresses when configured with an address of 0.0.0.0 or ::

- Fix a bug in APR/native socket close handling that resulted in
  unexpected errors for upgraded connections

Along with lots of other bug fixes and improvements

For full details, see the changelog:
http://svn.apache.org/repos/asf/tomcat/trunk/webapps/docs/changelog.xml

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.0.M17/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1112/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tags/TOMCAT_9_0_0_M17/

The proposed 9.0.0.M17 release is:
[ ] Broken - do not release
[ ] Alpha - go ahead and release as 9.0.0.M17

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Remaining poller thread properties of Nio2Endpoint in tomcat 8

[Huxing Zhang]

Hi there,

I have observed that there are some poller thread properties, e.g. 
pollerThreadPriority still remaining in org.apache.tomcat.util.net.Nio2Endpoint 
(line 148-150).

I do not see any place that is referring it, and it has been dropped in 8.5.x 
and 9.x.

Any ideas why it is still remaining? If not, I would like to remove them from 
8.0.x branch.

Thanks,
Huxing

Re: [VOTE] Release Apache Tomcat 8.5.10

[Huxing Zhang]

Hi,

The proposed 8.5.10 release is:
[ ] Broken - do not release
[ X ] Stable - go ahead and release as 8.5.10

All test cases passed.
Test web application works fine.
--
From:Mark Thomas 
Time:2017 Jan 6 (Fri) 07:39
To:dev@tomcat.apache.org 
Subject:[VOTE] Release Apache Tomcat 8.5.10


The proposed Apache Tomcat 8.5.10 release is now available for voting.

The major changes compared to the 8.5.9 release are:

- HTTP/2 fixes and improvements

- Simpler JSP file encoding detector that delegates XML prolog
  encoding detection to the JRE rather than using a custom XML
  parser.

- Improve the logic that selects an address to use to unlock the
  Acceptor to take account of platforms what do not listen on all
  local addresses when configured with an address of 0.0.0.0 or ::

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.10/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc8.5.x/tags/TOMCAT_8_5_10/

The proposed 8.5.10 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 8.5.10

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 9.0.0.M16

[Huxing Zhang]

Hi,

The proposed 9.0.0.M16 release is:
[ ] Broken - do not release
[ X ] Alpha - go ahead and release as 9.0.0.M16

Test cases all pass.
Example web app works fine.
--
From:Mark Thomas 
Time:2017 Jan 6 (Fri) 07:37
To:dev@tomcat.apache.org 
Subject:[VOTE] Release Apache Tomcat 9.0.0.M16


The proposed Apache Tomcat 9.0.0.M16 release is now available for voting.

This is a milestone release for the 9.0.x branch. It should be
noted that, as a milestone release:
- Servlet 4.0 is not finalised
- The EGs have not started work on JSP 2.4, EL 3.1 or WebSocket 1.2/2.0

The major changes compared to the 9.0.0.M15 release are:

- HTTP/2 fixes and improvements

- Simpler JSP file encoding detector that delegates XML prolog
  encoding detection to the JRE rather than using a custom XML
  parser.

- Improve the logic that selects an address to use to unlock the
  Acceptor to take account of platforms what do not listen on all
  local addresses when configured with an address of 0.0.0.0 or ::

Along with lots of other bug fixes and improvements

For full details, see the changelog:
http://svn.apache.org/repos/asf/tomcat/trunk/webapps/docs/changelog.xml

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.0.M16/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1110/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tags/TOMCAT_9_0_0_M16/

The proposed 9.0.0.M16 release is:
[ ] Broken - do not release
[ ] Alpha - go ahead and release as 9.0.0.M16

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: svn commit: r1775649 - in /tomcat/site/trunk: docs/whoweare.html xdocs/whoweare.xml

[Huxing Zhang]

Hi，

I believe the committer names are sorted by family name...
So probably you should not place yourself at last.

--
From:csutherl <csuth...@apache.org>
Time:2016 Dec 22 (Thu) 21:19
To:dev <dev@tomcat.apache.org>
Subject:svn commit: r1775649 - in /tomcat/site/trunk: docs/whoweare.html 
xdocs/whoweare.xml


Author: csutherl
Date: Thu Dec 22 13:19:34 2016
New Revision: 1775649

URL: http://svn.apache.org/viewvc?rev=1775649=rev
Log:
Adding myself to the whoarewe page

Modified:
tomcat/site/trunk/docs/whoweare.html
tomcat/site/trunk/xdocs/whoweare.xml

Modified: tomcat/site/trunk/docs/whoweare.html
URL: 
http://svn.apache.org/viewvc/tomcat/site/trunk/docs/whoweare.html?rev=1775649=1775648=1775649=diff
==
--- tomcat/site/trunk/docs/whoweare.html (original)
+++ tomcat/site/trunk/docs/whoweare.html Thu Dec 22 13:19:34 2016
@@ -443,6 +443,12 @@ A complete list of all the Apache Commit
 
 
 
+
+
+Coty Sutherland (csutherl at apache.org)
+
+
+
 
 Emeritus PMC members
 

Modified: tomcat/site/trunk/xdocs/whoweare.xml
URL: 
http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/whoweare.xml?rev=1775649=1775648=1775649=diff
==
--- tomcat/site/trunk/xdocs/whoweare.xml (original)
+++ tomcat/site/trunk/xdocs/whoweare.xml Thu Dec 22 13:19:34 2016
@@ -138,6 +138,9 @@ A complete list of all the Apache Commit
 
 Huxing Zhang (huxing at apache.org)
 
+
+Coty Sutherland (csutherl at apache.org)
+
 
 
 



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 8.5.9

[Huxing Zhang]

Hi, 

The proposed 8.5.9 release is:
[ ] Broken - do not release
[ X ] Stable - go ahead and release as <8.5.8> (should be 8.5.9)

Test case pass.
Our test web app works fine.
--
From:Mark Thomas 
Time:2016 Dec 6 (Tue) 04:45
To:dev@tomcat.apache.org 
Subject:[VOTE] Release Apache Tomcat 8.5.9


The proposed Apache Tomcat 8.5.9 release is now available for voting.

The major changes compared to the 8.5.8 release are:


- Improvements to SPNEGO authentication. Patches provided by Michael
  Osipov.

- Correct regression in I/O buffer handling.

- Improve handling of varargs in UEL expressions. Based on a patch by
  Ben.

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.9/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1109/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc8.5.x/tags/TOMCAT_8_5_9/

The proposed 8.5.9 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 8.5.8

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 9.0.0.M15

[Huxing Zhang]

Hi,

The proposed 9.0.0.M15 release is:
[ ] Broken - do not release
[ X ] Alpha - go ahead and release as 9.0.0.M15

Test cases pass.
Our test web app works fine.

--
From:Mark Thomas 
Time:2016 Dec 5 (Mon) 22:47
To:dev@tomcat.apache.org 
Subject:[VOTE] Release Apache Tomcat 9.0.0.M15


The proposed Apache Tomcat 9.0.0.M15 release is now available for voting.

This is a milestone release for the 9.0.x branch. It should be
noted that, as a milestone release:
- Servlet 4.0 is not finalised
- The EGs have not started work on JSP 2.4, EL 3.1 or WebSocket 1.2/2.0

The major changes compared to the 9.0.0.M13 release are:

- Improvements to SPNEGO authentication. Patches provided by Michael
  Osipov.

- Correct regression in I/O buffer handling.

- Improve handling of varargs in UEL expressions. Based on a patch by
  Ben.

Along with lots of other bug fixes and improvements

For full details, see the changelog:
http://svn.apache.org/repos/asf/tomcat/trunk/webapps/docs/changelog.xml

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.0.M15/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1108/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tags/TOMCAT_9_0_0_M15/

The proposed 9.0.0.M15 release is:
[ ] Broken - do not release
[ ] Alpha - go ahead and release as 9.0.0.M15

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 7.0.73

[Huxing Zhang]

The proposed 7.0.73 release is:
[ ] Broken - do not release
[ X ] Stable - go ahead and release as 7.0.73 Stable

--
From:Violeta Georgieva 
Time:2016 Nov 8 (Tue) 06:15
To:Tomcat Developers List 
Subject:[VOTE] Release Apache Tomcat 7.0.73


The proposed Apache Tomcat 7.0.73 release is now available for voting.

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.73/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1106/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_73/

The proposed 7.0.73 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 7.0.73 Stable

Regards,
Violeta

Re: [VOTE] Release Apache Tomcat 8.5.8

[Huxing Zhang]

Hi,

The proposed 8.5.8 release is:
[ ] Broken - do not release
[ X ] Stable - go ahead and release as 8.5.8

--
From:Mark Thomas 
Time:2016 Nov 4 (Fri) 05:52
To:dev@tomcat.apache.org 
Subject:[VOTE] Release Apache Tomcat 8.5.8


The proposed Apache Tomcat 8.5.8 release is now available for voting.

8.5.8 corrects a regression 8.5.7.

The major changes compared to the 8.5.6 release are:

- Implement header limits for HTTP/2

- Improve handling of I/O errors with async processing

- Fail earlier on invalid HTTP requests

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.8/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1104/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc8.5.x/tags/TOMCAT_8_5_8/

The proposed 8.5.8 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 8.5.8

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 9.0.0.M13

[Huxing Zhang]

Hi, 

The proposed 9.0.0.M13 release is:
[ ] Broken - do not release
[ X ] Alpha - go ahead and release as 9.0.0.M13

--
From:Mark Thomas 
Time:2016 Nov 4 (Fri) 05:42
To:dev@tomcat.apache.org 
Subject:[VOTE] Release Apache Tomcat 9.0.0.M13


The proposed Apache Tomcat 9.0.0.M13 release is now available for voting.

This is a milestone release for the 9.0.x branch. It should be
noted that, as a milestone release:
- Servlet 4.0 is not finalised
- The EGs have not started work on JSP 2.4, EL 3.1 or WebSocket 1.2/2.0

9.0.0.M13 corrects a regression reported in 9.0.0.M12.

The major changes compared to the 9.0.0.M11 release are:

- Implement header limits for HTTP/2

- Improve handling of I/O errors with async processing

- Fail earlier on invalid HTTP requests

Along with lots of other bug fixes and improvements

For full details, see the changelog:
http://svn.apache.org/repos/asf/tomcat/trunk/webapps/docs/changelog.xml

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.0.M13/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1103/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tags/TOMCAT_9_0_0_M13/

The proposed 9.0.0.M13 release is:
[ ] Broken - do not release
[ ] Alpha - go ahead and release as 9.0.0.M13

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 8.0.38

[Huxing Zhang]

The proposed 8.0.38 release is:
[ ] Broken - do not release
[ X ] Stable - go ahead and release as 8.0.38

--
From:Mark Thomas 
Time:2016 Oct 7 (Fri) 05:19
To:dev@tomcat.apache.org 
Subject:[VOTE] Release Apache Tomcat 8.0.38


The proposed Apache Tomcat 8.0.38 release is now available for voting.

The main changes since 8.0.37 are:

- Refactoring the non-container thread Async complete()/dispatch()
  handling to remove the possibility of deadlock

- Update the packaged version of the Tomcat Native Library to
  1.2.10 to pick up the latest Windows binaries built with
  OpenSSL 1.0.2j

- Improved UTF-8 handling for the RewriteValve


It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.0.38/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1098/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc8.0.x/tags/TOMCAT_8_0_38/

The proposed 8.0.38 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 8.0.38

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 8.5.6

[Huxing Zhang]

The proposed 8.5.6 release is:
[ ] Broken - do not release
[ ] Alpha  - go ahead and release as 8.5.6
[ ] Beta   - go ahead and release as 8.5.6
[ X ] Stable - go ahead and release as 8.5.6

--
From:Mark Thomas 
Time:2016 Oct 7 (Fri) 04:34
To:dev@tomcat.apache.org 
Subject:[VOTE] Release Apache Tomcat 8.5.6


The proposed Apache Tomcat 8.5.6 release is now available for voting.

The major changes compared to the 8.5.5 release are:

- Refactoring the non-container thread Async complete()/dispatch()
  handling to remove the possibility of deadlock

- Update the packaged version of the Tomcat Native Library to
  1.2.10 to pick up the latest Windows binaries built with
  OpenSSL 1.0.2j

- Improved UTF-8 handling for the RewriteValve


It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.6/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1097/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc8.5.x/tags/TOMCAT_8_5_6/

The proposed 8.5.6 release is:
[ ] Broken - do not release
[ ] Alpha  - go ahead and release as 8.5.6
[ ] Beta   - go ahead and release as 8.5.6
[ ] Stable - go ahead and release as 8.5.6

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat Native 1.2.10

[Huxing Zhang]

Hi Rainer,

Thanks for the detailed explanation, it is quite helpful.
I've added the clean up code in my building script, it should never happen 
again :)

Thanks,
Huxing
--
From:Rainer Jung <rainer.j...@kippdata.de>
Time:2016 Oct 9 (Sun) 19:26
To:Tomcat Developers List <dev@tomcat.apache.org>
Subject:Re: [VOTE] Release Apache Tomcat Native 1.2.10


Am 09.10.2016 um 12:04 schrieb Huxing Zhang:
> Hi Rainer,
>
> Thanks for your hint, I think I've found out the root cause.
>
> When I first compile openssl 1.1.0, the binaries have been installed to 
> /usr/local/openssl, the libcrypto.so.1.1 has been installed to 
> /usr/local/openssl/lib/.
>
> After I re-installed openssl 1.0.2j, the files in /usr/local/openssl has been 
> replaced, however the libcrypto.so.1.1 is still there, because openssl 1.0.x 
> did not produce that file.
>
> So when I recompile tc-native 1.2.10, with --with-ssl=/usr/local/openssl 
> (1.0.2j), the libcrypto.so.1.1 is referenced, where get_rfc3526_prime_8192 is 
> not exist.
>
> Following is the output:
>
> $objdump -p 
> /home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/native/.libs/libtcnative-1.so.0.2.10
>
> /home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/native/.libs/libtcnative-1.so.0.2.10:
>  file format elf64-x86-64
>
> Program Header:
> LOAD off0x vaddr 0x paddr 
> 0x align 2**21
>  filesz 0x00028244 memsz 0x00028244 flags r-x
> LOAD off0x00028248 vaddr 0x00228248 paddr 
> 0x00228248 align 2**21
>  filesz 0x1450 memsz 0x1b50 flags rw-
>  DYNAMIC off0x000282c8 vaddr 0x002282c8 paddr 
> 0x002282c8 align 2**3
>  filesz 0x0200 memsz 0x0200 flags rw-
> NOTE off0x0190 vaddr 0x0190 paddr 
> 0x0190 align 2**2
>  filesz 0x0024 memsz 0x0024 flags r--
> EH_FRAME off0x00023594 vaddr 0x00023594 paddr 
> 0x00023594 align 2**2
>  filesz 0x0dbc memsz 0x0dbc flags r--
>STACK off0x vaddr 0x paddr 
> 0x align 2**3
>  filesz 0x memsz 0x flags rw-
>
> Dynamic Section:
>   NEEDED   libssl.so.1.1
>   NEEDED   libcrypto.so.1.1
>   NEEDED   libapr-1.so.0
>   NEEDED   librt.so.1
>   NEEDED   libcrypt.so.1
>   NEEDED   libpthread.so.0
>   NEEDED   libc.so.6
>   SONAME   libtcnative-1.so.0
>   RPATH/usr/local/apr/lib:/usr/local/openssl/lib
>   INIT 0xf2e0
>   FINI 0x000225a8
>   GNU_HASH 0x01b8
>   STRTAB   0x5cf0
>   SYMTAB   0x0de8
>   STRSZ0x5b7e
>   SYMENT   0x0018
>   PLTGOT   0x00228588
>   PLTRELSZ 0x2c58
>   PLTREL   0x0007
>   JMPREL   0xc688
>   RELA 0xbf98
>   RELASZ   0x06f0
>   RELAENT  0x0018
>   VERNEED  0xbf08
>   VERNEEDNUM   0x0004
>   VERSYM   0xb86e
>   RELACOUNT0x0024
>
> Version References:
>   required from libpthread.so.0:
> 0x09691a75 0x00 05 GLIBC_2.2.5
>   required from libc.so.6:
> 0x0d696913 0x00 06 GLIBC_2.3
> 0x09691a75 0x00 04 GLIBC_2.2.5
>   required from libssl.so.1.1:
> 0x066d1f10 0x00 03 OPENSSL_1_1_0
>   required from libcrypto.so.1.1:
> 0x066d1f10 0x00 02 OPENSSL_1_1_0
>
> $nm /usr/local/openssl/lib/libcrypto.so.1.1 |  grep get_rfc3526_prime_8192
> 000a4830 T BN_get_rfc3526_prime_8192
>
> The solution will be cleaning up the /usr/local/openssl and re-compile 
> tc-native, and everything works fine.

Yes, that looks plausible. Glad that you fixed it.

Just one more explanation, how it comes your build rerefrences the *.1.1 
OpenSSL libraries:

When the link step runs during the build, it does not yet know about the 
version. Al it gets is the -lssl and -lcrypto flags. That means it will 
look for files libssl.so and libcrypto.so in the linker search path, 
including LD_LIBRARY_PATH at the time of linking and including any path 
given with "-L" flag.

These files libssl.so and libcrypto.so internally contain their 
so-c

Re: [VOTE] Release Apache Tomcat Native 1.2.10

[Huxing Zhang]

Hi Rainer,

Thanks for your hint, I think I've found out the root cause.

When I first compile openssl 1.1.0, the binaries have been installed to 
/usr/local/openssl, the libcrypto.so.1.1 has been installed to 
/usr/local/openssl/lib/.

After I re-installed openssl 1.0.2j, the files in /usr/local/openssl has been 
replaced, however the libcrypto.so.1.1 is still there, because openssl 1.0.x 
did not produce that file.

So when I recompile tc-native 1.2.10, with --with-ssl=/usr/local/openssl 
(1.0.2j), the libcrypto.so.1.1 is referenced, where get_rfc3526_prime_8192 is 
not exist.

Following is the output:

$objdump -p 
/home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/native/.libs/libtcnative-1.so.0.2.10

/home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/native/.libs/libtcnative-1.so.0.2.10:
 file format elf64-x86-64

Program Header:
LOAD off0x vaddr 0x paddr 
0x align 2**21
 filesz 0x00028244 memsz 0x00028244 flags r-x
LOAD off0x00028248 vaddr 0x00228248 paddr 
0x00228248 align 2**21
 filesz 0x1450 memsz 0x1b50 flags rw-
 DYNAMIC off0x000282c8 vaddr 0x002282c8 paddr 
0x002282c8 align 2**3
 filesz 0x0200 memsz 0x0200 flags rw-
NOTE off0x0190 vaddr 0x0190 paddr 
0x0190 align 2**2
 filesz 0x0024 memsz 0x0024 flags r--
EH_FRAME off0x00023594 vaddr 0x00023594 paddr 
0x00023594 align 2**2
 filesz 0x0dbc memsz 0x0dbc flags r--
   STACK off0x vaddr 0x paddr 
0x align 2**3
 filesz 0x memsz 0x flags rw-

Dynamic Section:
  NEEDED   libssl.so.1.1
  NEEDED   libcrypto.so.1.1
  NEEDED   libapr-1.so.0
  NEEDED   librt.so.1
  NEEDED   libcrypt.so.1
  NEEDED   libpthread.so.0
  NEEDED   libc.so.6
  SONAME   libtcnative-1.so.0
  RPATH/usr/local/apr/lib:/usr/local/openssl/lib
  INIT 0xf2e0
  FINI 0x000225a8
  GNU_HASH 0x01b8
  STRTAB   0x5cf0
  SYMTAB   0x0de8
  STRSZ0x5b7e
  SYMENT   0x0018
  PLTGOT   0x00228588
  PLTRELSZ 0x2c58
  PLTREL   0x0007
  JMPREL   0xc688
  RELA 0xbf98
  RELASZ   0x06f0
  RELAENT  0x0018
  VERNEED  0xbf08
  VERNEEDNUM   0x0004
  VERSYM   0xb86e
  RELACOUNT0x0024

Version References:
  required from libpthread.so.0:
0x09691a75 0x00 05 GLIBC_2.2.5
  required from libc.so.6:
0x0d696913 0x00 06 GLIBC_2.3
0x09691a75 0x00 04 GLIBC_2.2.5
  required from libssl.so.1.1:
0x066d1f10 0x00 03 OPENSSL_1_1_0
  required from libcrypto.so.1.1:
0x066d1f10 0x00 02 OPENSSL_1_1_0

$nm /usr/local/openssl/lib/libcrypto.so.1.1 |  grep get_rfc3526_prime_8192
000a4830 T BN_get_rfc3526_prime_8192

The solution will be cleaning up the /usr/local/openssl and re-compile 
tc-native, and everything works fine.

--
From:Rainer Jung <rainer.j...@kippdata.de>
Time:2016 Oct 8 (Sat) 19:47
To:Tomcat Developers List <dev@tomcat.apache.org>
Subject:Re: [VOTE] Release Apache Tomcat Native 1.2.10


Hi,

Am 08.10.2016 um 05:08 schrieb Huxing Zhang:
...

>  [echo] tc.library.path = 
> /home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/native/.libs

>  [echo] Running Tomcat Native Echo example ...
>  [java] Exception in thread "main" java.lang.UnsatisfiedLinkError: 
> /home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/native/.libs/libtcnative-1.so.0.2.10:
>  
> /home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/native/.libs/libtcnative-1.so.0.2.10:
>  undefined symbol: get_rfc3526_prime_8192
>  [java] at java.lang.ClassLoader$NativeLibrary.load(Native Method)
>  [java] at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1938)
>  [java] at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1854)
>  [java] at java.lang.Runtime.loadLibrary0(Runtime.java:870)
>  [java] at java.lang.System.loadLibrary(System.java:1122)
>  [java] at org.apache.tomcat.jni.Library.(Unknown Source)
>  [java] at org.apache.tomcat.jni.Library.initialize(Unknown Source)
>  [java] at org.apache.tomcat.jni.Echo.main(Unknown Source)
>  [java] 

Re: [VOTE] Release Apache Tomcat 9.0.0.M11

[Huxing Zhang]

The proposed 9.0.0.M11 release is:
[ ] Broken - do not release
[ X ] Alpha - go ahead and release as 9.0.0.M11

--
From:Mark Thomas 
Time:2016 Oct 7 (Fri) 03:52
To:dev@tomcat.apache.org 
Subject:[VOTE] Release Apache Tomcat 9.0.0.M11


The proposed Apache Tomcat 9.0.0.M11 release is now available for voting.

This is a milestone release for the 9.0.x branch. It should be
noted that, as a milestone release:
- Servlet 4.0 is not finalised
- The EGs have not started work on JSP 2.4, EL 3.1 or WebSocket 1.2/2.0

The major changes compared to the 9.0.0.M10 release are:

- Refactoring the non-container thread Async complete()/dispatch()
  handling to remove the possibility of deadlock

- Update the packaged version of the Tomcat Native Library to
  1.2.10 to pick up the latest Windows binaries built with
  OpenSSL 1.0.2j

- Improved UTF-8 handling for the RewriteValve

Along with lots of other bug fixes and improvements

For full details, see the changelog:
http://svn.apache.org/repos/asf/tomcat/trunk/webapps/docs/changelog.xml

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.0.M11/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1096/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tags/TOMCAT_9_0_0_M11/

The proposed 9.0.0.M11 release is:
[ ] Broken - do not release
[ ] Alpha - go ahead and release as 9.0.0.M11

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat Native 1.2.10

[Huxing Zhang]

Hi, 

Although it is a bit late, the tc native 1.2.10 example fails with openssl 
1.0.2j, following is the output:

Buildfile: /home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/build.xml

clean:
   [delete] Deleting directory 
/home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/dist

env:
 [echo] java.home = /opt/taobao/jdk1.8.0_65/jre
 [echo] user.home = /home/admin
 [echo] tc.library.path = 
/home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/native/.libs
 [echo]

prepare:
[mkdir] Created dir: 
/home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/dist

compile:
[mkdir] Created dir: 
/home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/dist/classes
[mkdir] Created dir: 
/home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/dist/classes/java
[mkdir] Created dir: 
/home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/dist/src
[mkdir] Created dir: 
/home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/dist/src/java
 [copy] Copying 37 files to 
/home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/dist/src/java
[javac] /home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/build.xml:220: 
warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 36 source files to 
/home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/dist/classes/java
 [copy] Copying 1 file to 
/home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/dist/classes/java

jar:
  [jar] Building jar: 
/home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/dist/tomcat-native-1.2.10.jar

env:
 [echo] java.home = /opt/taobao/jdk1.8.0_65/jre
 [echo] user.home = /home/admin
 [echo] tc.library.path = 
/home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/native/.libs
 [echo]

prepare:

compile:
[javac] /home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/build.xml:220: 
warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds

compile-examples:
[mkdir] Created dir: 
/home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/dist/classes/examples
[mkdir] Created dir: 
/home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/dist/src/examples
 [copy] Copying 6 files to 
/home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/dist/src/examples
[javac] /home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/build.xml:346: 
warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 3 source files to 
/home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/dist/classes/examples
 [copy] Copying 3 files to 
/home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/dist/classes/examples

run-echo:
 [echo] Running Tomcat Native Echo example ...
 [java] Exception in thread "main" java.lang.UnsatisfiedLinkError: 
/home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/native/.libs/libtcnative-1.so.0.2.10:
 
/home/admin/tomcat/tcnative/tomcat-native-1.2.10-src/native/.libs/libtcnative-1.so.0.2.10:
 undefined symbol: get_rfc3526_prime_8192
 [java] at java.lang.ClassLoader$NativeLibrary.load(Native Method)
 [java] at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1938)
 [java] at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1854)
 [java] at java.lang.Runtime.loadLibrary0(Runtime.java:870)
 [java] at java.lang.System.loadLibrary(System.java:1122)
 [java] at org.apache.tomcat.jni.Library.(Unknown Source)
 [java] at org.apache.tomcat.jni.Library.initialize(Unknown Source)
 [java] at org.apache.tomcat.jni.Echo.main(Unknown Source)
 [java] Java Result: 1

BUILD SUCCESSFUL
Total time: 3 seconds

On the other hand, tc-native + openssl 1.1.0 works fine.

Any ideas?

--
From:Mark Thomas 
Time:2016 Sep 27 (Tue) 00:18
To:dev@tomcat.apache.org 
Subject:[VOTE] Release Apache Tomcat Native 1.2.10


Version 1.2.10 includes the following change:

- Update minimum recommended OpenSSL version to 1.0.2j
- Windows binaries built with OpenSSL 1.0.2j

The proposed release artefacts can be found at [1],
and the build was done using tag [2].

The Apache Tomcat Native 1.2.10 is
 [ ] Stable, go ahead and release
 [ ] Broken because of ...

Thanks,

Mark


[1]
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-connectors/native/1.2.10/
[2] https://svn.apache.org/repos/asf/tomcat/native/tags/TOMCAT_NATIVE_1_2_10

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [PATCH] - rat-output.xml tweaks for tc8.0.x tc8.5.x trunk

[Huxing Zhang]

Hi Gavin,

Please file the patch to trunk, and it will be backported to 8.5.x, 8.x if 
possible.

--
From:Gavin McDonald 
Time:2016 Sep 23 (Fri) 07:17
To:Tomcat Developers List 
Subject:RE: [PATCH] - rat-output.xml tweaks for tc8.0.x tc8.5.x trunk




> -Original Message-
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Sent: Friday, September 23, 2016 3:25 AM
> To: Tomcat Developers List 
> Subject: Re: [PATCH] - rat-output.xml tweaks for tc8.0.x tc8.5.x trunk
> 
> Gavin,
> 
> On 9/22/16 1:03 AM, Gavin McDonald wrote:
> > Please find attached 3 patches for tweaks to the rat-excludes file in
> > trunk and the 8.0 and 8.5 branches.
> >
> > RAT tests are currently producing invalid xml reports due to files
> > that should be excluded (and therefore xml parser cant convert to html
> > for pretty reports etc)
> >
> > HTH
> >
> > Gav...
> 
> The attachment(s) must have been stripped. 

Yeah I noticed :(

> Would you like to file a BZ issue
> and attach to that?

Sure, not sure what component to put it under. Ideas ?

The patches affect versions 8, 8.5 and trunk , which version do you want me to 
use?

Thanks

Gav...

> 
> -chris



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 7.0.72

[Huxing Zhang]

The proposed 7.0.72 release is:
[ ] Broken - do not release
[ X ] Stable - go ahead and release as 7.0.72 Stable

Test cases ok.
Examples ok.
Our test app works fine.

--
From:Violeta Georgieva 
Time:2016 Sep 14 (Wed) 21:02
To:Tomcat Developers List 
Subject:[VOTE] Release Apache Tomcat 7.0.72


The proposed Apache Tomcat 7.0.72 release is now available for voting.

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.72/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1095/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_72/

The proposed 7.0.72 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 7.0.72 Stable

Regards,
Violeta
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org