Any news from JDK-8151981 in Java8 ?

Discussion:

João Paulo Varandas

2017-12-11 22:07:18 UTC

Hi guys!

We are also experiencing some odd issues here with setCallSiteTargetNormal.
https://bugs.openjdk.java.net/browse/JDK-8151981

Our cenario is:

- Web Application using Tomcat;
- 8 HTTP Threads;
- A single ScriptEngine for the whole application;

When a request hits the server, that request may be processed by a Nashorn
Script, this script is evaluated during runtime, run queries (Jdbc), and
return results (Maps and/or Collections) that are serialized to JSON before
being written to the response.

The problem is... sometimes 7 or more threads are getting stuck in the
setCallSiteTargetNormal and I have no clue why is that happening. Could you
guys help me out troubleshooting this? - Or, if there's a bug, what are the
recomended fixes I should do?

By the way, those are not freshly created ScriptEngines (which differ from
the normal issues related in the internet).
--
"Esta mensagem, incluindo seus anexos, pode conter informacoes
confidenciais e privilegiadas.
Se voce a recebeu por engano, solicitamos que a apague e avise o remetente
imediatamente.
Opinioes ou informacoes aqui contidas nao refletem necessariamente a
posicao oficial da Plusoft."

"Antes de imprimir, pense em sua responsabilidade e compromisso com o MEIO
AMBIENTE"

Hannes Wallnöfer

2017-12-12 13:11:49 UTC

Permalink

Hi João,

this functionality is part of java.lang.invoke package, not Nashorn, so we can’t help you here.

The best place to ask about this would be the core-libs-dev mailing list.

Regards,
Hannes

Post by JoÃ£o Paulo Varandas
Hi guys!
We are also experiencing some odd issues here with setCallSiteTargetNormal.
https://bugs.openjdk.java.net/browse/JDK-8151981
- Web Application using Tomcat;
- 8 HTTP Threads;
- A single ScriptEngine for the whole application;
When a request hits the server, that request may be processed by a Nashorn
Script, this script is evaluated during runtime, run queries (Jdbc), and
return results (Maps and/or Collections) that are serialized to JSON before
being written to the response.
The problem is... sometimes 7 or more threads are getting stuck in the
setCallSiteTargetNormal and I have no clue why is that happening. Could you
guys help me out troubleshooting this? - Or, if there's a bug, what are the
recomended fixes I should do?
By the way, those are not freshly created ScriptEngines (which differ from
the normal issues related in the internet).
--
"Esta mensagem, incluindo seus anexos, pode conter informacoes
confidenciais e privilegiadas.
Se voce a recebeu por engano, solicitamos que a apague e avise o remetente
imediatamente.
Opinioes ou informacoes aqui contidas nao refletem necessariamente a
posicao oficial da Plusoft."
"Antes de imprimir, pense em sua responsabilidade e compromisso com o MEIO
AMBIENTE"

Remi Forax

2017-12-12 13:52:39 UTC

Permalink

Hi Hannes,
it can also be Nashorn triggering too much deoptimizations creating a deoptimization storm.

Rémi

----- Mail original -----

Envoyé: Mardi 12 Décembre 2017 14:11:49
Objet: Re: Any news from JDK-8151981 in Java8 ?
Hi João,
this functionality is part of java.lang.invoke package, not Nashorn, so we can’t
help you here.
The best place to ask about this would be the core-libs-dev mailing list.
Regards,
Hannes

João Paulo Varandas

2017-12-12 14:13:09 UTC

Permalink

I see... I'm sorry about that, I haven't noticed the subpackage/components
in the bug report.

Post by Remi Forax
Hi Hannes,
it can also be Nashorn triggering too much deoptimizations creating a deoptimization storm.
Rémi
----- Mail original -----

Envoyé: Mardi 12 Décembre 2017 14:11:49
Objet: Re: Any news from JDK-8151981 in Java8 ?
Hi João,
this functionality is part of java.lang.invoke package, not Nashorn, so

we can’t

help you here.
The best place to ask about this would be the core-libs-dev mailing list.
Regards,
Hannes

Am 11.12.2017 um 23:07 schrieb João Paulo Varandas <
Hi guys!
We are also experiencing some odd issues here with

setCallSiteTargetNormal.

https://bugs.openjdk.java.net/browse/JDK-8151981
- Web Application using Tomcat;
- 8 HTTP Threads;
- A single ScriptEngine for the whole application;
When a request hits the server, that request may be processed by a

Nashorn

Script, this script is evaluated during runtime, run queries (Jdbc), and
return results (Maps and/or Collections) that are serialized to JSON

before

being written to the response.
The problem is... sometimes 7 or more threads are getting stuck in the
setCallSiteTargetNormal and I have no clue why is that happening. Could

you

guys help me out troubleshooting this? - Or, if there's a bug, what are

the

recomended fixes I should do?
By the way, those are not freshly created ScriptEngines (which differ

from

the normal issues related in the internet).
--
"Esta mensagem, incluindo seus anexos, pode conter informacoes
confidenciais e privilegiadas.
Se voce a recebeu por engano, solicitamos que a apague e avise o

remetente

imediatamente.
Opinioes ou informacoes aqui contidas nao refletem necessariamente a
posicao oficial da Plusoft."
"Antes de imprimir, pense em sua responsabilidade e compromisso com o

MEIO

AMBIENTE"

--
"Esta mensagem, incluindo seus anexos, pode conter informacoes
confidenciais e privilegiadas.
Se voce a recebeu por engano, solicitamos que a apague e avise o remetente
imediatamente.
Opinioes ou informacoes aqui contidas nao refletem necessariamente a
posicao oficial da Plusoft."

"Antes de imprimir, pense em sua responsabilidade e compromisso com o MEIO
AMBIENTE"

Hannes Wallnöfer

2017-12-12 14:35:02 UTC

Permalink

Hi Rémi,

Post by Remi Forax
Hi Hannes,
it can also be Nashorn triggering too much deoptimizations creating a deoptimization storm.

I agree. But given that the problem manifests itself in java.lang.invoke I think the first step is to understand what is going wrong there. Without a better understanding of the problem it is very hard to provide provide any help.

Hannes

Post by Remi Forax
Rémi
----- Mail original -----

f***@univ-mlv.fr

2017-12-12 19:41:27 UTC

Permalink

It's just that i've seen several times setCallSiteTargetNormal in the profile and each time it was my fault,
creating a GWT with the two branches swaped, invalidating SwitchPoints too vigorously, etc.

Rémi

----- Mail original -----

Envoyé: Mardi 12 Décembre 2017 15:35:02
Objet: Re: Any news from JDK-8151981 in Java8 ?
Hi Rémi,

Post by Remi Forax
Hi Hannes,
it can also be Nashorn triggering too much deoptimizations creating a
deoptimization storm.

I agree. But given that the problem manifests itself in java.lang.invoke I think
the first step is to understand what is going wrong there. Without a better
understanding of the problem it is very hard to provide provide any help.
Hannes

Post by Remi Forax
Rémi
----- Mail original -----