October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11145) multicastPrefix and anycastPrefix cannot be set

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-11145?page=com.atlassian.jira.plugin... ] Miroslav Novak updated WFLY-11145: ---------------------------------- Description: It's not possible to configure acceptor with {{multicastPrefix=jms.topic.}} and {{anycastPrefix=jms.queue."}}. Problem is that those 2 parameters must be set to {{extraProps}} variable in TransportConfiguration: https://github.com/apache/activemq-artemis/blob/a6b0b7e44291a76d6732c20b9... however in messaging integration we don't call TransportConfiguration constructor with extreProps map: https://github.com/wildfly/wildfly/blob/47b1db08fadb745706df7ba411db4f725... Ideally this CLI command should configure acceptor with anycast/multicast prefixes: {code} /subsystem=messaging-activemq/server=default/acceptor=acceptor:add(socket-binding=http,factory-class=org.apache.activemq.artemis.core.remoting.impl.netty.NettyAcceptorFactory,params={protocols="CORE",multicastPrefix="jms.topic",anycastPrefix="jms.queue"}) {code} was: It's not possible to configure acceptor with {{multicastPrefix=jms.topic.}} and {{anycastPrefix=jms.queue."}}. Problem is that those 2 parameters must be set to {{extraProps}} variable in TransportConfiguration: https://github.com/apache/activemq-artemis/blob/a6b0b7e44291a76d6732c20b9... however in messaging integration we don't call TransportConfiguration constructor with extreProps map: https://github.com/wildfly/wildfly/blob/47b1db08fadb745706df7ba411db4f725... > multicastPrefix and anycastPrefix cannot be set > ----------------------------------------------- > > Key: WFLY-11145 > URL: https://issues.jboss.org/browse/WFLY-11145 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 14.0.0.Final > Reporter: Miroslav Novak > Assignee: ehsavoie Hugonnet > Priority: Major > > It's not possible to configure acceptor with {{multicastPrefix=jms.topic.}} and {{anycastPrefix=jms.queue."}}. > Problem is that those 2 parameters must be set to {{extraProps}} variable in TransportConfiguration: > https://github.com/apache/activemq-artemis/blob/a6b0b7e44291a76d6732c20b9... > however in messaging integration we don't call TransportConfiguration constructor with extreProps map: > https://github.com/wildfly/wildfly/blob/47b1db08fadb745706df7ba411db4f725... > Ideally this CLI command should configure acceptor with anycast/multicast prefixes: > {code} > /subsystem=messaging-activemq/server=default/acceptor=acceptor:add(socket-binding=http,factory-class=org.apache.activemq.artemis.core.remoting.impl.netty.NettyAcceptorFactory,params={protocols="CORE",multicastPrefix="jms.topic",anycastPrefix="jms.queue"}) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11145) multicastPrefix and anycastPrefix cannot be set

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-11145?page=com.atlassian.jira.plugin... ] Miroslav Novak reassigned WFLY-11145: ------------------------------------- Assignee: ehsavoie Hugonnet (was: Jeff Mesnil) > multicastPrefix and anycastPrefix cannot be set > ----------------------------------------------- > > Key: WFLY-11145 > URL: https://issues.jboss.org/browse/WFLY-11145 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 14.0.0.Final > Reporter: Miroslav Novak > Assignee: ehsavoie Hugonnet > Priority: Major > > It's not possible to configure acceptor with {{multicastPrefix=jms.topic.}} and {{anycastPrefix=jms.queue."}}. > Problem is that those 2 parameters must be set to {{extraProps}} variable in TransportConfiguration: > https://github.com/apache/activemq-artemis/blob/a6b0b7e44291a76d6732c20b9... > however in messaging integration we don't call TransportConfiguration constructor with extreProps map: > https://github.com/wildfly/wildfly/blob/47b1db08fadb745706df7ba411db4f725... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11145) multicastPrefix and anycastPrefix cannot be set

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-11145?page=com.atlassian.jira.plugin... ] Miroslav Novak commented on WFLY-11145: --------------------------------------- [~ehugonnet] Could you take a look at it, please? thanks > multicastPrefix and anycastPrefix cannot be set > ----------------------------------------------- > > Key: WFLY-11145 > URL: https://issues.jboss.org/browse/WFLY-11145 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 14.0.0.Final > Reporter: Miroslav Novak > Assignee: ehsavoie Hugonnet > Priority: Major > > It's not possible to configure acceptor with {{multicastPrefix=jms.topic.}} and {{anycastPrefix=jms.queue."}}. > Problem is that those 2 parameters must be set to {{extraProps}} variable in TransportConfiguration: > https://github.com/apache/activemq-artemis/blob/a6b0b7e44291a76d6732c20b9... > however in messaging integration we don't call TransportConfiguration constructor with extreProps map: > https://github.com/wildfly/wildfly/blob/47b1db08fadb745706df7ba411db4f725... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11145) multicastPrefix and anycastPrefix cannot be set

by Miroslav Novak (Jira)

