[GUMP@vmgump-vm3]: Project tomcat-tc8.5.x-test-nio2 (in module tomcat-8.5.x) failed

2019-03-26 Thread Bill Barker 
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at gene...@gump.apache.org.

Project tomcat-tc8.5.x-test-nio2 has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 18 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- tomcat-tc8.5.x-test-nio2 :  Tomcat 8.x, a web server implementing the 
Java Servlet 3.1,
...


Full details are available at:

http://vmgump-vm3.apache.org/tomcat-8.5.x/tomcat-tc8.5.x-test-nio2/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed
 -INFO- Project Reports in: 
/srv/gump/public/workspace/tomcat-8.5.x/output/logs-NIO2
 -INFO- Project Reports in: 
/srv/gump/public/workspace/tomcat-8.5.x/output/test-tmp-NIO2/logs
 -WARNING- No directory 
[/srv/gump/public/workspace/tomcat-8.5.x/output/test-tmp-NIO2/logs]



The following work was performed:
http://vmgump-vm3.apache.org/tomcat-8.5.x/tomcat-tc8.5.x-test-nio2/gump_work/build_tomcat-8.5.x_tomcat-tc8.5.x-test-nio2.html
Work Name: build_tomcat-8.5.x_tomcat-tc8.5.x-test-nio2 (Type: Build)
Work ended in a state of : Failed
Elapsed: 18 mins 58 secs
Command Line: /usr/lib/jvm/java-8-oracle/bin/java -Djava.awt.headless=true 
-Dbuild.sysclasspath=only -Dsun.zip.disableMemoryMapping=true 
org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml 
-Djunit.jar=/srv/gump/public/workspace/junit/target/junit-4.13-SNAPSHOT.jar 
-Djava.net.preferIPv4Stack=/srv/gump/public/workspace/tomcat-8.5.x/true 
-Dobjenesis.jar=/srv/gump/public/workspace/objenesis/main/target/objenesis-3.1-SNAPSHOT.jar
 -Dtest.reports=output/logs-NIO2 -Dexecute.test.nio2=true 
-Dexamples.sources.skip=true 
-Dbase.path=/srv/gump/public/workspace/tomcat-8.5.x/tomcat-build-libs 
-Djdt.jar=/srv/gump/packages/eclipse/plugins/R-4.10-201812060815/ecj-4.10.jar 
-Dtest.relaxTiming=true 
-Dcommons-daemon.jar=/srv/gump/public/workspace/apache-commons/daemon/target/commons-daemon-1.1.1-SNAPSHOT.jar
 -Dtest.temp=output/test-tmp-NIO2 -Dtest.accesslog=true 
-Dexecute.test.nio=false 
-Dtest.openssl.path=/srv/gump/public/workspace/openssl-1.1.1/dest-20190327/bin/openssl
 -Dexecute
 .test.apr=false -Dtest.excludePerformance=true 
-Deasymock.jar=/srv/gump/packages/easymock3/easymock-3.6.jar 
-Dhamcrest.jar=/srv/gump/packages/hamcrest/hamcrest-core-1.3.jar 
-Dcglib.jar=/srv/gump/packages/cglib/cglib-nodep-2.2.jar test 
[Working Directory: /srv/gump/public/workspace/tomcat-8.5.x]
CLASSPATH: 
/usr/lib/jvm/java-8-oracle/lib/tools.jar:/srv/gump/public/workspace/tomcat-8.5.x/output/build/webapps/examples/WEB-INF/classes:/srv/gump/public/workspace/tomcat-8.5.x/output/testclasses:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit4.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/tomcat-8.5.x/output/build/bin/bootstrap.jar:/srv/gump/public/workspace/tomcat-8.5.x/output/build/bin/tomcat-juli.jar:/srv/gump/public/workspace/tomcat-8.5.x/output/build/lib/annotations-api.jar:/srv/gump/public/workspace/tomcat-8.5.x/output/build/lib/servlet-api.ja
 
