Petals SE RMI

Improve exception handling over RMI to prevent classloader issues

View this issue in another formatViewView
- XML
- Word
- Printable

Details

Type: Improvement Request
Status: Resolved
Priority: 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

Ascending order - Click to sort in descending order

Victor NOËL made changes - Thu, 10 Mar 2016 - 10:47:47 +0100

Field	Original Value	New Value
Status	New [ 10000 ]	Open [ 10002 ]
Priority		Major [ 3 ]
Assignee	Christophe DENEUX [ cdeneux ]	Victor NOËL [ vnoel ]

Victor NOËL made changes - Thu, 10 Mar 2016 - 10:47:52 +0100

Status

Open [ 10002 ]

In Progress [ 10003 ]

Victor NOËL made changes - Thu, 10 Mar 2016 - 11:16:31 +0100

Status	In Progress [ 10003 ]	Resolved [ 10004 ]
Fix Version/s		1.7.0 [ 10581 ]
Resolution		Fixed [ 1 ]

People

Assignee:

Victor NOËL

Reporter:

Victor NOËL
Watchers:

0

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