Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Flaky test cleanup following on v6.3.0 release

Open
  • Is something wrong?
#2,238 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
java
Domain
backend, testing

Research direction

Start by running the unchecked tests listed in the issue, including AMQ4083Test, NetworkAdvancedStatisticsTest, and NetworkBridgeReconnectOnHandshakeFailureTest, to reproduce the failures. Read each test and its supporting test class to determine whether the failure is intermittent or a real regression. Done means the listed flaky failures are stabilized or fixed and the corresponding checklist entries can be marked complete.

Written by the indexing model from the issue text.

Description

In Progress (@mattrpav)

  • (2x) AMQ4083Test.testExpiredMsgsBeforeNonExpiredWithTX:192 Inflight count should reach zero, currently: 7
  • NetworkAdvancedStatisticsTest.testNetworkAdvancedStatisticsErrors:143->assertNetworkStats:406 Timed out waiting for connector exception counts local>=1 remote>=0
  • NetworkBridgeReconnectOnHandshakeFailureTest.testBridgeReconnectsAfterRemoteBrokerRestart:263 Bridge should go down

Backlog fixes

  • AbortSlowAckConsumer0Test.testSlowConsumerIsAbortedViaJmx:99->AbortSlowConsumer0Test.testSlowConsumerIsAbortedViaJmx:123 no slow consumers left expected:<0> but was:<1>
  • VirtualConsumerDemandTest.testToTopicWithDurable:1358
  • MQTTSubscriptionRecoveryTest.testDurableSubscriptionsAreRecovered:91->MQTTTestSupport.restartBroker:133 » IO Transport Connector could not be registered in JMX: java.io.IOException: Failed to bind to server socket: mqtt://0.0.0.0:46365?transport.subscriptionStrategy=mqtt-default-subscriptions due to: java.net.BindException: Address already in use
  • RequestReplyToTopicViaThreeNetworkHopsTest.runWithTempTopicReplyTo:458 no errors
  • InMemoryJobSchedulerTest.testAddCronAndByteSequence:92 » TestTimedOut test timed out after 60000
  • UsageBlockedDispatchTest>CombinationTestSupport.runBare:113->CombinationTestSupport.runBare:107->testFillMemToBlockConsumer:167 did not get a message
  • CachedLDAPAuthorizationModuleLegacyTest>AbstractCachedLDAPAuthorizationMapLegacyTest.testSynchronousUpdate:123 expected null, but was:<[]>
  • JMSClientNioPlusSslTest>JMSClientTest.testDurableConsumerSync:718->JMSClientTestSupport.createConnection:140->createConnection:40 » JmsConnectionRemotelyClosed org.apache.qpid.proton.engine.TransportException: AMQP header mismatch value 0, expecting 41. In state: HEADER0 [condition = amqp:connection:framing-error]
  • DurableSubscriptionOffline1Test.testOfflineSubscriptionCanConsumeAfterOnlineSubs:243 expected:<10> but was:<0>
  • DurableSubscriptionOffline2Test.testJMXCountersWithOfflineSubs:101 got message: 0
  • DurableFiveBrokerNetworkBridgeTest>CombinationTestSupport.runBare:107->testDurablePropagationSyncTtl4BrokerRestart:647->testDurablePropagation:793->assertNCDurableSubsCount:831 Expected 2 NC durable sub(s) on Broker_C_C for TEST.FOO, but got 1

Done

  • JMSInteroperabilityTest.testOpenWireToQpidObjectMessageWithOpenWireCompression:493 » MessageFormat Failed to read object: null - Real test failure fixed by #2256
  • (2x) ActiveDurableSubscriptionBrowseExpireTest.testBrowseExpireActiveSub
  • (2x) TwoBrokerVirtualTopicSelectorAwareForwardingTest.testSelectorAwareForwarding(
  • (2x) AutoFailoverClusterTest>FailoverClusterTest.testClusterURIOptionsStrip:71 clients should connect to multiple brokers
Dominant language
Java
Stars
2.5k
Forks
1.5k
Avg merge
14h 42m
Merged PRs (30d)
85

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/activemq

All issues in apache/activemq

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.