What does uncaught exception javalang error mean in a Blackberry curve 9320 and how do you fix it?

Answer 1

The solution to this problem is simple...

You should go to Options > Advance Options (Applications) > BB Key > Edit Permisions > Set to default.

The error will go away, BUT, you will lose your previous app permissionss and they won't have access to specific functions.

Answer 2

There is no fix other than to delete the program that is throwing the exception; it is clearly faulty.

An exception is an "exceptional circumstance", but this does not mean to imply that such circumstances are rare, it is simply that well-written software catches and handles all its exceptions and deals with them gracefully. The end-user need never be aware they are occurring. That's clearly not the case here and is a sign the software is poorly-written.

When an exception is "thrown" by a function, it simply means the function encountered an error that it wasn't able to deal with. For instance, if a caller requests an element from a sequence container and the given iterator is outwith the range of the container, an out_of_range exception may be thrown by the container object because the object cannot return an acceptable value to the caller let alone determine why the given iterator was out of range. Ultimately it is the caller's responsibility to deal with the error, not the callee.

In order for a caller to handle an exception the caller must first be aware that an exception could be thrown by the callee (and if an exception could be thrown, the programmer must always assume it will be thrown). In order to "catch" an exception, the caller must first "try" the operation. However, there will often be cases where the caller can only catch certain exceptions. Any exception it cannot specifically handle must be thrown back to its caller (and to its caller) until a caller has all the information it needs to deal with the specific error. Often, a caller will catch an exception and simply add whatever information it can provide before throwing the exception to its caller. When the exception finally reaches a handler that can actually deal with the problem gracefully, it should have all the information it needs to trace the exception back to the point it was actually thrown.

If an exception has no appropriate handler, it will eventually be thrown back to the main function. And if the main function has no appropriate handler, the program terminates with an ungraceful "uncaught exception" error. It may well be that the exception was handled en route to the main function, with each caller adding information that may have been helpful in determining the source of the exception, but if the main function doesn't handle the exception, all that information is lost.

With well-written software this should never occur. Even if an exception cannot be handled in such a way as to allow the program to continue running, a good program will include a "catch-all" exception handler in the main function that will at least log the error and provide a more graceful exit, such as prompting the user to send the exception information back to the developer and apologising for the inconvenience. That's clearly not the case here, so the best thing to do is delete the program and inform the developer.

Answer 3

That means that the application you were running had a programming bug. You must contact the vendor/developer of the application that failed for a software patch, upgrade, or fix.