Skip to main content

Exception Handling in ADF

This blog will give you an overview on how you can successfully deal with unhandled Runtime exceptions in an ADF application.

This will give you an idea of:
  1. How to catch the unhandled exceptions.
  2. Write a separate log file with stacktrace and thread dumps.
  3. Redirect the user to an static error page

#1. Catch unhandled exceptions : 

Create a class "MyExceptionHandler" which extends : Override handleException() method.

    public void handleException(FacesContext facesContext, Throwable throwable, PhaseId phaseId) throws Throwable {
        // this method is going to create a separate file with stacktrace and thread dumps

        // redirect to error page

 Create a folder "services" inside : ViewController\src\META-INF and then create a file named "".
In the file, add the absolute name of your custom exception handler class (package name and class name without the “.class” extension)
For more info check :

 I had some problems adding this folder in the generated EAR file. So please check the ViewController deployment profile. You need to add the project source path also as a contributor to your WEB-INF/classes folder.

#2. Log file with stacktrace and thread dumps :

Either you can write this logic inside "MyExceptionHandler" class or inside a Singleton object. So that we can make sure when we report the problem, we have an unique id to identify the log file.
I preferred writing the logic in "MyExceptionHandler" class. The relevant contents of the class is below. 
There is an inner class(IncidentContext) also to track the unique id of the exception incident.

    private static final ThreadLocal<IncidentContext[]> incidentContext = new ThreadLocal<IncidentContext[]>() {

        protected IncidentContext[] initialValue() {

            return new IncidentContext[1];
    private void writeException(Throwable t) {

        IncidentContext context = incidentContext.get()[0];
        if (context == null) {
            context = new IncidentContext("No additional context");

        StringBuilder incident = new StringBuilder();

        Calendar calendar = Calendar.getInstance();

        String incidentID = String.format("%s-%2$tY%2$tm%2$td_%2$tH%2$tM%2$tS", context.identification , calendar);
        String incidentFile = String.format("incident-%s.log", incidentID);

        incident.append(format(" Filename    : %s\n", incidentFile));
        incident.append(format(" Date        : %1$tB %1$te, %1$tY\n", calendar));
        incident.append(format(" Time        : %1$tl:%1$tM:%1$tS %1$tp\n", calendar));
        incident.append(format(" Unexpected error context: %s\n\n %s\n", context.text, ExceptionUtils.getFullStackTrace(t)));

        incident.append(format(" ** THREAD DUMP:\n\n%s\n", dumpThreads()));
        String filePath = ExceptionWriter.getCurrentInstance().getFilePath();
        File f = new File(filePath, incidentFile);

        boolean traceWritten = false;
        try (FileOutputStream fos = new FileOutputStream(f)) {
            traceWritten = true;
        } catch (FileNotFoundException e) {
            logger.error("The original exception was :" + incident.toString(), e);
        } catch (IOException e) {
            logger.error("The original exception was :" + incident.toString(), e);

    private String dumpThreads() {

        ThreadMXBean bean = ManagementFactory.getThreadMXBean();
        ThreadInfo[] infos = bean.dumpAllThreads(true, true);

        StringBuilder stack = new StringBuilder();

        for (ThreadInfo info : infos) {

        return stack.toString();
    private final static class IncidentContext {

        public static long incidentCount = 1L;

        public final String identification;
        public final String text;

        IncidentContext(Long id, String txt) {

            identification = id.toString();
            text = txt;

        IncidentContext(String txt) {

            identification = String.format("#%d", incidentCount++);
            text = txt;

You also need to create a session scope bean. Which will be used in the error page to report the exception ID, so that the end user can report this to the system administrators.
Register it in the adfc-config.xml.

<managed-bean id="ew1">
    <managed-bean-name id="ew2">ExceptionWriter</managed-bean-name>
    <managed-bean-class id="ew3">my.exception.ExceptionWriter</managed-bean-class>
    <managed-bean-scope id="ew4">session</managed-bean-scope>

The class should look like :
public class ExceptionWriter {
    private String filePath;
    private String exceptionID;
    public static ExceptionWriter getCurrentInstance() {

        return (ExceptionWriter) JsfUtils.getExpressionValue("#{ExceptionWriter}");

    public String getFilePath() {
        filePath = getDirectory();      
        return filePath;
    // Reads the folder to write the log file from web.xml context-param.

   // default folder : D://incident
    private String getDirectory() {
        String directoryName = ContextUtil.getContextProperty(FacesContext.getCurrentInstance(), "incidentFilePath");
        File theDir = new File(directoryName);
        if(theDir.exists() &&theDir.isDirectory()) {
            return directoryName;
        return "D://incident";

    public void setExceptionID(String exceptionID) {
        this.exceptionID = exceptionID;

    public String getExceptionID() {
        return exceptionID;


 #3. Redirect the user to an static error page :

    private void redirectToErrorPage(FacesContext facesContext) throws IOException {
        ExternalContext ectx = facesContext.getExternalContext();

The Error.jspx:
<?xml version='1.0' encoding='UTF-8'?>
<jsp:root xmlns:jsp="" version="2.1" xmlns:f="" xmlns:h="" xmlns:af="">
  < contentType="text/html;charset=UTF-8"/>
    <af:document id="d1">
      <af:form id="f1">
              <af:panelHeader text="The server is unable to respond at this time. Thank you for your patience." id="ph1">               
                <af:outputFormatted value="An unexpected error occurred, please contact System Administrator with the following number : #{ExceptionWriter.exceptionID}" id="of2"/>

                <!-- PUT a navigation to the HOME page of your application here -->


#4. Results :


  1. Thanks for sharing this informative information.You may also refer.....Exception handling in java An exception or exceptional event is a problem that arises during the execution of a program..


Post a Comment

Popular posts from this blog

Chatbots and Oracle Cloud Services

Thanks to Oracle A-Team, I had a chance to work with Chatbots.
3 pure NodeJS applications, on couple of Oracle Cloud platforms and Facebook messenger, and my chatbot was running.

Let me explain, the architecture a bit. To start with, following is the simple representation of how it works.

Bean Based ADF Table with List View in detailStamp facet

One of our projects, we had to display a "tree type" table with different datamodel for children. To solve this, I choose a normal af:table with a detailStamp facet with a List view inside it.
But pretty soon, I ran into an issue of correctly identifying the "disclosed" rows. Since my table's datasource is a bean, not ADF managed datacontrol.

So I solved it using a discloseListener on the af:table.

Full Application is on GitHub :

Classes invloved :

1. : dataProvider class for af:table
2. : dataProvider for the list view inside detailStamp of the table.
3. : provides the methods for populating af:table and af:listView. Also has a discloseListener method to correctly populate the listView datasource.

af:table definition :