View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006043 | SymmetricDS | Bug | public | 2023-10-23 17:00 | 2023-10-23 18:00 |
| Reporter | pmarzullo | Assigned To | pmarzullo | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.14.9 | ||||
| Target Version | 3.14.10 | Fixed in Version | 3.14.10 | ||
| Summary | 0006043: ConcurrentConnectionManager expects nodeId-channel in the white list, but only the nodeId is put in the white list | ||||
| Description | The ConcurrentConnectionManager, in the reserveConnection method, expects the value of nodeId-channel in the white list data structure. But the JMX interface documents (therefore only) puts the nodeId into the white list. Change the ConcurrentConnectionManager to check for the nodeId only (e.g., 0000) in the white list instead of nodeId-channel (e.g., 0000-default). | ||||
| Tags | data sync | ||||
|
SymmetricDS: 3.14 1bcef335 2023-10-23 17:05:03 Details Diff |
0006043: ConcurrentConnectionManager expects nodeId-channel in the white list, but only the nodeId is put in the white list |
Affected Issues 0006043 |
|
| mod - symmetric-core/src/main/java/org/jumpmind/symmetric/transport/ConcurrentConnectionManager.java | Diff File | ||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-10-23 17:00 | pmarzullo | New Issue | |
| 2023-10-23 17:00 | pmarzullo | Status | new => assigned |
| 2023-10-23 17:00 | pmarzullo | Assigned To | => pmarzullo |
| 2023-10-23 17:00 | pmarzullo | Tag Attached: data sync | |
| 2023-10-23 17:02 | pmarzullo | Relationship added | related to 0006044 |
| 2023-10-23 17:11 | pmarzullo | Status | assigned => resolved |
| 2023-10-23 17:11 | pmarzullo | Resolution | open => fixed |
| 2023-10-23 17:11 | pmarzullo | Fixed in Version | => 3.14.10 |
| 2023-10-23 18:00 | pmarzullo | Changeset attached | => SymmetricDS 3.14 1bcef335 |
| 2023-10-27 20:06 | admin | Status | resolved => closed |