Blackberry jvm error code & their description Part 3
505 VM_BAD_CODE:
Bad Byte Code An error has occurred in the JIT compiler.
506 Uncaught Exception
An uncaught Java exception was thrown in the initial VM Java thread, thus ending the only live thread in the system. The eventlog contains the traceback for the exception.
507 Unsatisfied Link
A dependency on a COD file could not be satisfied because the COD file is missing.
508 Invalid object
A problem has been detected with a debugger command to the VM.
509 VM_PPO_INFINITE_LOOP:
infinite loop in PPO phase of GC The maximum iteration count for the PPO phase of a GC must be the maximum number of file handles in the system. This error indicates that the iteration count exceeds the maximum. Hence, a flaw exists in the PPO loop or a corrupted file system. The extra hex integer in the error string is the flash id of the current record where the infinite loop was detected.
510 Deadlock
All threads are waiting on objects, resulting in deadlock. The system cannot recover from this state because no thread can release a lock.
511 Debug connection died
A problem has occurred while debugging that may be caused by a VM problem or an incorrect debugging command being sent to the VM.
512 GC Aborted
An idle garbage collection has been interrupted by a user event (for instance, a key was pressed or the trackwheel was used).
513 needs running
An opcode requires that a class execute before it can continue execution.
514 needs running
A new instance of a class has been allocated and it must be initialized by the default constructor before it can be used.
515 Object group too big
The reachable objects form a group that cannot be represented properly by the JVM because either there are too many objects or the total size of the objects is too large.
516 Persistent ids exhausted
When committing a persistent object, the JVM found that the persistent store id counter reached its limit. The object was not committed and a critical error was reported. This error should not occur unless a device is heavily used for years.
517 Filesystem corrupt
An inconsistency was detected in the JVM persistent object store.
518 Unexpected longjmp
A garbage collection marking phase was terminated via a longjmp. This indicates that the marking phase was interrupted when it should have completed without interruption. This error should not occur because these actions are executed when the device is not idle, and GCs can only be interrupted when the device is idle.
519 Internal Error
The JVM host is missing or has been disabled.
520 Internal Return
This is an internal state that indicates a Java method return needs to be executed.
521 Dangerous Wait
An Object.wait() was executed by a thread that holds a lock on another object.
522 Interlaced synchronization
A thread acquired two locks on objects in an order that doesn't match the order in which a lock on the two types were previously acquired. This indicates a future potential deadlock situation and is reported. The check is only available in the simulator under the control of the JvmDebugLocks application switch.
523 System process died
A critical Java process has terminated, and the device cannot continue to operate in a normal manner.
524 LMM error
An object has been marked as recovered by the Low Memory Manager, but it was not freed during a garbage collection.
525 Bad persistent object
An auto-commit operation during a garbage collection detected a non-persistent object reachable from the persistent store root. The type of the object was output into the eventlog.
526 java.lang.Object not found
The class definition for java.lang.Object cannot be found.
527 java.lang.String not found
The class definition for java.lang.String cannot be found.
Bad Byte Code An error has occurred in the JIT compiler.
506 Uncaught Exception
An uncaught Java exception was thrown in the initial VM Java thread, thus ending the only live thread in the system. The eventlog contains the traceback for the exception.
507 Unsatisfied Link
A dependency on a COD file could not be satisfied because the COD file is missing.
508 Invalid object
A problem has been detected with a debugger command to the VM.
509 VM_PPO_INFINITE_LOOP:
infinite loop in PPO phase of GC The maximum iteration count for the PPO phase of a GC must be the maximum number of file handles in the system. This error indicates that the iteration count exceeds the maximum. Hence, a flaw exists in the PPO loop or a corrupted file system. The extra hex integer in the error string is the flash id of the current record where the infinite loop was detected.
510 Deadlock
All threads are waiting on objects, resulting in deadlock. The system cannot recover from this state because no thread can release a lock.
511 Debug connection died
A problem has occurred while debugging that may be caused by a VM problem or an incorrect debugging command being sent to the VM.
512 GC Aborted
An idle garbage collection has been interrupted by a user event (for instance, a key was pressed or the trackwheel was used).
513
An opcode requires that a class
514
A new instance of a class has been allocated and it must be initialized by the default constructor before it can be used.
515 Object group too big
The reachable objects form a group that cannot be represented properly by the JVM because either there are too many objects or the total size of the objects is too large.
516 Persistent ids exhausted
When committing a persistent object, the JVM found that the persistent store id counter reached its limit. The object was not committed and a critical error was reported. This error should not occur unless a device is heavily used for years.
517 Filesystem corrupt
An inconsistency was detected in the JVM persistent object store.
518 Unexpected longjmp
A garbage collection marking phase was terminated via a longjmp. This indicates that the marking phase was interrupted when it should have completed without interruption. This error should not occur because these actions are executed when the device is not idle, and GCs can only be interrupted when the device is idle.
519 Internal Error
The JVM host is missing or has been disabled.
520 Internal Return
This is an internal state that indicates a Java method return needs to be executed.
521 Dangerous Wait
An Object.wait() was executed by a thread that holds a lock on another object.
522 Interlaced synchronization
A thread acquired two locks on objects in an order that doesn't match the order in which a lock on the two types were previously acquired. This indicates a future potential deadlock situation and is reported. The check is only available in the simulator under the control of the JvmDebugLocks application switch.
523 System process died
A critical Java process has terminated, and the device cannot continue to operate in a normal manner.
524 LMM error
An object has been marked as recovered by the Low Memory Manager, but it was not freed during a garbage collection.
525 Bad persistent object
An auto-commit operation during a garbage collection detected a non-persistent object reachable from the persistent store root. The type of the object was output into the eventlog.
526 java.lang.Object not found
The class definition for java.lang.Object cannot be found.
527 java.lang.String not found
The class definition for java.lang.String cannot be found.
0 comments:
Post a Comment