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

2016-11-30 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.0.x-test-nio2 has an issue affecting its community

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

2016-11-30 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.0.x-test-nio2 has an issue affecting its community

[Bug 60433] java.nio.BufferOverflowException at java.nio.HeapByteBuffer.put(Unknown Source)

2016-11-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60433 Violeta Georgieva changed: What|Removed |Added Resolution|--- |DUPLICATE

[Bug 60372] BufferOverflowException at java.nio.HeapByteBuffer.put

2016-11-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60372 Violeta Georgieva changed: What|Removed |Added CC|

[Bug 60433] java.nio.BufferOverflowException at java.nio.HeapByteBuffer.put(Unknown Source)

2016-11-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60433 Sean changed: What|Removed |Added OS||All

[Bug 60433] New: java.nio.BufferOverflowException at java.nio.HeapByteBuffer.put(Unknown Source)

2016-11-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60433 Bug ID: 60433 Summary: java.nio.BufferOverflowException at java.nio.HeapByteBuffer.put(Unknown Source) Product: Tomcat 9 Version: 9.0.0.M13 Hardware: PC

Re: Early Access build 136 for JDK 9 & JDK 9 with Project Jigsaw are available on java.net

2016-11-30 Thread Rory O'Donnell
Hi Mark, The bug has been updated with the following suggestion, any comment ? Rgds,Rory "We could possibly add an API to explicitly set the default independently per protocol. So, it would then be possible to disable it for jar: URLs, but not other URL types. This would be a new API