Miroslav Novak created WFLY-11145: ------------------------------------- Summary: multicastPrefix and anycastPrefix cannot be set Key: WFLY-11145 URL: https://issues.jboss.org/browse/WFLY-11145 Project: WildFly Issue Type: Bug Components: JMS Affects Versions: 14.0.0.Final Reporter: Miroslav Novak Assignee: Jeff Mesnil It's not possible to configure acceptor with {{multicastPrefix=jms.topic.}} and {{anycastPrefix=jms.queue."}}. Problem is that those 2 parameters must be set to {{extraProps}} variable in TransportConfiguration: https://github.com/apache/activemq-artemis/blob/a6b0b7e44291a76d6732c20b9... however in messaging integration we don't call TransportConfiguration constructor with extreProps map: https://github.com/wildfly/wildfly/blob/47b1db08fadb745706df7ba411db4f725... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11144) Remove javax.ejb.api module dependency on javax.rmi.api

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-11144: --------------------------------------- Summary: Remove javax.ejb.api module dependency on javax.rmi.api Key: WFLY-11144 URL: https://issues.jboss.org/browse/WFLY-11144 Project: WildFly Issue Type: Task Components: EJB Reporter: Brian Stansberry Assignee: Brian Stansberry The javax.ejb.api module depends on javax.rmi.api. But I can't see any reason why; the code in the spec jar does not import anything from any of the classes in the javax.rmi and org.jboss.javax.rmi packages that the javax.rmi.api module exports. This is important because javax.rmi.api brings in a huge dependency tree. That module is really just a wrapper around javax.orb.api, exporting a subset of its packages. And javax.orb.api is a misnomer -- it's not just API, it's the entire orb, with implementation dependencies that transitively bring in a large chunk of the entire appserver codebase. So if javax.ejb.api does not need javax.rmi.api we need to remove that link. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11128) wsconsume failure on wildfly14 + JDK 11

by R Searls (Jira)

[ https://issues.jboss.org/browse/WFLY-11128?page=com.atlassian.jira.plugin... ] R Searls commented on WFLY-11128: --------------------------------- This failure also occurs on unix for wfly 13 and 14. The script runs with wfly12 using both jdk 10 and 11. This is an issue with changes made in jboss-modules.jar since version 1.7.0.Final. wfly12 uses jboss-modules:1.7.0.Final wfly13 uses jboss-modules:1.8.5.Final wfly14 uses jboss-modules:1.8.6.Final > wsconsume failure on wildfly14 + JDK 11 > --------------------------------------- > > Key: WFLY-11128 > URL: https://issues.jboss.org/browse/WFLY-11128 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 14.0.0.Final > Environment: Windows 7 64bits > JDK 11 > Wildfly 14 > Reporter: mazen mahmoud > Assignee: R Searls > Priority: Major > Attachments: HelloWorldService-imported.xml, HelloWorldService.xml, demo-service-code.zip, log.txt, logs.zip > > > running wsconsume on a single jax-ws service with JDK 11 failes. (see attached log.txt file) > the service is very simple. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-375) Traffic Generator Needs To Be "Checked" For Running State

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-375?page=com.atlassian.jira.plugin.... ] Matt Mahoney reassigned SWSQE-375: ---------------------------------- Assignee: Sunil kondkar (was: Michael Foley) > Traffic Generator Needs To Be "Checked" For Running State > --------------------------------------------------------- > > Key: SWSQE-375 > URL: https://issues.jboss.org/browse/SWSQE-375 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Assignee: Sunil kondkar > Priority: Minor > > Currently the Traffic Generator pod may be not yet be fully Running, but the Jenkins job completes. > Thus need to add Traffic Generator Pod Running State checker. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-375) Traffic Generator Needs To Be "Checked" For Running State

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-375?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-375: ------------------------------- Sprint: Kiali Sprint #12 > Traffic Generator Needs To Be "Checked" For Running State > --------------------------------------------------------- > > Key: SWSQE-375 > URL: https://issues.jboss.org/browse/SWSQE-375 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Assignee: Sunil kondkar > Priority: Minor > > Currently the Traffic Generator pod may be not yet be fully Running, but the Jenkins job completes. > Thus need to add Traffic Generator Pod Running State checker. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-295) Move jaeger-openshift Jenkins job from CNCF CI to B24

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-295?page=com.atlassian.jira.plugin.... ] Matt Mahoney closed SWSQE-295. ------------------------------ Release Notes Text: Completed, by Jeeva. Resolution: Done > Move jaeger-openshift Jenkins job from CNCF CI to B24 > ----------------------------------------------------- > > Key: SWSQE-295 > URL: https://issues.jboss.org/browse/SWSQE-295 > Project: Kiali QE > Issue Type: Bug > Reporter: Kevin Earls > Assignee: Jeeva Kandasamy > Priority: Minor > > This is a placeholder to remind you to move the jaeger-openshift jenkins job off of the CNCF CI and instead run it locally. It is contingent on talks between [~mmahoney] and the Jaeger development team. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-452) New Jenkins Slave For Jaeger Jobs

by Matt Mahoney (Jira)

Matt Mahoney created SWSQE-452: ---------------------------------- Summary: New Jenkins Slave For Jaeger Jobs Key: SWSQE-452 URL: https://issues.jboss.org/browse/SWSQE-452 Project: Kiali QE Issue Type: QE Task Reporter: Matt Mahoney Assignee: Michael Foley -- 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 October 2018