Hi Barry,
Yeah sorry, slight omission on my part.
I did download the "current" JDK.
I have no idea about library versions / mismatches - as I simply used
the "whole"JDK.
The process that is killed...
That might be specific to Mac - I don't exactly remember.
But it came about after some Googling - as I was having some real
issues with getting the dump to work.
and that seemed to solve it for me.
So now I just keep those lines in my clipboard manager for whenever I
need them.
I suppose the real questions is;
Does it matter if you use the whole JDK for getting jmap to work or
not?
Does using the JDK libraries simply allow the jmap application to use
appropriate libraries for it to run - or does it effect the way it
binds itself to the running process too - so that it does matter that
it does not match the JVM.
Could you not upgrade the JVM / JDK to be the same version?
Initially - I say - do whatever it takes to get it working... but I am
far from a java / library dependencies guru - so take it with a grain
of salt!
Gavin.
On Sep 16, 2:15 pm, Barry Chesterman <
barrychester...@gmail.com>
wrote:
> Those commands are similar to what I'm running (except I don't run the kill
> command on anything first)
>
> did you have the JDK on your mac?
> The jmap I'm running is a jmap I've put onto the Linux box specifically (the
> libjli.so was already there). Jmap wasn't on the box from the standard
> install, it is from a JDK I downloaded (which is supposed to be the same
> version of java which matches what's on the Linux box) I just copy the jmap
> file from the JDK stuff I downloaded.
>
> Is it possible that the libjli.so file that is already on the linux box is
> not the one the jmap from the JDK I downloaded expects perhaps?
>