[
https://issues.apache.org/jira/browse/ARTEMIS-5156?focusedWorklogId=944169&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-944169
]
ASF GitHub Bot logged work on ARTEMIS-5156:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 18/Nov/24 18:48
Start Date: 18/Nov/24 18:48
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on PR #5350:
URL:
https://github.com/apache/activemq-artemis/pull/5350#issuecomment-2483848870
I'm pretty much not using the proxy connection when I don't need to.
I set the failure check period too small (100 ms).. which is ok for the
consumption part, where I'm actually validating the proxy.
But for the preparation of the test, that's introducing failures (eventually
depending on GC.. etc.) in places where this is not supposed to.
Issue Time Tracking
-------------------
Worklog Id: (was: 944169)
Time Spent: 20m (was: 10m)
> Simplify and make LargeMessageFrozenTest more reliable
> ------------------------------------------------------
>
> Key: ARTEMIS-5156
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5156
> Project: ActiveMQ Artemis
> Issue Type: Test
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Minor
> Labels: pull-request-available
> Fix For: 2.39.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> LargeMessageFrozenTest uses a TCP Proxy.
> The TCP proxy is then turned of in an attempt to force failures.
> However I have seen sporadic connection failures on places where I didn't
> intend to fail. To make things better I'm isolating the usage of the Proxy
> only on the places where I intend to force a failure, what would make the
> test scenario more controllable and less likely to fail elsewhere.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact