Thanks Daniel and David!
I'll need a sponsor to help me push the change.
Sincerely yours,
Ivan
On 08.09.2014 6:03, David Holmes wrote:
Hi Ivan,
On 7/09/2014 4:07 PM, Ivan Gerasimov wrote:
Hello!
This is a proposal to address issue with wrong exit codes from a Java
processes on Windows.
In
Hi Ivan,
On 7/09/2014 4:07 PM, Ivan Gerasimov wrote:
Hello!
This is a proposal to address issue with wrong exit codes from a Java
processes on Windows.
In order to avoid a race, calls to _endthread(), exit and _exit() are
explicitly synchronized.
We allow simultaneous calls to _endthread() by m
On 9/7/14 12:07 AM, Ivan Gerasimov wrote:
Hello!
This is a proposal to address issue with wrong exit codes from a Java
processes on Windows.
In order to avoid a race, calls to _endthread(), exit and _exit() are
explicitly synchronized.
We allow simultaneous calls to _endthread() by multiple t
Thank you so much, Dmitry!
Yasumasa
(2014/09/07 23:49), Dmitry Samersoff wrote:
Yasumasa,
I'll sponsor the push.
-Dmitry
On 2014-09-07 17:04, Yasumasa Suenaga wrote:
Hi all,
This issue is related to JDK-8057556: JDP should better handle non-active
interfaces
http://mail.openjdk.java.net/
Yasumasa,
I'll sponsor the push.
-Dmitry
On 2014-09-07 17:04, Yasumasa Suenaga wrote:
> Hi all,
>
> This issue is related to JDK-8057556: JDP should better handle non-active
> interfaces
> http://mail.openjdk.java.net/pipermail/serviceability-dev/2014-September/015548.html
>
> JMX agent will
Hi all,
This issue is related to JDK-8057556: JDP should better handle non-active
interfaces
http://mail.openjdk.java.net/pipermail/serviceability-dev/2014-September/015548.html
JMX agent will be terminated silently when I run command as following:
java -Dcom.sun.management.jmxremote.port=7091
