Hi Jaroslav,
So ... activeReferenceQueue is a reference queue that embodies a thread
that does the polling and implements a psuedo-finalization mechanism.
This works fine in the normal case where the lifetime of the queue is
the lifetime of the "application". In the WAR case (and I don't know
Hi Folks,
Please review the following clean up and refactoring of the CDS code,
for JDK9
http://cr.openjdk.java.net/~iklam/8046070-cds-cleanup-v2/
https://bugs.openjdk.java.net/browse/JDK-8046070
Summary of fix:
Clean up and refactor the Class Data Sharing (CDS) code, including:
Hello Jaroslav,
Regardless of where it is implemented (in JDK or in NetBeans) it would
be impossible to create something that doesn't do polling in a single
thread and yet wait for two ReferenceQueues at the same time - one is
the queue of Runnable references which you run() and the other is t
Thanks Pavel. Reviewed.
-Chris.
On 28/07/14 16:11, Pavel Rappo wrote:
Well spotted, Chris! Here's the updated webrev which fixes that misunderstanding (see
test "AppletIsNotUsed"):
http://cr.openjdk.java.net/~prappo/8051422/webrev.01/
Thanks,
-Pavel
On 28 Jul 2014, at 15:37,
Well spotted, Chris! Here's the updated webrev which fixes that
misunderstanding (see test "AppletIsNotUsed"):
http://cr.openjdk.java.net/~prappo/8051422/webrev.01/
Thanks,
-Pavel
On 28 Jul 2014, at 15:37, Chris Hegarty wrote:
> Pavel,
>
> The implementation changes look fin
Pavel,
The implementation changes look fine.
It is surprising too see that NoApplet now succeeds to create the
InitialContext, which made to take another look at the code. So the
context can still be created, and it will throw an Exception on first
use, lookup, etc. Maybe it is worth expandin
> In response to previous feedback, I propose this revised change to the
> specification:
>
+1
Paul.
> --- a/src/share/classes/java/util/DoubleSummaryStatistics.javaSat Jul 19
> 11:22:08 2014 +0800
> +++ b/src/share/classes/java/util/DoubleSummaryStatistics.javaMon Jul 21
> 18:02:54
On 28/07/2014 11:04, Pavel Rappo wrote:
Hi everyone,
Could you please review my change for JDK-8051422?
http://cr.openjdk.java.net/~prappo/8051422/webrev.00/
-Pavel
JDK-8049270 was the original issue tracking this, I guess we should
close this as a dup now and move the labels.
In any case,
Hi Roger,
I think that may be a question for the AIX folks to answer as I'm not
familiar with the reasons for this addition. I've cc'd Volker. In the
interests of expediency I'd rather deal with that separately.
-Rob
On 24/07/14 22:40, roger riggs wrote:
Hi,
Seems like pretty simple; b
Hello David,
thanks for being patient with me. I'll do my best to describe the original
context.
Dne Po 28. července 2014 21:07:45, David Holmes napsal(a):
> I read the issue and still did not understand the nature of the problem.
> The netbeans bugs also did not shed any light on things for me.
Hi Henry,
sorry for no response, I missed this one.
Yes, this looks reasonable. You can proceed with the change, I'll
integrate it into upstream projects.
Thanks
Miran
On 28/07/14 11:11, Henry Jen wrote:
Hi Micoslav,
What do you think about the webrev[1]? Does it make sense for upstream
On 28/07/2014 5:23 PM, Jaroslav Tulach wrote:
Thanks for your reply.
Dne Pá 25. července 2014 12:45:02, Brian Goetz napsal(a):
So, let’s start with the problem, rather than the solution.
That is always better start.
Could you start
with writing up what issue you’re trying to address,
I be
Hi everyone,
Could you please review my change for JDK-8051422?
http://cr.openjdk.java.net/~prappo/8051422/webrev.00/
-Pavel
On 28/07/2014 7:28 PM, Peter Firmstone wrote:
Updated files attached, including update to State of Serialization draft.
For those who didn't get the attachment:
*State of Java Serialization - Draft*
Introduction
The Java Serialization framework enables object state to be frozen,
stored to
Updated files attached, including update to State of Serialization draft.
Note that the attached source code can be provided under the Oracle
agreement.
I'm a little time poor, so please contribute suggestions etc.
Regards,
Peter.
On 26/07/2014 7:57 PM, Peter Firmstone wrote:
I'm somewhat
Hi Micoslav,
What do you think about the webrev[1]? Does it make sense for upstream
maintainers?
[1] http://cr.openjdk.java.net/~henryjen/jdk9/8047724/0/webrev/
Cheers,
Henry
On 06/30/2014 03:14 PM, Alan Bateman wrote:
On 30/06/2014 02:30, Henry Jen wrote:
Ping.
Cheers,
Henry
Henry - th
One thing I should add is that an alternative solution to the WAR-leak
problem[2] is
repeated pooling.
The reason NetBeans did not use it, is that our performance team dislikes
repeatedly
executed tasks (you know, when various parts of the IDE wake up every 15s each
you
end up, due to # of
Thanks for your reply.
Dne Pá 25. července 2014 12:45:02, Brian Goetz napsal(a):
> So, let’s start with the problem, rather than the solution.
That is always better start.
> Could you start
> with writing up what issue you’re trying to address,
I believe I did that in the issue description.
18 matches
Mail list logo