On Tue, Aug 10, 2021 at 1:34 AM Luke Hutchison wrote:
> Maybe that should be part of the Instrumentation class, so that it is only
> accessible to Java agent code that is able to get a reference to an
> Instrumentation object.
>
Actually I take that last part back, that would
On Tue, Aug 10, 2021 at 12:51 AM Luke Hutchison
wrote:
> Could a getURLClassPath() method please be added to BuiltInClassLoader?
>
For security reasons, the getURLClassPath() method should return a copy of
ucp, not the reference to ucp, to prevent the caller from modifying the
system classpath.
Thank you Remi and David for your detailed explanations, this was very
helpful, and I understand the issues now. Please go ahead and close the
Jira bug I created for this (JDK-8173252), I see this is WAI.
On Tue, Jan 24, 2017 at 12:39 AM, wrote:
> Here is your code slightly
On Tue, Jan 24, 2017 at 12:02 AM, Remi Forax wrote:
> a worker thread of the executor will try to execute the code of the static
> method but because the static initializer is not finished, the worker
> thread has to wait
But what is the worker thread waiting for in the case
On Mon, Jan 23, 2017 at 11:37 PM, Luke Hutchison <luke.hu...@gmail.com>
wrote:
> On Mon, Jan 23, 2017 at 11:21 PM, Luke Hutchison <luke.hu...@gmail.com>
> wrote:
>
>> That looks like a variation of the classic class initialization deadlock
>>> problem. Your
On Mon, Jan 23, 2017 at 11:21 PM, Luke Hutchison <luke.hu...@gmail.com>
wrote:
> That looks like a variation of the classic class initialization deadlock
>> problem. Your main thread is blocked in es.submit(callable).get(); while
>> still within the static initializer o
On Mon, Jan 23, 2017 at 10:48 PM, David Holmes <david.hol...@oracle.com>
wrote:
> On 24/01/2017 2:41 PM, Luke Hutchison wrote:
>
>> If you run the code below, the active JVM thread (in the ExecutorService)
>> locks up when the lambda expression is called. The Eclipse
If you run the code below, the active JVM thread (in the ExecutorService)
locks up when the lambda expression is called. The Eclipse debugger is not
able to stop the locked-up thread, or get a stacktrace beyond the call into
the lambda.
The problem seems to be that some part of the Java 8 lambda