Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 5.0.0, 5.1.0
-
Component/s: File listening (consumer part)
-
Security Level: Public
-
- Environment:
- -
Issue Links
| Depends | |||||
|---|---|---|---|---|---|
|
|
||||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Major [ 3 ] | |
| Component/s | File listening (consumer part) [ 10397 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Link |
This issue depends on |
| Link | This issue blocks PETALSDISTRIB-587 [ PETALSDISTRIB-587 ] |
| Summary | The warning log trace identifying clearly the invoked service operation initiating a timeout is not generated | A warning log trace identifying clearly the invoked service operation initiating a timeout is not generated |
| Description |
The warning log trace identifying clearly the invoked service operation initiating a timeout is not generated because the method 'onExpiredAsyncJBIMessage(...)' is not correctly inherited.
The call to the parent method is missing: {code} super.onExpiredAsyncJBIMessage(asyncExchange, asyncContext); {code} |
A warning log trace identifying clearly the invoked service operation initiating a timeout is not generated because the method 'onExpiredAsyncJBIMessage(...)' is not correctly inherited.
The call to the parent method is missing: {code} super.onExpiredAsyncJBIMessage(asyncExchange, asyncContext); {code} |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 5.1.0 [ 10862 ] | |
| Resolution | Fixed [ 1 ] |
| Status | Resolved [ 10004 ] | Open [ 10002 ] |
| Resolution | Fixed [ 1 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Fix Version/s | 5.2.0 [ 11095 ] | |
| Fix Version/s | 5.1.0 [ 10862 ] |
| Fix Version/s | 5.0.2 [ 11194 ] |
| Affects Version/s | 5.0.0 [ 10931 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 5.1.1 [ 11195 ] | |
| Resolution | Fixed [ 1 ] |
| Fix Version/s | 5.2.0 [ 11095 ] |