On 29/10/2014 17:13, "Christian Thalinger"
wrote:
>
>> On Oct 29, 2014, at 10:06 AM, MacGregor, Duncan (GE Energy Management)
>> wrote:
>>
>> On 29/10/2014 16:55, "Christian Thalinger"
>> wrote:
>>>
On Oct 29, 2014, at 9:39 AM, MacGregor, Duncan (GE Energy Management)
wrote:
>>
> On Oct 29, 2014, at 10:06 AM, MacGregor, Duncan (GE Energy Management)
> wrote:
>
> On 29/10/2014 16:55, "Christian Thalinger"
> wrote:
>>
>>> On Oct 29, 2014, at 9:39 AM, MacGregor, Duncan (GE Energy Management)
>>> wrote:
>>>
>>> When weąve tried to debug some of our Java core in the co
On 29/10/2014 16:55, "Christian Thalinger"
wrote:
>
>> On Oct 29, 2014, at 9:39 AM, MacGregor, Duncan (GE Energy Management)
>> wrote:
>>
>> When we¹ve tried to debug some of our Java core in the context of
>>running a large application we¹ve been seeing long pauses (sometime very
>>long pauses o
> On Oct 29, 2014, at 9:39 AM, MacGregor, Duncan (GE Energy Management)
> wrote:
>
> When we’ve tried to debug some of our Java core in the context of running a
> large application we’ve been seeing long pauses (sometime very long pauses of
> over a minute) due to java.lang.invoke.MemberName$
When we’ve tried to debug some of our Java core in the context of running a
large application we’ve been seeing long pauses (sometime very long pauses of
over a minute) due to java.lang.invoke.MemberName$Factory.resolve() apparently
taking ages to complete. Testing with an openjdk build I see th
Thanks, John.
Best regards,
Vladimir Ivanov
On 10/29/14, 12:21 AM, John Rose wrote:
Good, I'm happy. Reviewed. — John
On Oct 28, 2014, at 12:04 PM, Vladimir Ivanov
mailto:vladimir.x.iva...@oracle.com>> wrote:
John, thanks for the feedback!
See my answers inline.
