Troubleshooting Problems Using Log Files (Release 9.2.5.3 Update)

If you need to view logging information for the Java client, open the Java Console open the Java Console in the browser of your choice. The Java Console displays all problems that the Java Virtual Machine on the client is having. Errors appear as uncaught exceptions in the console.

Note: You must have the appropriate internet options turned on to view the Java Console.

When you enable the Java Console in your browser, turn on these options:

• Java Console enabled.

• Java logging enabled.

• JIT compiler for virtual machine enabled.

If you need to troubleshoot errors in web applications:

• Verify that the problem is only a problem on the web.

  Test the fat client version of the same application against the same enterprise server that the web is using. Make sure that you use the same JD Edwards EnterpriseOne accounts and environments.

• Determine whether the problem happens in HTML, Java, or both.

  Since both Java and HTML use the Java runtime engine, they should behave the same. Some variation exists based on the inherent differences between the Portal, HTML page processing and Java interactive processing, but underlying functionality and processing should be the same.

• Re-create the problem on the web server.

  The logs will work in the Portal, HTML, and Java.

• Open a separate browser and use it to access the Web Server Monitor for the web server being used.

• Check the Standard Error Log (stderr.log) for errors.

  A common error you might see here is BSFN Failed. If you see this error, verify that the enterprise server is up and that the BSFN is not a T1 BSFN.

  T1 refers to Type 1 business functions, which are client-only business functions. They cannot run on a server.

• Check the Standard Output Log (stdout.log) for more information.

  For example, you can view the time and date stamps from the errors found in both the Jas.log and the standard error log to find more detailed information about what was occurring at about the same time that the errors occurred.

If you need more information, enable Debug.log and set Net Trace, which you can do in the [LOGS] section of jas.ini file. Re-create the problem, view the Debug.log, and look for more information.

You can also use the Server Manager to monitor web servers.

Try to find SQL statement information. SQL statements can give you an idea of what values are being passed. Some common failures include:

• Form Interconnects are passing incorrect information.

  Verify that the fat client is working correctly. Watch especially for null, blank, and zero problems, as well as special characters.

• String is too big.

  Note carefully what you did to get this error.

• Null values are being passed.

  The SQL statement information search will result in nothing being found. Check the SQL statements and make sure that correct values were passed. Determine where the failure occurred and make a note of it.

• The application stops responding.

  Check logs for BSFN failures.