Blackberry jvm error code & their description Part 2
109
PriorityMessageCount error:
The value returned by RimPriorityMessageCount is negative. It should always be greater than, or equal to, zero. This indicates an error in the operating system code. Extract the current (post-reset) BUGDISP and EVENTLOG.
110
Non-idle event downtime error:
A problem was detected in the accumulation of JVM down time, which represents how long the JVM has been idle. This usually indicates an error in the device firmware or the JVM. This could also occur if the tick count rolls over after 400 or more days of device time.
111
Font engine error
An error was detected in the font engine system on the device. Extract the current (post-reset) BUGDISP and EVENTLOG.
112
Java Native Assertion Failure
An error was detected in the Java native code. Extract the current (post-reset) BUGDISP and EVENTLOG.
200
Application manager threw an uncaught exception
The application manager event thread threw an uncaught exception and cannot continue execution.
201
Crypto initialization code failed
The initialization of the crypto system failed and the device cannot continue execution.
202
An attack on the key store has been detected
An attack has been detected and execution cannot continue.
203
Console process died
The application manager console process (usually the Ribbon) has died. This is likely due to an uncaught exception during execution.
204
Persistent Content Exception
An application tried to commit a plaintext object to the Persistent Store. This will only happen if Content Protection is on and a process tries to save something in the PersistentStore that is marked as plaintext. Since this exception was not handled, the persistent store is in a bad state. You should reset to roll back to the last good commit point.
Note: This is not a JVM erro; the JVM is simply diagnosing the problem. The eventlog contains information about the erroneous Java code.
501 VM_THREAD_SWITCHED:
Internal Error This is an error return used internally in the VM. It should never be reported as a device error.
502 VM_PROCESS_DEATH:
All processes exited The last Java process has terminated. There is nothing left to execute.
503 VM_THREAD_DEATH:
Internal Error This is an error return used internally in the VM. It should never be reported as a device error.
504 VM_THREAD_SWITCH:
Internal Error This is an error return used internally in the VM. It should never be reported as a device error.
PriorityMessageCount error:
The value returned by RimPriorityMessageCount is negative. It should always be greater than, or equal to, zero. This indicates an error in the operating system code. Extract the current (post-reset) BUGDISP and EVENTLOG.
110
Non-idle event downtime error:
A problem was detected in the accumulation of JVM down time, which represents how long the JVM has been idle. This usually indicates an error in the device firmware or the JVM. This could also occur if the tick count rolls over after 400 or more days of device time.
111
Font engine error
An error was detected in the font engine system on the device. Extract the current (post-reset) BUGDISP and EVENTLOG.
112
Java Native Assertion Failure
An error was detected in the Java native code. Extract the current (post-reset) BUGDISP and EVENTLOG.
200
Application manager threw an uncaught exception
The application manager event thread threw an uncaught exception and cannot continue execution.
201
Crypto initialization code failed
The initialization of the crypto system failed and the device cannot continue execution.
202
An attack on the key store has been detected
An attack has been detected and execution cannot continue.
203
Console process died
The application manager console process (usually the Ribbon) has died. This is likely due to an uncaught exception during execution.
204
Persistent Content Exception
An application tried to commit a plaintext object to the Persistent Store. This will only happen if Content Protection is on and a process tries to save something in the PersistentStore that is marked as plaintext. Since this exception was not handled, the persistent store is in a bad state. You should reset to roll back to the last good commit point.
Note: This is not a JVM erro; the JVM is simply diagnosing the problem. The eventlog contains information about the erroneous Java code.
501 VM_THREAD_SWITCHED:
Internal Error This is an error return used internally in the VM. It should never be reported as a device error.
502 VM_PROCESS_DEATH:
All processes exited The last Java process has terminated. There is nothing left to execute.
503 VM_THREAD_DEATH:
Internal Error This is an error return used internally in the VM. It should never be reported as a device error.
504 VM_THREAD_SWITCH:
Internal Error This is an error return used internally in the VM. It should never be reported as a device error.
0 comments:
Post a Comment