On Mon, May 13, 2019 at 4:11 PM Thomas Stüfe
wrote:
>
>
> On Mon, May 13, 2019 at 3:42 PM Thomas Stüfe
> wrote:
>
>>
>> Hi Martin,
>>
>> On Mon, May 13, 2019 at 2:08 PM Martin Buchholz
>> wrote:
>>
>>>
>>>
>>> I am happy this is resolved and the intermittent behavior explained. Yes,
we cou
On Mon, May 13, 2019 at 3:42 PM Thomas Stüfe
wrote:
>
> Hi Martin,
>
> On Mon, May 13, 2019 at 2:08 PM Martin Buchholz
> wrote:
>
>>
>>
>> I am happy this is resolved and the intermittent behavior explained. Yes,
>>> we could improve exception messages, especially since analyzing fork
>>> scenar
On Mon, May 13, 2019 at 4:08 PM Martin Buchholz wrote:
>
>>> I tried hard back in 2005 to provide pretty good java-level diagnostics
>>> when subprocess starting failed somehow (see WhyCantJohnnyExec) . At least
>>> the errno did get reported.
>>>
>>>
>> I know your code. For many years I wonder
>
>
>> I tried hard back in 2005 to provide pretty good java-level diagnostics
>> when subprocess starting failed somehow (see WhyCantJohnnyExec) . At least
>> the errno did get reported.
>>
>>
> I know your code. For many years I wondered who Johnny is :)
>
https://en.wikipedia.org/wiki/Rudolf_F
Hi Martin,
On Mon, May 13, 2019 at 2:08 PM Martin Buchholz wrote:
>
>
> I am happy this is resolved and the intermittent behavior explained. Yes,
>> we could improve exception messages, especially since analyzing fork
>> scenarios is cumbersome.
>>
>
> I tried hard back in 2005 to provide pretty
I am happy this is resolved and the intermittent behavior explained. Yes,
> we could improve exception messages, especially since analyzing fork
> scenarios is cumbersome.
>
I tried hard back in 2005 to provide pretty good java-level diagnostics
when subprocess starting failed somehow (see WhyCant
-dev@openjdk.java.net>
> *Envoyé: *Samedi 11 Mai 2019 20:49:02
> *Objet: *Re: Process.exec with the linux posix_spawn mode has a bug
>
> Hi Remi,
>
> David is right - a few more details:
> In both fork- and vfork-mode we fork/vfork the child process and in the
> child process then exec
- Mail original -
> De: "Alan Bateman"
> À: "core-libs-dev" , "Remi Forax"
>
> Envoyé: Dimanche 12 Mai 2019 10:32:59
> Objet: Re: Process.exec with the linux posix_spawn mode has a bug
> On 12/05/2019 09:23, fo...@univ-mlv.fr wrote:
>
On 12/05/2019 09:23, fo...@univ-mlv.fr wrote:
Thanks Thomas,
by the way, what is the purpose of jexec ?
jexec is legacy, should probably be removed [1].
It's good that the issue has been tracked down but I'm curious why it
was initially intermittent. I would have expected it to fail every tim
Thanks Thomas,
by the way, what is the purpose of jexec ?
Rémi
> De: "Thomas Stüfe"
> À: "David Lloyd"
> Cc: "Remi Forax" , "core-libs-dev"
>
> Envoyé: Samedi 11 Mai 2019 20:49:02
> Objet: Re: Process.exec with the linux posix_spawn
-
> De: "David Lloyd"
> À: "Remi Forax"
> Cc: "core-libs-dev" , "Roger Riggs"
> , "Alan Bateman"
>
> Envoyé: Samedi 11 Mai 2019 17:14:56
> Objet: Re: Process.exec with the linux posix_spawn mode has a bug
> On Sat, May 11, 20
Hi Remi,
David is right - a few more details:
In both fork- and vfork-mode we fork/vfork the child process and in the
child process then exec() the target binary (in this case "java" itself).
In posix_spawn mode, for complicated reasons, we start, via posix_spawn(),
the jspawnhelper - which, dep
On Sat, May 11, 2019 at 9:49 AM Remi Forax wrote:
>
> I've seen a weird error on my CI [1] since the 15th of February when using
> the jdk 13,
> i was not able to run jshell* using the programmatic API (java tool) anymore.
>
> Yesterday, i took the time to track that issue and i believe i've foun
I've seen a weird error on my CI [1] since the 15th of February when using the
jdk 13,
i was not able to run jshell* using the programmatic API (java tool) anymore.
Yesterday, i took the time to track that issue and i believe i've found the
root cause, trying to execute the java launcher using P
14 matches
Mail list logo
