|
If you were logged in you would be able to see more operations.
|
|
|
ActiveMQ
Created: 11/Jul/06 04:08 AM
Updated: 11/Jul/06 04:11 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
4.1.0,
4.0.2
|
|
|
If for example the broker is restarted, the broker will not inform a client using the broker again that it's connection state is gone.
Also the client would startup a background poll thread before its' connection was established. This cause it to go into a busy loop hiting the server and the server sending back clientID not specified error messages until the ConnectionInfo was sent to the broker.
|
|
Description
|
If for example the broker is restarted, the broker will not inform a client using the broker again that it's connection state is gone.
Also the client would startup a background poll thread before its' connection was established. This cause it to go into a busy loop hiting the server and the server sending back clientID not specified error messages until the ConnectionInfo was sent to the broker. |
Show » |
|
Bug
Resolved
Major
JMS connections using the http:// protocol may not detect connections failures correctly.