Re: Executors enhancement

2016-08-13 Thread Bernd Eckenfels
Hello, yes, an ExecutorService or Executor or ForkJoinPool depending on the minimum requirements you have. As a default you can eithter use ForJoinPool.commonPool() or Executors.newSingleThreadExecutor() or a DirectExecutor() if you dont want to handle the null case special. BTW: little nit, I w

Re: Executors enhancement

2016-08-13 Thread Christian Schulte
Am 08/09/16 um 19:04 schrieb e...@zusammenkunft.net: > So it is a good idea to find a good shared default, but an API quite > seldomly can isolate itself and the users about those aspects. So always > allow to provide an alternate Executor. This also helps with thread > naming, thread context, inte

Re: RFR: 8156500: deadlock provoked by new stress test com/sun/jdi/OomDebugTest.java

2016-08-13 Thread Mandy Chung
> On Aug 13, 2016, at 1:20 AM, Peter Levart wrote: > > Hi Mandy, > > On 08/13/2016 01:55 AM, Mandy Chung wrote: >>> On Aug 8, 2016, at 6:25 PM, Kim Barrett >>> wrote: >>> >>> full: >>> http://cr.openjdk.java.net/~kbarrett/8156500/jdk.04/ >>> >>> >>> http://cr.openjdk.java.net/~kbarre

Re: RFR: 8156500: deadlock provoked by new stress test com/sun/jdi/OomDebugTest.java

2016-08-13 Thread Peter Levart
Hi Mandy, On 08/13/2016 01:55 AM, Mandy Chung wrote: On Aug 8, 2016, at 6:25 PM, Kim Barrett wrote: full: http://cr.openjdk.java.net/~kbarrett/8156500/jdk.04/ http://cr.openjdk.java.net/~kbarrett/8156500/hotspot.04/ This looks very good. Have you considered having JVM_WaitForReference