r:/srv/gump/public/workspace/tomcat-8.5.x/output/build/lib/jsp-api.jar:/srv/gump/public/workspace/tomcat-8.5.x/output/build/lib/el-api.jar:/srv/gump/public/workspace/tomcat-8.5.x/output/build/lib/websocket-api.jar:/srv/gump/public/workspace/tomcat-8.5.x/output/build/lib/jaspic-api.jar:/srv/gump/public/workspace/tomcat-8.5.x/output/build/lib/catalina.jar:/srv/gump/public/workspace/tomcat-8.5.x/output/build/lib/catalina-ant.jar:/srv/gump/public/workspace/tomcat-8.5.x/output/build/lib/catalina-storeconfig.jar:/srv/gump/public/workspace/tomcat-8.5.x/output/build/lib/tomcat-coyote.jar:/srv/gump/public/workspace/tomcat-8.5.x/output/build/lib/jasper.jar:/srv/gump/public/workspace/tomcat-8.5.x/output/build/lib/jasper-el.jar:/srv/gump/public/workspace/tomcat-8.5.x/output/build/lib/catalina-tribes.jar:/srv/gump/public/workspace/tomcat-8.5.x/output/build/lib/catalina-ha.jar:/srv/gump/public/workspace/tomcat-8.5.x/output/build/lib/tomcat-api.jar:/srv/gump/public/workspace/tomcat-8.5.x/output/bu

Re: Tomcat Site Redesign

2019-03-26 Thread Christopher Schultz 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Konstantin,

On 3/25/19 17:41, Konstantin Kolinko wrote:
> My main concern is that the documentation is printable and is easy
> to use as a reference document.
> 
> 1) Not being able to print is a show-stopper. (Really.) Anything
> else is just a personal preference.

@media print {
  ...
}

Ought to be able to handle any changes required for print media. The
menus never have to print. Never. Because they will never be navigable
on paper. So they can just be removed. Horizontal, vertical, 3D,
zooming, it doesn't matter. Just remove them when then are printed and
it's not an issue.

The main body of the content is still a wall of text from top to
bottom. That should render just fine on a printer on in PDF.

> 2) Left-side menu allows to navigate to a needed page with a
> single click. I really like this feature of this menu.

Unless you scroll too far down the page. I've always been irritated
about this "feature" of the Tomcat documentation. Once you scroll away
from the menu, it's no longer "one click away". So if it could "stick"
to the top of the window (horizontal) or never scroll completely off
the top of the page, that would be a nice improvement.

>> It utilizes the Bootstrap 4 framework and is very trendy.
> 
> One announcement that made a big impression for me in year 2018 was
> this one: https://twitter.com/mislav/status/1022058279000842240 
> "We’re finally finished removing jQuery from http://GitHub.com
> frontend" [...]

IMO we should avoid javascript at all costs. Almost everything worth
doing can currently be done with CSS.

Bootstrap can use jQuery, but it doesn't have to.

> Regarding concerns raised in a subsequent thread on this topic 
> "Tomcat Website Redesign" thread 
> https://www.mail-archive.com/dev@tomcat.apache.org/msg132281.html
> 
>> a) Do nothing, i.e. keep the website as-is [1] for now
>> 
>> [...] IMO option (a) is not good because the site is very
>> outdated and not mobile friendly.  Many users nowadays view sites
>> on their phones and/or tablets, which a modern design can
>> address.
> 
> The current site was redesigned several years ago. (See the log 
> history of "/xdocs/stylesheets/tomcat-site.xsl" file)  I think it 
> should be mobile-friendly.
> 
> What are the specific issues?
> 
> Is it possible to make changes in small incremental reversible
> steps?

IMO, this *was* fairly incremental.

- -chris
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlyazfoACgkQHPApP6U8
pFiQ0A//cEB/ytCsQYwh//4WbHmXhx2AA6sjvdSPrneUKzDXM4RcC5snFyJom4oo
55hwpW1UALM9vxyvI0XFGOJ54sV7II5OUxXIecF6BZLi1Bj5bDe4aieSSIpN+hnF
MsWGSsSrl7IF38eCmT/QHuLuOjhMRxaDp9hrnE+EM+CgepyDrFXxFeHz5GCfLafq
lgu/wGFnmePS40UM/Cxw5USUFQ8ADGDS49k8l9R+deK0vN/FN2vT+W4blw3zheLj
mMBcC2quDI3/rICXUiEma6/3LYEGnilmL5mkPioyd0nQiMHLsUW/rTRqClBfVjFC
wXFuzCJwh6JFuOqjSj+jHmuSkLtq0/oUU3d0lW3O57EgpDaSdWjOOsUl3zk8v/Bt
BuVmdj6mmbJtMpXVpdiIHZ2XHk1ZnSCUjRg6h0DzuEtUIF3rVTJU9wgQBz3bc6uy
GBhSzDz1ttVEdC+09Mcv6wbMHo5xNp4G0UBEazRbtV14bxxBCF5FpRISBls/vHfL
x7AoGf/8cakr7iAsgn9LNqlF0LGmj/n5M4PnhyjmFPsfIsJJigp4uWJHbzH3qEqe
jZicpUgRq6FDosKAUrtkyAD8YD31zlvKlzrX2dsqBofHvnIERmJdjQosubVDkaVV
Wzc9kLPbBwZCCnvD0+8HryW+FuqleNtcJ3/JnyAqInqCI2reEJE=
=lW6v
-END PGP SIGNATURE-

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

