August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10769) New mod_cluster nodes can become overloaded; should be ramping-up

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10769?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10769: ---------------------------------- Fix Version/s: 14.0.0.CR1 > New mod_cluster nodes can become overloaded; should be ramping-up > ----------------------------------------------------------------- > > Key: WFLY-10769 > URL: https://issues.jboss.org/browse/WFLY-10769 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Fix For: 14.0.0.CR1 > > > Add support for MODCLUSTER-449. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10634) mod_cluster custom load metric classes are loaded from the subsystem classloader

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10634?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10634: ---------------------------------- Fix Version/s: 14.0.0.CR1 > mod_cluster custom load metric classes are loaded from the subsystem classloader > -------------------------------------------------------------------------------- > > Key: WFLY-10634 > URL: https://issues.jboss.org/browse/WFLY-10634 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 14.0.0.CR1 > > > The mod_cluster custom load metrics classes are loaded from the subsystem classloader which requires users to tinker with our module structure. This is wrong since there is no way to specify which module to use. > We should just expose {{module}} attribute on the custom load metric (defaults to current default which is mod_cluster module, so no compatibility issues). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10489) Rename mod_cluster Tomcat/JBossWeb-era "connector" attribute to listener

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10489?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10489: ---------------------------------- Fix Version/s: 14.0.0.CR1 > Rename mod_cluster Tomcat/JBossWeb-era "connector" attribute to listener > ------------------------------------------------------------------------ > > Key: WFLY-10489 > URL: https://issues.jboss.org/browse/WFLY-10489 > Project: WildFly > Issue Type: Enhancement > Components: mod_cluster > Affects Versions: 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 14.0.0.CR1 > > > mod_cluster listener attribute name is still "connector" (from the Tomcat/JBoss Web days) which is confusing. > The goal is to rename this to listener. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-26) [Artemis 2.x Upgrade] MDB doesn't find its source queue when useJndi property is set to false

by Martyn Taylor (JIRA)

