LinkedIn
I'd like to add you to my professional network on LinkedIn.
- Buddhi
Buddhi Mihara
Trainee at WSO2
Sri Lanka
Confirm that you know Buddhi Mihara:
https://www.linkedin.com/e/8dy5yl-hq94tunk-4a/isd/19202831884/ZGdDgSEA/?hs=false&tok=3uMZUR6ar9kS41
--
You are receiving Inv
If you do get such a heap dump, please make .tar.gz of the same
available to us. We could debug at our end as well.
Thanks
-Sundar
On Friday 10 January 2014 01:06 AM, Vladimir Ivanov wrote:
Heap dumps enables post-mortem analysis of OOMs.
Pass -XX:+HeapDumpOnOutOfMemoryError to VM and it'll
Heap dumps enables post-mortem analysis of OOMs.
Pass -XX:+HeapDumpOnOutOfMemoryError to VM and it'll dump the heap
before exiting or use jmap (-dump:live,format=b,file= ) or
visualvm to take a snapshot from a running process.
There are a number of tools to browse the contents.
Best regards,
In Nashorn-land, can you "pre-compile" scripts and re-use the compiled entities
in the same way you can with Rhino? And if so, are you re-using those
instances between executions of your cron-like functions in Prudence?
-Original Message-
From: nashorn-dev-boun...@openjdk.java.net
[mai
Is there a reason why we are missing tags jdk8-b70 ... jdk8-b81 in the
JDK 8 nashorn repo?
-- Jon
hg tags -R nashorn | grep jdk8
jdk8-b120691:55cbc2d00c93
jdk8-b119682:c3343930c73c
jdk8-b118679:8d014b039b44
jdk8-b117
Hi Marcus,
Looks like some of the details have been chopped off. Is there a GC log
available? If there is a problem with MethodHandle a work around might be a
simple as expanding perm.. but wait, this is meta space now and it should grow
as long as your system has memory to give to the process.
Indeed, scripts are reused in this case, though I can't guarantee that
there isn't a bug somewhere on my end.
I'm wondering if it might be triggered by another issue: Prudence
supports an internal crontab-life feature (based on cron4j), and these
are again Nashorn scripts being run, once a min
Tal,
I've been thowing requests at the Prudence test app for the last 20
minutes or so. I do see that it uses a lot of metaspace, close to 50M in
my case. The test app seems to load/unload 2 classes per request with
Rhino compared to 4 classes per request with Nashorn, which is probably
due t
You may download the latest release of Prudence, run it and bombard it
with hits (use ab or a similar tool):
http://threecrickets.com/prudence/download/
To get the GC logs, start it like so:
JVM_SWITCHES=\
-Xloggc:/full/path/to/logs/gc.log \
-XX:+PrintGCDetails \
-XX:+PrintTenuring
Tal - The GC people 10 meters behind me want to know if you have a repro of
your full GC to death problem that they can look at? They’re interested.
/M
On 09 Jan 2014, at 16:29, Kirk Pepperdine wrote:
> Hi Marcus,
>
> Looks like some of the details have been chopped off. Is there a GC log
>
Changeset: d1d4d669373c
Author:sundar
Date: 2014-01-09 19:23 +0530
URL: http://hg.openjdk.java.net/nashorn/jdk9/nashorn/rev/d1d4d669373c
8031359: Invocable.getInterface() works incorrectly if interface has default
methods
Reviewed-by: attila, hannesw
! src/jdk/nashorn/api/scriptin
Please review http://cr.openjdk.java.net/~sundar/8031359/
Bug: https://bugs.openjdk.java.net/browse/JDK-8031359
Thanks,
-Sundar
Unfortunately, this workaround is unacceptable in many deployment
environments. I would thus consider this a showstopping bug for Nashorn,
and I hope it can be escalated.
(I understand that this is not the Nashorn project's "fault," but the
bottom line is that Nashorn cannot be used in long-ru
Regarding OOME, it's expected in this situation.
If you look at the end of the log, you'll see a set of consecutive Full
GCs. It means Java heap is almost full and reached it's maximum size.
And application is almost halted - VM collects the whole heap over and
over again (>98% of application
This almost certainly stems from the implementation from MethodHandle
combinators being implemented as lambda forms as anonymous java classes. One of
the things that is being done for 8u20 is to drastically reduce the number of
lambda forms created. I don’t know of any workaround at the moment
15 matches
Mail list logo