buildbot failure in on tomcat-85-trunk

2019-03-26 Thread buildbot 
The Buildbot has detected a new failure on builder tomcat-85-trunk while 
building tomcat. Full details are available at:
https://ci.apache.org/builders/tomcat-85-trunk/builds/1717

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-tomcat-85-commit' 
triggered this build
Build Source Stamp: [branch 8.5.x] d056c7735584049449c0227ea5bfc281604814f1
Blamelist: Mark Thomas 

BUILD FAILED: failed compile_1

Sincerely,
 -The Buildbot




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

[tomcat] branch 8.5.x updated: Add release date for 8.5.39

2019-03-26 Thread markt 
This is an automated email from the ASF dual-hosted git repository.

markt pushed a commit to branch 8.5.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git


The following commit(s) were added to refs/heads/8.5.x by this push:
 new d056c77  Add release date for 8.5.39
d056c77 is described below

commit d056c7735584049449c0227ea5bfc281604814f1
Author: Mark Thomas 
AuthorDate: Tue Mar 26 23:51:31 2019 +

Add release date for 8.5.39
---
 webapps/docs/changelog.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/webapps/docs/changelog.xml b/webapps/docs/changelog.xml
index dee1320..86ec3a7 100644
--- a/webapps/docs/changelog.xml
+++ b/webapps/docs/changelog.xml
@@ -118,7 +118,7 @@
 
   
 
-
+
   
 
   


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

Issue 62814: Use readable names for cluster channel/map options in documentation

2019-03-26 Thread Devarsh Desai 
Hi,

This email is referencing Bug 62814
.

Some small notes while looking into the additional documentation needed:

SEND_OPTIONS_ASYNCHRONOUS and SEND_OPTIONS_SYNCHRONIZED_ACK contain a
duplicated comment section within the Channel class. From first glance, it
seems we should detail the nuances between them.

The channel options summary table

contains multiple rows with the same text (photo attached). To polish it
up, is it OK to refactor the flag's javadoc in order to present the
apt descriptions?

Could you point me to the sample configuration files which should be
updated.

Regards,
Devarsh Desai

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

Re: Wiki migration

2019-03-26 Thread Mark Thomas 
On 25/03/2019 22:24, Konstantin Kolinko wrote:
> пт, 15 мар. 2019 г. в 21:32, Mark Thomas :
>>
>> On 15/03/2019 18:05, Konstantin Kolinko wrote:
>>> пт, 15 мар. 2019 г. в 20:07, Mark Thomas :

 All,

 I am going to attempt the wiki migration. [...]
>>
>>> 2. Links used by Confluence are not pretty, with all those '+'s
>>>
>>> 3. It does to integrate well with e-mail.
>>>
>>> As currently, it is not configured to echo changes to the dev@ mailing list,
>>> and if done so it cannot send plaintext e-mails.
>>
>> That issue is 50% confluence (it marks the changes email as bulk with no
>> option to change that) and 50% ezmlm (it automatically drops bulk
>> email). That problem should be solvable. I'll pester infra about that one.
> 
> Any progress here?

I asked on slack but I think the question got overlooked. I've raised:
https://issues.apache.org/jira/browse/INFRA-18107

Mark

> As an idea: Maybe configure a separate mailing list to which such
> notifications are posted?
> 
> If there needs to be a special configuration to accept "bulk" emails
> and accept HTML emails, it may be easier to configure a separate
> mailing list with such relaxed configuration rather then fine-tune
> configuration of dev@tomcat.
> 
> 
> Best regards,
> Konstantin Kolinko
> 
> -
> 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: Release Announcement: General Availability of Java 12 / JDK 12

2019-03-26 Thread Mark Thomas 
On 26/03/2019 11:34, Mark Thomas wrote:
> And on a similar topic DTLS 1.3 support is also required.

As I read up more on QUiC I realised DTLS 1.3 is not required.

