Hi Hannes, it can also be Nashorn triggering too much deoptimizations creating a deoptimization storm.
Rémi ----- Mail original ----- > De: "Hannes Wallnöfer" <hannes.wallnoe...@oracle.com> > À: "João Paulo Varandas" <joaovaran...@inpaas.com> > Cc: nashorn-dev@openjdk.java.net > 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 <joaovaran...@inpaas.com>: >> >> 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"
