Zend Server Best Practices > Development > Monitoring Rules > Java Exception

Java Exception

Description: When Java code called through the Java Bridge fails due to an uncaught Java exception, it generates an error. The “Uncaught Java exception” Rule determines if Uncaught Java Exceptions are reported or not.

Information Collected:

The most important details are:

Function Name - As displayed in the Issue’s General Details
Error Data - Listed in the Error Data tab including the Java Stack and Java error string.

In most cases, these details alone should be enough to indicate what happened to trigger an event.

Applicable Diagnostic Actions:

Click on a link to see how to perform each action tools are listed in order of relevance to helping solve the event:

Open code in editor
Run the Debugger
Run the Profiler
Redefine database queries
View information in the Logs

Possible Causes and Solutions:

Based on the exception type, investigate the Java code and fix to stop generating the event – all relevant information should be collected in the issue.

False Positives - Sometimes developers write code to intentionally trigger an Uncaught Java Exception. Not all triggered exceptions are indicative of a problem in your code or environment and they may be no indication of unacceptable behavior. If this is the case, set issues triggered by this function to ignored.


	Related Links: Advanced Diagnostics with Zend Server