I have seen references to fairly tight integration with the TLS1.3
implementation. I haven't got far enough to say whether JSSE and/or
OpenSSL have the necessary API.

Mark


> 
> Mark
> 
> 
> On 26/03/2019 10:36, Rory O'Donnell wrote:
>> Hi Remy,
>>
>> The best place to start the discussion would be nio-dev mailing list -
>> http://mail.openjdk.java.net/mailman/listinfo/nio-dev
>>
>> subscribe first...
>>
>> I hope that helps, Rory
>>
>>
>> On 26/03/2019 09:42, Rémy Maucherat wrote:
>>> Hi Rory,
>>>
>>> On Wed, Mar 20, 2019 at 10:07 AM Rory O'Donnell
>>> mailto:rory.odonn...@oracle.com>> wrote:
>>>
>>>    Hi Mark,
>>>
>>> *1) Release Announcement: General Availability of Java 12 / JDK 12
>>> [1] *
>>>
>>>   * JDK 12, the reference implementation of Java 12, is now Generally
>>>     Available.
>>>   * GPL-licensed OpenJDK builds from Oracle are available here:
>>>     https://jdk.java.net/12
>>>
>>> This release includes the following  eight features:
>>>
>>>   * JEP 189: Shenandoah: A Low-Pause-Time Garbage Collector
>>> (Experimental)
>>>   * JEP 230: Microbenchmark Suite
>>>   * JEP 334: JVM Constants API
>>>   * JEP 340: One AArch64 Port, Not Two
>>>   * JEP 341: Default CDS Archives
>>>   * JEP 344: Abortable Mixed Collections for G1
>>>   * JEP 346: Promptly Return Unused Committed Memory from G1
>>>   * JEP 325: Switch Expressions (Preview)
>>>     
>>>
>>> Thanks to everyone who contributed JDK 12, whether by creating
>>> features
>>> or enhancements, logging  bugs, or downloading and testing the
>>> early-access builds.
>>>
>>>
>>> Moving forward, HTTP/3 is around the corner. As you probably know, it
>>> is based on top of UDP. As you might know, NIO2, which Tomcat can
>>> optionally use, does not have support for UDP. UDP NIO2 support was
>>> apparently planned when it was originally introduced, but was removed
>>> due to schedule constraints. As a result, it is not possible to use
>>> NIO2 for HTTP/3 clients or servers. Is there going to be a plan to fix
>>> this ?
>>> It seems like a good JEP candidate, but there's no JEP in the index at
>>> the moment: https://openjdk.java.net/jeps/0
>>>
>>> Rémy
>>>  
>>>
>>>
>>> *2) JDK 13 EA build 12, under both the GPL and Oracle EA licenses, is
>>> now available at **http://jdk.java.net/13**.*
>>>
>>>   * Proposed - Schedule for JDK 13 [2]
>>>       o 2019/06/13 Rampdown Phase One
>>>       o 2019/07/18 Rampdown Phase Two
>>>       o 2019/08/08 Initial Release Candidate
>>>       o 2019/08/22 Final Release Candidate
>>>       o 2019/09/17 General Availability
>>>   * Recent Bug fixes of Interest
>>>       o Build 9:
>>>           + 8214719: Deprecate -Xverify:none option
>>>           + 8216360: Deprecate -XX:CompilationPolicyChoice
>>>       o Build 10:
>>>           + 8218995: Deprecate the -XX:FailOverToOldVerifier option
>>>       o Build 12 : 8160247: Mark deprecated javax.security.cert APIs
>>>         with forRemoval=true
>>>           + 8220050: Deprecate -XX:-ThreadLocalHandshakes
>>>           + Apache Lucene Reported - 8219448: split-if update_uses
>>>             accesses stale idom data
>>>   * Changes in this build [3]
>>>
>>> Rgds,Rory
>>>
>>> [1]
>>> https://mail.openjdk.java.net/pipermail/jdk-dev/2019-March/002718.html
>>> [2]
>>> https://mail.openjdk.java.net/pipermail/jdk-dev/2019-March/002716.html
>>> [3] Changes
>>> 
>>> 
>>>
>>> in this build
>>>
>>>
>>> -- 
>>> Rgds,Rory O'Donnell
>>> Quality Engineering Manager
>>> Oracle EMEA , Dublin, Ireland
>>>
>> -- 
>> Rgds,Rory O'Donnell
>> Quality Engineering Manager
>> Oracle EMEA , Dublin, Ireland 
>>
> 
> 
> -
> 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: Release Announcement: General Availability of Java 12 / JDK 12

