HotSwap

Patch name: hotswap.patch
Description: hotswap.txt

Implementation Notes

Thomas Wuerthinger, Dynamic Code Evolution for the Java HotSpotVirtual Machine

General Design Decisions

  • Arbitrary changes possible (including changes to subtype relationships)
  • No performance penalty before or after the change
  • No introduced indirections
  • Continued execution of old active methods
  • Only simple, comprehensible strategies for field matching or method transitions
  • Change possible at any point when the VM is suspended
  • Graceful handling of accesses to deleted fields or calls of deleted methods

Status

  • General mechanisms including the modifications to the garbage collector implemented, however still stability issues.
  • Missing critical feature: Determine safety of type narrowing changes.
  • Next step: Stabilize using the hotswapping test suite.
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Sun Microsystems community and they might not be employed or in any way formally affiliated with Sun Microsystems. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Sun nor any other party necessarily agrees with them.

Copyright 1994-2009 Sun Microsystems, Inc.
Powered by Atlassian Confluence
Sun Guidelines on Public Discourse Privacy Policy Terms of Use Trademarks Site Map Employment Investor Relations Contact