December 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6846) Redistribution loses large messages when server with HA is restarted

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-6846?page=com.atlassian.jira.plugin.... ] Miroslav Novak commented on WFLY-6846: -------------------------------------- Based on JBEAP-5258 and WFLY-6844. This issue is fixed in ActiveMQ to 1.1.0.wildfly-018/Wildfly 11. I'll close this jira. > Redistribution loses large messages when server with HA is restarted > -------------------------------------------------------------------- > > Key: WFLY-6846 > URL: https://issues.jboss.org/browse/WFLY-6846 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Bartosz Baranowski > Assignee: ehsavoie Hugonnet > Priority: Major > Labels: downstream_dependency > Fix For: 11.0.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6846) Redistribution loses large messages when server with HA is restarted

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-6846?page=com.atlassian.jira.plugin.... ] Miroslav Novak closed WFLY-6846. -------------------------------- Resolution: Done > Redistribution loses large messages when server with HA is restarted > -------------------------------------------------------------------- > > Key: WFLY-6846 > URL: https://issues.jboss.org/browse/WFLY-6846 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Bartosz Baranowski > Assignee: ehsavoie Hugonnet > Priority: Major > Labels: downstream_dependency > Fix For: 11.0.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6847) Lost large messages if backup is shutdown during synchronization

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-6847?page=com.atlassian.jira.plugin.... ] Miroslav Novak commented on WFLY-6847: -------------------------------------- Based on JBEAP-5258 and WFLY-6844. This issue is fixed in ActiveMQ to 1.1.0.wildfly-018/Wildfly 11. I'll close this jira. > Lost large messages if backup is shutdown during synchronization > ---------------------------------------------------------------- > > Key: WFLY-6847 > URL: https://issues.jboss.org/browse/WFLY-6847 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Bartosz Baranowski > Assignee: ehsavoie Hugonnet > Priority: Major > Labels: downstream_dependency > Fix For: 11.0.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6847) Lost large messages if backup is shutdown during synchronization

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-6847?page=com.atlassian.jira.plugin.... ] Miroslav Novak closed WFLY-6847. -------------------------------- Resolution: Done > Lost large messages if backup is shutdown during synchronization > ---------------------------------------------------------------- > > Key: WFLY-6847 > URL: https://issues.jboss.org/browse/WFLY-6847 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Bartosz Baranowski > Assignee: ehsavoie Hugonnet > Priority: Major > Labels: downstream_dependency > Fix For: 11.0.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6847) Lost large messages if backup is shutdown during synchronization

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-6847?page=com.atlassian.jira.plugin.... ] Miroslav Novak updated WFLY-6847: --------------------------------- Fix Version/s: 11.0.0.Final > Lost large messages if backup is shutdown during synchronization > ---------------------------------------------------------------- > > Key: WFLY-6847 > URL: https://issues.jboss.org/browse/WFLY-6847 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Bartosz Baranowski > Assignee: ehsavoie Hugonnet > Priority: Major > Labels: downstream_dependency > Fix For: 11.0.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8217) ActiveMQ leaks connections if a JMS message is sent from an MDB

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-8217?page=com.atlassian.jira.plugin.... ] Miroslav Novak resolved WFLY-8217. ---------------------------------- Resolution: Done > ActiveMQ leaks connections if a JMS message is sent from an MDB > --------------------------------------------------------------- > > Key: WFLY-8217 > URL: https://issues.jboss.org/browse/WFLY-8217 > Project: WildFly > Issue Type: Bug > Components: JMS, Transactions > Affects Versions: 10.1.0.Final > Environment: Running on Windows 10. Java(TM) SE Runtime Environment (build 1.8.0_92-b14) > Reporter: Scott Van Wart > Assignee: ehsavoie Hugonnet > Priority: Minor > Fix For: 13.0.0.Final > > Attachments: leak.zip, leak.zip, log.txt, log.txt, server.log > > > If an MDB causes a JMS message to be sent during the call to onMessage(), ActiveMQ won't close its connection. I'm using JMS2 through an @Inject'ed JMSContext. My sample project is an EAR with an EJB JAR (containing a service and an MDB) and a JAX-RS endpoint (entry point for the test). > 1) Build the EAR > 2) Run wildfly with the standalone-full.xml configuration: > {{standalone.bat --server-config=standalone-full.xml}} > 3) Enable debug and error reporting for leaked connections with ActiveMQ/CCM: > {{jboss-cli.bat -c}} > {{/subsystem=jca/cached-connection-manager=cached-connection-manager:write-attribute(name=debug,value=true)}} > {{/subsystem=jca/cached-connection-manager=cached-connection-manager:write-attribute(name=error,value=true)}} > 4) Deploy the EAR. > 5) Access http://localhost:8080/leak-web/rest/test?message=Hi > The REST endpoint will send a message to the test topic (Defined in leak-ejb/src/main/java/test/mdb/TestTopic.java). TestTopicListener (in the same package as TestTopic) will receive the message and send a second message to the topic. Upon returning from TestTopicListener.onMessage(), the message is sent, but this shows up in the logs > (see attached log.txt) > I have no idea why JIRA attached each file twice. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8217) ActiveMQ leaks connections if a JMS message is sent from an MDB

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-8217?page=com.atlassian.jira.plugin.... ] Miroslav Novak updated WFLY-8217: --------------------------------- Fix Version/s: 13.0.0.Final > ActiveMQ leaks connections if a JMS message is sent from an MDB > --------------------------------------------------------------- > > Key: WFLY-8217 > URL: https://issues.jboss.org/browse/WFLY-8217 > Project: WildFly > Issue Type: Bug > Components: JMS, Transactions > Affects Versions: 10.1.0.Final > Environment: Running on Windows 10. Java(TM) SE Runtime Environment (build 1.8.0_92-b14) > Reporter: Scott Van Wart > Assignee: ehsavoie Hugonnet > Priority: Minor > Fix For: 13.0.0.Final > > Attachments: leak.zip, leak.zip, log.txt, log.txt, server.log > > > If an MDB causes a JMS message to be sent during the call to onMessage(), ActiveMQ won't close its connection. I'm using JMS2 through an @Inject'ed JMSContext. My sample project is an EAR with an EJB JAR (containing a service and an MDB) and a JAX-RS endpoint (entry point for the test). > 1) Build the EAR > 2) Run wildfly with the standalone-full.xml configuration: > {{standalone.bat --server-config=standalone-full.xml}} > 3) Enable debug and error reporting for leaked connections with ActiveMQ/CCM: > {{jboss-cli.bat -c}} > {{/subsystem=jca/cached-connection-manager=cached-connection-manager:write-attribute(name=debug,value=true)}} > {{/subsystem=jca/cached-connection-manager=cached-connection-manager:write-attribute(name=error,value=true)}} > 4) Deploy the EAR. > 5) Access http://localhost:8080/leak-web/rest/test?message=Hi > The REST endpoint will send a message to the test topic (Defined in leak-ejb/src/main/java/test/mdb/TestTopic.java). TestTopicListener (in the same package as TestTopic) will receive the message and send a second message to the topic. Upon returning from TestTopicListener.onMessage(), the message is sent, but this shows up in the logs > (see attached log.txt) > I have no idea why JIRA attached each file twice. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8217) ActiveMQ leaks connections if a JMS message is sent from an MDB

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-8217?page=com.atlassian.jira.plugin.... ] Miroslav Novak commented on WFLY-8217: -------------------------------------- afaict this was fixed in scope of JBEAP-7503. I'll set this jira as resolved. > ActiveMQ leaks connections if a JMS message is sent from an MDB > --------------------------------------------------------------- > > Key: WFLY-8217 > URL: https://issues.jboss.org/browse/WFLY-8217 > Project: WildFly > Issue Type: Bug > Components: JMS, Transactions > Affects Versions: 10.1.0.Final > Environment: Running on Windows 10. Java(TM) SE Runtime Environment (build 1.8.0_92-b14) > Reporter: Scott Van Wart > Assignee: ehsavoie Hugonnet > Priority: Minor > Attachments: leak.zip, leak.zip, log.txt, log.txt, server.log > > > If an MDB causes a JMS message to be sent during the call to onMessage(), ActiveMQ won't close its connection. I'm using JMS2 through an @Inject'ed JMSContext. My sample project is an EAR with an EJB JAR (containing a service and an MDB) and a JAX-RS endpoint (entry point for the test). > 1) Build the EAR > 2) Run wildfly with the standalone-full.xml configuration: > {{standalone.bat --server-config=standalone-full.xml}} > 3) Enable debug and error reporting for leaked connections with ActiveMQ/CCM: > {{jboss-cli.bat -c}} > {{/subsystem=jca/cached-connection-manager=cached-connection-manager:write-attribute(name=debug,value=true)}} > {{/subsystem=jca/cached-connection-manager=cached-connection-manager:write-attribute(name=error,value=true)}} > 4) Deploy the EAR. > 5) Access http://localhost:8080/leak-web/rest/test?message=Hi > The REST endpoint will send a message to the test topic (Defined in leak-ejb/src/main/java/test/mdb/TestTopic.java). TestTopicListener (in the same package as TestTopic) will receive the message and send a second message to the topic. Upon returning from TestTopicListener.onMessage(), the message is sent, but this shows up in the logs > (see attached log.txt) > I have no idea why JIRA attached each file twice. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8579) Topic messages are sent to all shared non-durable subscription participants

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-8579?page=com.atlassian.jira.plugin.... ] Miroslav Novak commented on WFLY-8579: -------------------------------------- If MDBs are configured like: {code} @MessageDriven(name = "mdb1", activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Topic"), @ActivationConfigProperty(propertyName = "destination", propertyValue = "jms/topic/InTopic"), @ActivationConfigProperty(propertyName = "clientID", propertyValue = "testing-client-id"), @ActivationConfigProperty(propertyName = "subscriptionName", propertyValue = "testing-subscription-name"), @ActivationConfigProperty(propertyName = "shareSubscriptions", propertyValue = "true"), @ActivationConfigProperty(propertyName = "subscriptionDurability", propertyValue = "Durable")}) {code} and deployed to nodes in cluster then all are sharing the same subscription. So in case above if 200 messages are sent to InTopic then sum of all messages received by MDB across cluster is 200. I'll close this jira. > Topic messages are sent to all shared non-durable subscription participants > --------------------------------------------------------------------------- > > Key: WFLY-8579 > URL: https://issues.jboss.org/browse/WFLY-8579 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Scott Van Wart > Assignee: ehsavoie Hugonnet > Priority: Major > Attachments: duplicate-shared.zip > > > I have two MDBs with a subscription to a topic. The same clientId and a subscriptionName are specified in the activation config properties for each MDB. subscriptionDurability is omitted (defaulted to NonDurable). > When I send a single message to this topic, both MDBs receive the message. According to JSR 343, 8.3.2 Shared non-durable subscriptions: > bq. A non-durable shared subscription is used by a client that needs to be able to > share the work of receiving messages from a non-durable topic subscription > amongst multiple consumers. A non-durable shared subscription may > therefore have more than one consumer. *Each message from the subscription will be delivered to only one of the consumers on that > subscription.* > Setting the subscriptionDurability property to Durable works as expected (each message is delivered to only one consumer in that subscription). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8579) Topic messages are sent to all shared non-durable subscription participants

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-8579?page=com.atlassian.jira.plugin.... ] Miroslav Novak closed WFLY-8579. -------------------------------- Resolution: Explained > Topic messages are sent to all shared non-durable subscription participants > --------------------------------------------------------------------------- > > Key: WFLY-8579 > URL: https://issues.jboss.org/browse/WFLY-8579 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Scott Van Wart > Assignee: ehsavoie Hugonnet > Priority: Major > Attachments: duplicate-shared.zip > > > I have two MDBs with a subscription to a topic. The same clientId and a subscriptionName are specified in the activation config properties for each MDB. subscriptionDurability is omitted (defaulted to NonDurable). > When I send a single message to this topic, both MDBs receive the message. According to JSR 343, 8.3.2 Shared non-durable subscriptions: > bq. A non-durable shared subscription is used by a client that needs to be able to > share the work of receiving messages from a non-durable topic subscription > amongst multiple consumers. A non-durable shared subscription may > therefore have more than one consumer. *Each message from the subscription will be delivered to only one of the consumers on that > subscription.* > Setting the subscriptionDurability property to Durable works as expected (each message is delivered to only one consumer in that subscription). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2018