2019-03-26 Thread Mark Thomas 
And on a similar topic DTLS 1.3 support is also required.

Mark


On 26/03/2019 10:36, Rory O'Donnell wrote:
> Hi Remy,
> 
> The best place to start the discussion would be nio-dev mailing list -
> http://mail.openjdk.java.net/mailman/listinfo/nio-dev
> 
> subscribe first...
> 
> I hope that helps, Rory
> 
> 
> On 26/03/2019 09:42, Rémy Maucherat wrote:
>> Hi Rory,
>>
>> On Wed, Mar 20, 2019 at 10:07 AM Rory O'Donnell
>> mailto:rory.odonn...@oracle.com>> wrote:
>>
>>    Hi Mark,
>>
>> *1) Release Announcement: General Availability of Java 12 / JDK 12
>> [1] *
>>
>>   * JDK 12, the reference implementation of Java 12, is now Generally
>>     Available.
>>   * GPL-licensed OpenJDK builds from Oracle are available here:
>>     https://jdk.java.net/12
>>
>> This release includes the following  eight features:
>>
>>   * JEP 189: Shenandoah: A Low-Pause-Time Garbage Collector
>> (Experimental)
>>   * JEP 230: Microbenchmark Suite
>>   * JEP 334: JVM Constants API
>>   * JEP 340: One AArch64 Port, Not Two
>>   * JEP 341: Default CDS Archives
>>   * JEP 344: Abortable Mixed Collections for G1
>>   * JEP 346: Promptly Return Unused Committed Memory from G1
>>   * JEP 325: Switch Expressions (Preview)
>>     
>>
>> Thanks to everyone who contributed JDK 12, whether by creating
>> features
>> or enhancements, logging  bugs, or downloading and testing the
>> early-access builds.
>>
>>
>> Moving forward, HTTP/3 is around the corner. As you probably know, it
>> is based on top of UDP. As you might know, NIO2, which Tomcat can
>> optionally use, does not have support for UDP. UDP NIO2 support was
>> apparently planned when it was originally introduced, but was removed
>> due to schedule constraints. As a result, it is not possible to use
>> NIO2 for HTTP/3 clients or servers. Is there going to be a plan to fix
>> this ?
>> It seems like a good JEP candidate, but there's no JEP in the index at
>> the moment: https://openjdk.java.net/jeps/0
>>
>> Rémy
>>  
>>
>>
>> *2) JDK 13 EA build 12, under both the GPL and Oracle EA licenses, is
>> now available at **http://jdk.java.net/13**.*
>>
>>   * Proposed - Schedule for JDK 13 [2]
>>       o 2019/06/13 Rampdown Phase One
>>       o 2019/07/18 Rampdown Phase Two
>>       o 2019/08/08 Initial Release Candidate
>>       o 2019/08/22 Final Release Candidate
>>       o 2019/09/17 General Availability
>>   * Recent Bug fixes of Interest
>>       o Build 9:
>>           + 8214719: Deprecate -Xverify:none option
>>           + 8216360: Deprecate -XX:CompilationPolicyChoice
>>       o Build 10:
>>           + 8218995: Deprecate the -XX:FailOverToOldVerifier option
>>       o Build 12 : 8160247: Mark deprecated javax.security.cert APIs
>>         with forRemoval=true
>>           + 8220050: Deprecate -XX:-ThreadLocalHandshakes
>>           + Apache Lucene Reported - 8219448: split-if update_uses
>>             accesses stale idom data
>>   * Changes in this build [3]
>>
>> Rgds,Rory
>>
>> [1]
>> https://mail.openjdk.java.net/pipermail/jdk-dev/2019-March/002718.html
>> [2]
>> https://mail.openjdk.java.net/pipermail/jdk-dev/2019-March/002716.html
>> [3] Changes
>> 
>> 
>>
>> in this build
>>
>>
>> -- 
>> Rgds,Rory O'Donnell
>> Quality Engineering Manager
>> Oracle EMEA , Dublin, Ireland
>>
> -- 
> Rgds,Rory O'Donnell
> Quality Engineering Manager
> Oracle EMEA , Dublin, Ireland 
> 


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

Re: Release Announcement: General Availability of Java 12 / JDK 12

2019-03-26 Thread Rory O'Donnell 

Hi Remy,

The best place to start the discussion would be nio-dev mailing list - 
http://mail.openjdk.java.net/mailman/listinfo/nio-dev


subscribe first...

