The whole point of my post was to ask you guys what you wanted to help you resolve problems with memory/storage usage within the JVM, and we are now in a pointless argument about semantics. Maybe I could do with being in a job where I can waste my time this way.
Perhaps I won't bother to make the doc helpful! :=( BTW corruption is something very different to a leak, this is walking over someone else's memory/storage, at least that is what it means to me and the dumps I have to diagnose, which are not always due to JVM code. I am going to leave this and get tea (supper or evening meal or whatever you want me to call it) ready before I get even more grumpy. ------------------------------------------------------------------------------------------------------------------ Mike Poil Java z/OS Level 3 Service IBM United Kingdom Limited, Hursley Park, Winchester SO21 2JN Internal: 246824 External: +44 (0)1962 816824 Java debugging: http://www.ibm.com/developerworks/java/jdk/diagnosis/ ------------------------------------------------------------------------------------------------------------------ Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
