Petals SE RMI

Improve exception handling over RMI to prevent classloader issues

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.6.0
  • Fix Version/s: 1.7.0
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    When the RMI SE throws an Exception on the container side, this exception is sent over RMI and sometimes produces classloader issue if the client does not have the needed classes in its classloader (for example exceptions thrown by the router).

    We should prevent such situation by properly wrapping the exception is something deserializable on the client side.

    Show
    When the RMI SE throws an Exception on the container side, this exception is sent over RMI and sometimes produces classloader issue if the client does not have the needed classes in its classloader (for example exceptions thrown by the router). We should prevent such situation by properly wrapping the exception is something deserializable on the client side.
  • Environment:
    -

Activity

People

Dates

  • Created:
    Thu, 10 Mar 2016 - 10:47:38 +0100
    Updated:
    Thu, 10 Mar 2016 - 11:16:31 +0100
    Resolved:
    Thu, 10 Mar 2016 - 11:16:30 +0100
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.