[ https://issues.jboss.org/browse/WFWIP-26?page=com.atlassian.jira.plugin.s... ] Martyn Taylor commented on WFWIP-26: ------------------------------------ [~jmesnil] Any thoughts on this. One of the early assumptions we had made was that all the calls would go via JNDI > [Artemis 2.x Upgrade] MDB doesn't find its source queue when useJndi property is set to false > --------------------------------------------------------------------------------------------- > > Key: WFWIP-26 > URL: https://issues.jboss.org/browse/WFWIP-26 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Martin Styk > Assignee: Martyn Taylor > Priority: Blocker > Labels: activemq, feature-branch-blocker > > Having a MDB configured as follows: > {code} > @MessageDriven(name = "mdb", > activationConfig = { > @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), > @ActivationConfigProperty(propertyName = "destination", propertyValue ="InQueue"), > @ActivationConfigProperty(propertyName = "useJNDI", propertyValue = "false"), > }) > {code} > MDB is not able to receive messages from InQueue. > Server logs: > {noformat} > 09:53:29,128 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151004: Instantiating javax.jms.Queue "jms/queue/InQueue" directly since UseJNDI=false. > 09:53:29,188 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "Mdb.jar" (runtime-name : "Mdb.jar") > 09:53:29,306 INFO [org.wildfly.naming] (default task-1) WildFly Naming version 1.0.7.Final > 09:53:29,364 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151000: awaiting topic/queue creation jms/queue/InQueue > 09:53:31,366 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151001: Attempting to reconnect org.apache.activemq.artemis.ra.inflow.ActiveMQActivationSpec(ra=org.wildfly.extension.messaging.activemq.ActiveMQResourceAdapter@2bd07716 destination=jms/queue/InQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15) > 09:53:31,368 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151004: Instantiating javax.jms.Queue "jms/queue/InQueue" directly since UseJNDI=false. > 09:53:33,480 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151004: Instantiating javax.jms.Queue "jms/queue/InQueue" directly since UseJNDI=false. > 09:53:35,092 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0236: Suspending server with no timeout. > {noformat} > In {{ActiveMQActivation.setup()}}, call to {{setupDestination()}} is made. Destiantion InQueue is instantiated there. However, during the {{ActiveMQMessageHandler.setup()}} call. consumer can not be created for this destination and exception {{AMQ119017: Queue InQueue does not exist}} is being thrown. > {code:title=ActiveMQActivation.setup()} > protected synchronized void setup() throws Exception { > logger.debug("Setting up " + spec); > setupCF(); > setupDestination(); > Exception firstException = null; > for (int i = 0; i < spec.getMaxSession(); i++) { > ClientSessionFactory cf = null; > ClientSession session = null; > try { > cf = factory.getServerLocator().createSessionFactory(); > session = setupSession(cf); > ActiveMQMessageHandler handler = new ActiveMQMessageHandler(factory, this, ra.getTM(), (ClientSessionInternal) session, cf, i); > handler.setup(); > handlers.add(handler); > } catch (Exception e) { > ... > } > } > ... > } > {code} > This is regression against Artemis 1.5. > Wildfly: https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (06c878a313d3cad323889d017e60fd5533204d1a) > Artemis: upstream master (577b62d5210cdcc0f86ab9bb1b24e944c877dfe7) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2823) FEEL Parser: `not` breaks with `list contains`

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2823?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2823: ----------------------------------- Labels: (was: Stunner) > FEEL Parser: `not` breaks with `list contains` > ----------------------------------------------- > > Key: DROOLS-2823 > URL: https://issues.jboss.org/browse/DROOLS-2823 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > > *list contains([1,2,3,4,5,6], 3)* returns true > *not(list contains([1,2,3,4,5,6], 3))* returns “list contains([1,2,3,4,5,6], 3)”, it should return false > Most likely related to an issue with the parse tree branches -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-91) [Artemis 2.x upgrade] artemis: artemis/hornetq: memory exhaustion via UDP and JGroups discovery

by Martyn Taylor (JIRA)

[ https://issues.jboss.org/browse/WFWIP-91?page=com.atlassian.jira.plugin.s... ] Martyn Taylor commented on WFWIP-91: ------------------------------------ It was removed during a refactor. Added back via: https://github.com/apache/activemq-artemis/pull/2227 > [Artemis 2.x upgrade] artemis: artemis/hornetq: memory exhaustion via UDP and JGroups discovery > ----------------------------------------------------------------------------------------------- > > Key: WFWIP-91 > URL: https://issues.jboss.org/browse/WFWIP-91 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Martyn Taylor > Priority: Blocker > > When 3rd party tool send multicast messages to Artemis which is configured with UDP Disovery and JGroups Discovery, Artemis creates a huge byte array at receiving the unexpected multicast message. So, it results in heap memory exhaustion, full GC and OutOfMemoryError in the worst case. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10455) Update JPA documentation, remove references to older ORM versions

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-10455?page=com.atlassian.jira.plugin... ] Scott Marlow updated WFLY-10455: -------------------------------- Summary: Update JPA documentation, remove references to older ORM versions (was: Update JPA documentation, remove references to older ORM versions and only reference 5.3.x) > Update JPA documentation, remove references to older ORM versions > ----------------------------------------------------------------- > > Key: WFLY-10455 > URL: https://issues.jboss.org/browse/WFLY-10455 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Minor > Fix For: 14.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-86) [Artemis 2.x upgrade] Duplicated messages in scenario with stop/start JMS bridge

by Justin Bertram (JIRA)

[ https://issues.jboss.org/browse/WFWIP-86?page=com.atlassian.jira.plugin.s... ] Justin Bertram commented on WFWIP-86: ------------------------------------- I'm going to change this from "Blocker" to "Major" since this is not a regression as far as I can tell. > [Artemis 2.x upgrade] Duplicated messages in scenario with stop/start JMS bridge > -------------------------------------------------------------------------------- > > Key: WFWIP-86 > URL: https://issues.jboss.org/browse/WFWIP-86 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Justin Bertram > Priority: Blocker > > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-86) [Artemis 2.x upgrade] Duplicated messages in scenario with stop/start JMS bridge

by Justin Bertram (JIRA)

[ https://issues.jboss.org/browse/WFWIP-86?page=com.atlassian.jira.plugin.s... ] Justin Bertram updated WFWIP-86: -------------------------------- Priority: Major (was: Blocker) > [Artemis 2.x upgrade] Duplicated messages in scenario with stop/start JMS bridge > -------------------------------------------------------------------------------- > > Key: WFWIP-86 > URL: https://issues.jboss.org/browse/WFWIP-86 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-376) Kiali-QE-REST Refactore For Istio 1.0

by Matt Mahoney (JIRA)

Matt Mahoney created SWSQE-376: ---------------------------------- Summary: Kiali-QE-REST Refactore For Istio 1.0 Key: SWSQE-376 URL: https://issues.jboss.org/browse/SWSQE-376 Project: Kiali QE Issue Type: QE Task Reporter: Matt Mahoney Assignee: Matt Mahoney Circuit Breaker and Virt Service test cases failing -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 August 2018