Just to close off this thread,
I got around the issue by using the entire JDK, it would appear that
just using jmap on its own doesn't work with the standard JVM
libraries (no doubt jmap needs specific libraries that only come with
the JDK).
I just put the JDK (downloaded and extracted straight
Have you tried
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/jrun4/jre/lib/amd64/jli/
then run jmap
Cheers,
Simon
On 16 September 2011 14:46, Gavin Baumanis beauecli...@gmail.com wrote:
Hi Barry,
Yeah sorry, slight omission on my part.
I did download the current JDK.
I have no idea about
Hi Barry,
I have these notes for running jmap on my mac.
// Check for this
ps -ef | grep hsdbd
// if it is running - kill it;
sudo kill -9 pid
// Get the PID of JRUN
sudo ps-ef | grep jrun
// Map the heap.
sudo jmap -dump:format=b,file=heap.bin pid
Hope this helps.
Gavin.
On Sep 16, 7:53
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
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 wholeJDK.
The process that is killed...
That might be specific to Mac - I don't exactly remember.
But it came about after some Googling -
