[jira] [Commented] (ARTEMIS-4821) OperationContext may leak between servers in embedded mode

["Clebert Suconic (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867435#comment-17867435 ] 

Clebert Suconic commented on ARTEMIS-4821:
------------------------------------------

The issue here was really on the Test. The test is sharing the same context between the SendAckThread. (not your test's fault.. it needs to be fixed).


I may have other intermittent failures because of this, but this issue here should not bother anyone using the standalone server. However if you're using many Embedded servers in the same VM you may face this issue.

(I don't know of anyone who would have more than one server in the same VM apart for our test suite.. so, for that reason I'm marking this issue as Non Critical just to reflect the release notes).


> OperationContext may leak between servers in embedded mode
> ----------------------------------------------------------
>
>                 Key: ARTEMIS-4821
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4821
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.35.0
>            Reporter: nmeylan
>            Priority: Major
>         Attachments: MessageCount230Test.java, MessageCount235Test.java
>
>
> After upgrading from 2.30 to 2.34 one of my test case is failling {{QueueImpl::getMessageCount()}} does not returns what was expected
> See attached Test [^MessageCount235Test.java]  case *testMessageCount_whenFailoverHappenWhileBridgeIsOpen* which is failing, I attempt other scenario which succeed
> I link also  [^MessageCount230Test.java] for version 2.30 (it is another file because due to renaming of master/slave, SimpleString and migration to junit5, code needs to be adapt), all scenario are succeed
>  
> {code:java}
> Topology: Simulating DC1 (1 primary + backup pair)
> Simulating DC2 1 single primary node
> 1. Produce messages on dc1Primary1
> 2. Start a bridge from dc1Primary1 to dc2Primary1
> 3. Stop dc1Primary1 while transfer has started but not finished
> 4. dc1Backup1 become alive
> 5. Start a bridge from dc1Backup1 to dc2Primary1
> 6. dc2Primary1 has received all messages produced originally
> 7. Expected: messageCount on dc1Backup1 to be equal to 0, but actual is > 0
> Notes: if address is not paging, there is no issue
> {code}
> After investigation it happen only when address is paging.
> Also as I face the issue only when using bridge, issue might be due to async acknowledgement



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@activemq.apache.org
For additional commands, e-mail: issues-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact