
|
If you were logged in you would be able to see more operations.
|
|
|
Setup:
| Client Producer: |
5.0-SNAPSHOT |
| Broker A: |
4.1.1 |
| Broker B: |
5.0-SNAPSHOT |
| Client Consumer: |
5.0-SNAPSHOT |
Messages from the producer are sent to Broker A, which discovers Broker B via standard multicast discovery (each broker was given a unique name before starting). Consumer is connected to Broker B, set to consume messages from the same queue.
After a small number of successful transfers, (I've seen between 0 and 7) Broker B will display this message on each send attempt by the producer, and break the network connection between Broker A and B (which is re-established immediately):
Seemed like this might be relevant – here's the directory structure for Broker B's data directory – note data file named data-kaha-1 vs. data--1:
|
|
Description
|
Setup:
| Client Producer: |
5.0-SNAPSHOT |
| Broker A: |
4.1.1 |
| Broker B: |
5.0-SNAPSHOT |
| Client Consumer: |
5.0-SNAPSHOT |
Messages from the producer are sent to Broker A, which discovers Broker B via standard multicast discovery (each broker was given a unique name before starting). Consumer is connected to Broker B, set to consume messages from the same queue.
After a small number of successful transfers, (I've seen between 0 and 7) Broker B will display this message on each send attempt by the producer, and break the network connection between Broker A and B (which is re-established immediately):
Seemed like this might be relevant – here's the directory structure for Broker B's data directory – note data file named data-kaha-1 vs. data--1:
|
Show » |
made changes - 22/Nov/07 11:24 PM
| Field |
Original Value |
New Value |
|
Assignee
|
|
Rob Davies
[ rajdavies
]
|
made changes - 22/Nov/07 11:27 PM
|
Fix Version/s
|
|
5.0.0
[ 11712
]
|
|
Status
|
Open
[ 1
]
|
Resolved
[ 5
]
|
|
Resolution
|
|
Fixed
[ 1
]
|
|