java.lang.IndexOutOfBoundsException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • Had an error where on IMAPS clicking on a message generated an exception. Instead of the user being informed of the error they had a perpetual spinning globe. Services should catch the runtime error and return appropriate response to client. In this case (clicking on a message in preview list display) client got an HTTP 200 back with an empty result. Should return an error message. See stack trace below. In general the error handling should be improved to never have perpetual spinning globe and when possible return relevant info to the user (though arguably other than auth failures it should always be a transient error). Suggestions (not fully baked - review for improvements): 1. Catch run-time errors in Ajax Controllers and return response with error message indicating service is down. Catch EmailPreviewExceptions in Ajax controllers and return message from exception text. Would need to review EmailPreviewExceptions and possibly separate auth from other? a) For non-ajax controllers going to an error page should be fine. 2. Change UI so it doesn't display all errors as a 504 error ERROR [uP-PortletExec-2-admin-RESOURCE-[IMAPemail-preview]] controller.EmailMessageController.[] Mar/28 14:33:12 - Error encountered while attempting to retrieve message java.lang.IndexOutOfBoundsException at com.sun.mail.imap.IMAPFolder.checkRange(IMAPFolder.java:449) at com.sun.mail.imap.IMAPFolder.getMessage(IMAPFolder.java:1378) at org.jasig.portlet.emailpreview.dao.javamail.JavamailAccountService.getMessage(JavamailAccountService.java:154)
    via by James Wennmacher,
  • Had an error where on IMAPS clicking on a message generated an exception. Instead of the user being informed of the error they had a perpetual spinning globe. Services should catch the runtime error and return appropriate response to client. In this case (clicking on a message in preview list display) client got an HTTP 200 back with an empty result. Should return an error message. See stack trace below. In general the error handling should be improved to never have perpetual spinning globe and when possible return relevant info to the user (though arguably other than auth failures it should always be a transient error). Suggestions (not fully baked - review for improvements): 1. Catch run-time errors in Ajax Controllers and return response with error message indicating service is down. Catch EmailPreviewExceptions in Ajax controllers and return message from exception text. Would need to review EmailPreviewExceptions and possibly separate auth from other? a) For non-ajax controllers going to an error page should be fine. 2. Change UI so it doesn't display all errors as a 504 error ERROR [uP-PortletExec-2-admin-RESOURCE-[IMAPemail-preview]] controller.EmailMessageController.[] Mar/28 14:33:12 - Error encountered while attempting to retrieve message java.lang.IndexOutOfBoundsException at com.sun.mail.imap.IMAPFolder.checkRange(IMAPFolder.java:449) at com.sun.mail.imap.IMAPFolder.getMessage(IMAPFolder.java:1378) at org.jasig.portlet.emailpreview.dao.javamail.JavamailAccountService.getMessage(JavamailAccountService.java:154)
    via by James Wennmacher,
    • java.lang.IndexOutOfBoundsException at com.sun.mail.imap.IMAPFolder.checkRange(IMAPFolder.java:449) at com.sun.mail.imap.IMAPFolder.getMessage(IMAPFolder.java:1378) at org.jasig.portlet.emailpreview.dao.javamail.JavamailAccountService.getMessage(JavamailAccountService.java:154)

    Users with the same issue

    Axelo
    1 times, last one,