Suppress transaction rolled back servlet exceptions on LDAP-related errors

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Duplicate
    • None
    • Component/s: None
    • None

      When LDAP errors are thrown in Crowd, the resulting error (rather than the original LDAP exception) is displayed on the screen:

      System Error System Error
      
      A system error has occurred please contact your administrator.
      If this problem continues to occur please contact Atlassian by opening a support request with the following information:
      
          * A description of your problem and what you were doing at the time it occurred
          * Cut & paste the error and system information found below
          * Attach the application server log file (if possible).
      
      Cause :
      javax.servlet.ServletException: Transaction rolled back because it has been marked as rollback-only
      
      Stack Trace :
      
      javax.servlet.ServletException: Transaction rolled back because it has been marked as rollback-only
      at com.opensymphony.webwork.dispatcher.DispatcherUtils.serviceAction(DispatcherUtils.java:284)
      at com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:202)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
      at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118)
      at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
      at com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
      

      This causes at least one additional back and forth on support to obtain the needed logs and get to the root cause of the problem.

            Assignee:
            Justin Koke
            Reporter:
            DonnaA
            Votes:
            2 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: