Petals SE RMI

Asynchronous calls from concurrent RMI clients are not supported

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

Details

Type: Bug
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 1.6.0
Fix Version/s: 1.7.0
Component/s: Component
Security Level: Public

Description:

Hide

If several concurrent RMI clients sent InOut exchanges using RemoteDeliveryChannel.send(MessageExchange) through the same Petals SE RMI, a mix can occurs retrieving replies.
This is due to the usage of RemoteDeliveryChannel.accept() that read replies directly from the Petals microkernel router without filtering against the current RMI client. So a RMI client can receive the reply of another RMI client.

A workaround is to use a synchronous sent for InOut exchange.

This problem occurs running the integration tests about container attachment/detachement.

Show
If several concurrent RMI clients sent InOut exchanges using RemoteDeliveryChannel.send(MessageExchange) through the same Petals SE RMI, a mix can occurs retrieving replies. This is due to the usage of RemoteDeliveryChannel.accept() that read replies directly from the Petals microkernel router without filtering against the current RMI client. So a RMI client can receive the reply of another RMI client. A workaround is to use a synchronous sent for InOut exchange. This problem occurs running the integration tests about container attachment/detachement.

Environment:

-

Issue Links

Depends

This issue blocks:
~~PETALSESBCONT-364~~ "No endpoint(s) matching the target service" when attaching a container

Activity

Transition

Status Change Time

Execution Times

Last Executer

Last Execution Date

New

Open

13d 2h 3m

1

Christophe DENEUX

Wed, 9 Dec 2015 - 17:17:33 +0100

Open

In Progress

5s

1

Christophe DENEUX

Wed, 9 Dec 2015 - 17:17:38 +0100

In Progress

Resolved

2m 13s

1

Christophe DENEUX

Wed, 9 Dec 2015 - 17:19:51 +0100

People

Assignee:

Christophe DENEUX

Reporter:

Christophe DENEUX
Watchers:

0

Dates

Created:

Thu, 26 Nov 2015 - 15:14:19 +0100

Updated:

Tue, 1 Mar 2016 - 10:19:03 +0100

Resolved:

Wed, 9 Dec 2015 - 17:19:51 +0100