The following sections describe some of the situations you might
encounter with shared classes and also the tools that are available to assist
in diagnosing problems.
Using shared classes trace
Use shared classes trace output only for debugging internal problems
or for a very detailed trace of activity in the shared classes code.
Dealing with initialization problems
Shared classes initialization requires a number of operations
to succeed. A failure might have many potential causes, and it is
difficult to provide detailed message information following an initialization
failure. Some common reasons for failure are listed here.
Dealing with verification problems
Verification problems (typically seen as java.lang.VerifyErrors)
are potentially caused by the cache returning incorrect class bytes.