Netty-servelet transport stalls JMS connections, leaving remote JMS clients in stale/limbo state if a client idles for a period of time.
HornetQ HTTP transport over netty-servlet does not work as expected
- Clebert Suconic
- Tyronne Wickramarathne
- Votes:
-
0 Vote for this issue
- Watchers:
-
3 Start watching this issue
- Created:
- Updated:
- Resolved: