Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 4.2.4
-
Component/s: Micro-kernel
-
Security Level: Public
-
- Environment:
- -
Issue Links
| Depends | |||
|---|---|---|---|
|
|||
Activity
| Fix Version/s | 4.3.2 [ 10608 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 5.0.0 [ 10413 ] | |
| Resolution | Fixed [ 1 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Link |
This issue depends on |
| Description |
In the container MessageExchange implementation, there seems to be error in the logic that checks the state of an exchange when the status is set (in method setStatus()).
For example, it is not possible to set the Error status when one is provider and the message is in-out... there is no reason for this specific case. Also, a provider can't set DONE on an in-out message, there is no reason for that, actually the opposite would be expected when a provider has set the out message or even the fault message! This should be fixed. |
In the container MessageExchange implementation, there seems to be error in the logic that checks the state of an exchange when the status is set (in method setStatus()).
For example, it is not possible to set the Error status when one is provider and the message is in-out... there is no reason for this specific case. There is also some strange case where the provider can't set the done status on an InOnly message with a fault... which cannot happen at that point normally! This should be fixed. |
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Blocker [ 1 ] | |
| Assignee | Christophe DENEUX [ cdeneux ] | Victor NOËL [ vnoel ] |