I hope that helps, Rory


On 26/03/2019 09:42, Rémy Maucherat wrote:

Hi Rory,

On Wed, Mar 20, 2019 at 10:07 AM Rory O'Donnell 
mailto:rory.odonn...@oracle.com>> wrote:


   Hi Mark,

*1) Release Announcement: General Availability of Java 12 / JDK 12
[1] *

  * JDK 12, the reference implementation of Java 12, is now Generally
    Available.
  * GPL-licensed OpenJDK builds from Oracle are available here:
https://jdk.java.net/12

This release includes the following  eight features:

  * JEP 189: Shenandoah: A Low-Pause-Time Garbage Collector
(Experimental)
  * JEP 230: Microbenchmark Suite
  * JEP 334: JVM Constants API
  * JEP 340: One AArch64 Port, Not Two
  * JEP 341: Default CDS Archives
  * JEP 344: Abortable Mixed Collections for G1
  * JEP 346: Promptly Return Unused Committed Memory from G1
  * JEP 325: Switch Expressions (Preview)
    

Thanks to everyone who contributed JDK 12, whether by creating
features
or enhancements, logging  bugs, or downloading and testing the
early-access builds.


Moving forward, HTTP/3 is around the corner. As you probably know, it 
is based on top of UDP. As you might know, NIO2, which Tomcat can 
optionally use, does not have support for UDP. UDP NIO2 support was 
apparently planned when it was originally introduced, but was removed 
due to schedule constraints. As a result, it is not possible to use 
NIO2 for HTTP/3 clients or servers. Is there going to be a plan to fix 
this ?
It seems like a good JEP candidate, but there's no JEP in the index at 
the moment: https://openjdk.java.net/jeps/0


Rémy


*2) JDK 13 EA build 12, under both the GPL and Oracle EA licenses, is
now available at **http://jdk.java.net/13**.*

  * Proposed - Schedule for JDK 13 [2]
      o 2019/06/13 Rampdown Phase One
      o 2019/07/18 Rampdown Phase Two
      o 2019/08/08 Initial Release Candidate
      o 2019/08/22 Final Release Candidate
      o 2019/09/17 General Availability
  * Recent Bug fixes of Interest
      o Build 9:
          + 8214719: Deprecate -Xverify:none option
          + 8216360: Deprecate -XX:CompilationPolicyChoice
      o Build 10:
          + 8218995: Deprecate the -XX:FailOverToOldVerifier option
      o Build 12 : 8160247: Mark deprecated javax.security.cert APIs
        with forRemoval=true
          + 8220050: Deprecate -XX:-ThreadLocalHandshakes
          + Apache Lucene Reported - 8219448: split-if update_uses
            accesses stale idom data
  * Changes in this build [3]

Rgds,Rory

[1]
https://mail.openjdk.java.net/pipermail/jdk-dev/2019-March/002718.html
[2]
https://mail.openjdk.java.net/pipermail/jdk-dev/2019-March/002716.html
[3] Changes



in this build


-- 
Rgds,Rory O'Donnell

Quality Engineering Manager
Oracle EMEA , Dublin, Ireland


--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland

Re: Release Announcement: General Availability of Java 12 / JDK 12

2019-03-26 Thread Rémy Maucherat 
Hi Rory,

On Wed, Mar 20, 2019 at 10:07 AM Rory O'Donnell 
wrote:

>Hi Mark,
>
> *1) Release Announcement: General Availability of Java 12 / JDK 12 [1] *
>
>   * JDK 12, the reference implementation of Java 12, is now Generally
> Available.
>   * GPL-licensed OpenJDK builds from Oracle are available here:
> https://jdk.java.net/12
>
> This release includes the following  eight features:
>
>   * JEP 189: Shenandoah: A Low-Pause-Time Garbage Collector (Experimental)
>   * JEP 230: Microbenchmark Suite
>   * JEP 334: JVM Constants API
>   * JEP 340: One AArch64 Port, Not Two
>   * JEP 341: Default CDS Archives
>   * JEP 344: Abortable Mixed Collections for G1
>   * JEP 346: Promptly Return Unused Committed Memory from G1
>   * JEP 325: Switch Expressions (Preview)
> 
>
> Thanks to everyone who contributed JDK 12, whether by creating features
> or enhancements, logging  bugs, or downloading and testing the
> early-access builds.
>

