Often, Java error messages can seem cryptic and difficult to resolve. The complexity and diversity of the Java environment is such that each error occurrence can seem unique. The type of Application Server being used and the idiosyncrasies associated with its particular setup can add additional opportunities for error creation.
When it comes to deciphering Java errors, the Internet can sometimes be your best friend. This is especially true if the error seems to be related to a particular Application Server like WebSphere or WebLogic. Doing an Advanced Google search on the error message and the name of the Application Server can often pinpoint the exact cause of the error or at least point you in the right direction.
Here are a few common Java errors and their possible causes and remedies:
This error indicates that an array has been accessed with an illegal index. The index is either negative or greater than or equal to the size of the array.
This error can occur when the statement "IF LAST OF g_exp IS EQUAL TO 1" is executed in the event Window_ACTIVATED and a "GET ROW HIGHLIGHTED" is being used when a row has not been highlighted. The subscript therefore returns a value of 0, which is invalid. Always test that the subscript is greater than 0 before proceeding. The error occurs on the web because Java is a lot stricter than C.
This error can also occur when executing the TIRFNUMD function from an EJB. This can be caused by an uninitialized attribute view.
This error occurs when an application tries to load in a class through its string name using: The forName method in class Class .
This error means what it says. To help the Class be found, make sure that the location of the Class (or the JAR file containing it) is in the CLASSPATH environment variable. Another possible cause of this error is not generating and deploying all of the procedures needed by the application.
If you get this error that references TCPIPTranEntry, you probably need to install the TCP/IP Middleware. The TCPIPTranEntry.class file is contained within the file odc85.tcpip.jar. This gets installed as part of the TCP/IP Middleware option. Check your ca.olf file for this key. If it is present, install the option. If the TCP/IP Middleware option is missing from your ca.olf file, call CA Licensing at 800-225-5224 (631-881-6801) to obtain the key. Once the TCP/IP option is installed, create a new gen85rt.jar to clear up the error when running the proxy.
The class Exception and its subclasses are a form of Throwable that indicates conditions that a reasonable application might want to catch.
This type of java error can occur if the wrong case is used when specifying parameters in the jdbccfg.properties file. When in doubt, check the spelling for typos and pay special attention to case.
Thrown if an application tries to call a specified method of a class (either static or instance), and that class no longer has a definition of that method.
This error in conjunction with the TIRFDDUR (Date Duration Function) can be caused by using older versions of a number of RI Triggers. Regenerating the RI Triggers resolves the problem.
Thrown by String methods to indicate that an index is either negative or greater than the size of the string.
This error in conjunction with a customized TIRCRUNC runtime and a "String index out of range: 0" message can occur if the mkcrun jcl is incorrectly modified. For example: if you forget to remove the comments after the codepage, i.e., if lines are:
0 437 AllFusion Gen default translation tables (REQUIRED)
An error has occurred in the script on this page.
Error: Object doesn't support this property or method.
The CA Gen Toolset no longer allows you to add a control without giving it a name but sometimes models have this condition for unknown reasons.