Skip navigation.

Migration Guide

   Previous Next vertical dots separating previous/next from contents/index/pdf Contents View as PDF   Get Adobe Reader


Best Coding Practices for JVM Migration

Read the Relevant Specifications

Example 1: Reflection

Example 2: Reflection Revisited

Example 3: Serialization

Never Use Deprecated Unsafe Methods

Minimize the Use of Finalizers

Don't Depend on Thread Priorities

Don't Use Internal sun.* or COM.jrockit.* Classes

Override java.Object.hashCode for User Defined Classes When Using java.util.Hashtable

Do Careful Thread Synchronization

Expect Only Standard System Properties

Minimize the Number of Java Processes

Avoid Calling System.gc()


An Application Does Not Run

Slow-to-Start Applications

Large Memory Consumption

Slow Performance vis-a-vis HotSpot

Randomly Appearing Bugs

WebLogic JRockit Throws Errors HotSpot Does Not Throw

Slow Performance in Development Mode

WebLogic JRockit Does Not Run Jakarta Tomcat as a Windows Service

Support for the /3GB Windows Startup Option

Support for PAE on Windows

Other Frequently Asked Questions

Profiling and Debugging with WebLogic JRockit

Profiling WebLogic JRockit


How JVMPI Works

Changing the JVMPI Default Behavior

Additional JVMPI Documentation

Debugging with WebLogic JRockit

Java Virtual Machine Debugger Interface (JVMDI)

How JVMDI Works

JVMDI Documentation

Migrating to WebLogic JRockit

About Application Migration

Why Migrate?

Migration Restrictions

Migration Support

Migration Procedures

Environment Changes

Other Tips

Tuning WebLogic JRockit JVM for Your Application

Testing the Application

Why Test?

How to Test

Submitting Migration Tips


Skip footer navigation  Back to Top Previous Next