Moving forward, HTTP/3 is around the corner. As you probably know, it is
based on top of UDP. As you might know, NIO2, which Tomcat can optionally
use, does not have support for UDP. UDP NIO2 support was apparently planned
when it was originally introduced, but was removed due to schedule
constraints. As a result, it is not possible to use NIO2 for HTTP/3 clients
or servers. Is there going to be a plan to fix this ?
It seems like a good JEP candidate, but there's no JEP in the index at the
moment: https://openjdk.java.net/jeps/0

Rémy


>
> *2) JDK 13 EA build 12, under both the GPL and Oracle EA licenses, is
> now available at **http://jdk.java.net/13**.*
>
>   * Proposed - Schedule for JDK 13 [2]
>   o 2019/06/13 Rampdown Phase One
>   o 2019/07/18 Rampdown Phase Two
>   o 2019/08/08 Initial Release Candidate
>   o 2019/08/22 Final Release Candidate
>   o 2019/09/17 General Availability
>   * Recent Bug fixes of Interest
>   o Build 9:
>   + 8214719: Deprecate -Xverify:none option
>   + 8216360: Deprecate -XX:CompilationPolicyChoice
>   o Build 10:
>   + 8218995: Deprecate the -XX:FailOverToOldVerifier option
>   o Build 12 : 8160247: Mark deprecated javax.security.cert APIs
> with forRemoval=true
>   + 8220050: Deprecate -XX:-ThreadLocalHandshakes
>   + Apache Lucene Reported - 8219448: split-if update_uses
> accesses stale idom data
>   * Changes in this build [3]
>
> Rgds,Rory
>
> [1] https://mail.openjdk.java.net/pipermail/jdk-dev/2019-March/002718.html
> [2] https://mail.openjdk.java.net/pipermail/jdk-dev/2019-March/002716.html
> [3] Changes
> <
> http://hg.openjdk.java.net/jdk/jdk/log?rev=reverse%28%22jdk-13%2B11%22%3A%3A%22jdk-13%2B12%22-%22jdk-13%2B11%22%29=1000>
>
> in this build
>
>
> --
> Rgds,Rory O'Donnell
> Quality Engineering Manager
> Oracle EMEA , Dublin, Ireland
>
>

[tomcat] branch master updated: Fix await implementations

2019-03-26 Thread remm 
This is an automated email from the ASF dual-hosted git repository.

remm pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomcat.git


The following commit(s) were added to refs/heads/master by this push:
 new b885f0c  Fix await implementations
b885f0c is described below

commit b885f0cc858f51e995d4fe1c3fb86654cefa2edd
Author: remm 
AuthorDate: Tue Mar 26 10:11:22 2019 +0100

Fix await implementations

In case they ever get used again, they need to use the notify flags as
the semaphore gets released later.
---
 java/org/apache/tomcat/util/net/Nio2Endpoint.java | 36 ++-
 1 file changed, 22 insertions(+), 14 deletions(-)

diff --git a/java/org/apache/tomcat/util/net/Nio2Endpoint.java 
b/java/org/apache/tomcat/util/net/Nio2Endpoint.java
index c58aac9..0028edb 100644
--- a/java/org/apache/tomcat/util/net/Nio2Endpoint.java
+++ b/java/org/apache/tomcat/util/net/Nio2Endpoint.java
@@ -1433,30 +1433,38 @@ public class Nio2Endpoint extends 
AbstractJsseEndpoint

[tomcat] branch master updated: Deprecate unused methods

2019-03-26 Thread remm 
This is an automated email from the ASF dual-hosted git repository.

remm pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomcat.git


The following commit(s) were added to refs/heads/master by this push:
 new 661dca7  Deprecate unused methods
661dca7 is described below

commit 661dca729413795830c57b6d557b00d296594caa
Author: remm 
AuthorDate: Tue Mar 26 10:03:18 2019 +0100

Deprecate unused methods

I doubt these methods will ever be useful, so deprecate them before
possible removal.
---
 java/org/apache/tomcat/util/net/SocketWrapperBase.java | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/java/org/apache/tomcat/util/net/SocketWrapperBase.java 
