IBM User Guide for Java V7 on Windows > Performance > Class data sharing between JVMs

Considerations and limitations of using class data sharing

Consider these factors when deploying class data sharing in a product and using class data sharing in a development environment.

• Cache size limits
  The maximum theoretical cache size is 2 GB. The size of the cache you can specify is limited by the amount of available disk space and available virtual address space.
• JVMTI RetransformClasses() is unsupported
  You cannot run RetransformClasses() on classes loaded from the shared class cache.
• Runtime bytecode modification
  Any JVM using a JVM Tool Interface (JVMTI) agent that can modify bytecode data must use the modified=<modified_context> suboption if it wants to share the modified classes with another JVM.
• Operating system limitations
  You cannot share classes between 32-bit and 64-bit JVMs. Temporary disk space must be available to hold cache information. The operating system enforces cache permissions.
• Using SharedClassPermission
  If a SecurityManager is being used with class data sharing and the running application uses its own class loaders, you must grant these class loaders shared class permissions before they can share classes.

Parent: Class data sharing between JVMs

Error 404 - Not Found

The document you are looking for may have been removed or re-named. Please contact the web site owner for further assistance.