-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
AMQ 7.2.0.GA
-
None
-
Documentation (Ref Guide, User Guide, etc.)
-
-
Not Yet Documented
There seem to be an issue on the broker with the Artemis/Core protocol when it needs to handle a large amount of connections with that protocol.
Basically, if you try to create lots of connection pairs: (~1024 on my workstation ... noticed w/ ~200 on our lab) some of those connections will fail with "ActiveMQConnectionTimedOutException[errorType=CONNECTION_TIMEDOUT message=AMQ119013: Timed out waiting to receive cluster topology. Group:null]"
Reproducer steps:
1. Build the images (only once):
docker-compose -f docker-compose-maestro-infra.yml -f docker-compose-maestro-sut.yml -f docker-compose-maestro-reproducer.yml build
2. Run the reproducer:
docker-compose -f docker-compose-maestro-infra.yml -f docker-compose-maestro-sut.yml -f docker-compose-maestro-reproducer.yml up
Additional details about the reproducer is available on the README.md provided along with the code.
Versions affected:
- A-MQ 7.2.0.CR5
- Apache Artemis 2.6.2
- Apache Artemis 2.7.0-20180816.220317-109 (nightly build as of today, taken from Apache Nexus)
- is related to
-
ENTMQBR-1721 DB2 sending larger message (1MB) crashes the whole server
- Closed
-
JBEAP-15451 [QE] (7.2.z) (Artemis) ARTEMIS-2089 DB2 sending larger message (1MB) crashes the whole server
- Closed
-
JBEAP-15456 [QA](7.1.z) (Artemis) DB2 sending larger message (1MB) crashes the whole server
- Closed
-
WFLY-11022 DB2 sending larger message (1MB) crashes the whole server
- Closed
- relates to
-
AMQDOC-2183 Consider development of tutorial/tuning content for AMQ 7 customers
- Closed