b/java/org/apache/tomcat/util/net/SocketWrapperBase.java
index 03679cb..ea14e2c 100644
--- a/java/org/apache/tomcat/util/net/SocketWrapperBase.java
+++ b/java/org/apache/tomcat/util/net/SocketWrapperBase.java
@@ -970,6 +970,7 @@ public abstract class SocketWrapperBase {
  *  false if the operation is still pending and
  *  the specified timeout has passed
  */
+@Deprecated
 public boolean awaitReadComplete(long timeout, TimeUnit unit) {
 return true;
 }
@@ -984,6 +985,7 @@ public abstract class SocketWrapperBase {
  *  false if the operation is still pending and
  *  the specified timeout has passed
  */
+@Deprecated
 public boolean awaitWriteComplete(long timeout, TimeUnit unit) {
 return true;
 }


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

[Bug 63287] New: Inconsistent log level practices in Catalina component

2019-03-26 Thread bugzilla 
https://bz.apache.org/bugzilla/show_bug.cgi?id=63287

Bug ID: 63287
   Summary: Inconsistent log level practices in Catalina component
   Product: Tomcat 9
   Version: 9.0.x
  Hardware: All
OS: All
Status: NEW
  Severity: enhancement
  Priority: P2
 Component: Catalina
  Assignee: dev@tomcat.apache.org
  Reporter: anu...@163.com
  Target Milestone: -

Inconsistent log level practices in similar code snippets as well as the
modification suggestion are shown below.

* Report1 *
the problematic snippet:
 JAASMemoryLoginModule.java ===
file path: tomcat\java\org\apache\catalina\realm\JAASMemoryLoginModule.java
logging statement line: 403
modification suggestion: change log level to ERROR
399 try {
400 digester.push(this);
401 digester.parse(file);
402 } catch (Exception e) {
403 log.warn(sm.getString("jaasMemoryLoginModule.parseError", 
file.getAbsolutePath()), e);
404 } finally {
405 digester.reset();
406 }

the similar snippet:
 MbeansDescriptorsDigesterSource.java =
filepath:tomcat\java\org\apache\tomcat\util\modeler\modules\MbeansDescriptorsDigesterSource.java
logging statement line:171
166 try {
167 // Push our registry object onto the stack
168 digester.push(loadedMbeans);
169 digester.parse(stream);
170 } catch (Exception e) {
171 log.error(sm.getString("modules.digesterParseError"), e);
172 throw e;
173 } finally {
174 digester.reset();
175 }

* Report2 *
the problematic snippet:
 AccessLogValve.java ===
file path: tomcat\java\org\apache\catalina\valves\AccessLogValve.java
logging statement line: 642
modification suggestion: change log level to WARN
639 try {
640 charset = B2CConverter.getCharset(encoding);
641 } catch (UnsupportedEncodingException ex) {
642 log.error(sm.getString(
643 "accessLogValve.unsupportedEncoding", encoding),
ex);
644 }

the similar snippets:
 Response.java =
file path: tomcat\java\org\apache\coyote\Response.java
logging statement line: 550
547 try {
548 charset = B2CConverter.getCharset(charsetValue);
549 } catch (UnsupportedEncodingException e) {
550 log.warn(sm.getString("response.encoding.invalid",
charsetValue), e);
551 }

 MessageDigestCredentialHandler.java ===
file path:
tomcat\java\org\apache\catalina\realm\MessageDigestCredentialHandler.java
logging statement line: 75
72 try {
73 this.encoding = B2CConverter.getCharset(encodingName);
74 } catch (UnsupportedEncodingException e) {
75 log.warn(sm.getString("mdCredentialHandler.unknownEncoding",
76 encodingName, encoding.name()));
77 }

 Connector.java 
file path: tomcat\java\org\apache\catalina\connector\Connector.java
logging statement line: 752
749 try {
750 uriCharset = B2CConverter.getCharset(URIEncoding);
751 } catch (UnsupportedEncodingException e) {
752 log.warn(sm.getString("coyoteConnector.invalidEncoding",
753 URIEncoding, uriCharset.name()), e);
754 }

* Report3 *
the problematic snippet:
 StaticMembershipProvider.java =
file path:
tomcat\java\org\apache\catalina\tribes\membership\StaticMembershipProvider.java
logging statement line: 402
modification suggestion: change log level to ERROR
397 try {
398 sleep(pingInterval);
399 ping();
400 }catch (InterruptedException ix) {
401 }catch (Exception x) {
402
log.warn(sm.getString("staticMembershipProvider.pingThread.failed"),x);
403 }


the similar snippet:
 StaticMembershipProvider.java =
file path:
tomcat\java\org\apache\catalina\tribes\membership\StaticMembershipProvider.java
logging statement line:274
271 try {
272 if (!useThread) ping();
273 } catch (ChannelException e) {
274
log.error(sm.getString("staticMembershipProvider.heartbeat.failed"), e);
275 }

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