Details
Bug
Resolved
Major
-
- Environment:
- -
Issue Links
| Depends | |||||
|---|---|---|---|---|---|
|
|
||||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Major [ 3 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Link | This issue blocks PETALSDISTRIB-587 [ PETALSDISTRIB-587 ] |
| Link |
This issue depends on |
| Fix Version/s | 1.3.0 [ 11121 ] |
| 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 ] |
| Resolution | Fixed [ 1 ] |
| Status | Resolved [ 10004 ] | Open [ 10002 ] |
| Resolution | Fixed [ 1 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Fix Version/s | 1.1.1 [ 11160 ] | |
| Affects Version/s | 1.1.0 [ 10836 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 1.2.1 [ 11157 ] | |
| Fix Version/s | 1.3.0 [ 11121 ] | |
| Resolution | Fixed [ 1 ] |