We are using vaadin 6.8.11 with liferay. We are almost into production stage and facing a big dilemma with the “Internal Error Message” being shown on top center of liferay page. We did override “terminalError” method in the Application and tried to log into our custom logs. But still the Error message shows up and this gets the customer worried since they think that the whole system is unstable. Also when the user clicks the “Click here to continue” they are taken back to the previous page and all their values are saved. So we ideally want to ignore the big banner message and just log them and fix any unhandled exception accordingly. Since the exceptions occur very randomly we can’t replicate in our qa environment.
see
this method in the Application class. You can just provide your own Application.CustomizedSystemMessages with both the internalError caption and message set to null. This should disable the notification completely. You can also control/modify other error messages this way.
We are still stuck with this. We have already implemented the terminal errors as explained in the vaadin book to catch these exception but this is the stack trace. As we can see the handleServiceException takes over the error messaging and throws the InternalError on the page Is there a workarund to avoid “handleServiceException” to take over the error handling. Any help is appreciated. The question is we want to identify the reason/stacktrace from where we got this error so we can handle this, instead of setInternalErrorNotificationEnabled(false). The exception message is null and there is no way to identify what is the cause of this message.
at com.vaadin.terminal.gwt.server.AbstractApplicationPortlet.handleServiceException(AbstractApplicationPortlet.java:1473)
at com.vaadin.terminal.gwt.server.AbstractApplicationPortlet.handleRequest(AbstractApplicationPortlet.java:495)
at com.vaadin.terminal.gwt.server.AbstractApplicationPortlet.serveResource(AbstractApplicationPortlet.java:734)
at com.sun.portal.portletcontainer.appengine.filter.FilterChainImpl.doFilter(FilterChainImpl.java:177)
at com.liferay.portal.kernel.portlet.PortletFilterUtil.doFilter(PortletFilterUtil.java:76)
at com.liferay.portal.kernel.servlet.PortletServlet.service(PortletServlet.java:100)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)