[JBoss JIRA] (WFLY-10898) Opentracing extension configured with a wrong name in host-excludes
by Yeray Borges (JIRA)
[ https://issues.jboss.org/browse/WFLY-10898?page=com.atlassian.jira.plugin... ]
Yeray Borges updated WFLY-10898:
--------------------------------
Summary: Opentracing extension configured with a wrong name in host-excludes (was: Opentracing extension is configured with wrong name in host-excludes)
> Opentracing extension configured with a wrong name in host-excludes
> -------------------------------------------------------------------
>
> Key: WFLY-10898
> URL: https://issues.jboss.org/browse/WFLY-10898
> Project: WildFly
> Issue Type: Bug
> Reporter: Yeray Borges
> Assignee: Yeray Borges
>
> The Opentracing extension name is {{org.wildfly.extension.microprofile.opentracing}}, however the excluded-extensions section in host-excludes is configured with an incorrect name {{org.wildfly.extension.microprofile.opentracing-smallrye}}
> Legacy domain.xml template is fine, the issue is only in domain-host-excludes feature group.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFWIP-21) [Artemis 2.x upgrade] Lost message when MDB is resending messages under high load
by Erich Duda (JIRA)
[ https://issues.jboss.org/browse/WFWIP-21?page=com.atlassian.jira.plugin.s... ]
Erich Duda edited comment on WFWIP-21 at 8/22/18 4:17 AM:
----------------------------------------------------------
Good catch [~jbertram]. I will increase number of delivery attempts and run it again.
> [Artemis 2.x upgrade] Lost message when MDB is resending messages under high load
> ---------------------------------------------------------------------------------
>
> Key: WFWIP-21
> URL: https://issues.jboss.org/browse/WFWIP-21
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis
> Reporter: Miroslav Novak
> Assignee: Martyn Taylor
> Priority: Blocker
> Labels: activemq, feature-branch-blocker
>
> Test scenario:
> * Start cluster A of nodes node-1, node-3
> * Start cluster B of nodes node-2, node-4
> * Send messages to queue on node-1
> * Deploy mdbs to servers in cluster A. This mdb reads messages from local queue, sends them to remote queue on cluster B and inserts them into database
> * Deploy mdbs to servers in cluster B. This mdb reads messages from local queue and inserts them into database
> * Cause CPU overload (for 5 min) on server node-2 when mdbs on cluster1 and 2 are processing mesages
> * Restart failed server
> * Let MDBs to process remaining messages
> Pass Criteria: Number of sent message is equal number of records(lines) in database and messages in
> Actual Result:
> Sometimes happens that one record is missing in database which means that one message was not processed be MDB in cluster 2.
> This looks like broker related regression against Artemis 1.5.
> Wildfly: https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (06c878a313d3cad323889d017e60fd5533204d1a)
> Artemis tag 2.5.0.Final
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months