Early Access builds of JDK 9 b134 are available on java.net
by Rory O'Donnell
Hi Galder,
Early Access b134 <https://jdk9.java.net/download/> for JDK 9 is
available on java.net, summary of changes are listed here
<http://www.java.net/download/java/jdk9/changes/jdk-9+134.html>.
There have been a number of fixes , since the last availability email
, to bugs reported by Open Source projects :
* 8156841 sun.security.pkcs11.SunPKCS11 poller thread retains a
strong reference to the context class loader
* 8146961 Fix PermGen memory leaks caused …
[View More]by static final Exceptions
* 8163353 NPE in ConcurrentHashMap.removeAll()
* 8160328 ClassCastException: sun.awt.image.BufImgSurfaceData cannot
be cast to sun.java2d.xr.XRSurfaceData after xrandr change output
Secondly, there are a number of interesting items to bring to our attention
* JDK 9 Rampdown Phase 1: Process proposal [1]
* The Java team has published the “Oracle JRE and JDK Cryptographic
Roadmap” [2] java.com/cryptoroadmap <http://java.com/cryptoroadmap>
* The Quality Report for September 2016 is now available [3], thank
you for your continued support!
Highlights from the Quality Report for September :
* 21 new Open Source projects have joined the Outreach program
* Projects filed 35 new issues in the JDK Bug System, this is almost
double the number of bugs in the previous six months!
* Continuing to provide excellent feedback via the OpenJDK dev mailing
lists
Thank you!
Rgds,Rory
[1] http://mail.openjdk.java.net/pipermail/jdk9-dev/2016-August/004777.html
[2] java.com/cryptoroadmap <http://java.com/cryptoroadmap>
[3]
https://wiki.openjdk.java.net/display/quality/Quality+Outreach+Report+Sep...
--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland
[View Less]
8 years, 6 months
- 1
- 0
Unwrapping exceptions
by Radim Vansa
When enhancing functional API implementation, I've stumbled upon the way
the exceptions from lambdas should be thrown to user code.
Intuitively I've expected that when my lambda throws an exception, I'll
catch it from cache.eval(...). That may be the case when the lambda is
still executed locally, but when it goes remote, the exception is
wrapped into RemoteException etc.
In the past, exceptions being thrown were a matter of failure inside
Infinispan, but what about here? User does not …
[View More]need to know where the
functional expression has been executed, so it seems to me that he
should get the exception directly.
WDYT?
Radim
--
Radim Vansa <rvansa(a)redhat.com>
JBoss Performance Team
[View Less]
8 years, 7 months
- 3
- 6