James Server
  1. James Server
  2. JAMES-96

Mailet container should not trap exceptions in init()

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 1.2.1
    • Fix Version/s: 2.2.0
    • Labels:
      None
    • Environment:
      Operating System: All
      Platform: All

      Description

      If a custom mailet throws a RuntimeException in init(), the container traps it and rethrows
      a MessagingException, giving little indication of what occurred. The container really
      ought to provide the stack trace of the failure.

        Activity

        Mark Thomas made changes -
        Workflow Default workflow, editable Closed status [ 12565881 ] jira [ 12581285 ]
        Mark Thomas made changes -
        Workflow jira [ 23423 ] Default workflow, editable Closed status [ 12565881 ]
        Noel J. Bergman made changes -
        Status Open [ 1 ] Closed [ 6 ]
        Fix Version/s 2.2.0a19 [ 10689 ]
        Resolution Fixed [ 1 ]
        Noel J. Bergman made changes -
        Priority Minor [ 4 ]
        Assignee James Developers Mailing List [ server-dev@james.apache.org ]
        Component/s SpoolManager & Processors [ 10630 ]
        Environment Operating System: All
        Platform: All
        Operating System: All
        Platform: All
        Component/s Mailet API [ 10631 ]
        Description If a custom mailet throws a RuntimeException in init(), the container traps it and rethrows
        a MessagingException, giving little indication of what occurred. The container really
        ought to provide the stack trace of the failure.
        If a custom mailet throws a RuntimeException in init(), the container traps it and rethrows
        a MessagingException, giving little indication of what occurred. The container really
        ought to provide the stack trace of the failure.
        Serge Knystautas made changes -
        Field Original Value New Value
        issue.field.bugzillaimportkey 18124 13428
        benengber created issue -

          People

          • Assignee:
            Unassigned
            Reporter:
            benengber
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development