[JBoss JIRA] (WFLY-11060) Duplicated messages in scenario with stop/start JMS bridge
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-11060?page=com.atlassian.jira.plugin... ]
Jeff Mesnil updated WFLY-11060:
-------------------------------
Summary: Duplicated messages in scenario with stop/start JMS bridge (was: [Artemis 2.x upgrade] Duplicated messages in scenario with stop/start JMS bridge)
> Duplicated messages in scenario with stop/start JMS bridge
> ----------------------------------------------------------
>
> Key: WFLY-11060
> URL: https://issues.jboss.org/browse/WFLY-11060
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 14.0.0.Final
> Reporter: Miroslav Novak
> Assignee: Justin Bertram
>
> There are duplicated messages in scenario where JMS bridge is stopped and started.
> Test Scenario:
> * Start 2 servers and configure JMS from node-1 to node-3
> * Start sending messages to queue InQueue to node-1
> * Stop JMS bridge using management operation (CLI)
> * Wait for 5 sec
> * Start JMS bridge using management operation
> * Start receiving mesage from node-3 from OutQueue
> Expected results:
> There are no lost/duplicated mesages.
> Actual Result:
> Receiver got duplicated messages.
> Link to failed Jenkins run:
> https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (WFLY-11059) Clients do not failover to backup even it if backup started and keep retrying connection
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-11059?page=com.atlassian.jira.plugin... ]
Jeff Mesnil updated WFLY-11059:
-------------------------------
Affects Version/s: 14.0.0.Final
> Clients do not failover to backup even it if backup started and keep retrying connection
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-11059
> URL: https://issues.jboss.org/browse/WFLY-11059
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 14.0.0.Final
> Reporter: Miroslav Novak
> Assignee: Martyn Taylor
> Priority: Critical
> Attachments: NettyColocatedClusterFailoverTestCase.testFailbackClientAckQueueNIO.zip
>
>
> Test Scenario:
> * Start 2 servers in colocated topology with shared store
> * Start procuder and consumer sending/receiving messages to/from queue on 1st server(to live)
> * Kill 1st server and wait for backup on 2nd server to start
> * Clients failover to backup to 2nd server and wait for them to finish
> * Check that number of sent/received messages is the same
> Result:
> Sometimes happens that clients do not failover to backup to 2nd server and retry connection. I can see that backup on 2nd server started and created cluster with colocated live server but clients did not connect to it.
> Clients are retrying connection:
> {code}
> 07:32:16,676 Thread-36 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl:794] Trying reconnection attempt 163/-1
> 07:32:16,676 Thread-39 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:446] Connector NettyConnector [host=rhel7-large-42748, port=5445, httpEnabled=fa
> lse, httpUpgradeEnabled=false, useServlet=false, servletPath=/messaging/ActiveMQServlet, sslEnabled=false, useNio=true] using native epoll
> 07:32:16,676 Thread-36 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl:1080] Trying to connect with connectorFactory = org.apache.activemq.artemis.co
> re.remoting.impl.netty.NettyConnectorFactory@6568a014, connectorConfig=TransportConfiguration(name=null, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=5445&useNio=true
> &host=rhel7-large-42748&useNioGlobalWorkerPool=true&blockOnNonDurableSend=false&retryIntervalMultiplier=1-0&maxRetryInterval=2000&producerMaxRate=-1&blockOnDurableSend=true&connectionTTL=60000&compressLargeMessa
> ge=false&reconnectAttempts=-1&ignoreJTA=false&cacheLargeMessagesClient=false&scheduledThreadPoolMaxSize=5&useGlobalPools=true&callFailoverTimeout=60000&initialConnectAttempts=1&clientFailureCheckPeriod=30000&blo
> ckOnAcknowledge=true&consumerWindowSize=1048576&minLargeMessageSize=102400&finalizeChecks=false&autoGroup=false&threadPoolMaxSize=30&confirmationWindowSize=-1&transactionBatchSize=1048576&callTimeout=30000&preAc
> knowledge=false&enable1xPrefixes=true&cacheDestinations=false&connectionLoadBalancingPolicyClassName=org-apache-activemq-artemis-api-core-client-loadbalance-RoundRobinConnectionLoadBalancingPolicy&dupsOKBatchSiz
> e=1048576&incomingInterceptorList=&initialMessagePacketSize=1500&consumerMaxRate=-1&enableSharedClientID=true&HA=true&retryInterval=2000&factoryType=0&failoverOnInitialConnection=false&outgoingInterceptorList=&p
> roducerWindowSize=65536
> 07:32:16,676 Thread-39 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:600] AMQ211002: Started EPOLL Netty Connector version 4.1.16.Final to rhel7-larg
> e-42748:5445
> 07:32:16,676 Thread-36 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:446] Connector NettyConnector [host=rhel7-large-42748, port=5445, httpEnabled=fa
> lse, httpUpgradeEnabled=false, useServlet=false, servletPath=/messaging/ActiveMQServlet, sslEnabled=false, useNio=true] using native epoll
> 07:32:16,676 Thread-38 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl:794] Trying reconnection attempt 163/-1
> 07:32:16,676 Thread-38 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl:1080] Trying to connect with connectorFactory = org.apache.activemq.artemis.co
> re.remoting.impl.netty.NettyConnectorFactory@43d7f9fb, connectorConfig=TransportConfiguration(name=null, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=5445&useNio=true
> &host=rhel7-large-42748&useNioGlobalWorkerPool=true&blockOnNonDurableSend=false&retryIntervalMultiplier=1-0&maxRetryInterval=2000&producerMaxRate=-1&blockOnDurableSend=true&connectionTTL=60000&compressLargeMessa
> ge=false&reconnectAttempts=-1&ignoreJTA=false&cacheLargeMessagesClient=false&scheduledThreadPoolMaxSize=5&useGlobalPools=true&callFailoverTimeout=60000&initialConnectAttempts=1&clientFailureCheckPeriod=30000&blo
> ckOnAcknowledge=true&consumerWindowSize=1048576&minLargeMessageSize=102400&finalizeChecks=false&autoGroup=false&threadPoolMaxSize=30&confirmationWindowSize=-1&transactionBatchSize=1048576&callTimeout=30000&preAc
> knowledge=false&enable1xPrefixes=true&cacheDestinations=false&connectionLoadBalancingPolicyClassName=org-apache-activemq-artemis-api-core-client-loadbalance-RoundRobinConnectionLoadBalancingPolicy&dupsOKBatchSiz
> e=1048576&incomingInterceptorList=&initialMessagePacketSize=1500&consumerMaxRate=-1&enableSharedClientID=true&HA=true&retryInterval=2000&factoryType=0&failoverOnInitialConnection=false&outgoingInterceptorList=&p
> roducerWindowSize=65536
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (WFLY-11059) Clients do not failover to backup even it if backup started and keep retrying connection
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-11059?page=com.atlassian.jira.plugin... ]
Jeff Mesnil moved WFWIP-122 to WFLY-11059:
------------------------------------------
Project: WildFly (was: WildFly WIP)
Key: WFLY-11059 (was: WFWIP-122)
Component/s: JMS
(was: Artemis)
> Clients do not failover to backup even it if backup started and keep retrying connection
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-11059
> URL: https://issues.jboss.org/browse/WFLY-11059
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Miroslav Novak
> Assignee: Martyn Taylor
> Priority: Critical
> Attachments: NettyColocatedClusterFailoverTestCase.testFailbackClientAckQueueNIO.zip
>
>
> Test Scenario:
> * Start 2 servers in colocated topology with shared store
> * Start procuder and consumer sending/receiving messages to/from queue on 1st server(to live)
> * Kill 1st server and wait for backup on 2nd server to start
> * Clients failover to backup to 2nd server and wait for them to finish
> * Check that number of sent/received messages is the same
> Result:
> Sometimes happens that clients do not failover to backup to 2nd server and retry connection. I can see that backup on 2nd server started and created cluster with colocated live server but clients did not connect to it.
> Clients are retrying connection:
> {code}
> 07:32:16,676 Thread-36 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl:794] Trying reconnection attempt 163/-1
> 07:32:16,676 Thread-39 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:446] Connector NettyConnector [host=rhel7-large-42748, port=5445, httpEnabled=fa
> lse, httpUpgradeEnabled=false, useServlet=false, servletPath=/messaging/ActiveMQServlet, sslEnabled=false, useNio=true] using native epoll
> 07:32:16,676 Thread-36 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl:1080] Trying to connect with connectorFactory = org.apache.activemq.artemis.co
> re.remoting.impl.netty.NettyConnectorFactory@6568a014, connectorConfig=TransportConfiguration(name=null, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=5445&useNio=true
> &host=rhel7-large-42748&useNioGlobalWorkerPool=true&blockOnNonDurableSend=false&retryIntervalMultiplier=1-0&maxRetryInterval=2000&producerMaxRate=-1&blockOnDurableSend=true&connectionTTL=60000&compressLargeMessa
> ge=false&reconnectAttempts=-1&ignoreJTA=false&cacheLargeMessagesClient=false&scheduledThreadPoolMaxSize=5&useGlobalPools=true&callFailoverTimeout=60000&initialConnectAttempts=1&clientFailureCheckPeriod=30000&blo
> ckOnAcknowledge=true&consumerWindowSize=1048576&minLargeMessageSize=102400&finalizeChecks=false&autoGroup=false&threadPoolMaxSize=30&confirmationWindowSize=-1&transactionBatchSize=1048576&callTimeout=30000&preAc
> knowledge=false&enable1xPrefixes=true&cacheDestinations=false&connectionLoadBalancingPolicyClassName=org-apache-activemq-artemis-api-core-client-loadbalance-RoundRobinConnectionLoadBalancingPolicy&dupsOKBatchSiz
> e=1048576&incomingInterceptorList=&initialMessagePacketSize=1500&consumerMaxRate=-1&enableSharedClientID=true&HA=true&retryInterval=2000&factoryType=0&failoverOnInitialConnection=false&outgoingInterceptorList=&p
> roducerWindowSize=65536
> 07:32:16,676 Thread-39 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:600] AMQ211002: Started EPOLL Netty Connector version 4.1.16.Final to rhel7-larg
> e-42748:5445
> 07:32:16,676 Thread-36 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:446] Connector NettyConnector [host=rhel7-large-42748, port=5445, httpEnabled=fa
> lse, httpUpgradeEnabled=false, useServlet=false, servletPath=/messaging/ActiveMQServlet, sslEnabled=false, useNio=true] using native epoll
> 07:32:16,676 Thread-38 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl:794] Trying reconnection attempt 163/-1
> 07:32:16,676 Thread-38 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl:1080] Trying to connect with connectorFactory = org.apache.activemq.artemis.co
> re.remoting.impl.netty.NettyConnectorFactory@43d7f9fb, connectorConfig=TransportConfiguration(name=null, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=5445&useNio=true
> &host=rhel7-large-42748&useNioGlobalWorkerPool=true&blockOnNonDurableSend=false&retryIntervalMultiplier=1-0&maxRetryInterval=2000&producerMaxRate=-1&blockOnDurableSend=true&connectionTTL=60000&compressLargeMessa
> ge=false&reconnectAttempts=-1&ignoreJTA=false&cacheLargeMessagesClient=false&scheduledThreadPoolMaxSize=5&useGlobalPools=true&callFailoverTimeout=60000&initialConnectAttempts=1&clientFailureCheckPeriod=30000&blo
> ckOnAcknowledge=true&consumerWindowSize=1048576&minLargeMessageSize=102400&finalizeChecks=false&autoGroup=false&threadPoolMaxSize=30&confirmationWindowSize=-1&transactionBatchSize=1048576&callTimeout=30000&preAc
> knowledge=false&enable1xPrefixes=true&cacheDestinations=false&connectionLoadBalancingPolicyClassName=org-apache-activemq-artemis-api-core-client-loadbalance-RoundRobinConnectionLoadBalancingPolicy&dupsOKBatchSiz
> e=1048576&incomingInterceptorList=&initialMessagePacketSize=1500&consumerMaxRate=-1&enableSharedClientID=true&HA=true&retryInterval=2000&factoryType=0&failoverOnInitialConnection=false&outgoingInterceptorList=&p
> roducerWindowSize=65536
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (WFLY-10742) Wildfly 13 having wrong version of Maven dependency
by Peter K (JIRA)
[ https://issues.jboss.org/browse/WFLY-10742?page=com.atlassian.jira.plugin... ]
Peter K commented on WFLY-10742:
--------------------------------
BTW. how is it possible, that jars in the WEB-INF/lib are not loaded into the classpath?
> Wildfly 13 having wrong version of Maven dependency
> ---------------------------------------------------
>
> Key: WFLY-10742
> URL: https://issues.jboss.org/browse/WFLY-10742
> Project: WildFly
> Issue Type: Bug
> Environment: wildfly-13.0.0.Final on Ubuntu 16.04.5 LTS (GNU/Linux 4.4.0-119-generic x86_64) with Java 1.8.0_171
> Reporter: Peter K
> Assignee: Bartosz Baranowski
>
> I have following Maven dependency in my pom.xml:
> {code:xml}
> <dependency>
> <groupId>com.google.guava</groupId>
> <artifactId>guava</artifactId>
> <version>20.0</version>
> </dependency>
> {code}
> A) When running it on wildfly-13.0.0.Final on Ubuntu 16.04.5 LTS (GNU/Linux 4.4.0-119-generic x86_64) with Java 1.8.0_171, it is complaining about a missing method in the Guava library (which is a Guava version < 20.0):
> {noformat}
> 2018-07-23 10:43:21,718 ERROR [stderr] (Thread-182) Exception in thread "Thread-182" java.lang.NoSuchMethodError: com.google.common.collect.Sets$SetView.iterator()Lcom/google/common/collect/UnmodifiableIterator;
> 2018-07-23 10:43:21,718 ERROR [stderr] (Thread-182) at org.reflections.Reflections.expandSuperTypes(Reflections.java:380)
> 2018-07-23 10:43:21,719 ERROR [stderr] (Thread-182) at org.reflections.Reflections.<init>(Reflections.java:126)
> 2018-07-23 10:43:21,719 ERROR [stderr] (Thread-182) at org.nd4j.linalg.api.ops.factory.DefaultOpFactory.<init>(DefaultOpFactory.java:71)
> 2018-07-23 10:43:21,719 ERROR [stderr] (Thread-182) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 2018-07-23 10:43:21,719 ERROR [stderr] (Thread-182) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> 2018-07-23 10:43:21,719 ERROR [stderr] (Thread-182) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 2018-07-23 10:43:21,719 ERROR [stderr] (Thread-182) at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> 2018-07-23 10:43:21,719 ERROR [stderr] (Thread-182) at java.lang.Class.newInstance(Class.java:442)
> 2018-07-23 10:43:21,719 ERROR [stderr] (Thread-182) at org.nd4j.linalg.factory.Nd4j.initWithBackend(Nd4j.java:6192)
> 2018-07-23 10:43:21,720 ERROR [stderr] (Thread-182) at org.nd4j.linalg.factory.Nd4j.initContext(Nd4j.java:6087)
> 2018-07-23 10:43:21,720 ERROR [stderr] (Thread-182) at org.nd4j.linalg.factory.Nd4j.<clinit>(Nd4j.java:201)
> 2018-07-23 10:43:21,720 ERROR [stderr] (Thread-182) at java.lang.Thread.run(Thread.java:748)}}
> {noformat}
> B) It runs on Mac OS X 10.13.5 with Java 1.8.0_144 without errors.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months